@tpavlic heyyy... i do agree that using roskinetic and xenial is kind of a dumb thing... could you help me with something ? are you using the m500 drone with voxl 1 here to do the "docker pull ros:noetic-robot" command? if you are i do get an error saying Error: Status 410 trying to pull repository library/ros: "<html>\r\n<head><title>410 Gone</title></head>\r\n<body>\r\n<center><h1>410 Gone</h1></center>\r\n<hr><center>openresty</center>\r\n</body>\r\n</html>\r\n" i really kind of want to use the higher versions of python and a more recent ubuntu distribution. any tips or suggestions ?

@Eric-Katzfey Thank you for such a quick response! Saved me a few hours down the wrong rabbit hole.

@jmltt You do not need RC for offboard mode. However, you will have to look and see how your failsafes are set for lost RC to see what it will do. But definitely make sure that you are doing things in a safe manner!

@czarsimon You may want to open your own thread, RB5 handles IMUs differently than VOXL 2 so the solution will likely be different

@Eric-Katzfey Dear Moderator, I am a Drones Engnineer fimiliar with Python, C,C++, PX4 and QGC, Kindly tell me which hardware modems and radios are required in order to develop the SWARM Drones formation and Mesh Networking, I am new to Starling Platforms and Need help

@Zarrar By "doing it on your own" we mean that we have not done the work to enable any of these features. You would need to do that. And since we have not done that work we cannot answer your specific questions on how to do it. But that is the beauty of the Starling drone. It is an open platform for doing exactly this kind of development work. We would love to hear how you are able to use the Starling for SWARM Formation!

@labkit it is part of the SDK but not installed on the kernel - on you voxl2 please run the following: sudo apt-get install voxl-ros2-foxy sudo apt-get install voxl-microdds-agent sudo apt-get install voxl-mpa-to-ros2 voxl-configure-mpa-to-ros2 Once this is done you should be ready to use ros2 by running source /opt/ros/foxy/setup.bash as well as export ROS_HOME=/opt/ros/foxy Hope this helps. Also ensure that for the voxl-configure-mpa-to-ros2 line you have an active internet connection on the voxl2 as this requires some pip installs. Thanks! Zach

@Stefan-Amundarain what do the flight logs tell you?

When we start voxl-tag-detector service with "en_tag_fixed_frame": true any change to offboard mode makes the drone loose the position, heavily drifting sideways. Isn't the px4 control referenced only to local frame? If so tag relocalization shouldn't affect the hold position. Is there any other configuration we are missing?

@Ariel-Saez I already fix the problem, any case someone have the same problem, you need to update the SDK with the proper SKU version, in my case the /data/modalai/sku.txt show me "MRB-D0003-1-V1-C7", and looking my modalai's bill, show I buy the MRB-D0003-2-V2-C7. Next I change my sku.txt with the right code: MRB-D0003-2-V2-C7, then I update my voxl and fix everything. update SDK documentation: https://docs.modalai.com/flash-system-image/ SKU config and documentation: https://docs.modalai.com/voxl-configure-mpa/

@Moderator Hello, thanks for your help. However I am still confused about what to do with this information. Is there a special version of the SDK I need to install for our version (M0054-2)? It says it requires SDK version 1.1.3+ and we are trying to install 1.2.0 which should be ok, correct?

Following up here. We upgraded to a voxl2 and stopped since this error. we think it might have been an issue with voxl flight on the newest SDK for auto exposure

@Amin-Bassiri The RB5 drone uses the PX4 autopilot software https://px4.io/

@Eric-Katzfey that did it, thanks!

@kgn-mdlai Is HITL interesting for your purposes? https://docs.modalai.com/voxl2-PX4-hitl/

Thanks for the wonderful support from team modal AI. Here is the solution which they have shared with me, which is tested and working 100%. Please download the attached file file: Download this Move into the ufs sub directory of that release ^: cd 2024-02-09-1.7.4-M0054-2/ufs Slide the SW2 switch to ON to be in QDL mode Plug in power and USB Run: sudo qdl --debug --storage ufs --include . prog_firehose_ddr.elf rawprogram_unsparse0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml