mcaraballo
commented
2 years ago This issue can be closed. It was my user error. Perhaps the only fix for this is documentation informing users to connect their Crossfire receivers to UARTSson the flight controller that have DMA, otherwise you'll get RC control and telemetry but wonder why Yaapu cant get the telemetry stream. The full resolution I used is here: https://discuss.ardupilot.org/t/4-1beta7-crossfire-support/74883/28?u=chronic
The roll, pitch, and yaw graphical Yaapu widget gauge does not respond to any physical changes in the orientation of the flight controller. I can see the corresponding telemetry values refreshing properly on the model telemetry page as I move my flight controller around. Furthermore, there is a flashing NO GPS error and NO TELEM message in the upper right, even though I can see GPS coordinates appearing in the lower right section of the Yaapu widget.
I am using a Matek H743 running ArduPlane V4.1.0dev (acfdf6a3) and a crossfire diversity receiver with SERIAL_7_PROTOCOL=23, and RC_OPTIONS=256. On my Radiomaster TX16S transmitter, I tried running various versions of the Yaapu script starting with the older “horus_crsf_190b_0.7” up to the current "FrskyTelemetryScript-Horus-Widget-1.9.5-beta1". I ensured that CRSF is turned on in the Yaapu config. I'm not sure if CRSF is supported, that this is a bug or my user error. I have my CRSF receiver wired to Tx6/Rx6 (Serial 7) of the Matek H743. The receiver is configured with CRSF TX and CRSF RX on outputs 1 and 2 respectively. I also have another 2 outputs of the crossfire diversity receiver connected to SERIAL 2 with the Mavlink version 2 protocol running on those outputs. I do apologize if this is a user error and not a bug. Thanks for all this amazing work!
