Fault 67 Safe communication

Fault: 67.10 (430Ahex | 17162dec)

Description: Fault in the SafeCom control byte

 

Response: FS – warning

Cause

Measure

Fault detected in the communication network of SEW-EURODRIVE. Safe communication nodes not configured correctly.

– Make sure that the same safety protocol has been set in fieldbus master and fieldbus slave.

– Make sure that the communication channel between fieldbus master and fieldbus slave has been configured correctly.

Fault: 67.20 (4314hex | 17172dec)

Description: Safety protocol system fault

 

Response: FS – system fault

Cause

Measure

Safety protocol signaled system fault.

– Acknowledge the fault.

– Restart safe communication.

– If the fault occurs again, switch the device off and on again.

– If the fault occurs repeatedly, contact SEW‑EURODRIVE Service.

Fault: 67.21 (4315hex | 17173dec)

Description: Safety protocol warning

 

Response: FS – warning

Cause

Measure

Safety protocol has signaled a warning.

– Acknowledge the warning.

– Restart safe communication.

– If the warning occurs again, switch the device off and on again.

– If the warning occurs repeatedly, contact SEW‑EURODRIVE Service.

Fault: 67.22 (4316hex | 17174dec)

Description: Faulty configuration of process data lengths

 

Response: FS – warning

Cause

Measure

Configured process data lengths of safety protocol in fieldbus master do not match expected lengths.

– Check the configuration of the communication parameters of the safety card.

– Acknowledge the warning.

– Restart safe communication.

– If the warning occurs again, switch the device off and on again.

– If the warning occurs repeatedly, contact SEW‑EURODRIVE Service.

Fault: 67.23 (4317hex | 17175dec)

Description: Configuration fault

 

Response: FS – system fault

Cause

Measure

Fault in configuration of safety protocol.

– Check the configuration of the communication parameters of the safety card.

– Acknowledge the warning.

– Restart safe communication.

– If the warning occurs again, switch the device off and on again.

– If the warning occurs repeatedly, contact SEW‑EURODRIVE Service.

Fault: 67.24 (4318hex | 17176dec)

Description: Cyclic data exchange fault

 

Response: FS – system fault

Cause

Measure

Fault detected in the cyclic data exchange.

– Acknowledge the warning.

– Restart safe communication.

– If the warning occurs again, switch the device off and on again.

– If the warning occurs repeatedly, contact SEW‑EURODRIVE Service.

Fault: 67.26 (431Ahex | 17178dec)

Description: Version fault

 

Response: FS – warning

Cause

Measure

Communication partner version not supported.

– Switch the device off and on again.

– If the fault occurs repeatedly, contact SEW-EURODRIVE Service.

Fault: 67.27 (431Bhex | 17179dec)

Description: Incompatibility fault during communication

 

Response: FS – warning

Cause

Measure

Incompatibility fault/software error detected in one of the communication partners even with correct CRC value of the telegram.

– Switch the device off and on again.

– If the fault occurs repeatedly, contact SEW‑EURODRIVE Service.

Fault: 67.28 (431Chex | 17180dec)

Description: Timeout

 

Response: FS – warning

Cause

Measure

Safety protocol has signaled a timeout.

– Make sure that the communication path is not interrupted (cables, voltages, load).

– Make sure that the communication channel between fieldbus master and fieldbus slave has been configured correctly.

– Make sure that the monitoring times set in the fieldbus master are not too short.

Fault: 67.29 (431Dhex | 17181dec)

Description: F-PI data too short

 

Response: FS – system fault

Cause

Measure

F-profile variant needs more data than has been received.

– Check the parameterization of the safety controller.

– Make sure that the correct F-module of the device description file (GSDML file) has been assigned to the corresponding slot of the hardware configuration.

Fault: 67.30 (431Ehex | 17182dec)

Description: Fault restarting CIP Safety™ communication

 

Response: FS – system fault

Cause

Measure

A fault was detected when restarting the CIP Safety™ communication. Process aborted. The existing data is retained.

– Check parameterization.

– Acknowledge the fault.

– Repeat the process.

Fault: 67.100 (4364hex | 17252dec)

Description: Safety protocol message

 

Response: FS – message

Cause

Measure

Safety protocol has signaled receipt of zero telegram or connection not established correctly.

– Acknowledge the message.

– If the message occurs again, check the communication channel.

Fault: 67.131 (4383hex | 17283dec)

Description: CIP Safety™ configuration started

 

Response: No response

Cause

Measure

The user has activated the CIP Safety™ protocol.

For information only.

Fault: 67.140 (438Chex | 17292dec)

