Topics created by Judoor 0

@Judoor-0 I'm not sure what those mavros commands are trying to do. But you can change the rate at which mavlink messages are streamed out of PX4. Take a look at the PX4 startup file /usr/bin/voxl-px4-start and look for the lines like: mavlink stream -u 14556 -s HIGHRES_IMU -r 10. Adding lines like that or modifying the existing ones can change the rates.

@Judoor-0 Thanks for the contribution, this is very helpful!

@Alex-Kushleyev thank you alex i'll try that

@Judoor-0 I would recommend re-flashing the latest SDK from downloads.modalai.com

Yes, /home/root gets wiped by default. When flashing a new SDK, /data is retained unless otherwise specified with a flag

@Judoor-0 , if you can reliably reproduce this, please look at output of top, which will show all the processes and amount of memory they are using, you can also sort them by memory usage, please check usage of the top tool. Hopefully this will allow you to pinpoint which process uses a lot of memory and more importantly increasing amount of memory.

You can check the memory usage per process and see if there is any process that uses more memory over time. Try to do that without flying first, but running the whole processing stack if possible.

Alex

@Jeremy-Schmidt Hi,
It's resolved now, in the mean time I had a response from the support.
Have a good day
Julien

Hi @Judoor-0
We have had one other report of something similar where the ToF connector flex comes loose from it's connector located on the M0173 board from high vibe or several hard landings.

If you can see whether or not the connector from the M0177 ToF flex looks like it is not planar on the mating M0173 board, try to use something rather benign electrically (like plastic tweezers) and see if you can reseat the connector into the M0173 board.
We have a good description of these connections shown here: https://docs.modalai.com/voxl2-coax-camera-bundles/

We are going to add in some additional mechanical support here to make sure this issue does not happen long term, despite high vibe/shock scenarios.

If this does not seem to be your problem, please let us know and I'll have to tag someone from the SW team to help you debug further.
Thanks!

@Alex-Kushleyev,

Cool, Thanks a lot!

@Judoor-0 Yep exactly, if the drone is already in fastboot before running the flashing script it can't identify which board it is (M0054-1, M0054-2, M0104-1) so it has to give you all options. This time since it has ADB access it can be smarter and just ask you the possible options it knows are supported for your hardware

@Zachary-Lowell-0 well it work now!
I found these lines on another thread of the forum:

sudo apt-get install voxl-ros2-foxy sudo apt-get install voxl-mpa-to-ros2 voxl-configure-mpa-to-ros2 source /opt/ros/foxy/mpa_to_ros2/install/setup.bash export ROS_HOME=/opt/foxy ros2 run voxl_mpa_to_ros2 voxl_mpa_to_ros2_node

And everything worked first time ! So please put these line directly on the documentation cause I lost so much time with this install !

@Judoor-0 , I am sorry, but i cannot help you with the mavsdk issue due to lack of knowledge of the subject. Please follow up in the appropriate thread and someone else should help you out!

Alex

@Vinny no problem for now I didn't try to charge it while being used it was just a question.
Julien

@Jetson-Nano , OK it seems we have two parallel threads going. please see my reply to the other thread https://forum.modalai.com/topic/3688/vision-sensors-not-detected-in-voxl2 and test it step by step as I suggested (reducing fps of imx214 camera first, then disabling sensors one by one)

Alex