Rockwell Automation Publication 1444-UM001D-EN-P - June 2018 499
CIP Objects Appendix A
If the main module is not configured to expect a particular auxiliary module,
then the status of that module is always reported as zero. This status applies
equally to the status data obtained via an object attribute request and to the
status data in the I/O data exchange. Object attribute requests for data such as
Auxiliary module firmware revision only require that the auxiliary module is
present and communicating.
In the unlikely event the auxiliary module is found to be in Boot Loader mode
(not running operation firmware), the main module sets the auxiliary module
status to a special code: Decimal: 65,534, Hexadecimal: 0xFFFE, Binary:
11111111 11111110.
Although the auxiliary module is responding, it is in a non-operational state
and is classed as a failure from the perspective of a Fault Relay.
Relay Status Decoding
The relay status uses two bits to communicate whether the relay is assigned (or
off ) and whether it is energized or not:
•bit 0 - assigned
• bit 1 - energized
Examples of expected values:
• value 0 - Off and de-energized
• value 1 - assigned and de-energized
• value 3 - assigned and energized
Bit Description
8 Relay 0 Is Not Inhibited
9 Relay 1 Is Not Inhibited
10 Relay 2 Is Not Inhibited
11 Relay 3 Is Not Inhibited
12 Relay 0 Drive Error
13 Relay 1 Drive Error
14 Relay 2 Drive Error
15 Relay 3 Drive Error
To Next Page
Loading...
Need help?
General