7/15/2017 12:14 AM | |
Joined: 3/14/2008 Last visit: 4/24/2024 Posts: 2065 Rating: (927)
|
Hi again! Because you have connected the Rbk variable of the PIDContL block, the readback value is activated. You get the low limit error, because the Rbk is below variable: "RbkWL_Li". You can set a value here to show an alarm when the readback value is below the value set. If you don't want to use the readback limit monitoring, you can do three things: - Disable the messages by setting variable: "RbkWL_MsgEn" to 0. No more messages displayed for the low alarm warning. You can do the same for: "RbkWH_MsgEn, which is the high limit. - Disable the limit monitoring. This means that output variable: "RbkWL_Act" is not set in case the readback falls below the limit.
- Set the low limit of the readback value to something like -9999 and the high limit to 9999. I always do this for limit settings. You wont get the alarms and during commisioning you know which values must be done. The invalid cpi signal is coming from the ConPerMon block that you connected to the controller right? ConPerMon is a difficult block to explain. It will monitor the process and outputs an futurist view of the PV and SP values to determine the performance of the PID controller. As a starter, you can do without this CPM block. It is not necessary to operate the PIDController. |
Last edited by: Oreca at: 7/15/2017 12:18:35 AMLast edited by: Oreca at: 7/15/2017 12:27:07 AMIf I could help you, you can use the RATE button. Thank you. |
|
7/15/2017 11:00 PM | |
Posts: 42 Rating: (0) |
Oreca Sit thanks a lot |
Follow us on