No OSD data before arming.

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. power on the rc transmitter and copter.
2. Now there is osd overlay, but the data is not beeing updated. Everyting at 0.
3. Arm the copter. Data appears. And stays for the remainder of the battery.

What is the expected output? What do you see instead?
OSD data as soon as power is turned on. Instead there is no data untill the 
copter is armed.

What version of the product are you using? On what operating system?
Mavlink osd. minimosd extra firmware, tool and charset from jan 2014 downloaded 
from this site. Win 7 64 for configuration. Its connected to APM 2.8 running 
arducopter 3.2.1

Please provide any additional information below.
Entirely possible(and perhaps likely? ;) that this is an APM issue rather than 
a minimosd extra issue, but perhaps someone here got a solution :)

Original issue reported on code.google.com by Akuji...@gmail.com on 21 Aug 2015 at 4:36

GoogleCodeExporter commented 9 years ago

To clarify, there is no message saying "waiting for mavlink" "no heartbeat" 
etc. (this would appear if i disconnect the signal cable) instead, there is 
full overlay, just no updated values. all at zero

Original comment by Akuji...@gmail.com on 21 Aug 2015 at 4:42

GoogleCodeExporter commented 9 years ago

Update: Have gone through the wiki page here and set the parameters acordingly. 
but still doesnt function as i would like. At the moment, only compass heading 
is shown before the copter is armed.

Original comment by Akuji...@gmail.com on 22 Aug 2015 at 2:35

uframer / minimosd-extra

No OSD data before arming. #138