Behavior - Allen-Bradley 1444-TSCX02-02RB User Manual

The Generalized Event Type Structure is as follows.
Table 139 - Event Data (eEVENT_LOG)
Byte Offset Structure
Within Member
Structure
0 Event Type
1 Event ID
2 Event Time
Seconds
6 Event Time
Subsecond
8...15 Event Specific
Information

Behavior

Events that are stored in the log fall in to one of these types: SYSTEM (0x01),
ALARM (0x02), BUFFER (0x03).
Each has a common header, followed by 8 bytes that are specific to the type.
Many events (such as startup) are self-explanatory 'change events' and have no
additional data that is provided in the event-specific information bytes.
Change Events
Change events are logged when there is a detected change in the status content
and are not triggered directly by the actual state ('good or bad').
Table 140 - System Event Types
ID Name
01 NetX start-up
02 Transitioned to Program
Mode
03 Configuration Count
update
04 Transitioned to Run mode
05 Switch to Out Of Box
Configuration
06 I/O connection opened
07 I/O connection closed
Rockwell Automation Publication 1444-UM001D-EN-P - June 2018
Data Description
Type
BYTE Events fall into one of these types:
• SYSTEM (0x01)
• ALARM (0x02)
• BUFFER (0x03).
BYTE For each Event, Type a range (0 up to a maximum 256) of Event
IDs are defined.
See event-specific definitions.
DWORD Seconds since 1970.
WORD Microseconds.
BYTE Last 8 bytes - See event-specific definitions in behavior section
Description
The communication processor has
reset/restarted
Configuration activity is underway
A configuration activity has
successfully completed
Configuration activity is complete
An instruction to switch the Out of Box
mode is being processed (reset type 1/
2)
Forward open for an I/O connection
received
Forward close for an I/O connection
received or connection lost
CIP Objects Appendix A
Bytes 8...15 Application
No data bytes are used
No data bytes are used
Bytes 10/11 indicate the new
count
No data bytes are used
No data bytes are used
No data bytes are used
No data bytes are used
409