Advertisement
DISTRIBUTED I/O
being downloaded from the installation tool and the
installation tool itself. For additional information on service
LED behavior, see Table 19 and Fig. 38.
L
W
Service LED L2
ON
ORKS
This LED is used to diagnose the state of the Distributed I/O
module. In general:
• The module is applicationless if the LED illuminates con-
tinuously.*
• The module has an application but it is not configured if
the LED is blinking.
• The module is running normally if L2 is off.
*Pushing the L
W
service button will force a new
ON
ORKS
commissioning of the module. While commissioning, LED L2
continuously illuminates red for less than 1 minute and then
returns to the normal state (L2 = OFF).
A more detailed diagnosis can be carried out by observing
the duration of the ON and OFF states of the service LED in
connection with power ON / OFF. Fig. 38 illustrates the
different service LED behaviors. These are the most common
behaviors, but others are possible since the state of the
service LED is under firmware control and can be affected
both by hardware and software anomalies.
Behavior
1
Power-up of the node
2
Power-up of the node
3
Power-up / Reset of the node
4
Anytime
5
Anytime
First power-up, applicationless
firmware state exported
First power-up, unconfigured
6
firmware state exported
First power-up, configured
firmware state exported
7
Anytime
EN0B-0090GE51 R0802
Table 19. Service LED behavior descriptions
Context
Bad node hardware. For Distributed I/O modules, perform the tests shown in
the previous section.
Bad node hardware. For Distributed I/O modules, perform the tests shown in
the previous section.
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.
Possible corrupt EEPROM. For a Neuron 3150 Chip-based node, use a newly
programmed PROM, or EEBLANK and follow bring-up procedure.
The module is unconfigured. Connect the Distributed I/O module to the CPU.
The CPU will configure the Distributed I/O module.
The OFF duration is approximately 1 second. The service LED should then
turn ON and stay on indicating an applicationless state.
The OFF duration is 1-15 seconds (depending on the application size and
system clock). The 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.
The OFF duration is indefinite (1-15 seconds to load internal EEPROM; stays
OFF indicating configured state.) The module is configured and running
normally.
The module is configured and running normally.
IMPORTANT
In Table 19, the words "configured", "unconfigured",
"application", and "applicationless" refer only to the
communication layer running on the Neuron® chip and not to
the controller application.
1
2
3
4
5
6
see table
7
1 sec
2 sec
Power
applied
to node
* Does not scale with the Neuron chip.
Fig. 38. Service LED behavior
Likely explanation
28
see table
3 sec
4 sec
5 sec
= ON
= OFF
Continuous
Continuous
Continuous
Repeated
Repeated*
Continuous
Time
(at 10 MHz,
approx.)
Advertisement
