Not all that sure myself how it re-armed but I do know it was disarmed. One thing I always do after disarming is to pop the throttle stick up and back before I even approach the multi, did that with the FlipFPV and no reaction, also looked in to see the LED wasn't indicating armed anymore, it was disarmed. I think what happened is the radio was leaning to the left off the strap and the throttle stick hung up on my jacket so it stayed there long enough to arm the board and the next bump brought the throttle up.
Fortunately the JR11X allows a throttle hold to be setup in both heli and acro mode so I'm going to use it for everything. I'm also going into the sketch on all the multiwii I currently have flying and comment out the motor stop so they spin as soon as it's armed, most of the rest already do that, MK, DJI WKM and Naza...
All it takes is that one time you DON'T do something you should, like unplug the battery before picking it up, to cause havoc, won't be happening again on any of my equipment.
Ken
Ken, I'm interested in making the system as safe as possible. Your input is valuable as it sounds like you know what you're doing, and have procedures to act safely, but still have had an accident.
So you're saying most of the rest spin the motors, presumably at minimum throttle, when they are armed but with the stick all the way down? Would that have helped in this case? Wouldn't they still have started spinning as soon as they armed, and still cause injury?
I have thought about making it so that the motors spin at min throttle for 2 seconds as soon as you arm it, regardless of the stick position. So if you arm, and then jam the stick up, they'll still only spin at low RPM for 2 seconds. Maybe could make it more. Do you think this would help?
Ken, that's almost the exact same idea and reasoning I had. It wouldn't completely eliminate the chance of injury, but being hit with minimum throttle is a lot better than... well anything higher than that. So lock it in to minimum throttle for at least 2-3 seconds. Before allowing it to respond to real throttle inputs.
At least until a beeper is built in, this seems like the best, the only thing, we can really do.