search

wjzlrong / arducam-osd

Automatically exported from code.google.com/p/arducam-osd
0 stars 0 forks source link

No throttle use displayed. (permanent 0%) #17

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I upgraded to 1.9 for MAVlink 0.9 today.
My first flight failed to display any throttle, it was stuck at 0%

Original issue reported on code.google.com by andre.kj...@gmail.com on 26 Feb 2012 at 4:34

GoogleCodeExporter commented 8 years ago 
If you have a tlog for this flight, can you attach it? thanks

Original comment by mandro...@googlemail.com on 27 Feb 2012 at 7:25

GoogleCodeExporter commented 8 years ago 
Hi, I do not have a .tlog for this flight, after upgrading to 1.9 - I wanted to 
test the OSD - not omit it's TX pin - and connect dronecell in paralell.
The problem is still reproducible on ground.

Original comment by andre.kj...@gmail.com on 27 Feb 2012 at 5:30

GoogleCodeExporter commented 8 years ago 
Please see attached file, not a flight log, but smaller, just as good.
I booted APM + OSD - and watched OSD (stuck at 0%) while moving throttle.most 
of the log have some throttle, there should be little time at 0%.
I can test a bugfixed version anytime.

Original comment by andre.kj...@gmail.com on 28 Feb 2012 at 6:07

Attachments:

GoogleCodeExporter commented 8 years ago 
Did you calibrate your radio? I can't reproduce it here.

Original comment by sbeni...@gmail.com on 2 Mar 2012 at 7:24

GoogleCodeExporter commented 8 years ago 
yes, it's calibrated - what about the tlog ? - it shows min/max value, and you 
calculate % ?

Original comment by andre.kj...@gmail.com on 2 Mar 2012 at 7:31

GoogleCodeExporter commented 8 years ago 
Yes. TLog isn't using just the MAVLink HUD msg data. Anyway, I can't reproduce 
it here. It's working fine with latest ArduPlane code.

Original comment by sbeni...@gmail.com on 3 Mar 2012 at 3:37

GoogleCodeExporter commented 8 years ago 
guess what : I erased APM settings - and it worked. - does not work if I import 
old config - but it works with new config.  very strange.

if you care to pinpoint the problem - see the attached config.
the config ended up as a mess after much testing, so I decided to do it all 
from scratch - except for the PID's I knew were good, and voltage/current 
calibration.

Original comment by andre.kj...@gmail.com on 3 Mar 2012 at 3:53

Attachments:

GoogleCodeExporter commented 8 years ago 
Yes. Wrong data on ch3 trim parameter can drive to errors like that. So, that's 
not about the OSD and I will set the status to invalid. Anyway, thanks by your 
feedback.

Original comment by sbeni...@gmail.com on 3 Mar 2012 at 4:21

GoogleCodeExporter commented 8 years ago 
ok, all the ch min/max values seem to be lost, that must have happened when I 
played with partial import (view difference) - this config would not have 
worked with AP at all.
Anyway - case closed :)

Original comment by andre.kj...@gmail.com on 3 Mar 2012 at 4:56