I loaded the APM 2.24 with all the default parameters today and went flying. Stabilization and FBWA worked fine but when switching to AUTO or RTL modes, the plane goes into a dive. I've tried setting waypoints with both relative and absolute altitudes with the same end results.
Does anyone know what is going on?
Thanks for your fast help again!
1.In this log the mission was broken (around waypoint 4 or 5) after that I set the waypoints manually in the APM.
2.I'll check the cables tomorrow.
3. Ok I was a bit confusing:D. When you turn on the Ardupilot it beeps 3 times a short sign and once a longer one and the sensors starts to initialize themselves (the plane have to be kept in a horizontal position) It takes around 15 secs. We usually test the plane's behavior on the ground before we fly in Stabilized mode. (we hold and turn it in every directions) sometimes the rudders don't make anything and sometimes they work correctly and countersteer to the opposite direction. Is it normal?
Re: #3, I'm still not quite understanding. APM can't beep at all (it doesn't have a buzzer/speaker). Maybe you mean your motor? You refer to "rudders" but I don't know what that means. Do you mean "rudder" (singular) or "ailerons" or something else?
This isn't failsafe kicking in is it? When you are in auto, could you be loosing radio contact and your RC receiver changing modes?
Just a thought.
The strange thing is that it also does the "failsafe kick" when the plane is whitin the RC's coverage!
I have been flying 2.24+ quite a bit lately and never had such an issue. Are you using an airspeed sensor? If so check that it is giving proper readings and that you have an appropriate value for cruise_speed.
Same thing happened to me...
Today I've uploaded ArduPlane 2.24 via APM software. Set up as usual - all left untouched except radio calibration, modes and airspeed sensor=off for today. Went flying - stabilize and fbw works ok, but when switched to RTL - plane goes to a dive.
Back home I wanted to analyze logs, and here what is tells me:
APM trunk] logs
logs enabled: ATTITUDE_MED GPS PM MODE CMD
No logs available for download
Log] logslogs enabled: ATTITUDE_MED GPS PM MODE CMD
No logs available for download
So is there anything wrong with my logs? It is enabled but not working???
Do I have to erase logs with 'Log Download' part of the APM? Or just 'Reset APM hardware to defaults' work fine? (First step after flashing new firmware)
UPDATE: after erasing all logs APM begin to behave normally - no dives etc.. (checked in RTL mode).
So maybe log erasing procedure must be added to 'factory reset' procedure?
My new plane is up and flying and almost crashed again on it's first flight. This is my 3rd APM so I hope you guys can help out. I've attached the flight logs from the GS. At about 42% I am still on the ground and verifying proper surfaces deflection...pitch is working as it should be in stabilize mode. At about 62%, while in flight I switched from manual to stabilize and the plane went into a vertical nose down attitude...luckily I was able to regain control.
Does anyone have any idea as to what could be going on?
Rigel: you'll need to tell us a lot more about your setup. How you're mounting APM (are you sure it's pointed forward and not backwards?), what kind of aircraft it's on and any special configuration it may have, whether you've done the full MP setup, etc. Photos are helpful. These probablems are almost always due to setup errors.
You mentioned it's your 3rd APM. Have you flown successively with the others?
my guess is your pitch needs reversing, either on the dip switchs or via the planner setup.
on the ground remeber that when in stabalise the plane should try leveling itself when you move it around.
from your log it looks like it pushes further into the dive.