Lenze E84Dxxxx - Manual (Page 77)

Communication manual 8400 protec PROFIBUS
Error messages
Possible causes and remedies
77
L
EDS84DPBUS EN 2.0 - 09/2010
Safety communication timeout [0x01bc6610]
Safety parameter timeout [0x01bc6611]
Safety Init error [0x01bc6612]
Profibus watchdog: Monitoring time expired [0x01bc8130]
Profibus: "Data_Exchange" status exited [0x01bc8131]
Response (Lenze setting printed in bold) Setting: not possible
None System fault Fault Trouble Quick stop by trouble : Warning locked Warning Information
Cause Remedy
This is an error message which occurs during each safe
parameter download.
Acknowledge error.
Response (Lenze setting printed in bold) Setting: not possible
None System fault Fault Trouble Quick stop by trouble : Warning locked Warning Information
Cause Remedy
Safety option SO20/SO30 does not respond to a
PROFISafe parameterisation telegram (PRM data) within
a set time interval (200 ms).
Activate safety option SO20/SO30.
Response (Lenze setting printed in bold) Setting: not possible
None System fault Fault Trouble Quick stop by trouble : Warning locked Warning Information
Cause Remedy
• Communication with safety option SO20/SO30 could
not initialised properly.
• The master did define a safety application but a
connection to the safety option has not been
detected internally.
Activate safety option SO20/SO30.
Response (Lenze setting printed in bold) Setting: C13880/1 (; adjustable response)
: None System fault ; Fault Trouble ; Quick stop by trouble ; Warning locked Warning ; Information
Cause Remedy
Permanent interruption of communication to the
PROFIBUS master.
• See also chapter " Permanent interruption of
PROFIBUS communication " ( 64) .
Check cables and terminals.
Response (Lenze setting printed in bold) Setting: C13880/1 (; adjustable response)
: None System fault ; Fault Trouble ; Quick stop by trouble ; Warning locked Warning ; Information
Cause Remedy
Data exchange via PROFIBUS has been stopped.
• See also chapter " Permanent interruption of
PROFIBUS communication " ( 64) .
Check cables and terminals.
The slave must receive new parameterisation and
configuration files from the master for again being able
to exchange data.