SWFirmware- Unknown Event Generated & No communication with BackupCPU
Hi, Can anyone help me to identify the reason behind the events as shown in screenshot 1 regarding SWFirmware & SWAlarmEvent?
When I browse to these events, it took me to control structure. Right after these events, I get another event with the message "Refresh is needed".
The second issue which I am facing is regarding the warning on the controller: "No communication BackupCPU with warning code 16#20020000
I have a redundant PM866 with some SOE & normal modules. I have tested the redundancy for the controller. Dual LED glows on both and when I powered off the primary controller, the redundant takes its place. Same with module bus failure. I am also able to ping both the controller network IP addresses.
When I browse to these events, it took me to control structure. Right after these events, I get another event with the message "Refresh is needed".
The second issue which I am facing is regarding the warning on the controller: "No communication BackupCPU with warning code 16#20020000
I have a redundant PM866 with some SOE & normal modules. I have tested the redundancy for the controller. Dual LED glows on both and when I powered off the primary controller, the redundant takes its place. Same with module bus failure. I am also able to ping both the controller network IP addresses.
Asked 5 months ago
Answers
0
There are several AlarmCond modules having parameter errors.
This common programmatic error (impossible to be screened by the Control Builder M during compilation of an application) has been brought up many times on AKS before: check validity and uniqueness of the SourceName+CondName combination, verify non-zero Severity and Class.
Each downloaded alarm must be given an, in the OPC server's realm, unique combo having no illegal characters like spaces, etc. nor a zero severity/class.
"Refresh is needed" is a natural internal system event that follows upon download. It is expected and makes sure obsoleted alarms are removed from the HMI.
Did you remember to activate the backup CPU's Ethernet port(s) with IPConfig and the serial cable? "Use Default Rule" is recommended, it adds 0.0.2.0 to the backup IP address compared to the primary, e.g. 172.16.80.151 makes the backup take 172.16.82.151. Primary CPU must be wired to the same IP-subnet as the secondary.
This common programmatic error (impossible to be screened by the Control Builder M during compilation of an application) has been brought up many times on AKS before: check validity and uniqueness of the SourceName+CondName combination, verify non-zero Severity and Class.
Each downloaded alarm must be given an, in the OPC server's realm, unique combo having no illegal characters like spaces, etc. nor a zero severity/class.
"Refresh is needed" is a natural internal system event that follows upon download. It is expected and makes sure obsoleted alarms are removed from the HMI.
Did you remember to activate the backup CPU's Ethernet port(s) with IPConfig and the serial cable? "Use Default Rule" is recommended, it adds 0.0.2.0 to the backup IP address compared to the primary, e.g. 172.16.80.151 makes the backup take 172.16.82.151. Primary CPU must be wired to the same IP-subnet as the secondary.
Add new comment