DISTRIBUTED I/O
EN0B-0090
28
Table 16. Service LED behavior descriptions.
Behavior
Context
Likely Explanation
1
Power-up of the node
Bad node hardware. For Distributed I/O modules, perform the tests shown in
the previous section.
2
Power-up of the node
Bad node hardware. For Distributed I/O modules, perform the tests shown in
the previous section.
3
Power-up / Reset of the node
The module is applicationless. May be caused by the Neuron chip firmware
when a mismatch occurs on application checksums. This behavior is normal if
the application was exported to come up
applicationless
.
4
Anytime
Possible corrupt EEPROM. For a Neuron 3150 Chip-based node, use a newly
programmed PROM, or EEBLANK and follow bring-up procedure.
5
Anytime
The module is unconfigured.
Connect the Distributed I/O module to the CPU. The CPU will configure the
Distributed I/O module.
6
First power-up,
Applicationless
firmware state exported
The OFF duration is approximately 1 second. Service LED should then turn
ON and stay on indicating an applicationless state.
6
First power-up,
Unconfigured
firmware state exported
The OFF duration is 1-15 seconds depending on the application size and
system clock. Service LED should then begin flashing as in behavior 5,
indicating an unconfigured state.
Connect the Distributed I/O module to the CPU. The CPU will configure the
Distributed I/O module.
6
First power-up,
Configured
firmware state exported
The OFF duration is indefinite (1-15 seconds to load internal EEPROM; stays
OFF indicating configured state.) The module is configured and running
normally.
7
Anytime
The module is configured and running normally.
