800xA 6.0.3.2 AlarmCondBasic problem
Hi guys,
we're working on a project with 800xA v6.0.3.2 (two redundant ASCS and OWS on a workgroup). We have a problem with alarm generation from FB AlarmCondBasic. So, when we make a first initial download after power-up, AlarmCondBasic gives us the code -30 and of course alarms are not functional. As soon as we make a second controller download, all AlarmCondBasic blocks suddenly are functional. Also if we make a Cold download, alarms again are not functional. As soon as we make a second controller download with minor software changes that are not related to alarms, alarms suddenly work fine. We tried this test with another controller that came fresh from factory (not updated with 6.0.3.2 firmware) and the result is the same.
Anybody knows what's the catch?
Thanks in advance,
Hrvoje
we're working on a project with 800xA v6.0.3.2 (two redundant ASCS and OWS on a workgroup). We have a problem with alarm generation from FB AlarmCondBasic. So, when we make a first initial download after power-up, AlarmCondBasic gives us the code -30 and of course alarms are not functional. As soon as we make a second controller download, all AlarmCondBasic blocks suddenly are functional. Also if we make a Cold download, alarms again are not functional. As soon as we make a second controller download with minor software changes that are not related to alarms, alarms suddenly work fine. We tried this test with another controller that came fresh from factory (not updated with 6.0.3.2 firmware) and the result is the same.
Anybody knows what's the catch?
Thanks in advance,
Hrvoje
Asked 27 days ago
Voted best answer
2
Hello,
I think this problem is caused during the define of the alarm (Start_Code).
Make sure that alarmclass, severity etc. is right during define (Not zero).
For example if the class or severity is written in normal application code and has an initial value of '0' then the first time the alarm will not be defined and give the status -30.
After a second download the alarm is defined in the right way and give a normal status (1-6).
I hope this will help you
I think this problem is caused during the define of the alarm (Start_Code).
Make sure that alarmclass, severity etc. is right during define (Not zero).
For example if the class or severity is written in normal application code and has an initial value of '0' then the first time the alarm will not be defined and give the status -30.
After a second download the alarm is defined in the right way and give a normal status (1-6).
I hope this will help you
Answered 27 days ago
Add new comment