I've just released ArduPlane 2.32
This is a minor update with 2 changes:
The new MANUAL_LEVEL option is a boolean option. If set to zero (which is the default) then the existing behaviour of doing automatic accelerometer calibration on every boot is used.
If you set MANUAL_LEVEL to 1 then it won't calibrate the accelerometers on boot and will instead use the values from the last time it did a calibration. The idea is that you get a good level once, then set MANUAL_LEVEL to 1. You can then redo the level using the mission planner or another ground station, or by setting MANUAL_LEVEL to 0 and restarting.
The compass learning change is based on feedback from the last release where noise in the magnetometer caused the learning to be quite bad for some people. The automatic offset learning should now be robust to quite large amounts of magnetic noise.
update your mission planner and then in the firmware tab update your APM then look in the configuration tab MANUAL_LEVEL 0 change the 0 to 1
Thanks very muth Brad. Know i have it. I forgot to update also the mission Planer.
Just an idea. Might helps;
Is your ESC big enough?
Can its bec handle all the servos, APM and everything else together?
If it can not, than it reboots, and your throttle setting gets messed up also in it.
Happened to me before.
If you got a telemetry look then we could look for causes in that. For example, it logs the board voltage, allowing us to tell if your BEC was keeping up OK.
If you did get a tlog then please post it.
I had a similar issue twice and after doing some tests I've discovered that my ESC BEC was not handling the current consumption.
I've added a separate BEC and never crashed again.
Tip for everybody. Add a separate BEC to your system and do not use the ESC to power APM and servos (mainly if you use digital servos).
You should consider adding a protection lens :
It is really light and might save your camera
Has the Arduplane 2.32 been well flight tested ?
Most tested code we've ever released. Many hours in the air, on sims and through automated code verification. And at this point there are so many thousands of APM boards in use that users quickly identify any edge cases that didn't show up in developer testing.
When i rotate my APM it never shows 90° It is ok til 60°.
Do you know why is that?
There must be a reason. :)
I had working 2.28 version, I updated newest Mission Planner:
Flight data worked then, but after 2.32 firmware update Flight data is lost, and eg. stabilize don't work anymore.
I had similar symtoms before 2.25 versions.
I have APM 1, 128 version.
Trying to compile 2.28 version by hand now
I have tested the current firmware on a 1280 APM1 and it worked fine. So I suspect its something else.
Are you familiar with building using the arduino IDE? Maybe you could add some debug code and see if you can work out what is wrong.
Yeah, I managed to build 2.28 by ide and it works, I will try later versions too to figure out.