Description: Restart by CIP Safety™

 

Response: FS – message

Cause

Measure

CIP Safety™ has triggered a restart.

For information only.

Fault: 67.141 (438Dhex | 17293dec)

Description: Fault in safety stack control

 

Response: FS – message

Cause

Measure

Fault detected in safety stack control (SSC) process.

For information only.

Fault: 67.142 (438Ehex | 17294dec)

Description: Fault in safety validator connection establishment engine

 

Response: FS – message

Cause

Measure

Fault in SCE in safety open sequence in content of receive data or in transmission of response data.

For information only.

Fault: 67.143 (438Fhex | 17295dec)

Description: Fault in safety validator connection establishment engine

 

Response: FS – message

Cause

Measure

Fault in SCE in safety close sequence in content of receive data or in transmission of response data.

For information only.

Fault: 67.144 (4390hex | 17296dec)

Description: Fault in safety message router object

 

Response: FS – message

Cause

Measure

Fault in SCE while receiving or transmitting an explicit message.

For information only.

Fault: 67.145 (4391hex | 17297dec)

Description: Fault in safety supervisor object

 

Response: FS – message

Cause

Measure

Fault detected in the safety supervisor object (SSO):

– in the communication connection to the fieldbus card

– in the safety open process

– in the Propos Apply TUNID service

For information only.

Fault: 67.146 (4392hex | 17298dec)

Description: Fault in safety validator object

 

Response: FS – message

Cause

Measure

Fault in the safety validator object (SVO) in the content of the I/O data received message.

For information only.

Fault: 67.147 (4393hex | 17299dec)

Description: Fault in safety validator client object

 

Response: FS – message

Cause

Measure

Fault in the safety validator client object (SVC). The TCOO message was received with incorrect ping status.

For information only.

Fault: 67.148 (4394hex | 17300dec)

Description: Fault in safety validator client object

 

Response: FS – message

Cause

Measure

Fault in safety validator client object (SVC) while checking received TCOO message.

For information only.

Fault: 67.149 (4395hex | 17301dec)

Description: Fault in safety validator server object

 

Response: FS – message

Cause

Measure

Fault in safety validator server object (SVS) while checking received message.

For information only.

Fault: 67.150 (4396hex | 17302dec)

Description: Fault in safety validator server object

 

Response: FS – message

Cause

Measure

Fault in safety validator server object (SVS) while checking received message.

For information only.

Fault: 67.151 (4397hex | 17303dec)

Description: Fault in CIP connection path EPATH

 

Response: FS – message

Cause

Measure

Fault analyzing CIP connection path EPATH.

For information only.

Fault: 67.152 (4398hex | 17304dec)

Description: Fault in connection configuration object

 

Response: FS – message

Cause

Measure

Fault detected in connection configuration object (CCO).

For information only.

Fault: 67.153 (4399hex | 17305dec)

Description: Fault writing to safety key

 

Response: FS – message

Cause

Measure

Fault in the SAPL Store KeyMem Data process. Process aborted. The existing data is retained.

For information only.

Fault: 67.154 (439Ahex | 17306dec)

Description: Fault when restarting via MOVISUITE®

 

Response: FS – log

Cause

Measure

Fault detected in the SAPL Reset Ownership process via MOVISUITE®. Process aborted. The existing data is retained.

For information only.

Fault: 67.155 (439Bhex | 17307dec)

Description: Fault in safety validator connection establishment engine TUNID

 

Response: FS – message

Cause

Measure

Fault checking the target unique network identifier (TUNID).

– Make sure that the IP address in the originator and the target is identical.

– Make sure that the SNN in the originator and the target is identical.

Fault: 67.156 (439Chex | 17308dec)

Description: Fault in safety validator connection establishment engine SCID

 

Response: FS – message

Cause

Measure

Fault checking safety configuration identifier (SCID).

Check the configuration of the following SCID values:

– Combination of the values of the safety configuration CRC (SCCRC) and the safety configuration

– Timestamp (SCTS)

Fault: 67.157 (439Dhex | 17309dec)

Description: Fault in safety validator connection establishment engine EKEY

 

Response: FS – message

Cause

Measure

Fault detected in the electronic key.

Check the configuration of the target electronic key in the engineering tool of the controller.

Fault: 67.158 (439Ehex | 17310dec)

Description: Fault in safety validator server client object timeout

 

Response: FS – message

Cause

Measure

Safety protocol has signaled a timeout.

– Make sure that the communication path was not interrupted (cables, voltages, load).

– Make sure that the communication channel between originator and target has been configured correctly.

– Make sure that the monitoring times set in the originator are not too low.