Fieldbus coupler/controller |
• 25 |
Fieldbus coupler 750-319 |
|
|
|
3.1.7 LED display
The coupler possesses several LEDs for on site display of the coupler operating status or the complete node.
LonWorks |
01 |
02 |
|
|
|
A |
|
C |
|
|
|
C |
|
|
|
|
A |
|
|
SERVICE |
B |
D |
|
|
|
|
|
|
|
STATUS |
24V |
0V |
|
|
ICOM |
|
|
|
|
I/O |
+ |
+ |
|
|
|
|
|
||
Fig. 3-6: |
Display elements 750-319 |
g031902x |
||
A differentiation between two LED groups is made.
The first group = fieldbus contains the solid color LEDs having the designation SERVICE (green), STATUS (red) und ICOM (green) indicating the operating status of the communication via LON.
The second group = internal bus consists of the three-color I/O LED (red/green/orange). This LED is used to display the status of the internal bus and software exception handling, i. e. the status of the fieldbus node.
LEDs located on the right-hand side in the coupler power supply section show the status of the supply voltage.
3.1.7.1 Blink code
Detailed fault messages are displayed with the aid of a blink code. A fault is cyclically displayed with up to 3 blink sequences.
•The first blink sequence (approx. 10 Hz) starts the fault display.
•The second blink sequence (approx. 1 Hz) following a pause. The number of blink pulses indicates the fault code.
•The third blink sequence (approx. 1 Hz) follows after a further pause. The number of blink pulses indicates the fault argument.
Modular I/O System
LONWORKS®
26 • Fieldbus coupler/controller Fieldbus coupler 750-319
3.1.7.2 Fieldbus status
The operating status of the communication via LON is signalled via the top LED group (SERVICE, STATUS and ICOM).
The SERVICE LED is directly connected to the Service Pin of the Neuron Chip and indicates the state of the Neuron-C application.
SERVICE- |
Meaning |
Trouble shooting |
LED |
|
|
green |
Configuration successfully completed. |
|
(lights up for |
Adress assigned and Neuron-C application is |
|
half a second |
active. |
|
and then |
|
|
remains off) |
|
|
green blinks |
No configuration, |
Press the Service-Pin of the coupler and check |
(1 second on, |
no addressing of the Network Management |
the Neuron-C application. |
1 second off) |
Tool (domain, subnet, node), Neuron-C |
|
|
application is not activated yet. |
|
green blinks |
No Neuron-C application loaded on the |
Load the Neuron-C application from your net- |
(1 second on, |
node. |
work management tool software into the node. |
2 seconds off |
|
|
then remains |
|
|
on) |
|
|
green blinks |
Watchdog Timer, |
Check the Neuron-C application, if necessary |
cyclically |
Neuron-C application error |
restart the application. |
The STATUS LED indicates that a coupler is activated. This is the case when a wink task is sent and when the communication of both network manager and DPRAM interface fails.
STATUS- |
Meaning |
Trouble shouting |
LED |
|
|
red blinks |
5 times within the WINK task |
|
(0,5 Hz) |
(fault messages basically have a greater priority |
|
|
than the WINK task. |
|
red blinks |
DPRAM interface communication fault (has |
Reset fieldbus coupler hardware by switching off |
(2 Hz) |
priority) |
the supply voltage of the coupler for about 3 |
|
|
seconds. |
|
|
Change the fieldbus coupler if necessary. |
The ICOM-LED indicates a communication and data exchange between Neuron® Chip and µC165.
ICOM-LED |
Meaning |
Trouble shooting |
green |
Data exchange |
|
off |
No data exchange |
Check bus system integrity |
Modular I/O System
LONWORKS®
|
|
|
Fieldbus coupler/controller • 27 |
|
|
|
Fieldbus coupler 750-319 |
|
|
|
|
3.1.7.3 Node status |
|
|
|
|
|
|
|
|
LED |
Color |
Meaning |
|
IO |
red /green |
The 'I/O' LED indicates the node operation and signals faults occur- |
|
|
/ orange |
ring. |
|
|
|
|
The coupler starts after switching on the supply voltage. The "I/O" LED flashes red. Following an error free start up the "I/O" LED changes to green steady light.
In the case of a fault the "I/O" LED continues blinking red. The fault is cyclically displayed with the blink code.
Fig. 3-7: Signalling the LED's node status |
g012111e |
After overcoming a fault, restart the coupler by cycling the power.
I/O-LED |
Meaning |
Trouble shooting |
|
green |
Data cycle on the internal bus |
|
|
off |
No data cycle on the internal bus |
|
|
red |
Coupler hardware defective |
Change the coupler |
|
red |
a) When starting: internal bus is initialized |
Evaluate the fault signal |
(fault code |
blinks |
b) During operation: general internal bus fault |
and fault argument) |
|
red |
Fault message during internal bus reset and |
Evaluate the fault signal |
(fault code |
blinks cyclically |
internal fault. |
and fault argument) |
|
Modular I/O System
LONWORKS®
28 • Fieldbus coupler/controller Fieldbus coupler 750-319
3.1.7.4 Fault message via the blink code of the I/O LED
Fault argument |
Fault description |
|
Trouble shooting |
|
Fault code 1: Hardware and configuration fault |
|
|
|
|
0 |
EEPROM check sum fault / check sum |
|
Change the fieldbus coupler |
|
|
fault in parameter area of the flash |
|
|
|
|
memory |
|
|
|
1 |
Overflow of the internal buffer memory |
|
Change the fieldbus coupler |
|
|
for the inline code |
|
|
|
2 |
Unknown data type |
|
Change the fieldbus coupler |
|
3 |
Module type of the flash program |
|
Change the fieldbus coupler |
|
|
memory could not be determined / is |
|
|
|
|
incorrect |
|
|
|
4 |
Fault during writing in the flash mem- |
|
Change the fieldbus coupler |
|
|
ory |
|
|
|
5 |
Fault when deleting the FLASH mem- |
|
Change the fieldbus coupler |
|
|
ory |
|
|
|
6 |
Changed I/O module configuration |
|
Change the fieldbus coupler |
|
|
found after AUTORESET |
|
|
|
Fault code 2: Fault in programmed configuration |
|
|
|
|
n* (n<0, n>65) |
Incorrect table entry |
|
Change the entry in the configuration for |
|
|
|
|
I/O module n. |
|
Fault code 3: Internal bus command fault |
|
|
|
|
0 |
I/O module(s) has (have) identified |
|
Determine where the module bus has been |
|
|
internal bus command as incorrect. |
|
interrupted by removing the fieldbus cable. |
|
|
|
|
Plug the end module in the middle of the |
|
|
|
|
node. Switch the coupler off and on again. |
|
|
|
|
If the I/O LED keeps blinking, displace the |
|
|
|
|
end module anew. If there is only one |
|
|
|
|
module left which is connected to the |
|
|
|
|
coupler and if the I/O LED lights up, either |
|
|
|
|
the module or the coupler is defective. |
|
|
|
|
Change the defective component. |
|
Fault code 4: Internal bus data fault |
|
|
|
|
n* (n<0, n>65) |
Interruption after the nth module |
|
Replace the nth module within the node |
|
Fault code 5: Register communication fault |
|
|
|
|
n* (n<0, n>65) |
Module bus fault during register com- |
|
Replace the nth module within the node |
|
|
munication |
|
|
|
Fault code 6: Fieldbus specific fault |
|
|
|
|
0 |
Fault code 6 is not implemented |
|
|
|
Fault code 7: I/O module not supported |
|
|
|
|
n* |
I/O module not supported at position n |
|
|
|
Fault code 8: unused |
|
|
|
|
0 |
Fault code 8 is not used. |
|
|
|
Fault code 9: CPU TRAP error |
|
|
|
|
1 |
Illegal Opcode |
|
|
|
2 |
Stack overflow |
|
|
|
3 |
Stack underflow |
|
|
|
4NMI
* The number of blink pulses (n) indicates the position of the I/O module. I/O modules without data are not counted (i.e. supply module without diagnosis)
Example: the 13th I/O module is removed.
1.The "I/O" LED generates a fault display with the first blink sequence (approx. 10 Hz).
2.The first pause is followed by the second blink sequence (approx. 1 Hz). The "I/O" LED blinks four times and thus signals the fault code 4 (internal bus data fault).
3.The third blink sequence follows the second pause. The "I/O" LED blinks twelve times. The fault argument 12 means that the internal bus is interrupted after the 12th I/O module.
Modular I/O System
LONWORKS®