maintaining stall warning
infrequentflyer789
You can't just fix the SW logic, in any meaningful way.
I beg to disagree, see post #213
The input data simply isn't there in this scenario.
Yes, you do not have a meaningful value for AoA (here represented by a NaN), so cannot use it in a context-free rule to indicate if the stall-warning should be sounded.
You could maybe give the SW memory so it uses last-valid value, which would catch the 447 scenario - but that adds complexity and failure modes there.
As you say, remembering any previous sensor value (e.g. AoA ) leads to extra complexity and failure modes.
However holding the current state of the stall-alarm would not introduce such problems.
In "IEEE FP speak" my AoA_trusted and your AoA are related by: AoA_trusted = NOT(isNaN(AoA)).