800xA system V6.1 need to adjust/delete some setpoints and high level alarms
HI All,
i am working with 800xA system V6.1 and i have some new values of set points need to be adjusted and some alarms to be deleted.
my question are as below:
1- should these changes/deletion be done in CM/FB connection by using CBM Or Control Structure?
2- can it be done while system online? and if yes, should i download the configuration to the controller
i am working with 800xA system V6.1 and i have some new values of set points need to be adjusted and some alarms to be deleted.
my question are as below:
1- should these changes/deletion be done in CM/FB connection by using CBM Or Control Structure?
2- can it be done while system online? and if yes, should i download the configuration to the controller
Asked 3 months ago
Answers
0
Regarding alarms,
Always apply correction from the source (the emitter) of the alarm (in most cases the PLC or its settings).
The 800xA HMI permit users having the Administrate security privilege to perform "Delete Alarm". This deletion will never propagate to any PLC because the OPC AE standard does not encompass deletion of alarms. The deleted alarm will resurface next time it is triggered or a refresh/failover takes place.
You must study the application and its object type libraries in detail to find out how you can deactivate or delete an alarm from the application.
And, yes download to AC 800M is required.
Regarding setpoints, they can be changed online from HMI or Control Builder M. No download required.
For persistence across cold starts, setpoint variables must be tagged with the Cold Retain attribute in the control project code and cold retain be saved regularly. The latter takes place in Control Builder when going offline but should be scheduled in the AC 800M OPC Server for continuous backing up adjustments.
Always apply correction from the source (the emitter) of the alarm (in most cases the PLC or its settings).
The 800xA HMI permit users having the Administrate security privilege to perform "Delete Alarm". This deletion will never propagate to any PLC because the OPC AE standard does not encompass deletion of alarms. The deleted alarm will resurface next time it is triggered or a refresh/failover takes place.
You must study the application and its object type libraries in detail to find out how you can deactivate or delete an alarm from the application.
And, yes download to AC 800M is required.
Regarding setpoints, they can be changed online from HMI or Control Builder M. No download required.
For persistence across cold starts, setpoint variables must be tagged with the Cold Retain attribute in the control project code and cold retain be saved regularly. The latter takes place in Control Builder when going offline but should be scheduled in the AC 800M OPC Server for continuous backing up adjustments.
0
Hi
First I would like to point out that you must analyze your application (code) and object types used.
Secondly, if alarm configuration is done using variables, I would prefer doing this in a couple of steps:
1. Establish that there are no logic connected to alarm outputs for the actual object (use Search function). If so, you have to address that and might end up modifing affected logic.
2. Go online with CB/FB and change the setpoint or configuration value, for example ConfigDiff (SignalInBool) to 0 (or to 2 for event).
3. Make sure that the Alarm List is cleared. (Now you now that you deactivated the correct object...)
4. When convenient, you must remember to change the initial value of the variables you have just edited (with a download) to make the change stay permanent. Or if desired, delete the alarming object.
If setpoints or alarm configuration is done using constants, then you have to do the change performing a download.
For alarms I would strongly recommend this approach. Remember to get rid of the alarming status or logic before you delete the actual object. Otherwise you might end up with orphaned alarms in the OPC-server.
If setpoint is accessible at a faceplate, you'll might need the operator role or an elevated role to change it.
Regards
First I would like to point out that you must analyze your application (code) and object types used.
Secondly, if alarm configuration is done using variables, I would prefer doing this in a couple of steps:
1. Establish that there are no logic connected to alarm outputs for the actual object (use Search function). If so, you have to address that and might end up modifing affected logic.
2. Go online with CB/FB and change the setpoint or configuration value, for example ConfigDiff (SignalInBool) to 0 (or to 2 for event).
3. Make sure that the Alarm List is cleared. (Now you now that you deactivated the correct object...)
4. When convenient, you must remember to change the initial value of the variables you have just edited (with a download) to make the change stay permanent. Or if desired, delete the alarming object.
If setpoints or alarm configuration is done using constants, then you have to do the change performing a download.
For alarms I would strongly recommend this approach. Remember to get rid of the alarming status or logic before you delete the actual object. Otherwise you might end up with orphaned alarms in the OPC-server.
If setpoint is accessible at a faceplate, you'll might need the operator role or an elevated role to change it.
Regards
Answered 3 months ago
Add new comment