Diagnostics and troubleshooting
Le
u
ze electronic
MA 255
i
75
TNT
35/7-2
4
V
13
Diagnostics and troubleshooting
If problems should occur during commissioning of the MA 255
i
you can refer to the following
table. Typical errors and their possible causes are described here as well as tips for their
elimination.
13.1
General causes of errors
Error
Possible error cause
Measures
Data loss
(DL bit)
Data telegram longer than the bus
telegram in bus cycle/memory size.
Increase in bus telegram length.
Toggle out data earlier.
Data in the RS 232
instead of in the
buffer
Incorrect order.
Correct order:
Provide data, toggle CTB.
PWR
status LED on the circuit board
Off
No supply voltage connected to the device. Check supply voltage.
Hardware error.
Send the device to customer service.
Green/orange,
flashing
Device in boot mode.
No valid firmware, send device to
customer service.
Continuous orange
light
Device error.
Send the device to customer service.
Firmware update failed.
MNS
LED on the housing (see figure 8.1 on page 34)
Green, flashing
Online, no net connection.
Restart if necessary.
Red, flashing
Timeout connection.
Check address and bus connection.
Red continuous light
Communication error on the DeviceNet: No
communication to controller established
("no data exchange").
Check interface.
Cannot be rectified by a reset.
Send the device to customer service.
Double address.
Check address setting.
PWR
LED on the housing (see figure 8.1 on page 34)
Off
No supply voltage connected to the device. Check supply voltage.
Device not yet recognized by the
DeviceNet.
Send the device to customer service.
Green, flashing
SERVICE active.
Service switch on RUN.
Red, flashing
Incorrect baud rate / address:
Address >64: no communication
Baud rate >4: no communication .
Check switch settings:
Address switch S1, S2,
Baud rate selector switch S3.
Red continuous light Device error.
Send the device to customer service.
Table 13.1:
General causes of errors