
6 Buscoupler startup and troubleshooting
After configuration of the master connection and electrical installation of the fieldbus node/station, operation of the system can begin.
After power to the Buscoupler and I/O modules has been applied, the Buscoupler verifies all internal functions, components and the communication interface by an internal diagnostic routine. Then the function modules and the existing configuration is determined. At the same time a hidden file is stored. It consists of an input and an output area which is located on the fieldbus RAM of the log chip. During the power up phase the ‘I/O ERR’ LED flashes with an increased frequency. After a faultless power up the fieldbus coupler enters the state ‘fieldbus start’. The green LED ‘RUN’ indicates that the Bus is operating normally.
In case of a fault the red ‘I/O ERR’ LED will continue flashing.
By counting the number and frequency of flashes the fault can be easily identified quickly and accurately. A varying number of flashes and frequencies defines the fault. The table below describes the fault condition based on the counted number of ‘I/O ERR’ LED flashes,2.581(55
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| VHTXHQFH |
| 3DXVH |
|
|
| VHTXHQFH |
| 3DXVH |
| VHTXHQFH |
|
|
| |||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
2.Blinking sequence error code
1
2
3
4
4
5
6
3.Blinking sequence error argument
0
1
2
0
N (N>0)
0
0
N(N>0)
N
description
overflow of internal buffer for inline code
unknown data type
error in programmed process image
error in comparison of tables: module N (programmed configuration), passive modules like supply terminal blocks do not count
modules have identified error in fieldbus commands
data error on fieldbus or fieldbus break at the coupler
fieldbus break after module N
filedbus error in register communications with module N
error in
0 | too lillte configuration data |
N (0<N<65) | error in 1st configuration byte |
Table 5: Diagnosis LEDs - on buscoupler
INTERBUS S / Startup | 23 |
:$*2Ç,2Ç6<67(0