Originally Posted by
CONF iture
...
From my personal experience, I have to figure why the trim stopped around 12 deg UP and why it did not later on follow my full fwd request on the sidestick ... ?
I have seen this mentioned before, and I could design an auto-trim function that had this undesired behaviour - which shows same symptoms as classical "integral wind-up". If the controller doesn't know the output is limited it continues to ask for higher values, and then has further to fall before output comes back in valid range. Surely a correct implementation would include 'integral limiting' or 'desaturation' which would mean mean it would start trimming down soon after fwd input.