List of Messages

0x1010

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x101B

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1115

Connection refused

Another user is already logged in. Further connection attempts not permissible

0x1116

Logout error

No user logged in when logout received

Only one online connection permissible at the same time

0x1117

Logout error

Invalid user info (name, ID) for logout received

Only one online connection permissible at the same time

0x1118

Timeout error

Online connection timed out

0x111A

Invalid user ID

Invalid user ID received

0x111C

Message overrun

New message received while old message is still pending

0x111F

Invalid socket ID

Invalid socket ID for online connection

0x1138

User ID error

Different user ID than logged in received

0x1147

Error setting real time clock

The attempt to set the SLC real time clock was not successful.

0x1170

Reset command

SLC info message: Reset command requested

0x1180

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1213

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x1240

SLC state has changed

Info 0: Previous SLC state

Info 1: New SLC state

SLC state:

0x00 - Invalid

0x0F - ON

0x33 - Loading

0x55 - STOP (defined EcoStruxure Machine Expert - Safety state "Safe")

0x66 - RUN (defined EcoStruxure Machine Expert - Safety state "Safe")

0x99 - HALT (defined EcoStruxure Machine Expert - Safety state "Debug")

0xAA - STOP (defined EcoStruxure Machine Expert - Safety state "Debug")

0xCC - RUN (defined EcoStruxure Machine Expert - Safety state "Debug")

0xF0 - No execution

0x1241

Variable overwritten

A variable has been overwritten

0x1242

Force list sent

A force list has been sent

0x1243

Force list: new element

An element has been added to the force list

0x1244

Force list: element deleted

An element has been deleted from the force list

0x1245

Force list deleted

The force list has been deleted

0x1310

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1311

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1312

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1313

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1314

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1315

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1316

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1317

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1318

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1319

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x131A

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x131B

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x131C

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x131D

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x131E

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x131F

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1330

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1331

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1332

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1333

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1334

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1335

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x1336

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x2017

Input checksum data error

The input checksum data are not equal.

0x201B

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x2211

Application start not successful

Application could not be started.

0x2213

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x3002

Project size exceeded

Insufficient SLC memory for project

0x3003

Instruction not implemented or incorrect data type

Instruction not implemented or incorrect data type

0x3004

Maximum size of POU exceeded

The size of the POU code is greater than 64 KB

0x3043

Maximum size of POU exceeded

Memory Error. Insufficient SLC memory for POU

0x3044

Maximum size of POU exceeded

Memory Error. The module size of a POU is greater than 64 KB

0x3048

POU inserted

A new POU was inserted into an existing project

0x3087

Division by zero

Division by zero

0x308D

Invalid project version

Incorrect project file version number. The project cannot be processed with this SLC firmware

0x3091

Service execution not possible

Service execution not possible

0x3094

Arithmetic overflow

Overflow during an arithmetic operation during execution of the user program.

0x30A4

Insufficient memory for force list

Memory not sufficient for the forced variables used

0x30A9

Debug watchdog

Debug watchdog (10 minutes) elapsed.

The SLC was in debug mode but the client has logged out

0x30AC

Too much data, out of memory

Too much data, out of memory

0x30C8

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x30E6

Additional information

Additional 16 bit error information

0x3235

Invalid memory address

Memory address in compiled EcoStruxure Machine Expert - Safety application does not match firmware

0x4412

Invalid parameters in safety-related application

Invalid parameters detected in safety-related application.

0x4413

Invalid safety-related application

Invalid safety-related application detected.

0x4414

Invalid file checksum

The safety-related application contains an invalid checksum.

0x4415

Error detected loading application file

Safety-related application file could not be loaded.

0x4421

Error detected internal file verification

An error was detected during an internal file verification.

0x4512

Invalid parameters in safety-related application

Invalid parameters detected in safety-related application.

0x4513

Invalid safety-related application

Invalid safety-related application detected.

0x4514

Invalid file checksum

The safety-related application contains an invalid checksum.

0x4515

Error detected loading application file

Safety-related application file could not be loaded.

0x4521

Error detected internal file verification

An error was detected during an internal file verification.

0x48

EcoStruxure Machine Expert - Safety connected/disconnected

Online connection from EcoStruxure Machine Expert - Safety to SLC has been connected or disconnected

0x4C

EcoStruxure Machine Expert - Safety connected/disconnected

Online connection from EcoStruxure Machine Expert - Safety to SLC has been connected or disconnected

0x55

EcoStruxure Machine Expert - Safety connected/disconnected

Online connection from EcoStruxure Machine Expert - Safety to SLC has been connected or disconnected

0x6042

Project file processing not successful

EcoStruxure Machine Expert - Safety project processing not successful

0x604B

Project does not match firmware (project header)

Project does not match firmware. Invalid project header

0x604F

Insufficient program memory

Insufficient memory for the application program

0x6055

Too many function calls

Too many function calls

0x6056

Too many function block instances

Too many function block instances

0x6057

Too many marker variables

Too many marker variables

0x605E

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x607C

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x608B

Modulo division by zero

Modulo division by zero during execution of the user program.

0x608C

Arithmetic overflow

Overflow during an arithmetic operation during execution of the user program.

0x80A0

Header CRC of the safety-related application invalid

The calculated CRC of the safety-related application header does not match the expected result.

Data is downloaded again automatically.

Info 1: Calculated CRC of the Header

0x8100

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x8108

Status internal communication management

This status information is generated hourly if delays have been detected in the internal SLC communication.

Info 0: maximum delay time in μs

Info 1: total number of delays in μs

The values of Info 0 and Info 1 are set to 0 during each power up.

0x8192

No send-buffer available

The message could not be sent because the message queue currently has no free buffers

0x8193

Message could not be sent

The SCMAR could not send a message

Info 1: message error ID

0x8194

No receive-buffer available

The message could not be received because the message queue currently has no free buffers

0x8195

Message could not be received

The SCMAR could not receive a message

0x8402

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8403

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8404

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8405

Interrupt triggered too early

Interrupt triggered too early.

Info 0: Cycle duration

0x8408

Cycle time error detected

Invalid internal cycle time.

0x8409

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x840D

Release of execution of logic not successful

Release of execution of logic not successful

0x840E

SLC Cycle time exceeded (processor 1)

SLC cycle time value is greater than permissible value according to parameter CycleTime

If Info 0 = 0x8000: the value of CycleTime is even less than the minimum time for transferring the input or output data via TM5 bus (Info 1: minimum time for transferring the data via TM5 bus)

If Info 0 = 0x9000: the value of CycleTime is not higher

Info 1: cycle time in μs

0x8410

SLC cycle time exceeded

The SCMAR cyclic task was delayed.

Info 1: last cycle time in microseconds

0x8412

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8413

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8414

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8417

Error storing local parameter data (processor 1)

Local storing of parameter data not successful

Data will be transferred again automatically at next startup

0x8418

Slot time info

Info 0: slot number

Info 1: time in μs

0x8420

Transmission error

Transmission error of internal data connections detected.

0x8421

Timout while generating 40 bit CT initial value

A timeout occurred while the random initial value for the 40 bit CT was generated.

0x8422

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x8423

Internal cycle time jitter

Internal SLC cycle time jitter was too high.

Info 0: Ratio between the measured cycle time of the current cycle and the cycle time of the previous cycle in percent.

Info 1: Measured cycle time of the last cycle in µs.

0x8481

Invalid firmware

Invalid firmware

0x8510

EcoStruxure Machine Expert - Safety user info

User info of EcoStruxure Machine Expert - Safety connection.

0x8511

EcoStruxure Machine Expert - Safety login

EcoStruxure Machine Expert - Safety connection established

0x8512

EcoStruxure Machine Expert - Safety logout

EcoStruxure Machine Expert - Safety connection closed

0x8515

Generic string message

Generic string message from EcoStruxure Machine Expert - Safety application

0x8580

Event buffer full

Too many events - event buffer is full

Safe Logger messages are not available

0x8600

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8601

Inoperable hardware

Inoperable hardware has been detected.

0x8602

Inoperable hardware

Inoperable hardware has been detected.

0x8604

Inoperable hardware

Inoperable hardware has been detected.

0x8606

Error detected voltage monitoring

Error detected monitoring supply voltage or temperature

0x8607

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x8609

Supply voltage error

Supply voltage out of limits

0x860A

Temperature error

Temperature in the module is too high or too low

0x860B

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x860D

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8611

Inoperable hardware

Inoperable hardware has been detected.

0x8612

Alert module temperature

The module temperature is close to the specified limit.

0x8702

Safe Logger data synchronized

Internal synchronization of Safe Logger data (from processor 2 to processor 1).

0x8703

Log file conversion on processor activated

Log file conversion on processor activated

0x8704

Real time clock set

Real time clock set

0x8705

Module restarted

Module restarted

0x8804

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x8805

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x8809

Insufficient memory for file data (processor 1)

Loading files from SLC memory key not successful.

This can be caused by insufficient memory for file data.

0x880B

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x880C

EcoStruxure Machine Expert - Safety project not available

One or more files of the EcoStruxure Machine Expert - Safety project are not available

0x8817

Invalid file on memory key

An invalid or outdated file was detected on the memory key.

0x8818

Invalid SLC UDID

The UDID of the SLC is invalid.

0x8AA2

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x8B00

Inoperable hardware

Inoperable hardware has been detected.

0x8C12

Inoperable hardware

Inoperable hardware has been detected.

0x8C13

Inoperable hardware

Inoperable hardware has been detected.

0x8C14

BS IDENT verification not successful

Verification of bootloader identification unsuccessful.

0x8C15

Inoperable hardware

Inoperable hardware has been detected.

0x8C16

Inoperable hardware

Inoperable hardware has been detected.

0x8C17

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x8C18

Inoperable hardware

Inoperable hardware has been detected.

0x8C19

Inoperable hardware

Inoperable hardware has been detected.

0x8C20

Inoperable hardware

Inoperable hardware has been detected.

0x8C21

Inoperable hardware

Inoperable hardware has been detected.

0x8C22

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9100

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x9202

Cross communication error

An error was detected receiving the module-internal cross communication data.

0x9402

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9403

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9404

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9405

Interrupt triggered too early

Interrupt triggered too early.

Info 0: Cycle duration

0x9408

Cycle time error detected

Invalid internal cycle time.

0x9409

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x940E

SLC Cycle time exceeded (processor 2)

SLC cycle time value is greater than permissible value according to parameter CycleTime

If Info 0 = 0x8000: the value of CycleTime is even less than the minimum time for transferring the input or output data via TM5 bus (Info 1: minimum time for transferring the data via TM5 bus)

If Info 0 = 0x9000: the value of CycleTime is not higher

Info 1: cycle time in μs

0x9412

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9413

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9414

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9417

Error storing local parameter data (processor 2)

Local storing of parameter data not successful

Data will be transferred again automatically at next startup

0x9418

Slot time info

Info 0: slot number

Info 1: time in μs

0x9420

Transmission error

Transmission error of internal data connections detected.

0x9421

Timeout while generating 40 bit CT initial value

