Yesterday I tried to execute a mission with my new APM 2.5 (with AP2.65) and one time the engine started and the plane take off (hand launch), but the compas calibration was wrong and I had to make a manual landing.
After that I couldn't initialized the mission never because the motor didn't start, on Mission Planer when I switch to AUTO, the orange line indicate correct waypoint. I tried many things like:
- reset APM2.5,
- switch off and switch on the apm,
- press the button "restart mission"
- Preflight reboot
- Goto WP1
But nothing start the engine :-(
Thanks for you ear me.
Replies
Hi Daniel,
There is a bug in the current ArduPlane 2.65 release that means that TAKEOFF doesn't work properly if both the "lat" and "lon" fields of the TAKEOFF command are zero. The lat/lon fields are normally ignored in takeoff, but the introduction of the special zero/zero waypoints (meaning "current location") had a side effect of changing how the altitude was interpreted in TAKEOFF with 0/0 for lat/lon as being "above sea level" instead of "above home". Unfortunately Mission Planner uses 0/0 when it creates TAKEOFF points.
The workaround is to set lat or lon to any non-zero value in your TAKEOFF commands. I have pushed a proper fix to git master, and I'm planning on doing a new release soon.
Cheers, Tridge
I had the same thing happen today.. Auto mode would not execute the takeoff command.. It used to work fine so not sure whats up.
Did you give it some throttle? It won't start until you give it >0 throttle on the transmitter. It's a safety precaution.
Oh sorry, you're talking arduplane..i'm more on the copter side. sorry!