412 Rockwell Automation Publication 1444-UM001D-EN-P - June 2018
Appendix A CIP Objects
DSP (Reported) Status Includes
21 • Source data is the DSP Status DWORD (Assembly Object Status DWORD 3).
• In the event log entry, bytes 8/11 are the previous DSP Status DWORD, bytes 12/15 are the new DSP
Status DWORD.
• The full DWORD is always stored (before/after). Examples of events in this category:
Bit 7 set when the DSP is running from a configuration from its own Flash memory.
Bit 10 set when the DSP has received a different configuration from the NetX, anytime since last
power cycle.
Main Transducer Status
22 • Source data is the first two bytes of the Channel/TX/Speed DWORD (Assembly Object Status DWORD
4).
• In the event log entry, bytes 8/9 are previous status bits 0-15, bytes 10/11 are the new status bits, 0-
15.
• Changes in enable settings, TX OK and Wire OFF Status (where applicable) are captured here.
Speed/Tacho Status
23 • Source data is the third byte of the Channel/TX/Speed DWORD (Assembly Object Status DWORD 4).
• In the event log entry, byte 8 is the previous state and 10 the current.
• Changes in enable settings, Tacho OK and the occurrence of new maximum speeds are captured here.
• When operating in redundant tacho mode, this event is also triggered if a tacho failure activates a
switch in tacho sources.
Relay Status
24 • Source data is the Relay Status DWORD (Assembly Object Status DWORD 21).
• Bits 0 to 12 represent the maximum possible system relay count of 13, a bit set to 1 indicates relay
energized.
• In the event log entry, bytes 8/9 are the previous Relay status bits 0-15, bytes 10/11 are the new Relay
status bits 0-15.
Expansion Module Exceptions
25 • Source data for this is the upper 2-bytes of the AuxR2/Comms Status DWORD (Assembly Object Status
DWORD 6).
• 15 of the 16 bits are actively used, 3 per auxiliary module, see Assembly Object
.
• In the event log entry, bytes 8/9 are the previous exception data, bytes 10/11 are the new exception
data.
• If an auxiliary module is reporting a specific type of communications error, it is reported here.
• The specific error being reported is encoded using the 3-bits.
Calibration Status
26 • Source data is the high byte of the Channel/TX/Speed DWORD (Assembly Object Status DWORD 4).
• Four bits are used there (0 to 3), a bit set indicates that channel has a calibration failure.
• In the event log entry, byte 8 is the previous state and 10 the current.
NV Configuration Bad
28 • Configuration data is stored in NetX Flash (NV) together with a 32-bit CRC.
• On recall of configuration data from Flash, the CRC is recalculated and compared.
• A mismatch of the two CRC prompts a recoverable critical error condition and this event is generated.
• The DSP is not reconfigured by the NetX, but continues to use the configuration data stored in its own
Flash.
• The DSP status reflects this (bit 7 & summary fault bit set) but this is not immediately seen in the
event log (no change/start-up).
IP Addressing
30…33 • 30 - Network Address Configuration: Dynamic (e.g. DHCP).
• 31 - Network Address Configuration: Static.
• 32 - Network Address Configuration: Read from the HW Switches (returned a valid address or 888).
• 33 - Network Address Configuration: HW Error (the base, address switches were not read correctly at
power cycle / reset).
• Report configuration status at module startup (power cycle / reset).
• Report configuration changes (Dynamic to Static and/or vice versa).
Table 140 - System Event Types (continued)
ID Name Description Bytes 8…15 Application
To Next Page
Loading...
Need help?
General