A timeout occurred while the random initial value for the 40 bit CT was generated.

0x9422

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x9423

Internal cycle time jitter

Internal SLC cycle time jitter was too high.

Info 0: Ratio between the measured cycle time of the current cycle and the cycle time of the previous cycle in percent.

Info 1: Measured cycle time of the last cycle in µs.

0x9481

Firmware not certified

The firmware is not certified, therefore the module must not be used for safety-related tasks.

0x9580

Event buffer full

Too many events - Event buffer is full

Safe Logger messages are not available

0x9600

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9601

Inoperable hardware

Inoperable hardware has been detected.

0x9602

Inoperable hardware

Inoperable hardware has been detected.

0x9604

Inoperable hardware

Inoperable hardware has been detected.

0x9605

Inoperable hardware

Inoperable hardware has been detected.

0x9606

Error detected voltage monitoring

Error detected monitoring supply voltage or temperature

0x9607

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x9609

Supply voltage error

Supply voltage out of limits

0x960A

Temperature error

Temperature in the module is too high or too low

0x960B

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x960C

Supply voltage reached alert level.

Supply voltage reached alert level.

Info 0:

5: voltage too low

6: voltage too high

0x9611

Inoperable hardware

Inoperable hardware has been detected.

0x9612

Alert module temperature

The module temperature is close to the specified limits.

0x9702

Safe Logger data synchronized

Internal synchronization of Safe Logger data (from processor 2 to processor 1).

0x9703

Log file conversion on processor activated

Log file conversion on processor activated

0x9704

Real time clock set.

Real time clock set

0x9705

Module restarted

Module restarted

0x9804

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x9805

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x9809

Insufficient memory for file data (processor 2)

Loading files from SLC memory key not successful.

This can be caused by insufficient memory for file data.

0x980B

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0x980C

EcoStruxure Machine Expert - Safety project not available

One or more files of the EcoStruxure Machine Expert - Safety project are not available

0x9817

Invalid file on memory key

An invalid or outdated file was detected on the memory key.

0x9AA0

Header CRC of the safety-related application invalid

The calculated CRC of the safety-related application header does not match the expected result.

Data will be downloaded again automatically.

Info 1: Calculated CRC of the Header

0x9B00

Inoperable hardware

Inoperable hardware has been detected.

0x9C12

Inoperable hardware

Inoperable hardware has been detected.

0x9C13

Inoperable hardware

Inoperable hardware has been detected.

0x9C14

BS IDENT verification not successful

Verification of bootloader identification unsuccessful.

0x9C15

Inoperable hardware

Inoperable hardware has been detected.

0x9C16

Inoperable hardware

Inoperable hardware has been detected.

0x9C17

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0x9C18

Inoperable hardware

Inoperable hardware has been detected.

0x9C19

Inoperable hardware

Inoperable hardware has been detected.

0x9C20

Inoperable hardware

Inoperable hardware has been detected.

0x9C21

Inoperable hardware

Inoperable hardware has been detected.

0x9C22

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xA101

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA107

SOD read error detected

The SLC memory key may be empty, or the project on the SLC memory key may be invalid.

0xA10E

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA10F

SDO abort received from node

Error SDO communication

Low word of Info 1: ID of safety-related module

0xA114

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA115

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA116

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA117

Parameter checksum numbers do not match

The number of checksums for this module does not correspond to the number of checksums expected.

The module is being reparameterized.

0xA317

Error detected in memory block frame transmission

Memory block for frame transmission cannot be passed to unit SHNF.

0xA513

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA514

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA64D

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA64E

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA742

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA743

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA744

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA745

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA746

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA747

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA748

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA749

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA74A

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA74B

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA74C

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA74D

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA74E

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA74F

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA750

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA751

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA752

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA753

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA754

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA755

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA756

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA757

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA758

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA759

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA75A

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA840

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xA841

Delay for extended Consecutive Timers too long

The delay between two received extended Consecutive Timers on the RxSPDO is too long

0xA842

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xAB1B

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xAF01

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xAF0C

Module initialization not successful

Module could not be initialized with the available parameters

0xAF18

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xAF19

Info internal file conversion

Error loading the UDID list

Additional info (Info 0):

0: error: invalid revision

1: error: invalid file length

2: error: invalid file header CRC

3: error: invalid number of CRCs

4: error: invalid data section

5: error: invalid data section revision

6: error: invalid data CRC

7: info: UDID file conversion ok

A file conversion was required due to a firmware update.

0xAF1A

Invalid parameter CRC

The SOD CRC could not be validated.

The calculated parameter CRC and the available parameter CRC are not identical.

Info 0: low byte instance, high byte CRC index

Info 1: calculated CRC

0xAF1D

Error unlocking file

An error was detected unlocking a downloaded file.

Info 0: cause of error

1: invalid file name

2: key could not be opened

3: key could not be read

4: key could not be written

5: key could not be closed

6: file could not be opened

7: file size could not be determined

8: file could not be read

9: file could not be written

A: file could not be closed

B: unlocked file invalid

C: internal error

0xAF21

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xAF23

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xAF31

Safety-related connection to module unavailable

Detected falling edge of SafeModuleOK.

This can be caused by incorrect synchronous communication.

0xAF40

SN_FAIL received (processor 1)

Error starting safety-related module.

Info 1, byte 0 and byte 1: ID of safety-related module

Info 1, byte 2: error group

0: device

1: application

2: parameter

3: vendor-specific

4: openSAFETY stack

Info 1, byte 3 if error group = 3: error code

0: parameter error

1: reserved

Info 1, byte 3 if error group = 4: error code

1: CRC error detected in the parameter set

Example: Info 1 = 0x01040007 means: safety-related node ID 0x0007, error group openSAFETY stack, CRC error detected in the parameter set

0xAF43

Transition to operating state Operational

Additional information:

Low word of Info 1: version of safety-related firmware (see parameter FW_Version of TM5/TM7 modules)

Other values: reserved

0xAF44

Transition to operating state Pre-operational

-

0xAF48

SPDO transmit queue is full

SPDO transmit queue is full

0xAF4F

Transition to operating state Operational

Additional information:

Low word of info 1: Firmware version

High word of info 1: SafeNODE ID

Info 0: Instance of openSAFETY stack

0xAF5F

Counter value for unsuccessful SNMT communication has changed

Errors (usually timeouts) were detected during SNMT communication.

SNMT is used for node guarding and module startup.

This message is generated at most once per 10 minutes.

Info 0: Difference of the counter value since last logger message.

Info 1: Counter value.

0xAF60

Counter of invalid openSAFETY frames has increased (processor 1)

The counter of invalid openSAFETY frames (SPDO and SSDO) has increased (serialization/deserialization).

Info 1: counter value.

This message is generated once per hour if the counter changes.

If the counter keeps changing, incorrect frames keep coming to the SLC.

This is normal if modules are unavailable or unused because the SPDOs coming from those nodes are zero and therefore invalid.

0xAF61

Counter for SPDO errors has increased (processor 1)

The counter of invalid cyclic safety-related data (SPDO) has increased.

Info 1: counter value

This message is generated once per hour if the counter has changed.

If the counter keeps changing, at least one SPDO connection keeps being unsuccessful.

This is normal if modules are unavailable or have not been started because an SPDO connection to such modules cannot be established.

0xAF62

Connection statistics counter has changed.

Connection statistics counter has changed. One or more SPDO connections (cyclic safety-related data) are not stable.

Info 0: number of connections that have been affected

Info 1: connection interruptions since last Safe Logger entry

This message is generated once in 10 minutes if a counter changes.

0xAF6E

Invalid initial value for the 40 bit CT connection

An invalid initial value for the 40 bit CT openSAFETY connection was calculated.

0xB101

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xB107

SOD read error detected

The SLC memory key may be empty, or the project on the SLC memory key may be invalid.

This condition can be the result of setting up a new target/memory key or of a format.

0xB317

Error detected in memory block frame transmission

Memory block for frame transmission cannot be passed to unit SHNF.

0xBF01

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xBF0C

Module initialization not successful

Module could not be initialized with the available parameters

0xBF18

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xBF1C

Operating state transition from Pre-operational to Operational

-

0xBF1D

Operating state transition from Operational to Pre-operational

-

0xBF21

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xBF23

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xBF31

Safety-related connection to module unavailable

Detected falling edge of SafeModuleOK.

This can be caused by incorrect synchronous communication.

0xBF40

SN_FAIL received (processor 2)

Error starting safety-related module.

Info 1, byte 0 and byte 1: ID of safety-related module

Info 1, byte 2: error group

0: device

1: application

2: parameter

3: vendor-specific

4: openSAFETY stack

Info 1, byte 3 if error group = 3: error code

0: parameter error

1: reserved

Info 1, byte 3 if error group = 4: error code

1: CRC error detected in the parameter set

Example: Info 1 = 0x01040007 means: safety-related node ID 0x0007, error group openSAFETY stack, CRC error detected in the parameter set

0xBF43

Transition to operating state Operational

-

0xBF44

Transition to operating state Pre-operational

-

0xBF48

SPDO transmit queue is full

SPDO transmit queue is full

0xBF4F

Transition to operating state Operational

Additional information:

Low word of info 1: Firmware version

High word of info 1: SafeNODE ID

Info 0: Instance of openSAFETY stack

0xBF5F

Counter value for unsuccessful SNMT communication has changed

Errors (usually timeouts) were detected during SNMT communication.

SNMT is used for node guarding and module startup.

This message is generated at most once per 10 minutes.

Info 0: Difference of the counter value since last logger message.

Info 1: Counter value.

0xBF60

Counter of invalid openSAFETY frames has increased (processor 2)

The counter of invalid openSAFETY frames (SPDO and SSDO) has increased (serialization/deserialization).

Info 1: counter value.

This message is generated once per hour if the counter changes.

If the counter keeps changing, incorrect frames keep coming to the SLC.

This is normal if modules are unavailable or unused because the SPDOs coming from those nodes are zero and therefore invalid.

0xBF61

Counter for SPDO errors has increased (processor 2)

The counter of invalid cyclic safety-related data (SPDO) has increased.

Info 1: counter value

This message is generated once per hour if the counter has changed.

If the counter keeps changing, at least one SPDO connection keeps being unsuccessful.

This is normal if modules are unavailable or have not been started because an SPDO connection to such modules cannot be established.

0xBF62

Connection statistics counter has changed.

Connection statistics counter has changed. One or more SPDO connections (cyclic safety-related data) are not stable.

Info 0: number of connections that have been affected

Info 1: connection interruptions since last Safe Logger entry

This message is generated once in 10 minutes if a counter changes.

0xBF6E

Invalid initial value for the 40 bit CT connection

An invalid initial value for the 40 bit CT openSAFETY connection was calculated.

0xC00D

UDID acknowledgement error

Not possible to acknowledge a UDID mismatch

Info 1: SADDR

0xC01A

Error remote control

Error remote control

Info 0:

0: Address error

1: Incorrect length (ENTER PASSWORD_CHANGE)

2: Incorrect length (the other commands)

3: Invalid pointer

Info 1: Length (not if info 0 = 0)

