@mario Hi Mario, both Yolov8 and Pytorch are on our roadmap to support. We do not have a good timeline yet though.

@Alex-Kushleyev @Vinny Thank you for your response. I'll test it.

@Namho Hello. Have you found a solution to this issue?

Hi @voxltester
Are you able to post a high res photo of the USB breakout board, both top and bottom?
Could save you the time and hassle of an RMA with a good high quality photo I can inspect.

The board was tested and passed before shipping, but these boards do have some small parts on that that are susceptible to damage if the board is dropped or if a tool or other item hits into it.

Thanks!

@Eric-Katzfey The EKF2_EV_CTRL param is set to 15 bits (all enabled). We don't have any cameras on the drone at the moment, though. Could that be introducing issues in the EKF2 and causing it to reset? I'll try disabling all vision stuff and see if it works different.

@Alex-Kushleyev I had a similar issue and this helped a lot. thanks.

@tom it looks like the groups are the same between machines (and yours except I'm not in docker), and the versions of adb, fastboot, and all android packages are the same. I was looking online and some people say it may be related to or solved by udev (https://askubuntu.com/questions/705537/no-permissions-fastboot-fastboot-and-adb-not-working) but I'm not sure I have more more time to troubleshoot this, and I didn't touch anything with udev on the working machine. Hopefully I'll be able to circle back to this eventually, but thank's for your help with everything!

@Alex-Kushleyev Thanks for your insightful reply!!

@groupo This code https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/master/src/mavlink_io.c?ref_type=heads#L156 sets up a pipe client to listen for Mavlink messages in the voxl-vision-hub application

@jonathankampia Yes, both qmc5883l and ist8310 are supported now.

@Stefan-Amundarain ,

It is always good to double check the firmware version of our ESCs and IO board (whichever you are using) so that you have control over the version that you are using and do not upgrade unless that is your intention or use outdated firmware. Typically when we release the new SDK we recommend updating ESC and IO board firmware because some features will require the update.

However, if you just receive a new board, you probably want to upgrade it to the firmware version that you have already been using or version required by the sdk.

Our voxl-esc tools (used for firmware update, checking) are used for IO board and ESC and make it easy to check and update firmware in an automated way to ensure you are running the firmware that you intended.

If you need more help with this, please let me know.

Alex

Nvm, solved, for some reason the voxl-vision-hub disappeared from the list, reinstall helped.

Now I wonder why the ... it disappeared, but at least I'm unblocked.

Thank you for your help and hints Alex. We will definitely try to use voxl-streamer and modify it for VP8.

Thank again,
Milan

@gitcoder You really shouldn't use ROS for this, especially when network bandwidth is limited. ROS and ROS 2 add significant network bandwidth both local to the device and over the network.

If you really need it over ROS 2, you should use a compressimage sensor message. Here's some code we found through a search https://answers.ros.org/question/385599/how-to-publish-a-compressedimage-in-ros2-foxy/

@ijones2 This is great news! It looks like everything is functioning as expected so no need to go through the unbricking process at this point.

It does appear that there is a fairly old SDK loaded on there so I would recommend flashing the latest SDK (1.3.3) from downloads.modalai.com under "VOXL 2 Platform Releases"

Just follow the instructions here to do so: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

@Alex-Kushleyev sounds good

@guyzoler Don't set a default gateway on the interface with a static IP.

@tom thank you for clarifying that.