🚀 "Stay Alive" / Hover Mode Default Behavior After Takeoff
📝 Summary
The drone should default to a "stay alive" (hovering) mode immediately after a successful connection and takeoff, preventing it from entering a "sleep" state while waiting for subsequent commands. This ensures a continuous flight state until an explicit landing/shutdown command is received.
🎯 Current (Undesired) Behavior
Currently, the drone may enter a "sleep" after about 10 seconds if not executing a command (e.g., takeoff, right, left), even while still airborne, requiring a manual "stay alive" command to maintain flight/hovering.
✅ Desired (New) Behavior
- When the user presses the Connect button, the drone establishes a connection.
- Upon executing a flight action like Takeoff, the drone should automatically enter and maintain a hovering state.
- The drone should never enter a sleep/idle state while airborne, but instead, it should stay hovering and ready to receive the next instruction (e.g., right, left, forward, etc.).
- The drone should only land or shut down upon receiving an explicit Land or Disconnect/Shutdown command.
💡 Justification
This change streamlines manual operation by removing the need for repeated "stay alive" commands, making the control logic more intuitive and robust for continuous flight missions. It aligns the behavior with common expectations for drone control interfaces.
⚠️ Historical Context / Prior Implementations
This functionality has been implemented and subsequently lost due to code changes in the past. Please ensure the new implementation is robust and test coverage is added to prevent regression.
🚀 "Stay Alive" / Hover Mode Default Behavior After Takeoff
📝 Summary
The drone should default to a "stay alive" (hovering) mode immediately after a successful connection and takeoff, preventing it from entering a "sleep" state while waiting for subsequent commands. This ensures a continuous flight state until an explicit landing/shutdown command is received.
🎯 Current (Undesired) Behavior
Currently, the drone may enter a "sleep" after about 10 seconds if not executing a command (e.g., takeoff, right, left), even while still airborne, requiring a manual "stay alive" command to maintain flight/hovering.
✅ Desired (New) Behavior
💡 Justification
This change streamlines manual operation by removing the need for repeated "stay alive" commands, making the control logic more intuitive and robust for continuous flight missions. It aligns the behavior with common expectations for drone control interfaces.
This functionality has been implemented and subsequently lost due to code changes in the past. Please ensure the new implementation is robust and test coverage is added to prevent regression.