V0N_hydro
Member
I want to keep wallclocktime roughly the same on 5 different controllers using factory talk alarms and events so the timestamps in the alarm log and alarm history are in the correct order.
The programs also need to know how long it has been since the last time the logic was executed for integral and derivative calculations which include delta t.
I am reading https://literature.rockwellautomation.com/idc/groups/literature/documents/at/ia-at003_-en-p.pdf and it sounds like the free running counter for PID loop changes in time could be the CST clock.
I am getting confused because the document also talks about keeping CST in sync within the backplane. Can anyone confirm that when there are multiple CPUs or modules in the same backplane or chassis that CST would actually slew within some of those modules to keep in sync with the chassis master, and that in my case where all of the controllers are in different chassis the CST in each chassis will never slew or step change to keep in sync with other CPUs but the wallclock time can be kept in sync by "enabling time synchronization"
Here are some relevant bits from the PDF about CST.
"Coordinated System Time (CST): A backplane clock propagated between all modules on the ControlLogix backplane.
Relevance to real world time is basically the difference between the Logix backplane time standard, which starts counting when power is applied to the CST Master in microseconds from January 1st, 1970, and time in the real world. The time relevant to the real-world time means building a correlation between the Logix backplane CST (which cannot be programmatically or externally influenced in anyway) and the real world clock (UTC).
CST enabled devices in a ControlLogix backplane synchronize their local clocks by using the CST protocol. Both CST and the PTP protocol are operational in a ControlLogix backplane. CST is used to synchronize the clocks to CST time and PTP is used to synchronize the clocks to System Time.System Time and CST time are related by System Time = CST time + offsetwhere offset is the Wall Clock Time (WCT) object CstOffset.On powerup, a CST Master, such as a 1756-L6x or 1756-L7x ControlLogix controller, or a 1756-ENxTx communication module, sends out a CST sync message that causes all CST Slave modules in the chassis to synchronize to the Master’s current CST. CST is zero at powerup and then continually increases. Every 4 ms CST update messages are sent out to slowly ramp the modules drift to keep it matched to the Master’s CST.
System Time: The absolute time value as defined by CIP Sync in the context of a distributed time system where all devices have a local clock that is synchronized with a common Master clock. System Time is a 64-bit integer value in units of nanoseconds or microseconds with a value of 0 corresponding to an epoch of January 1, 1970
Wall Clock Time (WCT): The controllers’ real-world time is represented as Wall Clock Time, which is the time the controller gets from the Grandmaster. For example, the controller WCT is used as the time source for the Alarm and Events instruction, better know as System Time.
Coordinated System Time (CST)CST is a backplane clock propagated between all modules on the ControlLogix backplane. Its presence is necessary whenever CST time coordination between modules in the chassis is required. This includes the following systems:•CIP Sync•SERCOS Motion•Integrated Motion on the EtherNet/IP network•Safety•SynchLink•RSLogix 5000 software, version 17 and earlier, SOE systems, for example, coordinated time based outputs, including MAOC operations, and synchronized analog scansCST is a free running clock with microsecond resolution that starts up when power is applied to the chassis.
System TimeThis clock is based on UTC (Coordinated Universal Time). It provides a time reference independent of time zone and daylight savings time settings. You use this, for example, these types of systems:•CIP Motion•CIP Sync•Sequence of Events, RSLogix 5000 software, version 18 and later•Scheduled OutputSystem Time relies on a combination of CST and CIP Sync to assure proper delivery through the rack. Additionally, it can be transported via Ethernet bridge modules to other devices that are on the EtherNet/IP network. It is the preferred clock to perform time stamps of events and is ultimately used to synchronize Integrated Motion on the EtherNet/IP network drives."
The programs also need to know how long it has been since the last time the logic was executed for integral and derivative calculations which include delta t.
I am reading https://literature.rockwellautomation.com/idc/groups/literature/documents/at/ia-at003_-en-p.pdf and it sounds like the free running counter for PID loop changes in time could be the CST clock.
I am getting confused because the document also talks about keeping CST in sync within the backplane. Can anyone confirm that when there are multiple CPUs or modules in the same backplane or chassis that CST would actually slew within some of those modules to keep in sync with the chassis master, and that in my case where all of the controllers are in different chassis the CST in each chassis will never slew or step change to keep in sync with other CPUs but the wallclock time can be kept in sync by "enabling time synchronization"
Here are some relevant bits from the PDF about CST.
"Coordinated System Time (CST): A backplane clock propagated between all modules on the ControlLogix backplane.
Relevance to real world time is basically the difference between the Logix backplane time standard, which starts counting when power is applied to the CST Master in microseconds from January 1st, 1970, and time in the real world. The time relevant to the real-world time means building a correlation between the Logix backplane CST (which cannot be programmatically or externally influenced in anyway) and the real world clock (UTC).
CST enabled devices in a ControlLogix backplane synchronize their local clocks by using the CST protocol. Both CST and the PTP protocol are operational in a ControlLogix backplane. CST is used to synchronize the clocks to CST time and PTP is used to synchronize the clocks to System Time.System Time and CST time are related by System Time = CST time + offsetwhere offset is the Wall Clock Time (WCT) object CstOffset.On powerup, a CST Master, such as a 1756-L6x or 1756-L7x ControlLogix controller, or a 1756-ENxTx communication module, sends out a CST sync message that causes all CST Slave modules in the chassis to synchronize to the Master’s current CST. CST is zero at powerup and then continually increases. Every 4 ms CST update messages are sent out to slowly ramp the modules drift to keep it matched to the Master’s CST.
System Time: The absolute time value as defined by CIP Sync in the context of a distributed time system where all devices have a local clock that is synchronized with a common Master clock. System Time is a 64-bit integer value in units of nanoseconds or microseconds with a value of 0 corresponding to an epoch of January 1, 1970
Wall Clock Time (WCT): The controllers’ real-world time is represented as Wall Clock Time, which is the time the controller gets from the Grandmaster. For example, the controller WCT is used as the time source for the Alarm and Events instruction, better know as System Time.
Coordinated System Time (CST)CST is a backplane clock propagated between all modules on the ControlLogix backplane. Its presence is necessary whenever CST time coordination between modules in the chassis is required. This includes the following systems:•CIP Sync•SERCOS Motion•Integrated Motion on the EtherNet/IP network•Safety•SynchLink•RSLogix 5000 software, version 17 and earlier, SOE systems, for example, coordinated time based outputs, including MAOC operations, and synchronized analog scansCST is a free running clock with microsecond resolution that starts up when power is applied to the chassis.
System TimeThis clock is based on UTC (Coordinated Universal Time). It provides a time reference independent of time zone and daylight savings time settings. You use this, for example, these types of systems:•CIP Motion•CIP Sync•Sequence of Events, RSLogix 5000 software, version 18 and later•Scheduled OutputSystem Time relies on a combination of CST and CIP Sync to assure proper delivery through the rack. Additionally, it can be transported via Ethernet bridge modules to other devices that are on the EtherNet/IP network. It is the preferred clock to perform time stamps of events and is ultimately used to synchronize Integrated Motion on the EtherNet/IP network drives."