device manual AS-i DP - Gateway
T10
Timeout on master mode
Unsuccessful change of the master into another operating mode, e.g. “Projection Mode”, “Protected Mode”.
Possible cause:
During change into the “Protected Mode” the master has detected a slave 0 and can thus not
change into this operating mode.
T11
Timeout MUX actualisation
A timeout was found during the update of the MUX fields, e.g.: analogue values slaves 1..31.
Possible causes:
Parts of the operating system have been overwritten by the plc.
Interference on the 24V power supply cable.
Rectification:
Use a switched-mode power supply to supply the
device.
6.1.5 Boot error (code B00...
B08)
B00
Controller boot error
After the device has been switched on, an error was found during initialization of the individual device
components.
For further details we refer you to the error list.
B01
master initalization
B02
master2 initalization
Unsuccessful initialization of the master.
Possible causes:
Unacceptable interference on the 24V power supply.
Unacceptable interference on the AS-i power supply.
Unacceptably high electrostatic charges and
electromagnetic fields in close proximity of the device.
Rectification:
Grounding of the device via the DIN rail, connection of the FE terminal to the plant ground.
Use a switched-mode power supply to supply the device.
B03
General FAT failure
An error was found in the data field of the FAT, “File Allocation Table”.
For further details we refer you to the error list.
B04
Only one master detected
The operating system could only detect one master in the system although it should be possible to address two
masters in the device.
Possible cause:
Defective hardware
B05
Two master detected
The operating system could detect two masters in the system although it should be possible to address only one
master in the device.
Possible cause:
Defective hardware
B06
Fieldbus type not expected
During automatic detection of the integrated field bus no released field bus module could be detected.
Possible cause:
Defective hardware
B07
Number of master mismatch
During inquiry about the version releases of the masters some invalid information was received.
Possible cause:
Defective hardware
6-37
