MVX Link Diagnostics
Check link health with voxl-inspect-vtx and voxl-inspect-vrx, fix common problems, and collect logs for support.
Table of contents
Inspect the link
voxl-inspect-vtx on the drone and voxl-inspect-vrx on the VRX print a live line of link statistics per video frame. Run them over ADB or SSH:
voxl-inspect-vtx # on the drone
voxl-inspect-vrx # on the VRX
Add -n to print each sample on a new line instead of updating one line, which is easier to copy into a support request.
Most useful columns on the VRX
| Column | Meaning |
|---|---|
total(ms) | Latency from the end of the camera exposure to the VRX drawing the frame. The display’s own scan-out is not included. |
vtx(ms), vrx(ms) | The part of that latency spent on the drone and on the VRX. |
decode(ms), render(ms) | Time to decode and to display the frame on the VRX. |
fps, rx fps | Displayed and received frame rates. |
rssi, snr, noise_floor | Signal strength, signal-to-noise ratio and noise at the VRX. Higher SNR is better. |
packet_loss | Share of video packets lost on the link. |
drops | Frames the VRX dropped. |
dmg flag/taint/hid | Frames the decoder flagged as damaged, frames affected by lost data, and damaged frames hidden by the Freeze video loss mode. |
vbat(VDC) | The VRX supply voltage. |
Most useful columns on the drone
| Column | Meaning |
|---|---|
cam(ms) | Camera latency, from the camera exposure to the encoded frame reaching the VTX. |
vtx(ms) | From the camera exposure until the frame has been sent, including cam(ms). |
out (mbps) | Video bitrate being sent. |
temp(C) | Radio temperature. |
pwr(dBm) | Transmit power. |
mcs | Current radio data rate setting. |
The other columns are for ModalAI support.
Common problems
| Symptom | What to check |
|---|---|
| No video, OSD shows INVALID ENCRYPTION KEY | The drone and VRX hold different keys. Install the same vtx.key on both. See Pairing & Encryption Keys. |
| No video, channel readout on the VRX is amber | The drone is frequency hopping and the VRX cannot follow it, usually because the keys differ. See Frequency Hopping. |
| No video at all | Check that both units are on the same channel and bandwidth: step through channels with buttons 1 and 4, or double-tap to scan. Check that both units run the same SDK release. |
| Picture breaks up at range | Use a narrower channel or the Adaptive profile, pick a clearer channel with the RF occupancy scanner, or turn on frequency hopping. See Channels, Bandwidth & Power. |
| Damaged frames bother the pilot | Switch Video Loss to Freeze. See OSD Menu & Display. |
| Recording does not start | Check the REC message on the OSD and the USB flash drive requirements. |
| Changes from the drone menu do nothing | Disarm the drone, then try again. On a second VRX, check that it is not an OBSERVER; see Multiple Ground Stations. |
| Frequency hopping does not start | See If hopping does not start. |
Collect logs for support
When you contact ModalAI about a link problem, include:
- The SDK version on the drone and the VRX. The VRX SETTINGS menu footer shows both.
Flight logs from both units for a flight that shows the problem. Turn logging on with VRX SETTINGS > RECORDING > Log before the flight (see Flight logs), then copy the logs off:
adb pull /data/mvx/vtx/logs/ # from the drone adb pull /data/mvx/vrx/logs/ # from the VRX- A few seconds of
voxl-inspect-vrx -nandvoxl-inspect-vtx -noutput while the problem is happening. The service logs from each unit:
journalctl -u voxl-vtx --no-pager > vtx.log # on the drone journalctl -u voxl-vrx --no-pager > vrx.log # on the VRX
Ask on the ModalAI forum or contact ModalAI support.