0xC01E

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xC030

Error initiating openSAFETY connection with 40 bit CT

Error detected while initiating a cyclic openSAFETY connection that is parameterized to use the 40 bit CT.

Info 1: ID of safety-related module

0xC080

Acknowledgement of module replacement (1 module)

The user has acknowledged a module replacement (1 module).

0xC081

Acknowledgement of module replacement (2 modules)

The user has acknowledged a module replacement (2 modules).

0xC082

Acknowledgement of module replacement (3 modules)

The user has acknowledged a module replacement (3 modules).

0xC083

Acknowledgement of module replacement (4 modules)

The user has acknowledged a module replacement (4 modules).

0xC084

Acknowledgement of module replacement (more than 4 modules)

The user has acknowledged a module replacement (more than 4 modules).

0xC085

Confirmation of a new firmware version

The user has confirmed a new firmware version

0xC087

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xC089

Safety-related module unavailable or condition related to nodeguarding (processor 1)

Safety-related module not found (SSDO communication to this module not successful).

Info 1: ID of safety-related module

0xC08A

Module is not started due to firmware revision mismatch (processor 1)

The module firmware version does not correlate with parameter MinRequiredFWRev.

Info 0: ID of safety-related module

Info 1: firmware version on the module

0xC08B

Info user action on SLC

A user action on the SLC has been executed due to remote access or the SLC ENTER button.

Info 0: action state:

0x00: The received remote command is valid and will be executed

0x01: ENTER button successful

0x02: ENTER button not successful (author, state, etc.)

0x03: Remote execution was successful

0x04: Remote execution was not successful (state, etc.)

0x05: Remote command is invalid

0x06: Remote ENTER command is invalid

0x07: Remote ENTER commands are not activated in EcoStruxure Machine Expert - Safety application

0x08: Remote ENTER command with incorrect password

0x09: Remote ENTER command is not idle

0x0A: Remote ENTER command is locked by the HMI

0x0B: remote ENTER command SK-ACKN has no authorization

0x0C: Remote ENTER command FW-ACKN has no authorization

0x0D: Remote ENTER command UDID-ACKN (SMX-CMX) has no authorization

0x0E: SK-ACKN is not possible, memory key was not changed

0x0F: FW-ACKN is not possible, no different FW was detected

0x10: SMX-ACKN is not possible, replaced modules not equal to 1

0x11: DMX-ACKN is not possible, replaced modules not equal to 2

0x12: TMX-ACKN is not possible, replaced modules not equal to 3

0x13: QMX-ACKN is not possible, replaced modules not equal to 4

0x14: CMX-ACKN is not possible, replaced modules less than 5

0x15: SK-CONTINUE not possible, SK-COPY is not started

0x16: SK-ACKN is required, no other actions possible

0x17: SK-FORMAT is running, no other actions possible

0x18: SK-COPY is running, no other actions possible

0x19: SK-ACKN is running, no other actions possible

0x1A: UDID-ACK (SMX-CMX) is running, no other actions possible

0x1B: Scanning of the modules is running, no other actions possible

0x1C: Remote response send not successful

0x1D: Incorrect length of the remote ENTER command PASSWORD_CHANGE, info 1: length

0x1E: Incorrect length of all other remote commands, info 1: length

Info 1: Number of remote command or position of confirmed SLC selection switch

0x0000 to 0x0x000F: position of SLC selection switch, e.g. 0x0000 is position "TEST"

0x0020: Acknowledge UDIDs of 5 or more modules

0x0030: Acknowledge UDIDs of 4 modules

0x0040: Acknowledge UDIDs of 3 modules

0x0050: Acknowledge UDIDs of 2 modules

0x0060: Acknowledge UDID of 1 module

0x0100: Acknowledge firmware revision

0x0200: Acknowledge memory key

0x1000: Test LEDs

0x2000: Start module scan

0x3000: Copy memory key

0x4000: Continue copying memory key

0x5000: Change password

0x6000: Format memory key

0x7000: Reset

0x8000: Delete user data

0x9000: Setup Mode activated

0x9100: Setup Mode deactivated

0xF000: Version info (only used for internal communication)

0xC08C

Safety-related device communication

Safety-related device communication

Info 0:

0: received command valid

1: invalid command (info 1: command)

2: UDID read not successful (info 1: ID of safety-related module)

3: response buffer too small (info 1: length)

0xC08D

Incorrect firmware version, vendor or module type

Firmware version of the safety-related module has not been acknowledged or vendor/module type do not match.

Info 1: ID of safety-related module

0xC08E

Parameter error safety-related module

The safety-related parameters for the module are not available or could not be downloaded.

Info 1: ID of safety-related module

0xC08F

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xC093

SLC in inaccessible state

SLC is in a state where it cannot be accessed via the internal command channel.

The SLC might be in defined safe state or the 24 Vdc I/O supply voltage is unavailable.

0xC094

Info Setup Mode

Info Setup Mode

See Info 0 for details.

Info 0:

1: Setup Mode activated during startup

2: Setup Mode activated by user

3: Setup Mode deactivated by user (triggers SLC reboot)

4: Hourly reminder that Setup Mode is active

5: Internal error (initialization)

6: Internal error (execution)

7: Memory key replacement has been confirmed automatically

8: Module replacement has been confirmed automatically

9: Firmware has been acknowledged automatically

0xC09A

Cyclic data connection not valid

Invalid cyclic data connection to SafeNODEs that are already in the operating state Operational.

Info 0:

0: Transmission time is longer than permitted by parameter "SafeDataDuration SDD"

1: No cyclic data received from some modules

Info : Number of affected modules

This message is generated during SLC bootup approximately 10 s after the last transition to the operating state Operational of a SafeNODE.

0xC120

Maximum frequency exceeded

The measured frequency exceeded the maximum frequency.

0xC125

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xC126

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xC132

Dual-channel evaluation: discrepancy time elapsed (processor 1)

The dual-channel evaluation (PLCopen function block equivalent or antivalent) has detected a discrepancy.

Info 0:

0: dual-channel evaluation = none

1: dual-channel evaluation = equivalent

2: dual-channel evaluation = antivalent

Info 1 syntax: $YZ

Y=1: WAIT FOR CHANNEL 02

Y=2: WAIT FOR CHANNEL 01

Y=3: FROM ACTIVE WAIT

Z=0: channel 1-2

Z=1: channel 3-4

Z=2: channel 5-6

Z=3: channel 7-8

Z=4: channel 9-10

Z=5: channel 11-12

Z=6: channel 13-14

Z=7: channel 15-16

Z=8: channel 17-18

Z=9: channel 19-20

See manual also

0xC141

Input error state has changed (processor 1)

Error detected at safety-related input channel.

Info 1[0]: errors of test pulse outputs (high nibble: high; low nibble: low)

Info 1[1]: input high

The bits of each nibble represent the channels 1-4 (LSB=channel 1)

An error is active if the corresponding bit is set.

All bits 0 if all errors cleared.

Some causes of errors can lead to several bits being set (such as cross circuits)

0xC142

Inoperable hardware

Inoperable hardware has been detected.

0xC143

Input error state has changed (processor 1)

Error detected at safety-related input channel.

Info 0 byte 0: test pulse output low

Info 0 byte 1: test pulse output high

Info 1: input high

Each bit of the info data represents one channel (LSB=channel 1)

An error is active if the corresponding bit is set.

All bits 0 if all errors cleared.

Some causes of errors can lead to several bits being set (such as cross circuits)

0xC151

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xC152

Input value differs between two processors

The input values differ between the two processors. This can be the result of signal chattering caused by different signal propagation times.

0xC1AE

Dual-channel evaluation not activated (processor 1)

Datapoint for dual-channel evaluation is used even though the corresponding dual-channel evaluation is not activated.

Info 0 byte 3: number of the channel whose dual-channel evaluation is not activated.

0xC1AF

Parameter error detected

Guard door interlock function block

0xC1B0

Discrepancy time increased

The parameterized value of the discrepancy time has been increased internally.

Info 0: Channel number of the affected channel

Info 1: New discrepancy time

0xC215

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xC220

Output channel test errors cleared (processor 1)

The output channel errors have been cleared (acknowledgment of message 0xC222 or 0xC224)

0xC222

Test status of output has changed (processor 1)

Error detected at safety-related output channel.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

Status in range from 0x00 to 0x1F see table

Both switches off, no current flow

Status Error Channel+ Channel-

%00000000 no - -

%00000001 yes open high

%00000010 yes high open

%00000011 yes high high

Test pulse from high side switch

Status Error Channel+ Channel-

%000x0100 no - -

%000x0101 yes open high

%000x0110 yes high open

%000x0111 yes high high

Test pulse from low side switch

Status Error Channel+ Channel-

%000x1000 yes low -

%000x1001 yes low high

%000x1010 yes - open or low

%000x1011 no - -

Both switches on

Status Error Channel+ Channel-

%000x1100 yes low -

%000x1101 yes low open and high

%000x1110 no - -

%000x1111 yes - high

Both switches off, current flow detected, resulting in non-resettable channel-specific error

Status Error Channel+ Channel-

%00010000 yes -

%00010001 yes open high

%00010010 yes high open

%00010011 yes high high

x - no difference in error handling if 0 or 1

Status is equal to 0x20: overload detected

Status is equal to 0x21: maximum switching frequency exceeded

Status is equal to 0x22: internal error detected

Example: Info 0 = 0x0100, Info 1 = 0x21000020 means:

Channel number: 6 5 4 3 2 1

Channel 1: overload detected

Channel 4: maximum switching frequency exceeded

Channel 6: Both switches off, no current flow, Error, Channel+ open, Channel- high

Channel 2,3,5: Both switches off, no current flow, No Error

0xC224

Test status of output has changed (processor 1)

Error detected at safety-related output channel.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

Both switches off

Channel status Error Output

0x00 no ok

0x01 yes (unrecoverable) undefined

0x02 yes (unrecoverable) undefined

0x03 yes high

Test pulse switch 1

Channel status Error Output

0x04 no ok

0x05 yes (unrecoverable) undefined

0x06 yes (unrecoverable) undefined

0x07 yes high

Test pulse switch 2

Channel status Error Output

0x08 yes (unrecoverable) undefined

0x09 yes (unrecoverable) undefined

0x0A no ok

0x0B yes high

Both switches on

Channel status Error Output

0x0C yes low

0x0D yes low

0x0E yes low

0x0F no ok

Other Errors

Channel status Error Error description

0x1E yes input feed by external 24V detected

0x1F yes channel switched off because the other channel of this connector detected an error

0x20 yes maximum current exceeded

0x21 yes maximum switching frequency exceeded

0x22 yes internal error

Example: Info 0 = 0x0300, Info 1 = 0x2100000F means:

Channel number: 6 5 4 3 2 1

Channel 1: Both switches on, no Error, Output OK

Channel 4: maximum switching frequency exceeded

Channel 6: Both switches off, error detected, output high

Channel 2,3,5: Both switches off, no Error, Output ok

0xC225

Overcurrent error

The total of the current for all outputs has exceeded the maximum value.

