List of Messages

Code	Short text	Description	Correctives
0x1010	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x101B	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x1115	Connection refused	Another user is already logged in. Further connection attempts not permissible	Only one user can log in to SLC at the same time
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	Restart online connection with valid user ID
0x111C	Message overrun	New message received while old message is still pending	Validate the safety-related system for operating state changes that may trigger unintended logger messages. Verify correct fieldbus connections of devices
0x111F	Invalid socket ID	Invalid socket ID for online connection	Verify Ethernet/TCP settings
0x1138	User ID error	Different user ID than logged in received	Only one online connection permissible at the same time
0x1147	Error setting real time clock	The attempt to set the SLC real time clock was not successful.	Reboot the system. If the error persists, contact your local Schneider Electric representative.
0x1170	Reset command	SLC info message: Reset command requested	-
0x1213	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
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 'Machine Expert - Safety' state "Safe") 0x66 - RUN (defined 'Machine Expert - Safety' state "Safe") 0x99 - HALT (defined 'Machine Expert - Safety' state "Debug") 0xAA - STOP (defined 'Machine Expert - Safety' state "Debug") 0xCC - RUN (defined 'Machine Expert - Safety' state "Debug") 0xF0 - No execution	-
0x1241	Variable error	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	-
0x2017	Input checksum data error	The input checksum data are not equal.	Modify TM5 cycle time Add a (non-existing) additional safety-related module and use at least one channel of it in the 'Machine Expert - Safety' application.
0x2211	Application start not successful	Application could not be started.	Re-compile and re-download projects in ’Machine Expert’ and 'Machine Expert - Safety'.
0x2213	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x3002	Project size exceeded	Insufficient SLC memory for project	Reduce project size.
0x3003	Instruction not implemented or incorrect data type	Instruction not implemented or incorrect data type	Either do not use this instruction or do not use this instruction in conjunction with this data type
0x3004	Maximum size of POU exceeded	The size of the POU code is greater than 64 KB	Reduce the size of the logical POU in the 'Machine Expert - Safety' project If possible, split application by using additional POUs.
0x3043	Maximum size of POU exceeded	Memory Error. Insufficient SLC memory for POU	Reduce the size of the POU
0x3044	Maximum size of POU exceeded	Memory Error. The module size of a POU is greater than 64 KB	Reduce the size of the POU
0x3048	POU inserted	A new POU was inserted into an existing project	-
0x3087	Division by zero	Division by zero	Verify program code
0x308D	Invalid project version	Incorrect project file version number. The project cannot be processed with this SLC firmware	Update SLC firmware
0x3091	Service execution not possible	Service execution not possible	Reset the SLC or download a project
0x3094	Arithmetic overflow	Overflow during an arithmetic operation during execution of the user program.	Verify correct use of arithmetic function blocks (ADD, SUB, MUL, DIV)
0x30A4	Insufficient memory for force list	Memory not sufficient for the forced variables used	Reduce the number of forced variables
0x30A9	Debug watchdog	Debug watchdog (10 minutes) elapsed. The SLC was in debug mode but the client has logged out	Restart TM5CSLC100FS / TM5CSLC200FS.
0x30AC	Too much data, out of memory	Too much data, out of memory	Too many variables in variable status. Visible variables in the open worksheets count for this limit. Close worksheets
0x30C8	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x30E6	Additional information	Additional 16 bit error information	See previous message
0x3235	Invalid memory address	Memory address in compiled 'Machine Expert - Safety' application does not match firmware	Re-compile and re-download 'Machine Expert - Safety' application. Update SLC firmware.
0x48	'Machine Expert - Safety' connected/disconnected	Online connection from 'Machine Expert - Safety' to SLC has been connected or disconnected	-
0x4C	'Machine Expert - Safety' connected/disconnected	Online connection from 'Machine Expert - Safety' to SLC has been connected or disconnected	-
0x55	'Machine Expert - Safety' connected/disconnected	Online connection from 'Machine Expert - Safety' to SLC has been connected or disconnected	-
0x6042	Project file processing not successful	'Machine Expert - Safety' project processing not successful	Re-compile and re-download projects in ’Machine Expert’ and 'Machine Expert - Safety'.
0x604B	Project does not match firmware (project header)	Project does not match firmware. Invalid project header	Re-compile and re-download projects in ’Machine Expert’ and 'Machine Expert - Safety'.
0x604F	Insufficient program memory	Insufficient memory for the application program	Reduce the size of the safety-related project.
0x6055	Too many function calls	Too many function calls	Reduce the number of function calls in the safety-related project
0x6056	Too many function block instances	Too many function block instances	Reduce the number of function blocks used in the safety-related project
0x6057	Too many marker variables	Too many marker variables	Reduce the number of marker variables used in the safety-related project
0x605E	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x607C	Invalid physical I/O start address	I/O buffer start address in compiled 'Machine Expert - Safety' application does not match firmware	Re-compile and re-download 'Machine Expert - Safety' application.
0x608B	Modulo division by zero	Modulo division by zero during execution of the user program.	Verify the code of the safety-related project for modulo arithmetic usage.
0x608C	Arithmetic overflow	Overflow during an arithmetic operation during execution of the user program.	Verify correct use of arithmetic function blocks (ADD, SUB, MUL, DIV)
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.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x8192	No send-buffer available	The message could not be sent because the message queue currently has no free buffers	Increase bandwidth on fieldbus for logger messages
0x8193	Message could not be sent	The SCMAR could not send a message Info 1: message error ID	Increase bandwidth on fieldbus for logger messages
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.	Verify other Safe Logger entries.
0x8403	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x8404	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x8405	Interrupt triggered too early	Interrupt triggered too early. Info 0: Cycle duration	Verify that the cycle time is not too short. Increase cycle time parameter of SLC in 'Machine Expert - Safety'
0x8408	Cycle time error detected	Invalid internal cycle time.	Set valid Sercos cycle time in ’Machine Expert’ project (4 ms maximum).
0x8409	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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 Cycle_Time Info 1: cycle time in μs If Info 0: 0x8000 (SLC only): the value of Cycle_Time is even less than the minimum time for transferring the input or output data via TM5 backplane bus (Info 1: minimum time for transferring the data via TM5 backplane bus)	Increase the value of the 'Machine Expert - Safety' parameter Cycle_Time SLC: decrease cycle times in ’Machine Expert’ (e.g.: 800us for TM5 backplane bus, Sercos)
0x8410	SLC cycle time exceeded	The SCMAR cyclic task was delayed. Info 1: last cycle time in microseconds	Increase the value of the 'Machine Expert - Safety' parameter Cycle Time
0x8412	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x8413	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x8414	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x8417	Error storing local parameter data (processor 1)	Local storing of parameter data not successful Data will be transferred again automatically at next startup	Restart SLC
0x8418	Slot time info	Info 0: slot number Info 1: time in μs	-
0x8481	Invalid firmware	Invalid firmware	Use latest firmware.
0x8510	'Machine Expert - Safety' user info	User info of 'Machine Expert - Safety' connection.	-
0x8511	'Machine Expert - Safety' login	'Machine Expert - Safety' connection established	-
0x8512	'Machine Expert - Safety' logout	'Machine Expert - Safety' connection closed	-
0x8515	Generic string message	Generic string message from '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.	Verify other Safe Logger entries.
0x8601	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8602	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8604	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8606	Error detected voltage monitoring	Error detected monitoring supply voltage or temperature	This may be a subsequent error. Verify previous Safe Logger entries. Verify supply voltage and temperature
0x8607	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x8609	Supply voltage error	Supply voltage out of limits	Verify that you use a stable supply voltage within the specified range
0x860A	Temperature error	Temperature in the module is too high or too low	Operate the product within the environmental specifications.
0x860B	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x8611	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
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.	Verify other Safe Logger entries.
0x8805	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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.	Reduce the size of the 'Machine Expert - Safety' application Use larger memory key
0x880B	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x880C	'Machine Expert - Safety' project not available	One or more files of the 'Machine Expert - Safety' project are not available	Download a valid 'Machine Expert - Safety' project
0x8AA2	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x8B00	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C12	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C13	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C14	BS IDENT verification not successful	Verification of bootloader identification unsuccessful.	Replace device
0x8C15	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C16	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C17	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x8C18	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C19	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C20	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C21	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x8C22	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x9100	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x9402	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x9403	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x9404	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x9405	Interrupt triggered too early	Interrupt triggered too early. Info 0: Cycle duration	Verify that the cycle time is not too short. Increase cycle time parameter of SLC in 'Machine Expert - Safety'
0x9408	Cycle time error detected	Invalid internal cycle time.	Set valid Sercos cycle time in ’Machine Expert’ project (4 ms maximum).
0x9409	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x940E	SLC Cycle time exceeded (processor 2)	SLC cycle time value is greater than permissible value according to parameter Cycle_Time Info 1: cycle time in μs If info 0: 0x8000 (SLC only): the value of Cycle_Time is even less than the minimum time for transferring the input or output data via TM5 backplane bus (Info 1: minimum time for transferring the data via TM5 backplane bus)	Increase the value of the 'Machine Expert - Safety' parameter Cycle_Time SLC: decrease cycle times in ’Machine Expert’ (e.g.: 800us for TM5 backplane bus, Sercos)
0x9412	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x9413	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x9414	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x9417	Error storing local parameter data (processor 2)	Local storing of parameter data not successful Data will be transferred again automatically at next startup	Restart SLC
0x9418	Slot time info	Info 0: slot number Info 1: time in μs	-
0x9481	Invalid firmware	Invalid firmware	Use latest firmware.
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.	Verify other Safe Logger entries.
0x9601	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9602	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9604	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9605	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9606	Error detected voltage monitoring	Error detected monitoring supply voltage or temperature	This may be a subsequent error. Verify previous Safe Logger entries. Verify supply voltage and temperature
0x9607	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x9609	Supply voltage error	Supply voltage out of limits	Verify that you use a stable supply voltage within the specified range
0x960A	Temperature error	Temperature in the module is too high or too low	Operate the product within the environmental specifications.
0x960B	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
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.	Replace the affected device.
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.	Verify other Safe Logger entries.
0x9805	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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.	Reduce the size of the 'Machine Expert - Safety' application Use larger memory key
0x980B	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0x980C	'Machine Expert - Safety' project not available	One or more files of the 'Machine Expert - Safety' project are not available	Download a valid 'Machine Expert - Safety' project
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.	Replace the affected device.
0x9C12	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9C13	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9C14	BS IDENT verification not successful	Verification of bootloader identification unsuccessful.	Replace device
0x9C15	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9C16	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9C17	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0x9C18	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9C19	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9C20	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9C21	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0x9C22	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xA101	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA107	SOD read error. The SLC memory key may be empty.	SOD read error. The project on the SLC memory key may be invalid.	Download project with 'Machine Expert - Safety'
0xA10E	SDO abort received	Error SDO communication Info 1: abort code Abort code description 0x05030000 Reserved 0504 0000h SSDO protocol timed out 0504 0001h Client/server Command ID invalid 0504 0002h Invalid block size 0504 0003h Invalid sequence number 0504 0004h Reserved 0504 0005h Out of memory 0601 0000h Unsupported access to an object 0601 0001h Attempt to read a write-only object 0601 0002h Attempt to write a read-only object 0602 0000h Object does not exist in the object dictionary 0604 0041h Object cannot be mapped to the SPDO 0604 0042h The number and length of the objects to be mapped would exceed SPDO length 0604 0043h General parameter incompatibility 0604 0047h General internal incompatibility in the device 0606 0000h Access not successful due to a hardware error 0607 0010h Data type does not match, length of service parameter does not match 0607 0012h Data type does not match, length of service parameter too high 0607 0013h Data type does not match, length of service parameter too low 0609 0011h Subindex does not exist 0609 0030h Value range of parameter exceeded (only for write access) 0609 0031h Value of parameter written too high 0609 0032h Value of parameter written too high 0609 0036h Value of parameter written too high 0800 0000h Value of parameter written too high 0800 0020h Data cannot be transferred or stored to the application 0800 0021h Data cannot be transferred or stored to the application because of local control 0800 0022h Data cannot be transferred or stored to the application because of the present device state 0800 0023h Data cannot be transferred or stored to the application because application is busy	Potential version conflict Use latest versions Verify compatibility of the SLC with 'Machine Expert - Safety' This condition occurs in 'Machine Expert - Safety' - if an SLC is used whose onboard flash memory already contains an application - and if this application was generated with former SoSafe Programmable version - or if the size of the application in the onboard flash memory is greater than that of the SoSafe Programmable application on the SLC memory key Potential solutions: Solution a): Use the chosen 'Machine Expert - Safety' version, compile and download the application. Solution b): If solution a is not possible, erase the onboard flash memory of the SLC.
0xA10F	SDO abort received from node	Error SDO communication Low word of Info 1: ID of safety-related module	Potential version conflict Use latest versions For SLC see also help text of Safe Logger message 0xA10E
0xA114	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA115	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA116	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA317	Error detected in memory block frame transmission	Memory block for frame transmission cannot be passed to unit SHNF.	If this error is detected on an SLC, update to latest SLC firmware.
0xA513	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA514	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA64D	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA64E	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA742	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA743	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA744	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA745	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA746	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA747	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA748	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA749	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA74A	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA74B	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA74C	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA74D	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA74E	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA74F	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA750	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA751	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA752	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA753	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA754	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA755	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA756	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA757	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA758	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA759	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA75A	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA840	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xA841	Delay for extended Consecutive Timers too long	The delay between two received extended Consecutive Timers on the RxSPDO is too long	- Reconfigure your network for shorter network cycle times - Reconfigure a shorter data duration in your safety-related application - Verify available bandwidth on fieldbus for safety-related communication
0xA842	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xAB1B	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xAF01	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xAF0C	Module initialization not successful	Module could not be initialized with the available parameters	Re-compile and re-download 'Machine Expert - Safety' project
0xAF18	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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.	Re-acknowledge all modules on SLC
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	Re-compile and re-download the safety-related application using the latest 'Machine Expert - Safety' version.
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	Verify SLC memory key (mounting, corrosion, integrity) Re-compile and re-download the safety-related application using the latest 'Machine Expert - Safety' version.
0xAF21	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xAF23	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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	Parameter error: Version conflict (the firmware of the module is not compatible with the device file, with 'Machine Expert - Safety', or with the SLC). Install the latest updates. Compile and download in ’Machine Expert’ and 'Machine Expert - Safety'. Encoder error: Encoder replacement must be acknowledged.
0xAF43	Transition to operating state Operational	-	-
0xAF44	Transition to operating state Pre-operational	-	-
0xAF48	SPDO transmit queue is full	SPDO transmit queue is full	Verify bandwidth on fieldbus for exchange of safety-related data
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.	Verify that there are no unavailable modules and that the network connection is stable
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.	Verify the timing parameters in 'Machine Expert - Safety'. Check for unavailable modules.
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.	Verify parameters for safety-related communication Verify that the network is stable
0xAF6E	Invalid initial value for the 40 bit CT connection	An invalid initial value for the 40 bit CT openSAFETY connection was calculated.	Update SLC firmware
0xB101	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xB107	SOD read error. The SLC memory key may be empty.	SOD read error. The project on the SLC memory key may be invalid.	Download project with 'Machine Expert - Safety'
0xB317	Error detected in memory block frame transmission	Memory block for frame transmission cannot be passed to unit SHNF.	If this error is detected on an SLC, update to latest SLC firmware.
0xBF01	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xBF0C	Module initialization not successful	Module could not be initialized with the available parameters	Re-compile and re-download 'Machine Expert - Safety' project
0xBF18	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xBF23	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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	Parameter error: Version conflict (the firmware of the module is not compatible with the device file, with 'Machine Expert - Safety', or with the SLC). Install the latest updates. Compile and download in ’Machine Expert’ and 'Machine Expert - Safety'. Encoder error. Encoder replacement must be acknowledged.
0xBF43	Transition to operating state to Operational	-	-
0xBF44	Transition to operating state Pre-operational	-	-
0xBF48	SPDO transmit queue is full	SPDO transmit queue is full	Verify bandwidth on fieldbus for exchange of safety-related data
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.	Verify that there are no unavailable modules and that the network connection is stable
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.	Verify the timing parameters in the 'Machine Expert - Safety'. Check for unavailable modules.
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.	Verify parameters for safety-related communication Verify that the network is stable
0xBF6E	Invalid initial value for the 40 bit CT connection	An invalid initial value for the 40 bit CT openSAFETY connection was calculated.	Update SLC firmware
0xC00D	UDID acknowledgement error	Not possible to acknowledge a UDID mismatch Info 1: SADDR	Also see description of error number 0x8409
0xC019	Error external startup flags	Error external startup flags Info 0: 0: Feature not enabled in 'Machine Expert - Safety' application 1: Both flags are set (only 1 permissible) 2: Module not available (flags may only be provided for modules that are available in the application) 3: Feature enabled in 'Machine Expert - Safety' but no flags downloaded Info 1: ID of the affected safety-related module (not for Info 0 = 0 or Info 0 = 3)	Info 0: 0: Verify parameter in application or format SLC memory key 1: or 2: Verify file 3: Download the file
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)	Verify remote control access
0xC01E	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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	Update the firmware of the module
0xC07F	Clear Data file deleted	A file was deleted via the command "Clear Data" Info 1: deleted file 1: Remanent Data File 2: Additional Parameter 3: Configuration file from the standard application 4: Extended machine options 5: Table objects	-
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.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xC089	Safety-related module unavailable or nodeguarding error (processor 1)	Safety-related module not found (SSDO communication to this module not successful). Info 1: ID of safety-related module	Verify that the module is valid in 'Machine Expert - Safety' and ’Machine Expert’ Verify network parameters This message can be the result of redundancy master switching even though the module is still running
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	Update your firmware to a valid version.
0xC08B	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, 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 'Machine Expert - Safety' application 0x08: remote ENTER command with incorrect password 0x09: remote ENTER command is not idle (last not ready, too many) 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, SK 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 < 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 SLC hex switch (e.g. 0 = TEST, see SLC Hardware Guide)	-
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	Error 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	Acknowledge firmware (FW-ACKN) Verify that the intended module has been connected. Verify that the safety-related application and the non-safety-related application match.
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	Verify the safety-related application
0xC08F	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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.	Verify ModuleOk in ’Machine Expert’ and 'Machine Expert - Safety' (must be 1) Check flashing sequence of communication LEDs of safety-related module. Restart SLC. Verify 24V I/O voltage. Verify Safe Logger for messages from SLC
0xC120	Maximum frequency exceeded	The measured frequency exceeded the maximum frequency.	Verify input signal
0xC125	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xC126	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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	Verify correct wiring and switch and respectively the parameter for discrepancy time
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)	Verify correct wiring.
0xC142	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
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)	Verify correct wiring.
0xC151	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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.	Verify correct wiring Verify input signals. If this message is generated as a result of chattering (contact bouncing), it can be ignored.
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.	Activate dual-channel evaluation for the corresponding channel or do not use this datapoint in the safety-related application.
0xC1AF	Parameter error: guard door interlock function block (processor 1)	Parameter error: guard door interlock function block	Verify parameter Potential version conflict
0xC215	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xC220	Output channel test errors cleared (processor 1)	The output channel errors have 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	Verify correct wiring Verify parameter "maximum switching frequency" (if available) Verify load After the cause of the error has been removed: switch off and on the affected channel
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	Verify correct wiring Verify parameter "maximum switching frequency" (I/O Configuration in ’Machine Expert’) Verify load
0xC225	Overcurrent error	The total of the current for all outputs has exceeded the maximum value.	Verify correct wiring
0xC226	Error XchangeData: different feedback signals (processor 1)	Error XchangeData: different feedback signals	Verify correct wiring
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	Verify correct connection of Release signal and SafeCtrl signal.
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.	Verify correct wiring Verify load
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)	Verify correct wiring.
0xC313	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
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.	Verify switching frequency used Get maximum switching frequency from data sheet
0xC316	Internal error voltage measurement out of range (processor 1)	Internal error voltage measurement out of range	Verify maximum switching frequency Verify correct wiring (check for backfeed voltage at output) Retry after power cycle of the module Replace the module and retry
0xC318	Backfeed voltage at the output (processor 1)	Backfeed voltage has been detected at the output of the module	Verify correct wiring
0xC320	Maximum switching frequency exceeded (processor 1)	The maximum switching frequency of the module has been exceeded	Verify correct switching frequency The maximum switching frequency is indicated in the data sheet
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.	Verify correct wiring This may be a subsequent error. Verify previous Safe Logger entries.
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	Verify correct connection of Release signal and SafeCtrl signal.
0xC404	OpenSAFETY communication error	OpenSAFETY communication error. Response: The safety-related function STO has been activated.	An openSAFETY communication error can be a subsequent error of an interruption of the Sercos communication. Remove the Sercos communication interruption. Verify the configuration of the parameters in 'Machine Expert - Safety' pertaining to the safety-related response time (MinDataTransportTime, MaxDataTransportTime, CommunicationWatchdog).
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.	Verify the encoder cable. Verify motor and drive.
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.	Verify the encoder cable. Verify motor and drive.
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.	This error can occur during a reboot of the device. Verify the other logger messages.
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.	This error can occur during a reboot of the device. Verify the other logger messages.
0xC415	Internal error, Cross communication	Internal error: Transmission error detected during cross communication. Response: Transition of the module to defined safe state.	This error can occur during a reboot of the device. Verify the other logger messages.
0xC418	Encoder configuration - Encoder resolution different	The configured encoder resolution in '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.	Verify configured encoder resolution in 'Machine Expert - Safety' Verify correct assignment of device
0xC419	Encoder configuration - Encoder type different	The configured encoder type in '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.	Verify configured encoder type in 'Machine Expert - Safety' Verify correct assignment of device
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.	Verify configured encoder resolution in 'Machine Expert - Safety'.
0xC41F	Internal error, ADC error	Verification of analog digital converter inputs not successful. Response: Transition of the module to defined safe state.	This error can occur during a reboot of the device. Verify the other logger messages.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify correct configuration of the speed limits for the safety-related functions SLS and SMS.
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.	Verify correct installation of system (wiring, supplies, etc.)
0xC449	Module bootup not successful	The safety-related module could not be initialized. Response: Transition of the module to defined safe state.	Verify correct installation of the safety-related module and correct settings of the jumpers. If this condition persists, contact your local Schneider Electric representative.
0xC44B	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.	Verify the SLC application Verify the HW STO input of the device. Verify the parameter HW_STO_Config. Check whether a position / speed limit of another safety-related function has been exceeded.
0xC44C	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.	Verify the SLC application. Check whether a position / speed limit of another safety-related function has been exceeded.
0xC510	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xC513	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xC515	Maximum switching frequency exceeded (processor 1)	The maximum switching frequency of the relay has been exceeded	Verify correct switching frequency
0xC520	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xC521	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xC5A4	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xC5F4	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
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)	Verify wiring of inputs
0xC605	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xC618	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xC619	Status of channel error evaluation has changed	Error status of an input has changed Info 1 syntax: $YYZZ YY: bitcoded, channelOK information ZZ: bitcoded channelOK information of last cycle	Verify correct wiring of connected sensors.
0xC621	Status of dual-channel evaluation has changed	Signal state of an input has changed Info 1 syntax: $YYZZ YY: bitcoded, signalOK information ZZ: bitcoded signalOK information of last cycle	Verify correct wiring of connected sensors and the settings of the threshold parameters.
0xC622	Status of threshold evaluation has changed	Status of dual-channel evaluation has changed Info 1 syntax: $YYZZ YY: bitcoded, dual-channelOK information ZZ: bitcoded dual-channelOK information of last cycle	Verify correct wiring of connected sensors and the settings of the threshold parameters and the discrepancy time.
0xC625	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xC626	Output current for sensor feed exceeded (processor 1)	Maximum current on outputs used to feed an external sensor was exceeded.	Verify correct wiring of connected sensors.
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 ...	Verify correct wiring Unused inputs of the thermocouple of the TM5STI4ATCFS module must be jumpered.
0xC628	Error during shunt test (processor 1)	Error during shunt test	Verify input signal See description of parameter DisableShunttest in the guide "'Machine Expert - Safety' Safety Modules Parameters".
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.	Verify that connected sensor matches configured sensor type
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	Verify threshold parameters and compare with range of set sensor type.
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	Verify the input value of the relevant function block
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.	Verify correct wiring.
0xC913	Speed differs between two channels	The speeds which are calculated on the basis of inputs A-B and Ai-Bi differ. Info 0: permissible difference Speed unit 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	Verify correct wiring Verify input signals
0xC914	Countervalue differs between two channels	The countervalues which are calculated on the basis of inputs A-B and Ai-Bi differ.	Verify correct wiring Verify input signals
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.	Verify correct wiring.
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.	Verify input signal Verify setting of parameter "Unit"
0xC918	Maximum acceleration exceeded	The measured acceleration exceeded the maximum acceleration	Verify input signal
0xC920	Input frequency out of range	The measured frequency is out of range. The module can only measure frequencies up to 7500Hz.	Verify input signal
0xC921	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xC922	Channel error not acknowledged	The channel error could not be acknowledged because the measured input frequency is not 0.	Verify input signal
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.	Verify correct wiring Verify input signals
0xCA02	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xCA06	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xCA0C	Error importing application files (processor 1)	'Machine Expert - Safety' application could not be imported. No valid application found on the SLC.	Re-download the 'Machine Expert - Safety' application.
0xCA0D	'Machine Expert - Safety' application download finished	A new 'Machine Expert - Safety' application has been downloaded to SLC. SLC will restart.	-
0xCA0F	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xCA11	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xCA13	Reset due to SCMAR restart	SLC restarted due to restart of SCMAR	-
0xCA15	Too many TM5 backplane bus input data errors	Too many errors detected during demultiplexing TM5 backplane bus input data frames.	Verify proper connection of TM5 backplane bus
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	If the message type is "Error", replace the hardware module.
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 'Machine Expert - Safety')	Reduce cycle times in ’Machine Expert’ (TM5 backplane bus, Sercos, Inter-Network-Crosslink-Task) and ensure that they are synchronous (for example: 800 μs each). Increase SafetyResponseTimeDefaults parameters in 'Machine Expert - Safety'.
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: External machine options inconsistent Info 1: 0x01: Machine option download will start again automatically 0x02: External machine options activated, but not configured	-
0xCB01	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xD00D	UDID acknowledgement error	Not possible to acknowledge a UDID mismatch Info 1: SADDR	Also see description of error number 0x8409
0xD019	Error external startup flags	Error external startup flags Info 0: 0: Feature not enabled in 'Machine Expert - Safety' application 1: Both flags are set (only 1 permissible) 2: Module not available (flags may only be provided for modules that are available in the application) 3: Feature enabled in 'Machine Expert - Safety' but no flags downloaded Info 1: ID of the affected safety-related module (not for info 0:0 or info 0: 3)	Info 0: 0: Verify parameter in application or format SLC memory key 1 or 2: Verify file 3: Download the file
0xD01E	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xD07F	Clear Data file deleted	A file was deleted via the command "Clear Data" Info 1: deleted file 1: Remanent Data File 2: Additional Parameter 3: Configuration file from the standard application 4: Extended machine options 5: Table objects	-
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.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xD089	Safety module unavailable or nodeguarding error (processor 2)	Safety module not found (SSDO communication to this module not successful). Info 1: ID of safety-related module	Verify that the module is valid in 'Machine Expert - Safety' and ’Machine Expert’ Verify network parameters This message can be the result of redundancy master switching even though the module is still running
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	Update your firmware to a valid version.
0xD08D	Error 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	Acknowledge firmware (FW-ACKN) Verify that the intended module has been connected. Verify that the safety-related application and the non-safety-related application match.
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	Verify the safety-related application
0xD08F	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xD120	Maximum frequency exceeded	The measured frequency exceeded the maximum frequency.	Verify input signal
0xD125	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xD126	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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	Verify correct wiring and switch and respectively the parameter for discrepancy time
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)	Verify correct wiring.
0xD142	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
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)	Verify correct wiring.
0xD151	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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.	Verify correct wiring Verify input signals. If this message is generated as a result of chattering (contact bouncing), it can be ignored.
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.	Activate dual-channel evaluation for the corresponding channel or do not use this datapoint in the safety-related application.
0xD215	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xD220	Output channel test errors cleared (processor 2)	The output channel errors have cleared (acknowledgement 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	Verify correct wiring Verify parameter "maximum switching frequency" (if available) Verify load After the cause of the error has been removed: switch off and on the affected channel
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	Verify correct wiring Verify parameter "maximum switching frequency" (I/O Configuration in ’Machine Expert’) Verify load
0xD225	Overcurrent error	The total of the current for all outputs has exceeded the maximum value.	Verify correct wiring
0xD226	Error XchangeData: different feedback signals (processor 2)	Error XchangeData: different feedback signals	Verify correct wiring
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	Verify correct connection of Release signal and SafeCtrl signal.
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.	Verify correct wiring Verify load
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)	Verify correct wiring.
0xD313	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
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.	Verify switching frequency used Get maximum switching frequency from data sheet
0xD316	Internal error voltage measurement out of range (processor 2)	Internal error voltage measurement out of range	Verify maximum switching frequency Verify correct wiring (check for backfeed voltage at output) Retry after power cycle of the module Replace the module and retry
0xD318	Backfeed voltage at the output (processor 2)	Backfeed voltage has been detected at the output of the module	Verify correct wiring
0xD320	Maximum switching frequency exceeded (processor 2)	The maximum switching frequency of the module has been exceeded	Verify correct switching frequency The maximum switching frequency is indicated in the data sheet
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.	Verify correct wiring This may be a subsequent error. Verify previous Safe Logger entries.
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	Verify correct connection of Release signal and SafeCtrl signal.
0xD404	OpenSAFETY communication error	OpenSAFETY communication error. Response: The safety-related function STO has been activated.	An openSAFETY communication error can be a subsequent error of an interruption of the Sercos communication. Remove the Sercos communication interruption. Verify the configuration of the parameters in 'Machine Expert - Safety' pertaining to the safety-related response time (MinDataTransportTime, MaxDataTransportTime, CommunicationWatchdog).
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.	Verify the encoder cable. Verify motor and drive.
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.	Verify the encoder cable. Verify motor and drive.
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.	This error can occur during a reboot of the device. Verify the other logger messages.
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.	This error can occur during a reboot of the device. Verify the other logger messages.
0xD415	Internal error, Cross communication	Internal error: Transmission error detected during cross communication. Response: Transition of the module to defined safe state.	This error can occur during a reboot of the device. Verify the other logger messages.
0xD418	Encoder configuration - Encoder resolution different	The configured encoder resolution in '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.	Verify configured encoder resolution in 'Machine Expert - Safety' Verify correct assignment of device
0xD419	Encoder configuration - Encoder type different	The configured encoder type in '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.	Verify configured encoder type in 'Machine Expert - Safety' Verify correct assignment of device
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.	Verify configured encoder resolution in 'Machine Expert - Safety'.
0xD41F	Internal error, ADC error	Verification of analog digital converter inputs not successful. Response: Transition of the module to defined safe state.	This error can occur during a reboot of the device. Verify the other logger messages.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify the motion profile of the drive. Verify the control loop parameters of the drive.
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.	Verify correct configuration of the speed limits for the safety-related functions SLS and SMS.
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.	Verify correct installation of system (wiring, supplies, etc.)
0xD449	Module bootup not successful	The safety-related module could not be initialized. Response: Transition of the module to defined safe state.	If jumper X8 is connected to the Lexium 62 ILM device, remove the jumper If this condition persists, contact your local Schneider Electric representative.
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.	Verify the SLC application Verify the HW STO input of the device. Verify the parameter HW_STO_Config. Check whether a position / speed limit of another safety-related function has been exceeded.
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.	Verify the SLC application. Check whether a position / speed limit of another safety-related function has been exceeded.
0xD510	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xD513	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xD515	Maximum switching frequency exceeded (processor 2)	The maximum switching frequency of the relay has been exceeded	Verify correct switching frequency
0xD520	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xD521	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xD5A4	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xD5F4	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
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)	Verify wiring of inputs
0xD605	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xD618	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xD619	Status of channel error evaluation has changed	Error status of an input has changed Info 1 syntax: $YYZZ YY: bitcoded, channelOK information ZZ bitcoded channelOK information of last cycle	Verify correct wiring of connected sensors.
0xD621	Status of dual-channel evaluation has changed	Signal state of an input has changed Info 1 syntax: $YYZZ YY: bitcoded, signalOK information ZZ: bitcoded signalOK information of last cycle	Verify correct wiring of connected sensors and the settings of the threshold parameters.
0xD622	Status of threshold evaluation has changed	Status of dual-channel evaluation has changed Info 1 syntax: $YYZZ YY: bitcoded, dual-channelOK information ZZ: bitcoded dual-channelOK information of last cycle	Verify correct wiring of connected sensors and the settings of the threshold parameters and the discrepancy time.
0xD625	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xD626	Output current for sensor feed exceeded (processor 2)	Maximum current on outputs used to feed an external sensor was exceeded.	Verify correct wiring of connected sensors.
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 ...	Verify correct wiring Unused inputs of the thermocouple of the TM5STI4ATCFS module must be jumpered.
0xD628	Error during shunt test (processor 2)	Error during shunt test	Verify input signal See description of parameter DisableShunttest in the guide "'Machine Expert - Safety' Safety Modules Parameters".
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.	Verify that connected sensor matches configured sensor type
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	Verify threshold parameters and compare with range of set sensor type.
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	Verify the input value of the relevant function block
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.	Verify correct wiring.
0xD913	Speed differs between two channels	The speeds which are calculated on the basis of inputs A-B and Ai-Bi differ. Info 0: permissible difference Speed unit 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	Verify correct wiring Verify input signals
0xD914	Countervalue differs between two channels	The countervalues which are calculated on the basis of inputs A-B and Ai-Bi differ.	Verify correct wiring Verify input signals
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.	Verify correct wiring.
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.	Verify input signal Verify setting of parameter "Unit"
0xD918	Maximum acceleration exceeded.	The measured acceleration exceeded the maximum acceleration	Verify input signal
0xD920	Input frequency out of range	The measured frequency is out of range. The module can only measure frequencies up to 7500Hz.	Verify input signal
0xD921	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xD922	Channel error not acknowledged	The channel error could not be acknowledged because the measured input frequency is not 0.	Verify input signal
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.	Verify correct wiring Verify input signals
0xDA02	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xDA06	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
0xDA0C	Error importing application files (processor 2)	'Machine Expert - Safety' application could not be imported. No valid application found on the SLC.	Re-download the 'Machine Expert - Safety' application.
0xDA0F	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
0xDA11	Inoperable hardware	Inoperable hardware has been detected.	Replace the affected device.
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	If the message type is "Error", replace the hardware module.
0xDB01	Potential subsequent message	This condition can be the result of a system restart or a power outage.	Verify other Safe Logger entries.
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	-
0xE008	Time/date changed	New date/time received from Sercos	-
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	Use latest versions. Re-download the firmware Replace hardware
0xE00D	Firmware download error processor 2	Firmware download to processor 2 not successful	Use latest versions. Re-download the firmware Replace hardware
0xE00E	SLC memory key unavailable	SLC memory key unavailable or invalid	Plug in correctly working SLC memory key
0xE00F	Mapping CRC error.	CRC of Sercos mapping of ’Machine Expert’ project not equal to CRC of Sercos mapping of 'Machine Expert - Safety' project. Info 1 = 'Machine Expert - Safety' mapping CRC	Recompile and download ’Machine Expert’ project and 'Machine Expert - Safety' project.
0xE010	Mapping CRC error.	CRC of Sercos mapping of ’Machine Expert’ project not equal to CRC of Sercos mapping of 'Machine Expert - Safety' project. Info 1 = ’Machine Expert’ mapping CRC	Recompile and download ’Machine Expert’ project and 'Machine Expert - Safety' project.
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	Reboot the SLC and retry. Recompile and redownload the safety-related application
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	Verify the password for the authorization
0xE017	Reboot OK	Reboot OK	-
0xE018	Reboot not authorized	Reboot not authorized	Verify the password for the reboot command
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: 0x6000: command "format SLC memory key"	-
0xE01B	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
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	Some versions of SLC generate 2 of these messages (with Info 0 = 0 and Info 0 = 1) upon every bootup. The messages can be ignored. Ensure that the safety-related project and the project of the target controller correspond. Ensure that there is sufficient asynchronous bandwidth available in the network. This condition can be the result of redundancy master switching even if the modules are still running.
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	Ensure that the safety-related application and the non-safety-related application match. Compile and download the non-safety-related application. Compile and download the safety-related application. With certain versions, this condition can be the result of unused safety-related modules in the ’Machine Expert’ project (no channels mapped).
0xE01E	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xE202	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xE212	Inconsistent SLC memory key files	The SCMAR and its verifier have inconsistent SLC memory key files	Both files were deleted automatically. Re-acknowledge the SLC memory key.
0xE213	Inconsistent SLC memory key files	The SCMAR and its verifier have inconsistent SLC memory key files	Both files were deleted automatically. Re-acknowledge the SLC memory key.
0xE214	Inconsistent SLC memory key files	The SCMAR and its verifier have inconsistent SLC memory key files	Both files were deleted automatically. Re-acknowledge the SLC memory key.
0xE215	Inconsistent SLC memory key files	The SCMAR and its verifier have inconsistent SLC memory key files	Both files were deleted automatically. Re-acknowledge the SLC memory key.
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	Acknowledge SLC memory key exchange Restart system
0xE217	Inconsistent UDID files	The SCMAR and its verifier have inconsistent UDID files	Both files were deleted automatically. Re-acknowledge the safety-related modules
0xE218	Inconsistent UDID files	The SCMAR and its verifier have inconsistent UDID files	Both files were deleted automatically. Re-acknowledge the safety-related modules
0xE219	Inconsistent UDID files	The SCMAR and its verifier have inconsistent UDID files	Both files were deleted automatically. Re-acknowledge the safety-related modules
0xE21A	Inconsistent UDID files	The SCMAR and its verifier have inconsistent UDID files	Both files were deleted automatically. Re-acknowledge the safety-related modules
0xE21B	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE21C	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE21D	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE21E	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE21F	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE220	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE221	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE222	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE223	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE224	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE225	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE226	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
0xE227	Inconsistent firmware revision files	The SCMAR and its verifier have inconsistent firmware revision files	Both files were deleted automatically. Re-acknowledge the firmware revisions
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	Verify bandwidth on fieldbus for safety-related communication
0xE250	Invalid configuration	This condition can be the result of a version conflict or an invalid project file.	Use the latest versions. Format the SLC memory key, re-compile the project in 'Machine Expert - Safety' and re-download the application to the SLC.
0xE254	Parameter file header length invalid	Internal error. The parameter file header length is invalid Info 1: length	Invalid data sets can be a result of too frequent safety-related application downloads. SCMAR processes are restarted after download and the next download may not be started until they have finished their restart. The state can be checked by means of function block safeRemoteControl().
0xE2D7	Duplicate UDIDs	Duplicate UDIDs were detected Info 0: ID of safety-related module A Info 1: ID of safety-related module B	Replace one of the modules
0xEF01	Message from Bihl+Wiedemann AS-i Safety Sercos Gateway BWU2984	This message has been generated by the Bihl+Wiedemann AS-i Sercos Gateway. Consult the documentation of the third party device for message details. Info 1: Error code of the third party device	Consult the documentation of the Bihl+Wiedemann AS-i Safety Sercos Gateway BWU2984