Originally Posted by
PiggyBack
The actual code is not as straightforward as suggested. The two AoA sensors will frequently not read exactly the same and the readings wil be noisy so when they are compared the output of each AoA sensor must be filtered and the comparison must allow a tolerance window. What if the disagreement is intermittant? Should the system reenable itself or stay off?
One would think that your line of thinking was pursued in considerable depth before implementing that system. (Only those involved in it will know).
I have had the opportunity in the last decade to participate in safety of flight component redesign IPTs. As you say it's not quite as simple as it sounds.
When you take something that has already been subjected to a variety of optimization and design constraints, and decisions, the amount of design space/room for revision shrinks considerably. (While my most recent experience was with hardware, not software, back when it was software (not flight systems software) the problem is as thorny for different reasons.