0xC226

Error XchangeData: different feedback signals (processor 1)

Error XchangeData: different feedback signals

0xC228

Incorrect activation sequence of SafeCtrl signal and Release signal (processor 1)

An incorrect activation sequence was detected at a safety-related output channel. This does not cause a channel error.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

State is equal to 0x23: Release signal was activated before SafeCtrl signal

State is equal to 0x24: Release signal and SafeCtrl signal were activated simultaneously

0xC229

Test status of output has changed (processor 1)

Error detected at safety-related output channel.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

For safety-related output channels of type A (SOx + / SOx -) see message 0xC222 for detailed descriptions.

For safety-related output channels of type B (SOx / COM) see message 0xC224 for detailed descriptions.

0xC2AC

Output high detected in operating state Pre-Operational (processor 1)

Not all outputs 0 in operating state Pre-Operational.

Info 1: output feedback states (LSB = channel 1)

The affected channels can be found in info 1 and need to be converted to binary format. Two bits each represent one channel (starting with channel 1 corresponding to the LSB).

Example: HEX - A00 corresponds to BIN 1010 0000 0000.

Channels 5 and 6 report an error.

0xC313

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xC315

Maximum switching frequency exceeded (processor 1)

The maximum switching frequency of the module has been exceeded.

The output channel may be switched off up to 5 times per minute at maximum; the minimum interval between two switch-off cycles is 500 ms.

0xC316

Internal error voltage measurement out of range (processor 1)

Internal error voltage measurement out of range

0xC318

Backfeed voltage at the output (processor 1)

Backfeed voltage has been detected at the output of the module

0xC320

Maximum switching frequency exceeded (processor 1)

The maximum switching frequency of the module has been exceeded

0xC321

Channel output state has changed (processor 1)

Channel output state has changed.

Info 1: 1: channel switched to error state.

Info 1: 2: channel error cleared.

0xC322

Incorrect activation sequence of SafeCtrl signal and Release signal

An incorrect activation sequence was detected at a safety-related output channel. This does not cause a channel error.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

State is equal to 0x23: Release signal was activated before SafeCtrl signal

State is equal to 0x24: Release signal and SafeCtrl signal were activated simultaneously

0xC323

Backfeed voltage still present at the output

Detected channel error cannot be reset. Backfeed voltage is still present at the output of the module.

0xC404

OpenSAFETY communication error

OpenSAFETY communication error.

Response:

The safety-related function STO has been activated.

0xC411

Encoder error (Sin²Cos² monitoring)

The monitoring of the sine and cosine traces has detected an error.

Response:

The safety-related function STO has been activated.

0xC412

Encoder error (quadrant monitoring)

Encoder monitoring: A deviation between digital and analog quadrant has been detected.

Response:

The safety-related function STO has been activated.

0xC413

Internal error, Cross comparison of input data

Internal error: Cross comparison of input data not successful.

Response:

Transition of the module to defined safe state.

0xC414

Internal error, Cross comparison of output data

Internal error: Cross comparison of output data not successful.

Response:

Transition of the module to defined safe state.

0xC415

Internal error, Cross communication

Internal error: Transmission error detected during cross communication.

Response:

Transition of the module to defined safe state.

0xC418

Encoder configuration - Encoder resolution different

The configured encoder resolution in EcoStruxure Machine Expert - Safety is different from the encoder resolution which has been reported by the drive.

Response:

Transition to operating state Operational is not possible. Module remains in the operating state Pre-operational.

0xC419

Encoder configuration - Encoder type different

The configured encoder type in EcoStruxure Machine Expert - Safety is different from the encoder type which has been reported by the drive.

Response:

Transition to operating state Operational is not possible. Module remains in the operating state Pre-operational.

0xC41B

Encoder configuration - Encoder resolution invalid

The encoder configuration is invalid. For rotary encoders the encoder resolution must be a power of 2.

Response:

Transition of the module to defined safe state.

0xC41F

Internal error, ADC error

Verification of analog digital converter inputs not successful.

Response:

Transition of the module to defined safe state.

0xC422

Module bootup

The bootup operation of the module has been completed.

0xC423

Operational

The module has transitioned to the operating state Operational.

0xC424

Pre-operational

The module has transitioned to the operating state Pre-operational.

0xC425

Diag Quit

The safety-related functions in the module have been reset.

0xC42E

Safety-related function SMS - speed limit exceeded

The speed of the drive exceeded the value in SMS_SpeedLimit.

Response:

The fallback safety-related function SS1 has been activated.

0xC42F

SDI - incorrect direction

The direction of movement of the motor does not match the configured direction of movement and position tolerance.

Response:

The fallback safety-related function SS1 has been activated.

0xC430

Safety-related function SOS - movement outside of standstill position window

The motor has moved outside the standstill position window configured by parameter SOS_PositionTolerance.

Response:

The fallback safety-related function STO has been activated.

0xC431

Safety-related function SS2 - movement outside of standstill position window

The motor has moved outside the standstill position window configured by parameter SS2_PositionTolerance.

Response:

The fallback safety-related function STO has been activated.

0xC432

Safety-related function SLS1 - Speed limit exceeded

The speed of the motor is greater than the value in SLS1_SpeedLimit.

Response:

The fallback safety-related function SS1 has been activated.

0xC433

Safety-related function SLS2 - Speed limit exceeded

The speed of the motor is greater than the value in SLS2_SpeedLimit

Response:

The fallback safety-related function SS1 has been activated.

0xC434

Safety-related function SLS3 - Speed limit exceeded

The speed of the motor is greater than the value in SLS3_SpeedLimit.

Response:

The fallback safety-related function SS1 has been activated.

0xC435

Safety-related function SLS4 - Speed limit exceeded

The speed of the motor is greater than the value in SLS4_SpeedLimit.

Response:

The fallback safety-related function SS1 has been activated.

0xC436

Safety-related function SS1 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SS1.

Response:

The fallback safety-related function STO has been activated.

0xC437

Safety-related function SS2 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SS2.

Response:

The fallback safety-related function STO has been activated.

0xC438

Safety-related function SLS1 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SLS1

Response:

The fallback safety-related function STO has been activated.

0xC444

Safety-related function SLS2 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SLS2.

Response:

The fallback safety-related function STO has been activated.

0xC445

Safety-related function SLS3 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SLS3.

Response:

The fallback safety-related function STO has been activated.

0xC446

Safety-related function SLS4 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SLS4

Response:

The fallback safety-related function STO has been activated.

0xC447

Speed limit for safety-related function SLS is invalid

The configuration of the speed limits for the safety-related functions SLS and SMS is invalid. The speed limits for the safety-related functions SLS and SMS must meet the following conditions:

SLS1 Speed Limit <= SLS2 Speed Limit <= SLS3 Speed Limit <= SLS4 Speed Limit <= SMS Speed Limit

Response:

Transition to operating state Operational is not possible. Module remains in operating state Pre-operational.

0xC448

SOD CRC invalid

SOD CRC invalid. The parameter set has been transmitted incorrectly or was stored incorrectly in the safety-related module.

Response:

Transition to operating state Operational is not possible. Module remains in the operating state Pre-operational.

0xC449

Module bootup not successful

The safety-related module could not be initialized.

Response:

Transition of the module to defined safe state.

0xC44B

Safety-related function STO active

The safety-related function STO is active. The axis is torque free.

FW < 1.3.0.0: The safety-related function STO was requested either by the SLC application, the HW STO input or as fallback for another safety-related function.

FW >= 1.3.0.0: The safety-related function STO was requested by the SLC application.

0xC44C

Safety-related function SS1 active

The safety-related function SS1 is active. The axis has been stopped and is now torque free.

FW < 1.3.0.0: SS1 was requested by the SLC application or as fallback for another safety-related function.

FW >= 1.3.0.0: SS1 was requested by the SLC application.

0xC44F

Safety-related function STO active (Fallback)

The safety-related function STO is active. The axis is torque free. The safety-related function STO was requested as fallback for another safety-related function.

0xC450

Safety-related function SS1 active (Fallback)

The safety-related function SS1 is active. The axis has been stopped and is now torque free. SS1 was requested as fallback for another safety-related function.

0xC451

Safety-related function STO active (HW)

The safety-related function STO is active. The axis is torque free. The safety-related function STO was requested by the HW STO input.

0xC452

Safety-related function STO active (FB deactivated)

The safety-related function STO is active. The axis is torque free. The safety-related function STO was requested because the SF_SafeMotionControl function block was deactivated.

0xC510

Inoperable hardware

Inoperable hardware has been detected.

0xC513

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xC515

Maximum switching frequency exceeded (processor 1)

The maximum switching frequency of the relay has been exceeded

0xC520

Inoperable hardware

Inoperable hardware has been detected.

0xC521

Inoperable hardware

Inoperable hardware has been detected.

0xC522

Internal parameter error

The module detected incorrect parameters (input channels used).

0xC523

Relay supply voltage error

The relay supply voltage is out of limits. The module-internal relay power supply (18 V or 21 V) is affected.

0xC5A4

Inoperable hardware

Inoperable hardware has been detected.

0xC5F4

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xC5F5

Reference input state does not match actual input state

At least one input channel does not have the state defined by the reference channel.

Info 1: differing inputs

Each bit of the info data represents one channel (LSB=channel 1)

An error is active if the corresponding bit is set.

All bits 0 if all errors cleared.

Some causes of errors can lead to several bits being set (such as cross circuits)

0xC605

Inoperable hardware

Inoperable hardware has been detected.

0xC618

Inoperable hardware

Inoperable hardware has been detected.

0xC619

Status of channel error evaluation has changed

Error status of an input has changed

Info 1 syntax: $YYZZ

yy: bitcoded, current channelOK information

ZZ: bitcoded channelOK information of last cycle

0xC621

Status of dual-channel evaluation has changed

Signal state of an input has changed

Info1 syntax: $yyzz

yy: bitcoded, current signalOK information

zz bitcoded signalOK information of last cycle

0xC622

Status of threshold evaluation has changed

Status of dual-channel evaluation has changed

Info 1 syntax: $YYZZ

yy: bitcoded, current dual-channelOK information

ZZ: bitcoded dual-channelOK information of last cycle

0xC625

Inoperable hardware

Inoperable hardware has been detected.

0xC626

Output current for sensor feed exceeded (processor 1)

Maximum current on outputs used to feed an external sensor was exceeded.

0xC627

No sensor connected

No sensor connected to at least one analog input channel.

Info 1:

Bit 0: Channel 1 not connected

Bit 1: Channel 2 not connected

Bit 2: Channel 3 not connected

...

0xC628

Error during shunt test (processor 1)

Error during shunt test

Info 1 provides information on the affected channel:

0: Input 1

1: Input 2

0xC6A7

Incorrect sensor type

Channel which is used to measure the temperature of the terminal is not set for PTx measurement even though another channel requires it.

Info 1 byte 3: number of the channel who requires the temperature of the terminal.

0xC6A8

Threshold parameter out of range

Threshold parameter is out of range of sensor type of corresponding channel.

Info 0: number of channels with incorrect parameter:

