TX16 Yappu Telemetry Error "No Ap Message for Mavlink id (141)

ArduCopter
1

So I have a Aurelia X6 Pro V2 that is giving my a serious headache!

The company currently cant solve the issue though they are working on it.

The issues is incorrect flight modes are stated by the TX16 radio and during flight, the controller will state and show Armed/ Disarmed ( though the copter is flying).

The flight mode and Armed status are correct on Mission Planner. ( All connected Via RFD900 radio) and there is no evidence of this in the logs.

There is a DRS-15 Parachute attached to the drone. It seems to cause these issues. When it is not connected we have only seen the issue once.

The error we see from the TX16 starts as “No Ap Message for Mavlink id (141)”

This should be translated to Altitude from what I can see in the Mavlink Common.xml file.

I have even tried another T16 controller and it has the same errors.

Any ideas are greatly appreciated.

2

20241004_083546
20241004_0835461920×1920 345 KB

you can also see there is some jumbled data in the telemetry logs on the TX16. Its correct in Mission planner log and sd card log.

3

So RFDesigns has confirm that this is an issues related to the Parachute (DRS-15) and the fact that is creates an additional Mavlink datastream and causes the Yappu telemetry script to get confused.

Strange that no one else is using DRS Parachute and Yappu, but I suspect most users are using HereLink.

1 Like