@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

@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

@Eric-Katzfey - Brilliant idea- thank you.

@Hector-Gutierrez Point a small fan at the VOXL 2 while you have it on your desktop. You need to have air flow. When it is on a drone and flying you get a lot of airflow from the propellers but on the desktop you should have a small fan.

@tom - that solved the problem . The solution was to download and build using voxl-cross:V2.7 Thanks for the very prompt response ! regards, Hector

@Moderator When you mentioned different WiFi adapters, do you mean that the Starling 2 is able to support newer WiFi adapters that are WiFi 6E capable too? Or only those that are listed here?

So this wouldn't be a scenario where the GPS is failing entirely, potentially making it in violation of FAA Remote ID, but would just be a weaker signal?

@wrossi17 , Starling 2 Max uses two 2S batteries connected in series, using the two xt30 connectors. If one of the batteries is not plugged in, the circuit is incomplete and the drone will not be powered. If you want to use a power supply to power the Starling 2 Max, with the drone we ship a special plug that plugs into one of the xt30 connectors, shorting it, so that the other xt30 can be powered with a single source. Please check the packaging of the drone for the plug (it may be in a small envelope) or you can make your own plug. Please let me know if you need more details about that. If you use a power supply, use a 3-4S (12-16V) to power Starling 2 Max for bench testing and it is not advised to try to arm while connected to a power supply. Alex

@wifa799 @Viktor-Gal You can use any CRSF (ELRS) receiver with the VOXL 2 and it will work. While we don't support flashing upstream builds of ELRS from the VOXL, if you update it yourself it will work without requiring any additional modification or patches. The patches from ModalAI just include some extra utilities for managing the receiver with the voxl-elrs tool such as the "unbind" command and pwm configuration from the VOXL. I'll see if I can provide a build for the betafpv receiver which matches the 3.5.3 version provided for our in-house M0184 receivers, but in the meantime you can definitely use firmware from the upstream ELRS repo.

@Viktor-Gal We don't get too many test cycles on OSX so ideally you flash on a linux machine if possible.

Just wanted to share: Using this approach, I was able to integrate CubePilot Here4

@Alex-Kushleyev I will look into replacing the motors, is there anything I can do to prevent motor failures like this? my platform has been having a lot of QVIO failures

@Randy-Mackay Do you know which version of the VOXL SDK is being used? We have recently transitioned over from voxl-qvio-server to voxl-openvins-server for VIO. OpenVINS is open source, so we have been investing our time there. Qvio is closed source and we can't really update the internals.