search

Guitarmath / arducopter

Automatically exported from code.google.com/p/arducopter
0 stars 0 forks source link

APM 2.0, Arducopter 2.5.3 Auto mode throttle issue #397

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Yesterday tried the new firmware.
Tuned from the defaults to my good working PIDs (much better now than older 
firmwares!)
But. Tuned in Acro mode (gyro) fine, then tuned in Stabilize mode fine too. But 
then I hit Auto mode (waypoints preplaned in MP) and then Hexa almost shut down 
the engines and started to fall from the sky. 
Was lucky and had enough time to recover.
Tried few times with the same result. then switching to Auto mode, get throttle 
almost idle (very low RPM). 
Where should be the problem?
Thanks

Virgis

Original issue reported on code.google.com by virgi...@gmail.com on 27 Mar 2012 at 2:57

GoogleCodeExporter commented 8 years ago 
Please post a flash log or T log. Thanks
Jason

Original comment by jasonshort on 27 Mar 2012 at 5:05

GoogleCodeExporter commented 8 years ago 
Jason,

 Is this what you need?
Thanks for support!

Virgis

Original comment by virgi...@gmail.com on 28 Mar 2012 at 6:35

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Reloaded firmware and it is gone!
Thanks.

Virgis

Original comment by virgi...@gmail.com on 9 Apr 2012 at 1:34

GoogleCodeExporter commented 8 years ago 
Virgis, 
    You sonar values are not looking good.  Attached is a plot of your sonar (in red) and your baro (in green).  The wiki has some good information on improving your sonar's resistance to interference so that might help.  Worst case, I'd disable it because it's certainly not doing any good!

Original comment by rmackay...@gmail.com on 10 Apr 2012 at 12:10

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
could those sonar issues be with wrong selection of Sonar? I can't remember the 
exact model I have, so maybe missed the one?

Virgis

Original comment by virgi...@gmail.com on 10 Apr 2012 at 2:11

GoogleCodeExporter commented 8 years ago 
Virgis,
     I don't think so because getting the wrong selection should just lead to the values being twice (or half) of what they should be.  But what we see in the logs is just a lot of spikes.  You can see it's ok for a very short period of time near the rigth...between 28.2 and 28.4...but it should look like that all the time.
     By the way - you can check the number that's printed on the back of your sonar.  It should be 1200 (XL-EZ 7m) or 1260 (XL-EZ 10m) or maybe 1030 (LV-EZ).

-Randy

Original comment by rmackay...@gmail.com on 10 Apr 2012 at 2:59

GoogleCodeExporter commented 8 years ago 
Issue closed. 
If you find this is an error please report it in the new issues list
https://github.com/diydrones/ardupilot/issues?labels=ArduCopter&page=1&state=ope
n

Original comment by Benny.Si...@gmail.com on 20 Jan 2013 at 7:52