@Chad-Sweet Thank you

@tom we can try that in a little bit and get back to you

@aashry Thank you for your quick reply. It is working now!

@yx We do all of our testing on linux machines so there shouldn't be an issue. What error are you seeing?

@tom @Chad-Sweet

Hello @Eli-Pollack! Have you been able to figure it out? I'm running into the same problem now and I found your question.

@aashry Unfortunately we don't do too much ROS work around here so I'm not sure if someone else will respond with a better answer, but... I would highly recommend pointing a fan at your VOXL while doing development on your bench and see if that affects performance. As you mentioned, VOXL2 is much more powerful and will likely perform much better in all ways (also much more developer friendly since it's runs Ubuntu 18 as opposed to VOXL's yocto build), but it makes sense that you want to get things working on your current hardware

@rjpking92 [image: 1688743456765-97fda936-3457-4092-955d-6b8d7d58f0ee-image.png] )

@Benjamin-Ruks This shows that GPS has been selected as NONE so it won't try to set up the LED, magnetometer, or GPS. That will have to be changed to HOLYBRO. You can directly modify the file /etc/modalai/voxl-px4.conf to change that value.

@Chad-Sweet Hi Chad, I think I am into a trouble similar to Wenxi LiU. It appears to me that qvio server is enable and running but, when trying to check odometry in QGC or even with voxl-inspect-qvio, all the T_imu_wrt_vio(m) data is in 0 even when moving the drone. In QGC it appears the XY coordinates are in absolute 0 and Z with an offset os 10 meter, it appears to be a -10.9 coordinate while it hasn't moved at all. I tried to open the link you attached to the answer but the page is down. Is it another page or someone that could help me to troubleshoot this problem? Regards,

Please refer to the troubleshooting documentation https://docs.modalai.com/flying-with-vio/#troubleshooting-vio