DISTRIBUTED I/O
EN0B-0090GE51 R0802 28
being downloaded from the installation tool and the
installation tool itself. For additional information on service
LED behavior, see Table 19 and Fig. 38.
LONWORKS Service LED L2
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
ONWORKS service button will force a new
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.
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 sec
1
2
3
4
5
6
7
ervice L
D Behavior
2 sec 3 sec 4 sec 5 sec
Time
(at 10 MHz,
approx.)
Power
applied
to node
Continuous
* Does not scale with the Neuron chi
.
Continuous
Continuous
Continuous
Repeated
Repeated*
see table
= ON = OFF
see table
Fig. 38. Service LED behavior
Table 19. 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.
4Anytime
Possible corrupt EEPROM. For a Neuron 3150 Chip-based node, use a newly
programmed PROM, or EEBLANK and follow bring-up procedure.
5Anytime
The module is unconfigured. Connect the Distributed I/O module to the CPU.
The CPU will configure the Distributed I/O module.
First power-up, applicationless
firmware state exported
The OFF duration is approximately 1 second. The service LED should then
turn ON and stay on indicating an applicationless state.
First power-up, unconfigured
firmware state exported
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.
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.