0: channel pair 0102

1: channel pair 0304

2: channel pair 0506

Info 1 byte 1: number of threshold parameter

Info 1 byte 2: type of incorrect threshold parameter:

0: Limit_Threshold_Low

1: Limit_Threshold_High

2: Limit_Threshold_Equivalent

3: Discrepancy_Time

10: Limit_Threshold_High

0xC70C

Error Utilities library: out of range

Info 0: cause of error

1: Overflow in function (Safe) DINT_TO_INT

2: Underflow in function (Safe) DINT_TO_INT

3: Overflow in function (Safe) DWORD_TO_TIME or (Safe) TIME_TO_DWORD

Info 1: absolute value at function input

0xC910

Simultaneous edges on channel A and B

The module repetitively detected simultaneous edges on channels A and B. This is not permissible in mode A-B and A-Ai-B-Bi.

0xC913

Speed differs between the two measurement channels

The speeds which are calculated on the basis of evaluated inputs differ (measurement channels depend on mode used A-A or A-B or A-B and Ai-Bi).

Info 0: permissible difference

Speed values given as set via parameter "Unit"

Info 1, byte 0 and byte 1: speed channel 0

Info 1, byte 2 and byte 3: speed channel 1

0xC914

Countervalue differs between two channels

The countervalues which are calculated on the basis of inputs A-B and Ai-Bi differ.

0xC915

Input A and Ai or input B and Bi are FALSE at the same time

The module repetitively recognized that A and Ai or B and Bi are FALSE at the same time. This is not permissible in mode A-B and A-Ai-B-Bi.

0xC917

Value of SafeFrequency signal out of range

The input frequency is out of range. The value of the SafeFrequency signal must be between -32768 and +32767.

0xC918

Maximum acceleration exceeded

The measured acceleration exceeded the maximum acceleration

0xC920

Input frequency out of range

The measured frequency is out of range. The module can only measure frequencies up to 7500Hz.

0xC921

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xC922

Channel error not acknowledged

The channel error could not be acknowledged because the measured input frequency is not 0.

0xC923

Channel error acknowledged

The channel error was acknowledged

0xC924

Frequency value differs between two processors

The frequency values which are calculated on the basis of inputs differ between the two processors. This condition can be the result of different signal propagation times between the two processors if there are no appropriate input signals.

0xCA02

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xCA06

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xCA0C

Error importing application files (processor 1)

EcoStruxure Machine Expert - Safety application could not be imported.

No valid application found on the SLC.

0xCA0D

EcoStruxure Machine Expert - Safety application download finished

A new EcoStruxure Machine Expert - Safety application has been downloaded to SLC.

SLC will restart.

0xCA0F

Inoperable hardware

Inoperable hardware has been detected.

0xCA11

Inoperable hardware

Inoperable hardware has been detected.

0xCA13

Reset due to SCMAR restart

SLC restarted due to restart of SCMAR

0xCA15

Too many TM5 bus input data errors

Too many errors detected during demultiplexing TM5 bus input data frames.

0xCA16

Flash memory test executed after SLC memory key format

Flash memory test of internal application memory.

This is performed automatically after SLC memory key format.

Result:

OK if message type = info

Error if message type = error

0xCA18

SPDO synchronization not successful

Not all required SPDO connection could be synchronized.

SPDO connection (cyclic data connection) to all safety-related IO modules must meet the timing requirements (except those that are optional)

Info 0: minimum transfer time for data (μs; see also data point "SLCioCycle")

Info 1 byte 2 and byte 3: states (1=OK) of the SPDO connections to the safety-related IO (1 Bit per SN, starting from LSB; ordered according to the Safety Node ID in EcoStruxure Machine Expert - Safety)

Info 1: byte 0 and byte 1: internal - do not use

0xCA19

Safety-related application CRC mismatch

The calculated CRCs are not matching the data in the memory.

Info 0: File index

Info 1: Calculated CRC

Data will be downloaded again automatically.

0xCA20

Inconsistent application data

Inconsistent application data found

Info 0:

0x01: User data inconsistent, download will be started automatically

0x02: Reserved

0x03: Data inconsistent, download will be restarted started automatically

Info 1: (valid for Info 0 = 0x02 only):

0x01: Machine option download will restart automatically

0x02: BOOL Commissioning options data missing

0x03: Extended Commissioning Options data missing

0x04: BOOL Commissioning options data provided, but not used

0x05: Extended Commissioning options data provided, but not used

0x06: Commissioning options activated, but not used

0x07: Commissioning options used, but not activated

0x10: This module does not support commissioning options with data types other than SAFEBOOL

0xCB01

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xCC02

Parameter error digital input

Invalid parameters for digital inputs

Info 0:

0x1000: Version conflict

0x2000: Length conflict

0x30yy: TON filter value too large, yy channel number

0x40yy: TOFF filter value too large, yy channel number

0x50yy: Discrepancy time too long, yy channel number

0x60yy: Dual-channel evaluation invalid, yy channel number

0x70yy: Channel not configured as digital input in EcoStruxure Machine Expert - Safety

0x8000: One channel of a dual- channel pair is not configured as digital input in EcoStruxure Machine Expert - Safety

Info 1: 0x0000xxyy:

xx, yy Channel number(s)

Info 1: Configured incorrect value

0xCC03

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xCC04

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xCC05

Error digital inputs

An error was detected at at least one digital input.

Info 0:

0x10xx: Error detected during internal hardware tests

--> Info 1: Channel number of affected channel

0x2000: Input data that is different between the two safety-related processors

--> Info 1: Bit information which channels are different

0xCC06

Channel configuration mismatch

A channel configuration in EcoStruxure Machine Expert does not match the channel configuration in EcoStruxure Machine Expert - Safety.

Info 1 indicates the number of the affected channel.

0xCC42

Parameter error digital output

-

0xCC50

Relay test error

An error was detected testing the relays.

Info 0:

0: relay does not switch correctly

1: an output is switched on

Info1 bit-wise shows which output is switched on

0xCC52

Error digital outputs

Error detected at digital outputs

Info 0:

0: Hardware test of outputs detected an error during runtime or the maximum switching frequency was exceeded

1: Release channel and output channel have been switched on simultaneously

2: Hardware test of outputs detected an error during power up

Info 1: Bit information indicates affected outputs

0xCC53

Indeterminable error digital outputs

Indeterminable error digital outputs

0xCC55

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xCC82

Parameter error analog input

Invalid parameters for analog inputs

Info 0:

0x1000: Version conflict

0x2000: Length conflict

0x30yy: Discrepancy time too long, yy channel number

0x40yy: Dual-channel evaluation invalid threshold

0x50yy: Channel not configured as analog input in EcoStruxure Machine Expert - Safety

0x6000: One channel of a dual-channel pair is not configured as analog input in EcoStruxure Machine Expert - Safety

Info 1: 0x0000xxyy:

xx, yy Channel number(s)

Info 1: Configured incorrect value

0xCC85

Analog input test error

The internal hardware test detected an error.

Info 0:

0xXX01: Error of a channel. Info 1: Channel number

0xXX02: ADC error

0xXX03: CRC error of calibration data

0xXXFF: Internal error

0xCC86

Error dual-channel analog input

The difference between the two analog inputs exceeded the configured limits.

Info 0: Number of affected channel

0xCC88

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xCC89

Input error state has changed

Error detected at analog input channel.

If Info 0 = 1:

Channel status has changed

Info 1:

0xXXXX____: old channel status

0x____XXXX: new channel status

If Info 0 = 2:

Analog input range exceeded

Info 1:

0xXXXX____: Channels exceeding upper limit

0x____XXXX: Channels exceeding lower limit

0xCCC2

Parameter error counter input

Invalid parameters for digital inputs

Info 0:

0x0100: Version conflict

0x0200: Length conflict

0x10yy: Counter mode invalid, yy channel number

0x20yy: Counter unit invalid, yy channel number

0x30yy: Counter timebase invalid, yy channel number

0x40yy: Use of safety–related input invalid, yy channel number

0x50yy: Channel not configured as counter input in EcoStruxure Machine Expert - Safety, yy channel number

0x60yy: Counter mode not configured as 'A' in EcoStruxure Machine Expert - Safety, yy channel number

0x70yy: SafeFrequencyInput and the corresponding SafeFrequencyTwoChannelInput are in use, yy channel number, info 1: 0x000000xx two channnel input

0x80yy: Counter mode not configured as 'AA' in EcoStruxure Machine Expert - Safety, yy channel number

0x90yy: Counter mode not configured as 'AA' or 'AB' in EcoStruxure Machine Expert - Safety

0xA0yy: One channel of a dual-channel pair is not configured as counter input in EcoStruxure Machine Expert - Safety, yy channel number. Info 1: 0x00yy00xx: yy, xx channel numbers

Info 1: Configured incorrect value

0xCCC5

Error frequency input

Maximum frequency exceeded.

Info 0: 0xFzyy, yy channel number, z-Mode: 1=A, 2=AA, 3=AB.

Info 1: Frequency in inc/s.

Difference between channels exceeded.

Info 0: 0xDzyy, yy channel number, z-Mode: 1=A, 2=AA, 3=AB.

Info 1: Difference in inc/h.

Difference between AA input channels exceeded.

Info 0: 0xE2yy, yy channel number.

Info 1: Difference in inc/h.

AB evaluation error.

Info 0: 0xA0yy Error AB evaluation for channel yy.

0xCCC6

Error frequency input AB mode

Quadrature decoder error.

Info 0: 0x10yy Timebase not supported.

Info 0: 0x20yy Error AB evaluation for channel yy.

Info 0: 0x30yy AB mode not supported for channel yy.

Info 0: 0x40yy Hardware error for channel yy.

Info 0: 0x80yy-0xC0yy A or AA mode not supported for channel yy.

0xCD82

Parameter error

EcoStruxure Machine Expert - Safety project not compatible with module firmware.

0xD00D

UDID acknowledgement error

Not possible to acknowledge a UDID mismatch

Info 1: SADDR

0xD01E

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xD080

Acknowledgement of module replacement (1 module)

The user has acknowledged a module replacement (1 module).

0xD081

Acknowledgement of module replacement (2 modules)

The user has acknowledged a module replacement (2 modules).

0xD082

Acknowledgement of module replacement (3 modules)

The user has acknowledged a module replacement (3 modules).

0xD083

Acknowledgement of module replacement (4 modules)

The user has acknowledged a module replacement (4 modules).

0xD084

Acknowledgement of module replacement (more than 4 modules)

The user has acknowledged a module replacement (more than 4 modules).

0xD085

Confirmation of a new firmware version

The user has confirmed a new firmware version

0xD087

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xD089

Safety-related module unavailable or condition related to nodeguarding (processor 2)

Safety module not found (SSDO communication to this module not successful).

Info 1: ID of safety-related module

0xD08A

Module is not started due to firmware revision mismatch (processor 2)

The module firmware version does not correlate with parameter MinRequiredFWRev.

Info 0: ID of safety-related module

Info 1: firmware version on the module

0xD08B

Info user action

