An interesting conversation - enjoying everyone’s (supportive) viewpoints.
Since no documentation or expected documentation is available in this scenario, I can see where different system engineers and programmers will implement code in various ways when not relying on foundation classes for code reuse.
From a typical users perspective, is for the
MA to remain idling until an initial stick input thrust spin up has been initiated. Yet even here the devil is in the details - should it be for a certain time interval as:
- Greater Than .5 seconds?
- Stick movement Greater Than 50 percent throttle?
- Some combination of above
- Greater than “X” inches (practically not possible based on accuracy limitations)
- Some combinations of the above
Actually, let’s say the initiation is currently based on a very small stick movement (say 5+ percent), then a RC giggle on a boat could have caused initiation, etc.
However, as some prior posters have pointed out, perhaps on newer DJI smaller craft (350 or smaller size), DJI programmers have coded drones like the
MA to facilitate “throw and activate spin-up) as a cool feature, not aware of potentially dangerous scenarios as discussed here.
But then what about a scenario such as a shutdown while in the air at say 200 feet? (Software/hardware/operator error). Wouldn’t the programmer or system engineer requirements specify to thrust up and hover IMMEDIATELY after reinitialization sequence? To me, I would program to this scenario over other more remote possibilities as discussed in this thread.
Happy trails and skyways, Michael
