Open GoogleCodeExporter opened 8 years ago
looks like you mag is misscalibrated. the plan is flying 45 degress of almosty
all the time
Original comment by Meee...@gmail.com
on 12 Mar 2012 at 4:30
try a few things.
1. disable the mag and fly.
2. move any high power cables away form the mag.
3. do a reset to lete it recalibrate from the start.
Original comment by Meee...@gmail.com
on 12 Mar 2012 at 4:34
1.- how do you see that the mag (not gyro?) say it's flying at 45degree roll or
pitch ? (I do not know what displays that info)
2.- I have no power close to it - and waved the damn thing for about 30 minutes
just to get north/south/east/west right.
-Please feel free to tell me how the magnetometer calibration should be done.
3.- most important : how come that RTL works fine, while AUTO fails to get to a
WP ?
Original comment by andre.kj...@gmail.com
on 12 Mar 2012 at 9:45
sorry - regarding "do a reset" - I even requested to be able to store the
MAG_Offset values.
Seriously - I waved the plane for well over 20 minutes before the thing settled
at something close to real compass directions. If I just reset it again - I'm
most likely to wave the plane again for an loong time. Is there no better
method ?
Original comment by andre.kj...@gmail.com
on 12 Mar 2012 at 9:54
disabled magnetometer.
please see attached log and observe two facts:
1.- RTL does a great job, turns to home with good authority
2.- AUTO does nothing - no attempt to turn, I switch to auto multiple times and
release the sticks, unless I saved it - a crash would be the only result.
Original comment by andre.kj...@gmail.com
on 12 Mar 2012 at 4:13
can you upload your param file?
Original comment by Meee...@gmail.com
on 14 Mar 2012 at 11:35
please see attachment.
Original comment by andre.kj...@gmail.com
on 14 Mar 2012 at 12:41
Because I've used a lot of UDP - and was afraid of some bizarre config
corruption:
This Is what I did: (Mission planner updated (1.1.47))
-uploaded firmware to APM
-rebooted APM
-erased config from terminal
-erased logs
-rebooted APM
-*entered* all PID, modes,voltage offset, current sensor, magnetometer
configuration again (did NOT import from .param)
-waved APM for ~8 minutes (a lot easier than waving whole plane) - got "sane"
-compass values, not perfect, but usable.
-created a new simple 5 WP mission
-did NOT connect any telemetry hardware since this was completed.
- flew, bad weather, poor visibility, (snow) - but RTL worked from three
directions.
- stabilize and FBWA worked fine.
-switched on AUTO - released sticks -*like before* - plane was only thrown
around by the wind into random roll, and I recovered at ~90degree angle (way
past the 40degree autopilot is configured to as max.)
also, on ground - enabling auto disabled pitch & roll stabilization. (the
plane does not attempt to correct it's attitude.)
Please see new config file - made entirely from scratch.
Original comment by andre.kj...@gmail.com
on 17 Mar 2012 at 4:59
Verified that the same error is with ver Arduplane 2.30 - this way:
-no GPS fix, plane on the floor - in stabilize mode - (it does stabilize)
-switching to AUTO , now there is no stabilization anymore, servos go to center.
- no GPS surely makes it unable to work, but the stabilization would not be
switched off if everything was right.
- BTW: this is the first time I report this without proper flight, because it's
storm outside. - all other reports are real mid-air tests.
Original comment by andre.kj...@gmail.com
on 18 Mar 2012 at 11:00
See http://code.google.com/p/ardupilot-mega/issues/detail?id=566
552 is not a bug - only a result of bug 566
Original comment by andre.kj...@gmail.com
on 18 Mar 2012 at 2:12
I have the same problem. Only difference is when I switched to Auto mode, the
plane returned to my launch point and kept circling.
I connected the APM1 to Ardupilotmega and flicked the radio's toggle switch
between Manual and Auto. At mode, the following appears:
AM out of commands!
Returning to Home
AM executing command ID #1?
When the change the mode from Auto to others, eg: RTL, they all worked fine, no
error s.
I am still trying to figure out the problem.
Original comment by tek...@gmail.com
on 8 May 2012 at 2:19
This is probably due to the "reset mission" parameter is set to a channel that
is beyond 1750pwm thus resetting the automission over and over. This makes it
just fly straight forward.
Original comment by knarkva...@gmail.com
on 9 May 2013 at 9:15
Original issue reported on code.google.com by
andre.kj...@gmail.com
on 10 Mar 2012 at 5:55