MPC test aborted: Downstream block reporting limited status

Hello,

I'm trying to control an air temperature loop, at first I was trying to manipulate the AO directly with the MPC block, but the response speed was very slow and the AO never went past 30% output. With a PID loop I get a decent response, so that's why I set a previously tuned PID block as slave of the MPC block. However, now that I'm trying to get the model for the MPC block I get the following error message:

Test was aborted because of the following reasons:

-Downstream block connected to "output_variable_name" is reporting limited status

The process is stabilized in 50°C, a 5% step change should be between 34.64°C and 65.35°C (AI zero=-99°C, max= 208°C; span=307°C).

I checked the SP_LIMS of the PID and everything seems to be ok, since the 5% step change I'm making is inside the limits, so what block or parameter does deltav refer as limited?

Please find below some screenshots of my module for further visualization of the problem. Many many thanks in advance.

Error dialog

Module diagram: (MPC block status is Out of service, I'm using the MPC pro block). DO is the fan switch, AI1 is a DP sensor (disturbance to MPC pro block), AO is output to a fan SCR. Connecting output of MPC to the PID RCAS.

Module diagram

PID and AO parameters:

PID parameters 1PID parameters 2   AO parameters

MPC parameters:

MPC parameters 1MPC parameters 2

MPC test setup

Edit 24/2/2020 16:26 EST

MPC block MV, CV and disturbance properties

MPC predictpro test configuration

  • In reply to JDWheelis:

    I tried to do another test after removing the check on "ignore errors" and expanding the AO2/SP_LO_LIM from 0 to -1 so when the pid gets to 0% the AO won't be limited thus carrying the limited status to the pid, but the test aborted anyways. I humbly ask you again about setting the limits of the sp/pv/mv because i thought i got it but looks like i do not.