2 powerlink error messages, Powerlink error messages, 9error messages – Lenze E94AYCEC User Manual
Page 61
![background image](/manuals/565769/61/background.png)
Lenze · E94AYCEC Communication module (POWERLINK CN) · Communication Manual · DMS 3.0 EN · 08/2014 · TD17
61
9
Error messages
9.2
POWERLINK error messages
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.2
POWERLINK error messages
• The POWERLINK error messages are displayed via code
/
.
• In order to distinguish between the error responses, the displayed error messages are preceded
with 3 characters:
Response
Meaning
EL_...
Trouble (Fault)
QL_...
Quick stop by trouble
WL_...
Warning locked
I__...
Information (Info)
Error number
Name
Description
hex
dec
0x1
1
EL_ LeaveData
Exchange
The POWERLINK data exchange has been completed (the node
recognises that it does not have the "DataExchange" status
anymore).
Causes & remedy:
• see error description
EPL: DataExchange exited [0x00c88131] ( 58)
Codes:
•
/
(error response)
0x3
3
QL_ LeaveData
Exchange
0x4
4
WL_LeaveData
Exchange
0x6
6
I__LeaveData
Exchange
0x18263 98915
EL_EPL_BOOTUP_1
The Managing Node could not start the POWERLINK network.
OR:
Not all required nodes were found.
Causes & remedy:
• see error description
EPL MN: Network has not been started (bootup-1) [0x00c88263]
Codes:
•
/
(error response)
0x38263 229987
QL_EPL_BOOTUP_1
0x48263 295523
WL_EPL_BOOTUP_1
0x68263 426595
I__EPL_BOOTUP_1
0x18264 98916
EL_EPL_BOOTUP_2
The Managing Node could not transfer all nodes into the
"NMT_CS_OPERATIONAL" status via process data exchange.
Causes & remedy:
• see error description
EPL MN: Not all nodes are in the operational status (bootup-2)
Codes:
•
/
(error response)
0x38264 229988
QL_EPL_BOOTUP_2
0x48264 295524
WL_EPL_BOOTUP_2
0x68264 426596
I__EPL_BOOTUP_2
0x18265 98917
EL_EPL_CN_SYNC_
LOSS
In the Controlled Node, the synchronisation cycle of the Managing
Node has failed. The Controlled Node automatically changes to the
"NMT_xx_PREOPERATIONAL_1" status and waits for a new run-up
by the Managing Node.
Causes & remedy:
• see error description
EPL: Synchronisation lost from MN [0x00c88265] ( 59)
Codes:
•
/
(monitoring threshold)
•
/
(error response)
•
/
(error counter)
0x38265 229989
QL_EPL_CN_SYNC_
LOSS
0x48265 295525
WL_EPL_CN_SYNC_
LOSS
0x68265 426597
I__EPL_CN_SYNC_
LOSS