A user action has been executed due to remote access or SLC ENTER button.

Info 0 = action state:

0x00: The received remote command was valid and will be executed

0x01: ENTER button successful

0x02 .. ENTER button not successful (author, state, ...)

0x03: Remote execution was successful

0x04: Remote execution was not successful (state, ...)

0x05: Remote command is invalid

0x06: Remote ENTER command is invalid

0x07: Remote ENTER commands are not activated in EcoStruxure Machine Expert - Safety application

0x08: Remote ENTER command with incorrect password

0x09: Remote ENTER command is not idle

0x0A: Remote ENTER command is locked by the HMI

0x0B: Remote ENTER command SK-ACKN has no authorization

0x0C: Remote ENTER command FW-ACKN has no authorization

0x0D: Remote ENTER command UDID-ACKN (SMX-CMX) has no authorization

0x0E: SK-ACKN not possible, memory key was not changed

0x0F: FW-ACKN not possible, no different FW was detected

0x10: SMX-ACKN is not possible, replaced modules not equal to 1

0x11: DMX-ACKN is not possible, replaced modules not equal to 2

0x12: TMX-ACKN is not possible, replaced modules not equal to 3

0x13: QMX-ACKN is not possible, replaced modules not equal to 4

0x14: CMX-ACKN is not possible, replaced modules less than 5

0xD08D

Incorrect firmware version, vendor or module type

Firmware version of the safety-related module has not been acknowledged or vendor/module type do not match.

Info 1: ID of safety-related module

0xD08E

Safety module parameter error

The safety-related parameters for the module are not available or could not be downloaded.

Info 1: ID of safety-related module

0xD08F

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xD094

Info Setup Mode

Info Setup Mode

See Info 0 for details.

Info 0:

1: Setup Mode activated during startup

2: Setup Mode activated by user

3: Setup Mode deactivated by user (triggers SLC reboot)

4: Hourly reminder that Setup Mode is active

5: Internal error (initialization)

6: Internal error (execution)

7: Memory key replacement has been confirmed automatically

8: Module replacement has been confirmed automatically

9: Firmware has been acknowledged automatically

0xD120

Maximum frequency exceeded

The measured frequency exceeded the maximum frequency.

0xD125

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xD126

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xD132

Dual-channel evaluation: discrepancy time elapsed (processor 2)

The dual-channel evaluation (PLCopen function block equivalent or antivalent) has detected a discrepancy.

Info 0:

0: dual-channel evaluation = none

1: dual-channel evaluation = equivalent

2: dual-channel evaluation = antivalent

Info 1 syntax: $YZ

Y=1: WAIT FOR CHANNEL 02

Y=2: WAIT FOR CHANNEL 01

Y=3: FROM ACTIVE WAIT

Z=0: channel 1-2

Z=1: channel 3-4

Z=2: channel 5-6

Z=3: channel 7-8

Z=4: channel 9-10

Z=5: channel 11-12

Z=6: channel 13-14

Z=7: channel 15-16

Z=8: channel 17-18

Z=9: channel 19-20

See manual also

0xD141

Input error state has changed (processor 2)

Error detected at safety-related input channel.

Info 1[0]: errors of test pulse outputs (high nibble: high; low nibble: low)

Info 1[1]: input high

The bits of each nibble represent the channels 1-4 (LSB=channel 1)

An error is active if the corresponding bit is set.

All bits 0 if all errors cleared.

Some causes of errors can lead to several bits being set (such as cross circuits)

0xD142

Inoperable hardware

Inoperable hardware has been detected.

0xD143

Input error state has changed (processor 2)

Error detected at safety-related input channel.

Info 0 byte 0: test pulse output low

Info 0 byte 1: test pulse output high

Info 1: input high

Each bit of the info data represents one channel (LSB=channel 1)

An error is active if the corresponding bit is set.

All bits 0 if all errors cleared.

Some causes of errors can lead to several bits being set (such as cross circuits)

0xD146

internal parameter error

The module detected incorrect parameters (output channels used).

0xD151

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xD152

Input value differs between two processors

The input values differ between the two processors. This can be the result of signal chattering caused by different signal propagation times.

0xD1AE

Dual-channel evaluation not activated (processor 2)

Datapoint for dual-channel evaluation is used even though the corresponding dual-channel evaluation is not activated.

Info 0 byte 3: number of the channel whose dual-channel evaluation is not activated.

0xD1B0

Discrepancy time parameter increased

The parameterized value of the discrepancy time has been increased internally.

Info 0: Channel number of the affected channel

Info 1: New discrepancy time

0xD215

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xD220

Output channel test errors cleared (processor 2)

The output channel errors have been cleared (acknowledgment of message 0xD222 or 0xD224)

0xD222

Test status of output has changed (processor 2)

Error detected at safety-related output channel.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

Status in range from 0x00 to 0x1F see table

Both switches off, no current flow

Status Error Channel+ Channel-

%00000000 no - -

%00000001 yes open high

%00000010 yes high open

%00000011 yes high high

Test pulse from high side switch

Status Error Channel+ Channel-

%000x0100 no - -

%000x0101 yes open high

%000x0110 yes high open

%000x0111 yes high high

Test pulse from low side switch

Status Error Channel+ Channel-

%000x1000 yes low -

%000x1001 yes low high

%000x1010 yes - open or low

%000x1011 no - -

Both switches on

Status Error Channel+ Channel-

%000x1100 yes low -

%000x1101 yes low open and high

%000x1110 no - -

%000x1111 yes - high

Both switches off, current flow detected, resulting in non-resettable channel-specific error

Status Error Channel+ Channel-

%00010000 yes -

%00010001 yes open high

%00010010 yes high open

%00010011 yes high high

x - no difference in error handling if 0 or 1

Status is equal to 0x20: overload detected

Status is equal to 0x21: maximum switching frequency exceeded

Status is equal to 0x22: internal error detected

Example: Info 0 = 0x0100, Info 1 = 0x21000020 means:

Channel number: 6 5 4 3 2 1

Channel 1: overload detected

Channel 4: maximum switching frequency exceeded

Channel 6: Both switches off, no current flow, Error, Channel+ open, Channel- high

Channel 2,3,5: Both switches off, no current flow, No Error

0xD224

Test status of output has changed (processor 2)

Error detected at safety-related output channel.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

Both switches off

Channel status Error Output

0x00 no ok

0x01 yes (unrecoverable) undefined

0x02 yes (unrecoverable) undefined

0x03 yes high

Test pulse switch 1

Channel status Error Output

0x04 no ok

0x05 yes (unrecoverable) undefined

0x06 yes (unrecoverable) undefined

0x07 yes high

Test pulse switch 2

Channel status Error Output

0x08 yes (unrecoverable) undefined

0x09 yes (unrecoverable) undefined

0x0A no ok

0x0B yes high

Both switches on

Channel status Error Output

0x0C yes low

0x0D yes low

0x0E yes low

0x0F no ok

Other Errors

Channel status Error Error description

0x1E yes input feed by external 24V detected

0x1F yes channel switched off because the other channel of this connector detected an error

0x20 yes maximum current exceeded

0x21 yes maximum switching frequency exceeded

0x22 yes internal error

Example: Info 0 = 0x0300, Info 1 = 0x2100000F means:

Channel number: 6 5 4 3 2 1

Channel 1: Both switches on, no Error, Output OK

Channel 4: maximum switching frequency exceeded

Channel 6: Both switches off, error detected, output high

Channel 2,3,5: Both switches off, no Error, Output ok

0xD225

Overcurrent error

The total of the current for all outputs has exceeded the maximum value.

0xD226

Error XchangeData: different feedback signals (processor 2)

Error XchangeData: different feedback signals

0xD228

Incorrect activation sequence of SafeCtrl signal and Release signal (processor 2)

An incorrect activation sequence was detected at a safety-related output channel. This does not cause a channel error.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

State is equal to 0x23: Release signal was activated before SafeCtrl signal

State is equal to 0x24: Release signal and SafeCtrl signal were activated simultaneously

0xD229

Test status of output has changed (processor 2)

Error detected at safety-related output channel.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

For safety-related output channels of type A (SOx + / SOx -) see message 0xC222 for detailed descriptions.

For safety-related output channels of type B (SOx / COM) see message 0xC224 for detailed descriptions.

0xD2AC

Output high detected in operating state Pre-Operational (processor 2)

Not all outputs 0 in operating state Pre-Operational.

Info 1: output feedback states (LSB = channel 1)

The affected channels can be found in info 1 and need to be converted to binary format. Two bits each represent one channel (starting with channel 1 corresponding to the LSB).

Example: HEX - A00 corresponds to BIN 1010 0000 0000.

Channels 5 and 6 report an error.

0xD313

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xD315

Maximum switching frequency exceeded (processor 2)

The maximum switching frequency of the module has been exceeded.

The output channel may be switched off up to 5 times per minute at maximum; the minimum interval between two switch-off cycles is 500 ms.

0xD316

Internal error voltage measurement out of range (processor 2)

Internal error voltage measurement out of range

0xD318

Backfeed voltage at the output (processor 2)

Backfeed voltage has been detected at the output of the module

0xD320

Maximum switching frequency exceeded (processor 2)

The maximum switching frequency of the module has been exceeded

0xD321

Channel output state has changed (processor 2)

Channel output state has changed.

Info 1: 1: channel switched to error state.

Info 1: 2: channel error cleared.

0xD322

Incorrect activation sequence of SafeCtrl signal and Release signal

An incorrect activation sequence was detected at a safety-related output channel. This does not cause a channel error.

Info 1 byte 0: status of channel 1

...

Info 1 byte 3: status of channel 4 (if available)

Info 0 byte 0: status of channel 5 (if available)

Info 0 byte 1: status of channel 6 (if available)

State is equal to 0x23: Release signal was activated before SafeCtrl signal

State is equal to 0x24: Release signal and SafeCtrl signal were activated simultaneously

0xD323

Backfeed voltage still present at the output

Detected channel error cannot be reset. Backfeed voltage is still present at the output of the module.

0xD404

OpenSAFETY communication error

OpenSAFETY communication error.

Response:

The safety-related function STO has been activated.

0xD411

Encoder error (Sin²Cos² monitoring)

The monitoring of the sine and cosine traces has detected an error.

Response:

The safety-related function STO has been activated.

0xD412

Encoder error (quadrant monitoring)

Encoder monitoring: A deviation between digital and analog quadrant has been detected.

Response:

The safety-related function STO has been activated.

0xD413

Internal error, Cross comparison of input data

Internal error: Cross comparison of input data not successful.

Response:

Transition of the module to defined safe state.

0xD414

Internal error, Cross comparison of output data

Internal error: Cross comparison of output data not successful.

Response:

Transition of the module to defined safe state.

0xD415

Internal error, Cross communication

Internal error: Transmission error detected during cross communication.

Response:

Transition of the module to defined safe state.

0xD418

Encoder configuration - Encoder resolution different

The configured encoder resolution in EcoStruxure Machine Expert - Safety is different from the encoder resolution which has been reported by the drive.

Response:

Transition to operating state Operational is not possible. Module remains in the operating state Pre-operational.

