MAVLink over Crossfire WiFi (TBS Lucid H7 Wing) reports “Stat runtime” error

ArduPlane
1

My partner and I are working on a Skyhunter build for a university mapping project, and we’re running into connectivity issues between ArduPilot and the TBS Crossfire WiFi module. We’re also seeing a “Stat runtime” error in Mission Planner when trying to connect over WIFI, so I want to include all of that here for clarity.

Hardware Setup

  • Flight Controller: TBS Lucid H7 Wing

  • Receiver: TBS Crossfire Nano Diversity

  • Radio: Crossfire TX Lite on Radiomaster Boxer

  • Aircraft: Skyhunter

  • Goal: ArduPilot → Crossfire WiFi → Mission Planner/QGC for telemetry & mission monitoring

Wiring

Crossfire Nano Diversity:

  • CH1 = CRSF TX

  • CH2 = CRSF RX

  • CH3 = MAVLink TX

  • CH4 = MAVLink RX

Flight Controller:

  • CRSF connected to UART6

  • MAVLink tested on UART4 and UART7

Neither UART produced a working WiFi → MAVLink → ground station connection.

What Works

  • We can connect normally over USB.

  • LUA script telemetry to the radio works fine (CRSF telemetry confirmed).

  • Crossfire WiFi module connects to laptop.

  • We can select the UDP link in Mission Planner or QGroundControl.

What Does NOT Work

1. Mission Planner USB connection

Sometimes Mission Planner gives:

“Stat: runtime” or freezes while loading parameters.

Other times it connects briefly and drops.
(Unsure if this is related to unsupported hardware or a boot issue.)

2. WiFi Telemetry

  • No MAVLink heartbeat over WiFi

  • “VCP unable to open” or unstable connection

  • Sometimes it connects, but immediately closes because no heartbeat is detected

  • Parameters never load

  • UDP link never becomes stable

Goal: We need reliable MAVLink telemetry over WiFi so we can monitor missions during survey flights.

2

This only worked for me up to Crossfire ver. 6.07 (very slowly, but it worked). Which version are you using? Currently I have ver. 6.36 and after 15 minutes it is still only trying to load params. I used the WiFi and MP app on my mobile.

3

I gave up on MavLink over Crossfire. I got it to “work” a couple of times, but never really functional enough to actually use it. I had much better luck with MavLink over ELRS, and MLRS.

1 Like
4

Yea, I concluded that “very slowly”=not practical

5

I am in the group working on this UAS, thank yall for the comments. We have decided for now to omit computer telemetry to finish the plane for this project. Then we will get a more traditional telemetry module after the project is over. Before we did that, I wanted to confirm that CTS and RTS are not required for Ardupilot? Our flight controller has plenty of UARTs and RX and TX pins, but none for RTS and CTS. I have read that they can be omitted with no issue.

6

CTS and RTS increase the performance and reliability of a serial connection. They do exist for exactly that reason.

But yes, with degradation of performance and reliability you can omit them.

7

Thank you for the quick response, do you know if there is a parameter that can make rx and tx accept the RTS and CTS data? We have plenty of open rx and tx pins that we could use if that is possible.