Why did my Navis float unexpectedly start its mission during pre-deployment testing?

There are two ways the N2 can start a mission without the user explicitly starting pressure activation or mission execute.nnNot Freezing the float:nIf the float is not frozen (I F command) and the dongle is removed, the N2 will eventually timeout. This is more of a precaution in the case the user forgot to start the mission and deployed the float. nnDongle Noise:nIf the user sends the I F command, then attempts to disconnect and the dongle removal is not clean, this may cause the float to wake back up. The float will then timeout and start a mission. Here it would be recommended that a switch is added inline to the dongle (similar to what we have in production)