That is always the issue with alarms. You have a fine line to walk. Too many alarms and people become complacent and learn to ignore alarms. Too few alarms and you don't draw the attention that is needed.
That's enough to anchor "alert == I might find a problem" in the user's mind.
Instead, the failsafe has the effect of merely invalidating the current test, and making the appliance unable to run a test correctly until either power cycled or the appliance's developer executes a secret series of commands that are not shared with us.
So of course an operator of the appliance found a way to feed in a false "I'm here!" with a loop, to trick the appliance into never going into failsafe…
That's for ~6.8% of all tests being false-positive, ~93.2% being true-negative, and ~3 tests that should have triggered failsafe did not.
I don't if you meant it as a counterpoint for what I said, but it really isn't.
The problem is that given any positive at all, the chance it points to a problem is still virtually zero.
If it was 6.8% of all tests as false positives and 2% true positives, probably people wouldn't have silenced the alarm.
If it goes off 8 times a day and 2 of them are true positives, then people have recent memories of having to fix problems pointed by the alarm.
The reduction I am arguing against is: "Historically, extra information and diagnostics that have an error margin results in worse outcomes because we misapply it; therefore don't build these systems."
And the nurses who want decent pay and can do travel nurse, do travel nurse