That's a good point. I looked at the possibility that latency played a role in this and noticed there are some other aspects that don't quite add up. Normally, the abrupt power loss incidents are only apparent in the motorVolts signals; the motorSpeed and motorCurrent signals don't have time to change. But, the
P4P incidents, this one and
P4 Dropped like a brick midflight
are different. The change in motorSpeed is apparent in the latter, and a change in motorCurrent can be seen in the first. I addition, neither of the .DATs exhibit a corrupt end of file that often happens with the abrupt power loss.
IMHO a failed prop causing the battery to disconnect is a bit of a stretch, at least for me. It's easier for me to believe that the vibration from a failed prop would dislodge a battery.... But, not a lot easier.