New PIDCONA faceplate values not updating
Hi all!
I've added a new PIDCONA with enabled gain scheduling. Programming were carried out online.
The PIDCONA is programmed to allow manual and auto modes, in addition to enabling gain scheduling.
I've disabled all autotuning or adaption settings both in the DB and PC elements.
After, what I believed to be, completion of programming, the faceplate variable values of the PIDCONA won't update.
In addition, the faceplate don't allow me to change between modes - for instance, from manual to auto. The faceplate returns the message that the action (setting of operational mode auto/manual) is not allowed.
When I look up the faceplate for the new PIDCONA, all values are constantly at zero. Even though, I know the MV is varying.
When programming changes on constants (i.e., limits, alarm limits etc) these are updated correspondingly in the faceplate (almost) simultaneously.
I've checked that the correct DB instance is defined for the PC element, and I observe that the measured variable is alive onto the PC element pin by using the GEPCD and GVD commands in the online builder.
A screen shot of my mentioned PC element is attached.
The controller is an AC450.
Any idea what's causing this?
Best,
Andreas
I've added a new PIDCONA with enabled gain scheduling. Programming were carried out online.
The PIDCONA is programmed to allow manual and auto modes, in addition to enabling gain scheduling.
I've disabled all autotuning or adaption settings both in the DB and PC elements.
After, what I believed to be, completion of programming, the faceplate variable values of the PIDCONA won't update.
In addition, the faceplate don't allow me to change between modes - for instance, from manual to auto. The faceplate returns the message that the action (setting of operational mode auto/manual) is not allowed.
When I look up the faceplate for the new PIDCONA, all values are constantly at zero. Even though, I know the MV is varying.
When programming changes on constants (i.e., limits, alarm limits etc) these are updated correspondingly in the faceplate (almost) simultaneously.
I've checked that the correct DB instance is defined for the PC element, and I observe that the measured variable is alive onto the PC element pin by using the GEPCD and GVD commands in the online builder.
A screen shot of my mentioned PC element is attached.
The controller is an AC450.
Any idea what's causing this?
Best,
Andreas
Voted best answer
Perhaps you forgot to set the database parameter ACT to 1?
Add new comment