@berayksl Hi there. being 1.4.3, you may want check the parameter in /etc/modalai/voxl-vision-hub.conf
that:
"en_vio": true,
Also, on some setups we noticed added latency that triggers the PX4's EV timeout and could explain the "invalid setpoint" log message. In PX4 please set EKF2_NOAID_TOUT
parameter in QGC to 8000000
.
Checking the above and before your next test flight, perform a hand test as follows:
- startup voxl portal & connect to the drone (web browser w/ip addr of the drone as the url--wifi must be running)
- goto the "vio" tab in portal
- pick up the drone and move it back and forth, then left and right. You should get something close to a "plus" trajectory in the portal screen (see attached). If it "flies away" then good chance calibration (imu, or camera, extrinsics) is off. If it stays frozen/unresponsive then there's a SDK configuration error.
- If you can repeat what is shown in the image, that confirms VIO is working properly and likely the above NOAID issue..

--
--
if you're still having issues on take off, then you can modify in /etc/modalai/voxl-open-vins-server.conf
and try the blind takeoff option by setting "en_vio_always_on": false
, but note VIO will not report any movements (vio position will report as if frozen) until you arm the drone.