0xD419

Encoder configuration - Encoder type different

The configured encoder type in EcoStruxure Machine Expert - Safety is different from the encoder type which has been reported by the drive.

Response:

Transition to operating state Operational is not possible. Module remains in the operating state Pre-operational.

0xD41B

Encoder configuration - Encoder resolution invalid

The encoder configuration is invalid. For rotary encoders the encoder resolution must be a power of 2.

Response:

Transition of the module to defined safe state.

0xD41F

Internal error, ADC error

Verification of analog digital converter inputs not successful.

Response:

Transition of the module to defined safe state.

0xD422

Module bootup

The bootup operation of the module has been completed.

0xD423

Operational

The module has transitioned to the operating state Operational.

0xD424

Pre-operational

The module has transitioned to the operating state Pre-operational.

0xD425

Diag Quit

The safety-related functions in the module have been reset.

0xD42E

Safety-related function SMS - speed limit exceeded

The speed of the drive exceeded the value in SMS_SpeedLimit.

Response:

The fallback safety-related function SS1 has been activated.

0xD42F

SDI - incorrect direction

The direction of movement of the motor does not match the configured direction of movement and position tolerance.

Response:

The fallback safety-related function SS1 has been activated.

0xD430

Safety-related function SOS - movement outside of standstill position window

The motor has moved outside the standstill position window configured by parameter SOS_PositionTolerance.

Response:

The fallback safety-related function STO has been activated.

0xD431

Safety-related function SS2 - movement outside of standstill position window

The motor has moved outside the standstill position window configured by parameter SS2_PositionTolerance.

Response:

The fallback safety-related function STO has been activated.

0xD432

Safety-related function SLS1 - Speed limit exceeded

The speed of the motor is greater than the value in SLS1_SpeedLimit.

Response:

The fallback safety-related function SS1 has been activated.

0xD433

Safety-related function SLS2 - Speed limit exceeded

The speed of the motor is greater than the value in SLS2_SpeedLimit

Response:

The fallback safety-related function SS1 has been activated.

0xD434

Safety-related function SLS3 - Speed limit exceeded

The speed of the motor is greater than the value in SLS3_SpeedLimit.

Response:

The fallback safety-related function SS1 has been activated.

0xD435

Safety-related function SLS4 - Speed limit exceeded

The speed of the motor is greater than the value in SLS4_SpeedLimit.

Response:

The fallback safety-related function SS1 has been activated.

0xD436

Safety-related function SS1 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SS1.

Response:

The fallback safety-related function STO has been activated.

0xD437

Safety-related function SS2 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SS2.

Response:

The fallback safety-related function STO has been activated.

0xD438

Safety-related function SLS1 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SLS1

Response:

The fallback safety-related function STO has been activated.

0xD444

Safety-related function SLS2 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SLS2.

Response:

The fallback safety-related function STO has been activated.

0xD445

Safety-related function SLS3 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SLS3.

Response:

The fallback safety-related function STO has been activated.

0xD446

Safety-related function SLS4 - invalid deceleration

The motor speed does not correspond to the deceleration ramp defined for the safety-related function SLS4

Response:

The fallback safety-related function STO has been activated.

0xD447

Speed limit for safety-related function SLS is invalid

The configuration of the speed limits for the safety-related functions SLS and SMS is invalid. The speed limits for the safety-related functions SLS and SMS must meet the following conditions:

SLS1 Speed Limit <= SLS2 Speed Limit <= SLS3 Speed Limit <= SLS4 Speed Limit <= SMS Speed Limit

Response:

Transition to operating state Operational is not possible. Module remains in operating state Pre-operational.

0xD448

SOD CRC invalid

SOD CRC invalid. The parameter set has been transmitted incorrectly or was stored incorrectly in the safety-related module.

Response:

Transition to operating state Operational is not possible. Module remains in the operating state Pre-operational.

0xD449

Module bootup not successful

The safety-related module could not be initialized.

Response:

Transition of the module to defined safe state.

0xD44B

Safety-related function STO active

The safety-related function STO is active. The axis is torque free. The safety-related function STO was requested either by the SLC application, the HW STO input or as fallback for another safety-related function.

0xD44C

Safety-related function SS1 active

The safety-related function SS1 is active. The axis has been stopped and is now torque free. SS1 was requested either by the SLC application or as fallback for another safety-related function.

0xD44F

Safety-related function STO active (Fallback)

The safety-related function STO is active. The axis is torque free. The safety-related function STO was requested as fallback for another safety-related function.

0xD450

Safety-related function SS1 active (Fallback)

The safety-related function SS1 is active. The axis has been stopped and is now torque free. SS1 was requested as fallback for another safety-related function.

0xD451

Safety-related function STO active (HW)

The safety-related function STO is active. The axis is torque free. The safety-related function STO was requested by the physical STO input.

0xD452

Safety-related function STO active (FB deactivated)

The safety-related function STO is active. The axis is torque free. The safety-related function STO was requested because the SF_SafeMotionControl function block was deactivated.

0xD510

Inoperable hardware

Inoperable hardware has been detected.

0xD513

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xD515

Maximum switching frequency exceeded (processor 2)

The maximum switching frequency of the relay has been exceeded

Info 0 = 0

Info 1:

Bit 0 = channel 1

Bit 1 = channel 2

Bit 2 = channel 3

Bit 3 = channel 4

Bit 4 = channel 5

Bit 5 = channel 6

0xD520

Inoperable hardware

Inoperable hardware has been detected.

0xD521

Inoperable hardware

Inoperable hardware has been detected.

0xD522

Internal parameter error

The module detected incorrect parameters (input channels used).

0xD523

Relay supply voltage error

The relay supply voltage is out of limits. The module-internal relay power supply (18 V or 21 V) is affected.

0xD5A4

Inoperable hardware

Inoperable hardware has been detected.

0xD5F4

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xD5F5

Reference input state does not match actual input state

At least one input channel does not have the state defined by the reference channel.

Info 1: differing inputs

Each bit of the info data represents one channel (LSB=channel 1)

An error is active if the corresponding bit is set.

All bits 0 if all errors cleared.

Some causes of errors can lead to several bits being set (such as cross circuits)

0xD605

Inoperable hardware

Inoperable hardware has been detected.

0xD618

Inoperable hardware

Inoperable hardware has been detected.

0xD619

Status of channel error evaluation has changed

Error status of an input has changed

Info 1 syntax: $YYZZ

YY: bitcoded, current channelOK information

ZZ bitcoded channelOK information of last cycle

0xD621

Status of dual-channel evaluation has changed

Signal state of an input has changed

Info 1 syntax: $YYZZ

YY: bitcoded, current signalOK information

ZZ: bitcoded signalOK information of last cycle

0xD622

Status of threshold evaluation has changed

Status of dual-channel evaluation has changed

Info 1 syntax: $YYZZ

YY: bitcoded, current dual-channelOK information

ZZ: bitcoded dual-channelOK information of last cycle

0xD625

Inoperable hardware

Inoperable hardware has been detected.

0xD626

Output current for sensor feed exceeded (processor 2)

Maximum current on outputs used to feed an external sensor was exceeded.

0xD627

No sensor connected

No sensor connected to at least one analog input channel.

Info 1:

Bit 0: Channel 1 not connected

Bit 1: Channel 2 not connected

Bit 2: Channel 3 not connected

...

0xD628

Error during shunt test (processor 2)

Error during shunt test

Info 1 provides information on the affected channel:

0: Input 1

1: Input 2

0xD6A7

Incorrect sensor type

Channel which is used to measure the temperature of the terminal is not set for PTx measurement even though another channel requires it.

Info 1 byte 3: number of the channel who requires the temperature of the terminal.

0xD6A8

Threshold parameter out of range

Threshold parameter is out of range of sensor type of corresponding channel.

Info 0: number of channels with incorrect parameter:

0: channel pair 0102

1: channel pair 0304

2: channel pair 0506

Info 1 byte 1: number of threshold parameter

Info 1 byte 2: type of incorrect threshold parameter:

0: Limit_Threshold_Low

1: Limit_Threshold_High

2: Limit_Threshold_Equivalent

3: Discrepancy_Time

10: Limit_Threshold_High

0xD70C

Error Utilities library: out of range

Info 0: cause of error

1: Overflow in function (Safe) DINT_TO_INT

2: Underflow in function (Safe) DINT_TO_INT

3: Overflow in function (Safe) DWORD_TO_TIME or (Safe) TIME_TO_DWORD

Info 1: absolute value at function input

0xD910

Simultaneous edges on channel A and B

The module repetitively detected simultaneous edges on channels A and B. This is not permissible in mode A-B and A-Ai-B-Bi.

0xD913

Speed differs between the two measurement channels

The speeds which are calculated on the basis of evaluated inputs differ (measurement channels depend on mode used A-A or A-B or A-B and Ai-Bi).

Info 0: permissible difference

Speed values given as set via parameter "Unit"

Info 1, byte 0 and byte 1: speed channel 0

Info 1, byte 2 and byte 3: speed channel 1

0xD914

Countervalue differs between two channels

The countervalues which are calculated on the basis of inputs A-B and Ai-Bi differ.

0xD915

Input A and Ai or input B and Bi are FALSE at the same time

The module repetitively recognized that A and Ai or B and Bi are FALSE at the same time. This is not permissible in mode A-B and A-Ai-B-Bi.

0xD917

Value of SafeFrequency signal out of range

The input frequency is out of range. The value of the SafeFrequency signal must be between -32768 and +32767.

0xD918

Maximum acceleration exceeded.

The measured acceleration exceeded the maximum acceleration

0xD920

Input frequency out of range

The measured frequency is out of range. The module can only measure frequencies up to 7500Hz.

0xD921

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xD922

Channel error not acknowledged

The channel error could not be acknowledged because the measured input frequency is not 0.

0xD923

Channel error acknowledged

The channel error was acknowledged

0xD924

Frequency value differs between two processors

The frequency values which are calculated on the basis of inputs differ between the two processors. This condition can be the result of different signal propagation times between the two processors if there are no appropriate input signals.

0xDA02

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xDA06

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xDA0C

Error importing application files (processor 2)

EcoStruxure Machine Expert - Safety application could not be imported.

No valid application found on the SLC.

0xDA0F

Inoperable hardware

Inoperable hardware has been detected.

0xDA11

Inoperable hardware

Inoperable hardware has been detected.

0xDA16

Flash memory test executed after SLC memory key format

Flash memory test of internal application memory.

This is performed automatically after SLC memory key format.

Result:

OK if message type = info

Error if message type = error

0xDB01

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xDC02

Parameter error digital input

Invalid parameters for digital inputs

Info 0:

0x1000: Version conflict

0x2000: Length conflict

0x30yy: TON filter value too large, yy channel number

0x40yy: TOFF filter value too large, yy channel number

0x50yy: Discrepancy time too long, yy channel number

0x60yy: Dual-channel evaluation invalid, yy channel number

0x70yy: Channel not configured as digital input in EcoStruxure Machine Expert - Safety

