You tell me.

No. You have way too many things going on in IMX. Just find a good start/end value. Don't have huge jumps in it. Don't have lots of random high areas and low areas and drastic changes. Try to keep it mostly flat. PIDs are hard enough to tune without you giving it a bunch of random crap that moves around a lot, especially in non-linear weird parameter scheduling stuff. Keep it simple.

Also you are maxed out up top. Might want to pull some req boost

Yes and no. IMX should really be more or less flat, and you should use DRL to compensate for needing more wg for a given boost. That is its purpose. Tuning this stuff blindly w/o really understanding at least the basics is going to be problematic. And if you are hitting 95% ANYWHERE (other than during spool) that means your req is likely too high.

Understanding PIDs is a general engineering/control topic. You won't find a PID explanation in the FR. IMX is there to prevent integrator windup, and generally in ME7 it can be used to provide feedforward control. Much of this is covered in the Tuning wiki and in lots of other places here.

Long story short: your WGDC will (mostly) follow IMX post processed by DRL.


I sense you don't really understand what DRL does either

The reason IMX is so important in ME7 is that in the steady state, P result is near zero and D is scheduled out with B_lddy. This means that I dominates.

On a WOT pull, I is maxed out due to integrator windup (accumulated error) so it is simply following IMX.

Also in the steady state, you would expect the output of the PID to be flat for a given flat boost set point. However, DC isn't linear with output boost, so the output of the PID is post processed by DRL.

Again, if you truly understand PIDs, you should already know the critical points here

1) integrator windup effects when there is long term error
2) linearizing the control output to compensate for varying process output gain.

You'll eventually send the I-trims to max and in extreme cases get a pos deviation code.