Rockwell Automation Allen-Bradley ArmorBlock 1732E-IB8M8SOER User Manual page 93

Ethernet/ip dual port 8-point sequence of events input and scheduled output modules
Table of Contents

Advertisement

Table 22 - Produced Assembly Instance 158 Data Structure (Continued)
Consumed
Bit 7
Bit 6
Byte
158...159
Pad (16 Bits)
160...167
Input Time Stamp 8 (64 bit)
168...171
Event Number 8 (32 bit)
172
Event Point 8
173
Reserved (Must be 0)
174...175
Pad (16 Bits)
176...183
Input Time Stamp 9 (64 bit)
184...187
Event Number 9 (32 bit)
188
Event Point 9
189
Reserved (Must be 0)
190...191
Pad (16 Bits)
192...195
Events Queued Count (32 Bits)
196
Reserved (Must be 0)
NewData – Set when new data has been detected upon that input and an unread event is queued for
that point. Cleared when all the time stamps for that point have been acknowledged or if the
corresponding NewDataAck bit transitions from 0...1.
EventOv – Set when the module begins to lose events for that input point. Events may be lost when new
events are either ignored or overwriting existing events which have yet to be acknowledged. Cleared
when the corresponding NewDataAck bit transitions from 0...1.
EventNumber – Running count of events which increments by one each new event. Allows controller to
check for a new event by comparing this number to the last retrieved event. Acknowledge of receipt of
event which causes next event to display is to write this EventNumber back into the output data EventAck
field. If the EventNumber reaches it maximum value and rolls over it should roll-over to 1 not 0.
Input Time Stamp – Timestamp corresponding to when an event was recorded at one of the modules
inputs.
Local Clock Offset – The offset from the local clock to the system time. This value is useful for detecting
steps in time. This value will update when a PTP update is received.
Where:
Offset Time Stamp – The time when the PTP message was received that caused the Local Clock Offset
to update. This value will initially be zero and the first timestamp will occur when the module
synchronizes with the master clock.
Grandmaster Clock ID – The ID number of the Grandmaster clock the module is synchronized to.
EventPoint – Which of the 8 channels the event was recorded on (values of 0...7).
EventData – Bit indicating if event was a change of state to a 1 or 0.
EventsQueuedCount – How many events are currently queued up which have not been read.
Synced to Master – 1 indicates the module is synchronized with a master clock. 0 indicates it is not.
In order to acknowledge receipt of an event the user must write this EventNumber back into the output
data EventAck field. The EventAck is in consumed assembly 159. When the users returns the EventAck,
then ack all time stamps in this assembly that are less than or equal to the EventAck.
Time stamps will be zero at power-up and after a time stamp is acknowledged. The time base and epoch
of the timestamps are determined by the grand-master clock of the system.
All data listed in this assembly is in Little Endian format, LSB first, in increasing byte order to MSByte last.
Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Bit 5
Bit 4
Bit 3
Appendix B
Data Tables
Bit 2
Bit 1
Bit 0
EventData8
Synched to
Master
93

Advertisement

Table of Contents
loading

This manual is also suitable for:

Allen-bradley armorblock 1732e-ob8m8sr

Table of Contents