Does anybody know why I don’t receive the flight mode sensor in my Radiomaster TX16s with a Crossfire Micro TX in the telemetry section?
I only receive 22 telemetry values, but not FM
According to the TBS manual the FM value should come from datasource FC so does Ardupilot 4.09 don’t send this value over Mavlink to the radio? However I do receive this value and a lot more in missionplanner.
You have the Yaapu script working using Mavlink and a Crossfire Micro TX in a TX16S?
When using CRSF protocol no telemetry data is send to the GCS using the XF Wifi, so basically that’s pretty useless.
If you made it work Than it’s a true miracle!, what did you do???
Wow two of the most annoying problems are fixed with the 1.41 firmware update on the WiFI module, UDP MavLink stays on and no need for a hotspot anymore, now only the possibility to receive telemetry data for the Yaapu widget over the crossfire MavLink without the need for an additional UART, very happy for now:grimacing:
After reading your comment about 1.41 I honestly dropped what I was doing, updated my MicroTXV2 and just tried it out. What a difference! I won’t be able to fly it for a few days but I’m very impressed.
I still have CRSF running to feed the Yaapu telemetry, and Mavlink on a separate UART, but if this turns out to be stable then I’ll be very pleased.
Happy to hear you also ahev success with the XS Wifi, but to be clear how did you connect this to the Nano RX? Are you using CRSF and Mavlink at the same time on different outputs? So CH. OUT1&2 for CRSF and CH. OUT3&4 Mavlink?
I didn’t knew that was even possible.
I do not think so.
To move forward in this issue I am still waiting for Ardupilot 4.1.0 at least in beta revision, for OpenTX 2.4.0 (here the CRSF Shot should be already implemented) and maybe also TBS will release a new enhanced revision for Crossfire.
I’m also still waiting for the 4.1.0 Ardupilot, not only for CRSF but also for MSP to finally support OSD in the DJI Goggles. Hopefully they release the beta soon, cheers.