Re: Bugger
Think of it like needing a manager to approve certain refunds in a shop. It's an unusual enough circumstance, something that shouldn't really happen, and thus they probably aren't going to be certain why it happened. Better to just cause a bit of inconvenience, and let someone on a better pay grade make the decision about the best way to proceed. Surely if you're in this business, you know users who click dialogues and warnings to continue, without considering why they are clicking them. Also I'd hope you're familiar with situations happening that 'can't' happen, and what look like obvious problems which aren't fixed by (repeatedly) making the obvious fix. All becomes routine, then something catastrophic happens because they weren't thoroughly investigated.
For once, the cause of it reading a low frequency was exactly what you'd expect, but the network running at that frequency 'shouldn't happen', but I'd guess the power train, which needs to be very efficient, may well be massively damaged if drivers kept pushing the restart button, which would strand the passengers for longer, quite aside from operating such a high energy system out of spec.
Biting the hand that feeds IT
