I set SERVO_BLH_DEBUG = 1 to enable MAVlink reporting of BlHeli error messages to track down "bad CRC" errors I'm seeing. On the Messages tab in Mission Planner, and also with the Yaapu telemetry script these "bad CRC" messages are reported correctly. However in the messages field of the ArduCopter OSD there are two spurious characters appended to the message. See attached screenshot.
Version
3.7.0-dev
Platform
[ ] All
[ ] AntennaTracker
[ x ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
Airframe type
X quad
Hardware type
KakuteF7 flight controller, Holybro Tekko32 4-in-1 ESCs.
I set SERVO_BLH_DEBUG = 1 to enable MAVlink reporting of BlHeli error messages to track down "bad CRC" errors I'm seeing. On the Messages tab in Mission Planner, and also with the Yaapu telemetry script these "bad CRC" messages are reported correctly. However in the messages field of the ArduCopter OSD there are two spurious characters appended to the message. See attached screenshot.
Version 3.7.0-dev
Platform [ ] All [ ] AntennaTracker [ x ] Copter [ ] Plane [ ] Rover [ ] Submarine
Airframe type X quad
Hardware type KakuteF7 flight controller, Holybro Tekko32 4-in-1 ESCs.