0x8000: One channel of a dual- channel pair is not configured as digital input in EcoStruxure Machine Expert - Safety

Info 1: 0x0000xxyy:

xx, yy Channel number(s)

Info 1: Configured incorrect value

0xDC03

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xDC04

Potential subsequent message

This condition can be the result of a system restart or a power outage.

0xDC05

Error digital inputs

An error was detected at at least one digital input.

Info 0:

0x10xx: Error detected during internal hardware tests

--> Info 1: Channel number of affected channel

0x2000: Input data that is different between the two safety-related processors

--> Info 1: Bit information which channels are different

0xDC06

Channel configuration mismatch

A channel configuration in EcoStruxure Machine Expert does not match the channel configuration in EcoStruxure Machine Expert - Safety.

Info 1 indicates the number of the affected channel.

0xDC42

Parameter error digital output

-

0xDC50

Relay test error

An error was detected testing the relays.

Info 0:

0: relay does not switch correctly

1: an output is switched on

Info1 bit-wise shows which output is switched on

0xDC51

Missing relay supply voltage

The module cannot boot because a relay supply voltage is not available.

Info 1:

1: Voltage unavailable at enable pin (pin brown C3)

2: Vcc voltage supply unavailable (one of the brown pins L3, M4, G1, G2)

4: During the relay test, the supply voltage at the enable pin was insufficient

0xDC52

Error digital outputs

Error detected at digital outputs

Info 0:

0: Hardware test of outputs detected an error during runtime or the maximum switching frequency was exceeded

1: Release channel and output channel have been switched on simultaneously

2: Hardware test of outputs detected an error during power up

Info 1: Bit information indicates affected outputs

0xDC53

Indeterminable error digital outputs

Indeterminable error digital outputs

0xDC55

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xDC82

Parameter error analog input

Invalid parameters for analog inputs

Info 0:

0x1000: Version conflict

0x2000: Length conflict

0x30yy: Discrepancy time too long, yy channel number

0x40yy: Dual-channel evaluation invalid threshold

0x50yy: Channel not configured as analog input in EcoStruxure Machine Expert - Safety

0x6000: One channel of a dual-channel pair is not configured as analog input in EcoStruxure Machine Expert - Safety

Info 1: 0x0000xxyy:

xx, yy Channel number(s)

Info 1: Configured incorrect value

0xDC85

Analog input test error

The internal hardware test detected an error.

Info 0:

0xXX01: Error of a channel. Info 1: Channel number

0xXX02: ADC error

0xXX03: CRC error of calibration data

0xXXFF: Internal error

0xDC86

Error dual-channel analog input

The difference between the two analog inputs exceeded the configured limits.

Info 0: Number of affected channel

0xDC88

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xDC89

Input error state has changed

Error detected at analog input channel.

If Info 0 = 1:

Channel status has changed

Info 1:

0xXXXX____: old channel status

0x____XXXX: new channel status

If Info 0 = 2:

Analog input range exceeded

Info 1:

0xXXXX____: Channels exceeding upper limit

0x____XXXX: Channels exceeding lower limit

0xDCC2

Parameter error counter input

Invalid parameters for digital inputs

Info 0:

0x0100: Version conflict

0x0200: Length conflict

0x10yy: Counter mode invalid, yy channel number

0x20yy: Counter unit invalid, yy channel number

0x30yy: Counter timebase invalid, yy channel number

0x40yy: Use of safety–related input invalid, yy channel number

0x50yy: Channel not configured as counter input in EcoStruxure Machine Expert - Safety, yy channel number

0x60yy: Counter mode not configured as 'A' in EcoStruxure Machine Expert - Safety, yy channel number

0x70yy: SafeFrequencyInput and the corresponding SafeFrequencyTwoChannelInput are in use, yy channel number, info 1: 0x000000xx two channnel input

0x80yy: Counter mode not configured as 'AA' in EcoStruxure Machine Expert - Safety, yy channel number

0x90yy: Counter mode not configured as 'AA' or 'AB' in EcoStruxure Machine Expert - Safety

0xA0yy: One channel of a dual-channel pair is not configured as counter input in EcoStruxure Machine Expert - Safety, yy channel number. Info 1: 0x00yy00xx: yy, xx channel numbers

Info 1: Configured incorrect value

0xDCC5

Error frequency input

Maximum frequency exceeded.

Info 0: 0xFzyy, yy channel number, z-Mode: 1=A, 2=AA, 3=AB.

Info 1: Frequency in inc/s.

Difference between channels exceeded.

Info 0: 0xDzyy, yy channel number, z-Mode: 1=A, 2=AA, 3=AB.

Info 1: Difference in inc/h.

Difference between AA input channels exceeded.

Info 0: 0xE2yy, yy channel number.

Info 1: Difference in inc/h.

AB evaluation error.

Info 0: 0xA0yy Error AB evaluation for channel yy.

0xDCC6

Error frequency input AB mode

Quadrature decoder error.

Info 0: 0x10yy Timebase not supported.

Info 0: 0x20yy Error AB evaluation for channel yy.

Info 0: 0x30yy AB mode not supported for channel yy.

Info 0: 0x40yy Hardware error for channel yy.

Info 0: 0x80yy-0xC0yy A or AA mode not supported for channel yy.

0xDD82

Parameter error

EcoStruxure Machine Expert - Safety project not compatible with module firmware.

0xE005

Start bootup

Start bootup

0xE006

Power outage

Shutdown because of 24 V supply voltage outage

0xE007

Reset after user operation

Reboot after user operation

Info 0:

1: internal (after FW-ACKN or project download)

2: remote control

3: new configuration (cycle time or TM5 bus configuration) received from non-safety-related controller

0xE008

Time/date changed

New date/time received from EcoStruxure Machine Expert - Safety

0xE009

Time/date changed

New date and time received from Sercos

0xE00A

New firmware received

New firmware has been downloaded

0xE00C

Firmware download error processor 1

Firmware download to processor 1 not successful

0xE00D

Firmware download error processor 2

Firmware download to processor 2 not successful

0xE00E

SLC memory key unavailable

SLC memory key unavailable or invalid

0xE00F

Mapping CRC error.

CRC of Sercos mapping of EcoStruxure Machine Expert project not equal to CRC of Sercos mapping of EcoStruxure Machine Expert - Safety project.

Info 1 = EcoStruxure Machine Expert - Safety mapping CRC

0xE010

Mapping CRC error.

CRC of Sercos mapping of EcoStruxure Machine Expert project not equal to CRC of Sercos mapping of EcoStruxure Machine Expert - Safety project.

Info 1 = EcoStruxure Machine Expert mapping CRC

0xE011

File has changed

File has changed

Info 0: file number

Info 1: new file size

0xE012

Error during file transfer

Error during file transfer (download)

Info 0: cause of error

0: no error

1: incorrect protocol version

2: file is already open

3: invalid file

4: maximum file size exceeded

5: error during writing data

6: invalid end of file transfer

7: invalid file transfer checksum

8: incorrect destination UDID

9: file too short

10: file may not be written

Info 1: file number in case of file error

0xE013

File transfer successful

File transfer successful

0xE015

File transfer authorization ok

File transfer authorization ok

0xE016

File transfer authorization not ok

File transfer authorization not ok

0xE017

Reboot OK

Reboot OK

0xE018

Reboot not authorized

Reboot not authorized

0xE019

Restart of safety-related processors delayed.

Restart of safety-related processors delayed.

The safety-related processors need to wait until the flash memory file system is ready.

0xE01A

Remote control access

Remote control access

Info 0:

2: success

7: authorization error

Info 1:

0x0060: command "format SLC memory key"

0x0070: command "Reset"

0xE01B

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xE01C

Error asynchronous communication

Error in the asynchronous communication:

Info 0: cause of error

0: error opening connection, info 1 contains the IP address of the destination host

1: connection could be opened (reported only after an open connection error)

2: connection abort (info 1: abort code; see 32175)

3: error received (info 1: internal error code; see 32175)

4: send queue getting full

5: send queue getting empty again

6: no connection available, info 1 contains the SADR of the device for which the connection is unavailable

Info 1: additional error info

0xE01D

Invalid mapping

There is a difference between the data channels in the safety-related application and the data channels of the bus system

Info 1: first invalid mapping object

0x00XXYYYY

XX: Subindex

YYYY: Index

0xE01E

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xE024

Cycle time had to be adjusted

The parametrized SLC cycle time is invalid because it is not an integer multiple of the Sercos cycle time.

An adjusted cycle time is used.

Info 1: Adjusted cycle time in μs

0xE025

Utilization alert communication processor

The maximum utilization level of the communication processor has almost been reached.

Info 1: Idle cycles per second

0xE026

Cycle time alert

The parametrized SLC cycle time is too short.

0xE202

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xE212

Inconsistent SLC memory key files

The SCMAR and its verifier have inconsistent SLC memory key files

0xE213

Inconsistent SLC memory key files

The SCMAR and its verifier have inconsistent SLC memory key files

0xE214

Inconsistent SLC memory key files

The SCMAR and its verifier have inconsistent SLC memory key files

0xE215

Inconsistent SLC memory key files

The SCMAR and its verifier have inconsistent SLC memory key files

0xE216

Invalid SLC memory key ID received

The SLC did not return a valid SLC memory key ID

This condition can be present during initial setup

0xE217

Inconsistent UDID files

The SCMAR and its verifier have inconsistent UDID files

0xE218

Inconsistent UDID files

The SCMAR and its verifier have inconsistent UDID files

0xE219

Inconsistent UDID files

The SCMAR and its verifier have inconsistent UDID files

0xE21A

Inconsistent UDID files

The SCMAR and its verifier have inconsistent UDID files

0xE21B

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE21C

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE21D

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE21E

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE21F

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE220

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE221

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE222

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE223

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE224

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE225

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE226

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE227

Inconsistent firmware revision files

The SCMAR and its verifier have inconsistent firmware revision files

0xE228

Inconsistent firmware revision files

Internal error. The SCMAR and its verifier have inconsistent firmware revision files.

0xE238

Communication with SLC not possible

The SCMAR verifier cannot communicate with the SLC

Info 1: flags of the safety-related register

0: Communication with processor 1 FW not possible

1: Communication with processor 2 FW not possible

2: Bootloader communication with processor 1 active

3: Bootloader communication with processor 2 active

4: Data transfer with processor 1 active (firmware update / parameter download / application memory format)

5: Data transfer with processor 1 active (firmware update / parameter download / application memory format)

6: processor 1 in defined safe state

7: processor 2 in defined safe state

0xE246

SNMT/SSDO frames dropped

SNMT and/or SSDO frames could not be sent

Info 1: number of dropped frames

0xE250

Invalid configuration

This condition can be the result of a version conflict or an invalid project file.

0xE254

Parameter file header length invalid

Internal error. The parameter file header length is invalid

Info 1: length

0xE2D7

Duplicate UDIDs

Duplicate UDIDs were detected

Info 0: ID of safety-related module A

Info 1: ID of safety-related module B

0xE2DE

Invalid firmware revision

Internal error. An invalid firmware revision was detected

Info 1: module address