FrSky telemetry (yaapu) working on F405, failing on BB Blue

@iter wrote:

I have 4 airframes with working FrSky/yaapu telemetry. All 4 use STM32 UCs. I’m building a new setup around a Beaglebone Blue. Most of the functionality is working, but I’m failing to bring up yaapu telemetry. I built from plane4.0 branch, tag Arduplane-stable).

I’m using a 232 cable from Amazon. The cable is good (tested on F405). I have it plugged into UART01. UART01 and its corresponding port assignment to SERIAL2 (-D /dev/ttyO1) work. If I connect a GPS to UART01 and set SERIAL2_PROTOCOL,5, I get GPS data. When I’m trying to get yaapu telemetry on this port, I set SERIAL2_PROTOCOL to 10.

This is the trace I get. The receiver seems to be polling every 12 milliseconds, but BBBL responds only to id 0x00:

bbbl-yaapu2940×200 17.4 KB

Here’s a zoom on the response:

bbbl-yaapu3911×191 20 KB

For reference, here’s the same trace from an F405 WING, where yaapu telementry is working correctly, and the uC responds to many of the messages:

bbbl-yaapu4931×233 29.9 KB

Posts: 1

Participants: 1

Read full topic