But MCAS (the Maneuvering Characteristics Augmentation System) per se is not the problem, the problem is whatever it is that makes it (mal) function not-as-intended, be it the sensors, the circuitry associated with the sensors, or a bug à la toyota in the software.
partially agree..
As a side note: to keep nose within a certain angle tolerance, the system obeys the PID controller rules.
There's a complex issue there, I guess;
-unknown external factor(s) which is just swinging that system based on PID controller rules (here could be many sub-items)
- attack angle sensor is OK, however, in certain conditions its signal cannot be processed properly by system (air flow whirl at place where sensor(s) mounted, micro/macro swinging of fuselage or whatever)
- attack angle sensor is NOK, low reliability
- PID controller is not capable to process exceeding certain limits incoming values, due to wrong coefficient settings or so;
- it is not possible in principle to design an appropriate PID system, due to exceeding all limits external factors (e.g. much unbalanced fuselage)
-missing of elementary redundancy (that not the case, I think, it's aviation);
-influence redundand control channels on each other, somehow (code, conception mistake);
-a lack of option to override that system (code, conception mistake);
-no docs and corresponding training program on that system behaving and misbehaving;
BR
Generally speaking, the PID regulation rules it's foundation of automation based on 'higher mathematics' and constant head ache by students.