Rockwell Automation Publication 1444-UM001D-EN-P - June 2018 409
CIP Objects Appendix A
The Generalized Event Type Structure is as follows.
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 139 - Event Data (eEVENT_LOG)
Byte Offset
Within
Structure
Structure
Member
Data
Type
Description
0 Event Type BYTE Events fall into one of these types:
• SYSTEM (0x01)
•ALARM (0x02)
• BUFFER (0x03).
1 Event ID BYTE For each Event, Type a range (0 up to a maximum 256) of Event
IDs are defined.
See event-specific definitions.
2Event Time
Seconds
DWORD Seconds since 1970.
6Event Time
Subsecond
WORD Microseconds.
8...15 Event Specific
Information
BYTE Last 8 bytes - See event-specific definitions in behavior section
Table 140 - System Event Types
ID Name Description Bytes 8…15 Application
01 NetX start-up The communication processor has
reset/restarted
No data bytes are used
02 Transitioned to Program
Mode
Configuration activity is underway No data bytes are used
03 Configuration Count
update
A configuration activity has
successfully completed
Bytes 10/11 indicate the new
count
04 Transitioned to Run mode Configuration activity is complete No data bytes are used
05 Switch to Out Of Box
Configuration
An instruction to switch the Out of Box
mode is being processed (reset type 1/
2)
No data bytes are used
06 I/O connection opened Forward open for an I/O connection
received
No data bytes are used
07 I/O connection closed Forward close for an I/O connection
received or connection lost
No data bytes are used
To Next Page
Loading...
Need help?
General