Profinet: ip address error [0x01bc6533, Profinet: stack init error [0x01bc6534, Profinet: safety communication timeout [0x01bc6610 – Lenze E84DxxxxxxxxxR User Manual

Page 65: Profinet: safety parameter timeout [0x01bc6611, Profinet: safety init error [0x01bc6612, 0x01bc6533, 0x01bc6610, 0x01bc6612, 0x01bc6611, 0x01bc6534

Advertising
background image

EDS84DPNET EN 4.0 - 11/2010

L

65

Communication manual 8400 protec PROFINET

Error messages

Possible causes and remedies

PROFINET: IP address error [0x01bc6533]

PROFINET: Stack init error [0x01bc6534]

PROFINET: Safety communication timeout [0x01bc6610]

PROFINET: Safety parameter timeout [0x01bc6611]

PROFINET: Safety init error [0x01bc6612]

Response (Lenze setting in bold)

Setting: not possible

…

None … System fault : Fault … Trouble … Quick stop by trouble … Warning locked … Warning … Information

Cause

Remedy

An invalid IP address has been assigned by the IO

controller via PROFINET or has been set in code

C13000

.

• Make sure that the IO controller has assigned a valid

IP address via PROFINET.

• Set a valid IP address.



Setting the IP configuration ( 27)

Response (Lenze setting in bold)

Setting: not possible

…

None … System fault : Fault … Trouble … Quick stop by trouble … Warning locked … Warning … Information

Cause

Remedy

The stack cannot be initialised with the parameters

selected by the user. This may be due to a station name

which does not comply with the PROFINET specification.

Check and, if necessary, adapt PROFINET parameters:



Setting the IP configuration ( 27)



Setting the station name ( 25)

Response (Lenze setting 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 occurring during every safe

parameter download.

Reset error.

Response (Lenze setting in bold)

Setting: not possible

…

None … System fault … Fault … Trouble … Quick stop by trouble : Warning locked … Warning … Information

Cause

Remedy

The SO20/SO30 safety option does not respond to a

PROFISafe parameterisation telegram (PRM data) within

a given time interval (200 ms).

Activate the SO20/SO30 safety option.

Response (Lenze setting in bold)

Setting: not possible

…

None … System fault … Fault … Trouble … Quick stop by trouble : Warning locked … Warning … Information

Cause

Remedy

• Communication with the SO20/SO30 safety option

could not be initialised correctly.

• The IO controller has defined a safety application,

however, no connection to the safety option was

recognised internally.

Activate the SO20/SO30 safety option.

Advertising