While we put our drone in take off mode and try autonomous flight, we think that the reason why the engine stops when switching between modes is the parameters (mission planner parameters). Anyone have any ideas on this?
Hello @Eray_Kosterelioglu !
Could you be a bit more descriptive? Perhaps even post a .bin flight log of the flight where you observed the issue?
We don’t have the flight log, but I can detail the issue as follows: When the aircraft is in our hand and in takeoff mode, the motor runs. However, when switching to other modes, the motor stops. When we try to start directly in loiter mode or other modes, the motor doesn’t run at all. Sometimes it works, and sometimes it doesn’t.
Is this about a multicopter or a fixed-wing UAV?
Are you able to arm the Flight Controller in these other modes?
This is fixed wing we can arm in every modes
TAKEOFF mode will automatically engage the throttle, unless you have configured one or more takeoff conditions.
On the contrary, most automatic flight modes will not engage the throttle, unless the autopilot thinks it is already flying.
1 Like
We can do a takeoff, but after the takeoff is over, the engine cuts off gas in other flight modes, but we have not tested this entire mission in the air. Our main problem is that when we put the aircraft into loiter mode without giving any task while it is on the ground, the engine cuts off gas and it is very scary to try this in the air.
Perhaps it’s desired behaviour, as part of the mission, perhaps it’s some sort of misconfiguration.
The flight code has been very well tested in these modes that it’s very unlikely this is a bug.
A .bin log would provide a definitive answer on why this happened.