VIO on Sentinel is disabled by default. The service file for VIO can be started by configuring the qvio server:
It will show the following prompt:
Would you like to enable the qvio service? This will start qvio as a background process Selecting yes will start the service, no will disable the service 1) yes 2) no
1 (yes) to enable the service. This will immediately start VIO and enable it on boot.
In order to check if VIO is running you can check with the following command:
systemctl status voxl-qvio-server
This will show you the status of the voxl-qvio-server.
If the status displays
active(runnning) then VIO is running and the VIO data is being sent to PX4.
If the status displays
failed then VIO failed to run. Make sure that camera index 2(downward facing tracking camera) and PX4 are running.
To restart VIO, you can simply restart the service file:
systemctl restart voxl-qvio-server
VIO should be restarted and the drone should be idle before any flight where VIO will be used.
VIO data can be viewed by manually running the voxl-camera-client command:
NOTE A library path was set for this command, if you’re command doesn’t execute, inside your adb shell run
This will print out position data in the following format:
T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)| state| error_code -0.11 -0.12 -0.06| -14.6 -30.1 -2.6| OKAY |
T_imu_wrt_vio represents your drones XYZ position in meters from your starting position. To validate this data, you can move the drone forwards and observe as the X value increases.
Once voxl-qvio-server is running, confirm quality data before flight by opening the mavlink inspector and checking that X&Y values are non-zero in the ODOMETRY mavlink telemetry packets.
Alternatively, if your computer running QGroundControl has its volume turned up you should hear it announce the swap from “manual” to “position” mode when you flip the flight mode switch from up to middle. If VIO data is not being transmitted, the system will fall back to altitude mode and you will hear “position mode rejected, altitude flight mode”. In this case, go back to manual flight mode (switch up) and wait a few more seconds for voxl-qvio-server to finish initializating.
If this doesn’t work, go back to “Viewing VIO Data” and reconfirm VIO is working with voxl-qvio-client. You can also check the voxl-qvio-server systemd service for indications of what might have gone wrong. We have a VIO parameters file helper located here to help easily configure into VIO or GPS mode. Specifically the EKF2_AID_MASK is often overlooked as an important parameter for VIO flight.
Some relevant PX4 parameters for VIO flight
# enable vision for height, position, and velocity, no GPS or barometer 1 1 EKF2_AID_MASK 280 6 1 1 EKF2_HGT_MODE 3 6 ## set MD to 0 to allow covarience from VIO to be used 1 1 EKF2_EV_NOISE_MD 0 6 ## Turn off EV Delay, VOXL will do proper timesyncing 1 1 EKF2_EV_DELAY 5.00 9 ## increase bias limit to prevent preflight check failure 1 1 COM_ARM_EKF_AB 0.01 9 ## Allow arming without GPS indoors 1 1 COM_ARM_WO_GPS 1 9
While looking at the ODOMETRY data in QGroundControl’s Mavlink Inspector, observe the xyz data as you move the quadcopter around. Make sure it aligns with NED coordinate frame. If there is a coordinate system mismatch PX4 will initially take off then very quickly run away out of control.
It is safer to take off in Position Flight Mode than it is to flip to this mode mid-flight from Manual Flight Mode.
Take off and land with the same instructions as listed above but this time with the Flight Mode switch in the middle position. The quadcopter should take off straight up and be much easier to control than in manual mode.
Be ready to flip back to manual mode should anything go wrong. It is safer to flip to manual mode and land than to kill the motors mid-flight. Killing the motors mid-flight may result in the propellers loosening from the reverse-torque and flying straight up off the quadcopter. Only kill the motors after landing and spooling down the motors OR in a serious emergency.