Leuze electronic GmbH + Co. KG
MA 238
i
54
13
Diagnostics and troubleshooting
If problems should occur during commissioning of the MA 238
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
13.2 Interface errors
Error
Possible error cause
Measures
No data to the PLC
Device setting incorrect.
Adjust device settings (data protocol,
baud rate, etc.).
No data sporadically
and/or the device "stalls" Problems with the voltage supply.
Check voltage range, supply sepa
-
rately if needed.
Data loss
(DL bit)
Data telegram longer than the bus tele
-
gram 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 device to customer service.
Green / orange, flashing Device in boot mode.
No valid firmware, send device to cus
-
tomer service.
Orange, continuous light Device error.
Send device to customer service.
Firmware update failed.
STATUS LED on the housing (see figure 5.1 on page 17)
Red, continuous light
Configuration error.
Check interface.
PWR LED on the housing (see figure 5.1 on page 17)
Off
No supply voltage connected to the
device.
Check supply voltage.
Green, flashing
SERVICE active.
Service switch on RUN.
Red, flashing
Incorrect baud rate / address.
Check switch settings.
Check baud rate or address.
Red, continuous light
Device error.
Send device to customer service.
L /A LEDs on the housing (see figure 5.1 on page 17)
Off
No connection.
Check wiring/IP address.
Table 13.1:
General causes of errors
Error
Possible error cause
Measures
No communication via
EtherCAT interface
STATUS LED, continu
-
ous red light
Incorrect wiring.
Check wiring.
Different protocol settings.
Check protocol settings.
Protocol not released.
Activate TCP/IP or UDP.
Sporadic errors at the
EtherCAT interface
Incorrect wiring.
Check wiring.
In particular, check wire shielding.
Check the cable used.
Effects due to EMC.
Check shielding (shield covering in
place up to the clamping point).
Check grounding concept and connec
-
tion to functional earth (FE).
Avoid EMC coupling caused by power
cables laid parallel to device lines.
Overall network expansion exceeded. Check max. network expansion as a
function of the max. cable lengths.
Figure 13.1: Interface error
