You might have both qvio and openvins running? That could lead to issues. Only one should be running at a time have you looked through the troubleshooting guide? https://docs.modalai.com/flying-with-vio/#troubleshooting-vio Usually looking at the ovins-overlay in voxl-portal offers good insight The common issues are vibration is too high, the extrinsics are incorrect or there are not enough features to track in the environment

I am having the exact same issue, if by any chance you see this @lakbit can you let me know if you found a solution since this thread?

@tom thank you for your assistance. I'll do that.

Hi @taiwohazeez, That is the cable that powers the VOXL. I'm suggesting you leave that plugged in and disconnect everything else. I see you still have the VOXL 2 WiFi Add-on board connected. Disconnect that as well all the cameras on the bottom of the VOXL, ESC, and GPS. Please have the VOXL powered off while you disconnect everything. Let me know how it goes, Ted

@tom @teddy-zaremba can you assist please? This is pretty urgent, I need to get this fixed. Also, the landing gears got broken, and I can't seem to be able to order new parts from the official website, is there a way I can go about it? Looking forward to your response. Thanks

@Hector-Gutierrez thanks for the suggestion. However, I have now seen this unstable behavior in all modes (manual, altitude, position and offboard), both indoor and outdoors. I suspect that qvio is failing and trying to reset mid flight (Error: Not stationary was observed multiple times on the qvio_overlay page on VOXL portal). I don't think the GPS is even being used (QGC reports 100 HDOP and 0 satellites). The only mode where the UAV is controllable is Manual, but the qvio error is still present. @Alex-Kushleyev would you be able to share some insight into what could be happening? How can we resolve this issue? Thanks, George

@tonygurney , I am assuming that you are using the ESC hardware version M0134 (you can confirm using voxl-esc scan tool. Here is the datasheet for M0134. https://docs.modalai.com/modal-esc-datasheet/ This ESC has an option (via installing a 0 ohm resistor) to provide 3.3V to pin 1 of J3. This is the same voltage that is used for the MCUs that run on the ESC and should be used with caution (if this voltage rail is brought down by overloading, the ESC will shut down). Please see image below that shows where 0 ohm resistor should be (carefully) installed to enable 3.3V on pin1 of J3 (marked in red) [image: 1753107113526-m0134-diagram.jpg] If you actually wanted 5V (VAUX), that is available on the other side of the board via two test points at the edge of the board. This voltage rail is provided by a separate switching regulator. See the following section : https://docs.modalai.com/modal-esc-datasheet/#neopixel-led-support If you REALLY need 5V to be present on pin1 of J3, then you can add a small wire jumper from the VAUX test point directly to the pin1 of J3 (which is marked with a white dot). This pin 1 of J3 is normally disconnected. Please only do this if you are comfortable performing this type of soldering and we cannot guarantee the results :). Alex

@Alex-Kushleyev - thanks, I submitted the RMA request, will let you know after I have the chance to replace and test the replacement parts. Thanks, Hector

@mrawding good afternoon, i see that your topic is quite old, but I am struggling with px4 firmware build and was wondering if you ever managed to successfully build your px4 firmware ? If you have done it recently, I would appreciate a helping hand in this topic: https://forum.modalai.com/topic/4539/voxl2-hitl-sim-with-gazebo-in-docker-vtol-frame-support/13?_=1751379111988

@Ligma We designed the VRX to be compatible with any off the shelf HDMI input display. We have used HDZERO goggles with the VRX so you should have no issues there

@Eric-Katzfey - Brilliant idea- thank you.