750-303 - Binar Elektronik

Buscoupler PROFIBUS-DP – 750-303 BRIOS2
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.
Sequence 1
High frequency Pause
Sequence 2
Low frequency Pause
Sequence 3
Low frequency Pause
I/O ERR
Hardware and
configuration error
Error code Error argument
No. of blinks No. of blinks Error description
1
0 EEPROM check sum error / check sum fault in parameter
area of the flash memory.
1 Overflow of the internal buffer memory for the inline code.
2 Unknown data type.
3 Module type of the flash program memory could not be determined
/ is incorrect.
4 Error during writing the flash memory.
5 Error when deleting the flash memory.
6 Changed I/O module configuration found after Autoreset.
7 Invalid firmware.
8 Timeout error serial EPROM.
Additional
configuration error
2
1 Process image is inactive at the switching operation Control
or Monitor mode.
2 Process image is bigger than the available cache.
3 Error by the process image compilation.
Internal bus
command error
3 0 Bus module(s) has (have) identified errors in the internal bus
communication.
Internal bus
data error
4
0 Data error on internal bus or internal bus break at the bus
coupler
n* (n>0) internal bus break after module N, passive modules like supply
terminal blocks do not count.
Register
communication error
Fieldbus specific
error
I/O module
not supported
5 n* Internal bus error during register communication with the I/O
module n.
6 0 Number of I/O modules exceeded. The process image is
bigger than the available cache.
7 n* I/O module not supported at position n.
Not used 8 - Not used
CPU-TRAP-error 9 - Not used
Blink code example:
* 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 diagnostics).
Assume that the 13th I/O module is removed. This will generate the following cyclically displayed blink sequence:
1. The ‘I/O’ LED generates a fault display with the first blink sequence (red, approx. 10 Hz) and then pause.
2. The first pause is followed by the second blink sequence (approx. 1 Hz). The ‘I/O’ LED blinks red four times
and then pause. This indicates the error code 4 meaning an Internal bus data error.
3. The second pause is followed by the third blink sequence (approx. 1 Hz). The ‘I/O’ LED blinks red twelve
times and then pause. The error argument 12 means that the internal bus is interrupted after the 12th I/O
module.
After elimination of the fault, the buscoupler can only be set to the normal working condition by another POWER ON
sequence.
The green I/O RUN LED flashes when accessing the I/O modules internal data channels. After being switched on, the
Buscoupler queries the configuration of the bus modules but does not carry out a data exchange with the I/O modules.
This means that the red I/O ERR LED will extinguish after a faultless startup. The green I/O RUN LED indicates that
data is being exchanged via the internal bus.
Page 4(4)
ver 1.02 eng 2002-09-09
ver 1.01 eng 2001-04-18
Batterivägen 4 • SE-461 38 TROLLHÄTTAN
tel +46 (0)520 47 32 10 • fax +46 (0)520 47 32 10
e-mail: support@binar.se • website: www.binar.se