Regarding to my previous question
Regarding your answers, we are using 800xa system with AC 800M controllers.I checked those settings that you have mentioned.
Regarding your third part answer, I must say yes time backwarded in the entire control system and HMI.
Kindly check the screenshots which i have inserted below I hope these screenshots will help you.
Best Regards.
Voted best answer
It may be so that the "alarm" you are seeing is in fact a simple event, just right click and select Event Details... an alarm should have "Process Condition Event". If you see "Process Simple Event", its just an event. The Control Builder M Alarm Conditions function is very good can view any alarm in the AC 800M, if you cannot find any alarm (CondState = 3, 4, 5) your controller does not send any alarm.
If the Alarm Conditions function finds your alarm but with CondState=0 (disabled/error) there are a couple of reasons why:
a) alarm is disabled by intent => check your logic setting
b) alarm is disabled due to parameter error => check parameters
Example of incorrect settings are Class=0, Severity=0, too long name, name with illegal characters. Please check the System Event List when you download to the controller. If you see "AlmDefErr" you have a parameter error.
Suggest speaking with the vendor of the library you are using.
About time sync; the screen shot from Control Builder M is only one small part of the settings. The dialog should not be empty like the one you sent images of. Try turning off Windows Firewall (or make exclusion for the ControlBuilderPro.exe) that fail to read the clock sync status out of the AC 800M; I need to know what your intentions are and what settings you have made. Please study chapter 7 of the Network Configuration User's Guide, 3BSE034463-510. Then return with more details.
The below image display a control network where 172.16.80.102 is SNTP slave to external reference 172.16.4.254 and in turn CNCP master for the remainder of the control network (which act CNCP slaves). Controller 111 and 120 have some issue (TQ=0) and should be investigated. The other slaving controllers have a TQ>2 which indicate they are in sync; higher number = better accuracy. The controller log of 102 will tell if external SNTP master is OK or not (AC 800M require the external reference to have a Stratum>0, or else it will report & ignore it). The rest of the system should have AfwTime = ON and W32Time = OFF, then AfwTimeService running in the AC 800M connectivity servers only. Any external node, e.g. a Domain Controller must run W32Time service in client mode only and point to, e.g. the connectivity server of AC 800M (which then must have W32Time running in server mode only). There are many more variants - but be careful not defining more than one (>1) client protocol per computer which may lead to oscillation and jitter.
Add new comment