APM 2.6, Arducopter 3.2.1
I am having an issue that data is not sent to the MinimOSD UNTIL I connect via the telemetry radio.
Thereafter everything works fine.
Note that all SR0_* and SR1_* parameters are set to non-zero values.
I wrote a MAVlink inspector using an Arduino Due, and saw the following:
- The APM only emits heartbeat messages initially
- Once the telemetry radio connects, it sends a REQUEST_DATA_STREAM message (two of them actually)
- Then all MAVlink message start up, and the OSD works 100%
This is a problem because the MinimOSD Tx is not connected (in order to allow the telemetry radio to work), so it cannot send a REQUEST_DATA_STREAM message.
Additionally, I am not sure that the MinimOSD send this message anyway.
Here is the output from the inspector. The first number is seconds elapsed, and the > or < indicates direction of the message.
==== Opening MAV 1…
==== Opening MAV 2…
0 > 0 (1, 1) > HEARTBEAT
1 > 0 (1, 1) > HEARTBEAT
…
26 > 0 (1, 1) > HEARTBEAT
27 > 0 (1, 1) > HEARTBEAT
27 < 0 (255, 190) < HEARTBEAT
27 < 66 (255, 190) < REQUEST_DATA_STREAM
27 < 66 (255, 190) < REQUEST_DATA_STREAM
27 > 42 (1, 1) > MISSION_CURRENT
27 > 35 (1, 1) > RC_CHANNELS_RAW
27 > 30 (1, 1) > ATTITUDE
27 > 74 (1, 1) > VFR_HUD
27 > 2 (1, 1) > SYSTEM_TIME
27 > 253 (1, 1) > STATUSTEXT
27 > 22 (1, 1) > PARAM_VALUE
…
33 > 22 (1, 1) > PARAM_VALUE
33 > 22 (1, 1) > PARAM_VALUE
34 > 22 (1, 1) > PARAM_VALUE
34 > 1 (1, 1) > SYS_STATUS
34 > 42 (1, 1) > MISSION_CURRENT
34 > 24 (1, 1) > GPS_RAW_INT
34 > 62 (1, 1) > NAV_CONTROLLER_OUTPUT
34 > 0 (1, 1) > HEARTBEAT
34 > 27 (1, 1) > RAW_IMU
34 > 29 (1, 1) > SCALED_PRESSURE
34 > 33 (1, 1) > GLOBAL_POSITION_INT
34 > 36 (1, 1) > SERVO_OUTPUT_RAW
34 > 35 (1, 1) > RC_CHANNELS_RAW
34 > 30 (1, 1) > ATTITUDE
…