The 3.2-rc10 firmware for vrubrain-v51 provided by virtualrobotix somehow manages to kill manual failsafe here.
When using a switch to trigger failsafe by sending a low (your failsafe) signal for channel 3, the copter does not enter failsafe, but turns off all engines and disables logging.
Turning off the transmitter, failsafe works.
I guess it somehow goes to "init_disarm_motors" directly (only way to log LANDED_MAYBE after LANDED).
I build the diydrones/ardupilot ArduCopter 3.2 branch myself, added DataFlash log statements to init_disarm_motors to be able to figure out which value makes it think disabling everything is fine, and the diydrones ArduCopter 3.2 branch just works fine, proper failsafe when pushing the switch.
I tried to figure out the exact diff of vr 3.2-rc10 vs diydrones, but vr builds have git revisions which are not in diydrones.
https://github.com/virtualrobotix/ar...ommit/9b5ae68c
I got logs, I can reproduce on the bench.
BE AWARE - DO NOT USE.
Cost me 2 quads already.
If you want to test on the bench, make sure to give enough throttle so "landed" in MP is false.
Turning off the transmitter, you'll go to LAND mode, and land.
Setting channel 3 low manually disables all engines and logging.
Re-arm afterwards, so you can see the disabled logging by the time gap in RCIN TimeMS.