minimOSD/w MWOSD: Displays over lay but NO DATA

[oldgazer1 (Oldgazer)]

Three separate minimOSDs/MWOSD firmware on three separate Pixhawks (1 2.4.6 and 2 2.4.8s) all bit the dust. I have flashed firmware, fonts, and tried every trick in the book. I can use the configurator to make changes to the over lay and those changes appear in the transmitted video, but I cannot get any data. I have switched from Telem1 to Telem2, and back again… I have tried with a telemetry radio in parallel and the radio works, but the OSD still does not get any data…

Any advice will be greatly appreciated.

[xfacta (Shawn)]

Protocol set to Mavlink1 ? Baud 57 (57600) of course.
I also set TELEM_DELAY to 5 secs, gives everything time to settle, maybe 2 secs would be OK too.

[xfacta (Shawn)]

Also
DEV_OPTIONS = 2 for DevOptionVFR_HUDRelativeAlt once the OSD’s are working

[oldgazer1 (Oldgazer)]

@xfacta

Protocol set to Mavlink1 ? Baud 57 (57600) of course.
I also set TELEM_DELAY to 5 secs, gives everything time to settle, maybe 2 secs would be OK too.

I tried that. Still no data. I did forget to mention the OSD is displaying ArduCopter startup status messages, but still no dynamic data. This has got to be an ArduCopter thing…

[xfacta (Shawn)]

This old discussion covers most things:

minimOSD Bug or Feature?

Hi, I have recently added FPV & minimOSD to my octo. (Arducopter 3.5.4) Everything works as a charm, except that the flight mode field does seem to a) show garbage and b) does not change even when flight modes do change. Basically it forever displays “M_O” (see pic) as flightmode while all the other fields update as I would expect during flight. As I am new to minimOSD wanted to ask if others have the same problem and if there is a known solution ? Regards & Thanks, Christian [minimOSD%20I…