Diagmessages of module SafeMotion
Further Information
- 0001, Primary MC: GLOBAL_Fault with Code 0xXX and Additional Code 0xXX
- 0002, Primary MC: GLOBAL_Shutdown with Code 0xXX and Additional Code 0xXX
- 0003, Secondary MC: GLOBAL_Fault with Code 0xXX and Additional Code 0xXX
- 0004, Secondary MC: GLOBAL_Shutdown with Code 0xXX and Additional Code 0xXX
- 0005, Primary MC: Stored GLOBAL_Fault with Code 0xXX and Additional Code 0xXX
- 0006, Secondary MC: Stored GLOBAL_Fault with Code 0xXX and Additional Code 0xXX
- 0007, Diag-Message-Overflow: II messages got lost
- 0008, Primary MC: the CRC of the FRAM Data was wrong (Diag-Code=II)
- 0009, Secondary MC: the CRC of the FRAM Data was wrong (Diag-Code=II)
- 0010, Reserved CfgData has to be zero st offset II
- 0011, The password is wrong
- 0012, The user was not found
- 0013, The CRC of the login data does not match
- 0014, The serial number of the login data does not match
- 0015, The login watchdog has been expired
- 0016, The user was logged out before
- 0017, The user has not sufficient access rights
- 0018, The reserved area of the CfgData was not 0
- 0019, The CRC of the CfgData was wrong
- 001A, The user name is wrong at word offset 0xXX when changing the password
- 001B, The requested number of users is too big
- 001D, The user update flags are wrong at word offset 0xXX when changing the password
- 001E, The wrong user (user II) is logged in when changing the password (user II found in the received data)
- 0021, the maximum Global-Shutdown counter was exceeded in the Vendor Data (maximum value: II, actual value: II)
- 0080, Safety reports FSoE Group error on channel A
- 0081, Safety reports FSoE Group error on channel B
- 0082, Safety reports STO module error on channel A
- 0083, Safety reports STO module error on channel B
- 0084, Safety reports FSIN module (digital Inputs) error on channel A
- 0085, Safety reports FSIN module (digital Inputs) error on channel B
- 0086, Safety reports Brake module error on channel A
- 0087, Safety reports Brake module error on channel B
- 0088, Safety reports Encoder overrange error on channel A
- 0089, Safety reports Encoder overrange error on channel B
- 0090, Safety reports Encoder underrange error on channel A
- 0091, Safety reports Encoder underrange error on channel B
- 0092, Safety reports Primary Safety Feedback error on channel A
- 0093, Safety reports Primary Safety Feedback error on channel B
- 0094, Safety reports Secondary Safety Feedback error on channel A
- 0095, Safety reports Secondary Safety Feedback error on channel B
- 0096, Safety reports Encoder voltage statemachine fault on channel A
- 0097, Safety reports Encoder voltage statemachine fault on channel B
- 0098, Safety reports Emergency Stop on channel A
- 0099, Safety reports Emergency Stop on channel B
- 00AD, Safety reports not defined Drive Command on channel A SS
- 00AE, Safety reports not defined Drive Command on channel B SS
- 00B0, Safety Card is in Bootloader mode. Download of valid Firmware is required.
- 00FF, Internal Error, Additional Errorcode 0xXX
- 0101, Primary MC: Completed RAM TEST: Starttime: 0xXX and Stoptime: 0xXX . The calculated timediff is 0xXX.
- 0102, Secondary MC: Completed RAM TEST: Starttime: 0xXX and Stoptime: 0xXX . The calculated timediff is 0xXX.
- 0103, C1 MCTEST Info: Arg1: 0xXX, Arg2: 0xXX, Arg3: 0xXX.
- 0104, C2 MCTEST Info: Arg1: 0xXX, Arg2: 0xXX, Arg3: 0xXX.
- 0115, Controller II: Maximum temperature exceeded. Temperature is 0xXX, should be <= 0xXX.
- 0116, Controller II: Minimum temperature alert. Temperature is 0xXX, should be >= 0xXX.
- 0117, Controller II: Temperature difference too high. Difference is II, should be <= II.
- 0118, Controller II: Maximum voltage alert (Partner_VCC). Voltage is 0xXX, should be <= 0xXX.
- 0119, Controller II: Minimum voltage alert (Partner_VCC). Voltage is 0xXX, should be >= 0xXX.
- 011A, Controller II: Maximum voltage alert (ECAT_VCC). Voltage is 0xXX, should be <= 0xXX.
- 011B, Controller II: Minimum voltage alert (ECAT_VCC). Voltage is 0xXX, should be >= 0xXX.
- 011E, Controller II: Timer Tick Difference is too high. Difference is 0xXX, should be >= 0xXX.
- 011F, Controller II: Minimum value alert (Individual ADC Check). Channel parameter = II. Actual value is 0xXX.
- 0120, Controller II: Maximum value alert (Individual ADC Check). Channel parameter = II. Actual value is 0xXX.
- 0121, Module Shutdown due to minimum value alert (Individual ADC Check). Channel parameter = II.
- 1000, The size of the safe User Parameter is too small (II), the expected size is II
- 1003, The reserved data of the SafeOut User Parameter of module II at byte offset 0xXX has to be 0
- 1004, The reserved data of the SafeIn User Parameter of module II at byte offset 0xXX has to be 0
- 100A, The version of the Product-Code (0xXX) is unequal the expected value of 0xXX
- 100B, The feature bits 0xXX of axis A are not supported, the allowed feature bits are 0xXX
- 100C, The feature bits 0xXX of axis B are not supported, the allowed feature bits are 0xXX
- 100F, The version (II (VII.II)) of the safety card is not released, not certified and shall only be used for non-safety-critical tests
- 1010, The default Project CRC is wrong, the received value is 0xXX
- 102A, Unallowed Safe User Parameter Version, Received=0xXX Expected=0xXX
- 102B, The Safe User Parameter Size (II) is unequal to the Safe User Parameter Size for the incremental download (SS)
- 102C, Unallowed Safe User Parameter Size for the rqeuested features, Received=II Expected=II
- 102D, Unallowed Safe User Parameter Ident, Received=II Expected=II
- 102E, Unallowed Safe User Parameter Size, Received=II Expected=II
- 102F, Unallowed Safe User Parameter Change in RUN, Offset=II Info=0xXX
- 1030, The size of the safe User Parameter is too big (II), the expected size is II
- 1515, Wrong SafetyCard Firmware: Number of supported axis does not fit with current device
- 1516, SafetyCard: Invalid Current scaling shift value for calculation configured. SafetyCard VendorData: II DriveApplication: II
- 2001, The II. connection has received an invalid FSoE-Cmd in state CONNECTION
- 2002, The II. connection has received an unknown FSoE-Cmd in state CONNECTION
- 2003, The II. connection has received an invalid FSoE-ConnID in state CONNECTION
- 2004, The II. connection has received an invalid FSoE-CRC in state CONNECTION
- 2005, The FSoE-Watchdog of the II. connection has been expired in state CONNECTION
- 2006, On the II. connection the received FSoE-Address (0xXX) does not match with the expected FSoE-Address (0xXX)
- 2007, On the II. connection the received connection data do not match with the sent values
- 200C, On the II. connection in state CONNECTION the Connection was restarted from the FSoE-Master
- 200E, A Module fault was detected on the II. connection in state CONNECTION
- 2011, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 1 was received which means that the communication partner has received an invalid FSoE-Cmd
- 2012, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 2 was received which means that the communication partner has received an unknown FSoE-Cmd
- 2013, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 3 was received which means that the communication partner has received an invalid FSoE-ConnID
- 2014, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 4 was received which means that the communication partner has received an invalid FSoE-CRC
- 2015, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 5 was received which means that the FSoE-Watchdog has been expired in the communication partner
- 2016, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 6 was received which means that the communication partner has received an invalid FSoE-Address
- 2017, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 7 was received which means that the communication partner has received connection data do not match with the sent values
- 2018, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 8 was received which means that the communication partner has received an invalid communication parameter length
- 2019, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 9 was received which means that the communication partner has received an invalid FSoE Watchdog
- 201A, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 10 was received which means that the communication partner has received an invalid application parameter length
- 201B, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 11 was received which means that the communication partner has received invalid application parameter data
- 201C, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 12 was received
- 201D, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 13 was received
- 201E, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 14 was received which means that the communication partner has detected a module fault
- 201F, On the II. connection in state CONNECTION a FSoE-Reset with Error-Code 0xXX was received
- 2041, The II. connection has received an invalid FSoE-Cmd in state PARAMETER
- 2042, The II. connection has received an unknown FSoE-Cmd in state PARAMETER
- 2043, The II. connection has received an invalid FSoE-ConnID in state PARAMETER
- 2044, The II. connection has received an invalid FSoE-CRC in state PARAMETER
- 2045, The FSoE-Watchdog of the II. connection has been expired in state PARAMETER
- 2047, On the II. connection the received parameter data do not match with the sent values
- 2048, On the II. connection the received communication parameter length (II) does not match with the expected value of 2
- 2049, On the II. connection the received FSoE Watchdog (II) is outside the allowed area from 2 to 60000
- 204A, On the II. connection the received application parameter length (II) is unequal the expected length of II
- 204B, On the II. connection the received application parameter data are wrong
- 204C, On the II. connection in state PARAMETER the Connection was restarted from the FSoE-Master
- 204E, A Module fault was detected on the II. connection in state PARAMETER
- 2051, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 1 was received which means that the communication partner has received an invalid FSoE-Cmd
- 2052, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 2 was received which means that the communication partner has received an unknown FSoE-Cmd
- 2053, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 3 was received which means that the communication partner has received an invalid FSoE-ConnID
- 2054, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 4 was received which means that the communication partner has received an invalid FSoE-CRC
- 2055, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 5 was received which means that the FSoE-Watchdog has been expired in the communication partner
- 2056, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 6 was received which means that the communication partner has received an invalid FSoE-Address
- 2057, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 7 was received which means that the communication partner has received connection data do not match with the sent values
- 2058, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 8 was received which means that the communication partner has received an invalid communication parameter length
- 2059, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 9 was received which means that the communication partner has received an invalid FSoE Watchdog
- 205A, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 10 was received which means that the communication partner has received an invalid application parameter length
- 205B, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 11 was received which means that the communication partner has received invalid application parameter data
- 205C, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 12 was received
- 205D, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 13 was received
- 205E, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 14 was received which means that the communication partner has detected a module fault
- 205F, On the II. connection in state PARAMETER a FSoE-Reset with Error-Code 0xXX was received
- 2061, On the II. connection in state PARAMETER a wrong Command was received, which means that the Safe-Parameter size is wrong (Expected size: II, Received size: II)
- 2081, The II. connection has received an invalid FSoE-Cmd in state DATA
- 2082, The II. connection has received an unknown FSoE-Cmd in state DATA
- 2083, The II. connection has received an invalid FSoE-ConnID in state DATA
- 2084, The II. connection has received an invalid FSoE-CRC in state DATA
- 2085, The FSoE-Watchdog of the II. connection has been expired in state DATA
- 208C, On the II. connection in state DATA the Connection was restarted from the FSoE-Master
- 208D, The FailSafeData command was received on the II. connection in state DATA
- 208E, A Module fault was detected on the II. connection in state DATA
- 2091, On the II. connection in state DATA a FSoE-Reset with Error-Code 1 was received which means that the communication partner has received an invalid FSoE-Cmd
- 2092, On the II. connection in state DATA a FSoE-Reset with Error-Code 2 was received which means that the communication partner has received an unknown FSoE-Cmd
- 2093, On the II. connection in state DATA a FSoE-Reset with Error-Code 3 was received which means that the communication partner has received an invalid FSoE-ConnID
- 2094, On the II. connection in state DATA a FSoE-Reset with Error-Code 4 was received which means that the communication partner has received an invalid FSoE-CRC
- 2095, On the II. connection in state DATA a FSoE-Reset with Error-Code 5 was received which means that the FSoE-Watchdog has been expired in the communication partner
- 2096, On the II. connection in state DATA a FSoE-Reset with Error-Code 6 was received which means that the communication partner has received an invalid FSoE-Address
- 2097, On the II. connection in state DATA a FSoE-Reset with Error-Code 7 was received which means that the communication partner has received connection data do not match with the sent values
- 2098, On the II. connection in state DATA a FSoE-Reset with Error-Code 8 was received which means that the communication partner has received an invalid communication parameter length
- 2099, On the II. connection in state DATA a FSoE-Reset with Error-Code 9 was received which means that the communication partner has received an invalid FSoE Watchdog
- 209A, On the II. connection in state DATA a FSoE-Reset with Error-Code 10 was received which means that the communication partner has received an invalid application parameter length
- 209B, On the II. connection in state DATA a FSoE-Reset with Error-Code 11 was received which means that the communication partner has received invalid application parameter data
- 209C, On the II. connection in state DATA a FSoE-Reset with Error-Code 12 was received
- 209D, On the II. connection in state DATA a FSoE-Reset with Error-Code 13 was received
- 209E, On the II. connection in state DATA a FSoE-Reset with Error-Code 14 was received which means that the communication partner has detected a module fault
- 209F, On the II. connection in state DATA a FSoE-Reset with Error-Code 0xXX was received
- 20C1, The II. connection has received an invalid FSoE-Cmd in state SHUTDOWN
- 20C2, The II. connection has received an unknown FSoE-Cmd in state SHUTDOWN
- 20C4, The II. connection has received an invalid FSoE-CRC in state SHUTDOWN
- 20E3, The II. connection has received the invalid FSoE-ConnID 0 in state SESSION
- 3100, No groups defined when trying to activate or deactivate groups
- 3101, The reserved bits are set in value II at offset II when trying to activate or deactivate groups
- 3102, The operation mode at offset II is not supported when trying to activate or deactivate groups
- 3103, The deactivation of groups is not enabled for any group so no replacement values should be downloaded
- 3104, The maximum number (II) of Cfg Data pages was exceeded in the Replacement Values Cfg Data
- 3105, Invalid FB output size size at offset II of the Replacement Values Cfg Data
- 3106, Unexpected groupindex in the Replacement values Cfg Data at offset 0xXX
- 3107, The download of the Activate Project Cfg Data was refused because II bytes of the Replacement Values Cfg Data were missing
- 3108, To activate the Group II the user has to logged in with access rights Bit 0-15 unequal 0 that the Safe Logic Program will be stopped when logging in
- 3109, No more definitions of individual replace values for analog FB Outputs in case of Group State unequal RUN are expected at offset II
- 310A, The offset in the definitions of individual replace values for analog FB Outputs in case of Group State unequal RUN was wrong at offset II
- 310B, The source process image offset of the Cyclic FRAM Data is outside the FB analog input area at offset II
- 310C, The source process image offset of the Cyclic FRAM Data has to even at offset II
- 310D, The size of the Cyclic FRAM Data was exceeding at offset II
- 310E, The received size of the Cyclic FRAM Data at word offset 24 of the Safe Logic Cfg Data (II) is unequal the calculated value of II
- 310F, The size of the Cyclic FRAM CfgData in the GroupCfgData was not dividable by 4 at offset II
- 3110, The offset of the Cyclic FRAM Data in the GroupCfgData was wrong at offset II
- 3111, The value of II at offset II is not allowed when trying to activate or deactivate groups
- 3113, FB CAMMON (Word-Offset 0xXX of the CfgData): The TDC2UpperLimit (II) is lower or equal than the maximum position jitter (II)
- 3114, FB CAMMON (Word-Offset 0xXX of the CfgData): The TDCUpperLimit (II) is lower or equal than the maximum position jitter (II)
- 3115, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of TDCLowerLimit (plus maximum position jitter) (II) is bigger or equal the configured position of 360� (II)
- 3116, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of BDCUpperLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of TDCLowerLimit (II)
- 3117, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of BDCUpperLimit (II) is smaller or equal the configured value of 180� (plus maximum position jitter) (II)
- 3118, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of BDCLowerLimit (plus maximum position jitter) (II) is greater or equal the configured value of 180� (II)
- 3119, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of OverrunMax (plus twice the maximum position jitter) (II) is bigger or equal the value of BDCLowerLimit (II)
- 311A, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of TDCUpperLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of OverrunMax (II)
- 311B, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of TDC1UpperLimit (plus the maximum position jitter) (II) is bigger or equal the configured position of 360� (II)
- 311C, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of TDC1LowerLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of TDC1UpperLimit (5d)
- 311D, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of TDC2LowerLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of BDCLowerLimit (II)
- 311E, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of TDC2UpperLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of TDC2LowerLimit (II)
- 311F, The maximum size of the Replacement Values was exceeded at Word-Offset 0xXX of the Group Cfg Data
- 3120, If no deactivation mode is enabled the offset of the replacement values shall be zero at Word-Offset 0xXX of the Group Cfg Data
- 3121, No more replacement values expected at byte-offset 0xXX of the Replacement Values Cfg Data
- 3200, The PROFIsafe-protocol is not supported on this device
- 3201, The F_ParVersion in the F_Prm_Flag2 of the F-Parameter at Word-Offset 0xXX is unequal 1 (PROFIsafe V2)
- 3202, The F_CRC1 of the F-Parameter at Word-Offset 0xXX is wrong
- 3203, The F_CRC_Length in the F_Prm_Flag1 of the F-Parameter is wrong at Word-Offset 0xXX, the expected value is 0 (3 Bytes CRC2)
- 3206, The I-Parameter CRC in the F-Parameter is wrong at Word-Offset 0xXX
- 3207, The F_Block_ID in the F_Prm_Flag2 of the F-Parameter is wrong at Word-Offset 0xXX, the expected value is 0 (No F_iPar_CRC, no F_WD_Time 2) or 1 (F_iPar_CRC, no F_WD_Time 2)
- 3208, The F_Source_Address in the F-Parameter at Word-Offset 0xXX is outside the allowed area of 1-0xFFFE
- 3209, The F_Destination_Address in the F-Parameter at Word-Offset 0xXX is outside the allowed area of 1-0xFFFE
- 320A, The F_WD_Time in the F-parameter at Word-Offset 0xXX is outside the allowed range from 2-60000
- 320B, The F_Destination_Address in the F-Parameter at Word-Offset 0xXX is wrong, the expected value is II
- 3300, The State OPERATIONAL was left in Restore Mode
- 3301, Only II CRCs were matching in Restore Mode
- 3302, The CRC of the Activate Project Cfg Data in Restore Mode does not match, the expected value was 0xXX
- 3303, No RestoreMode Slaves configured when trying to start the Restore Mode
- 3304, The CRC of the User List Cfg Data was not matching in Restore Mode, the expected value was 0xXX
- 3305, The download of the User List Cfg Data is not activated in Restore Mode
- 3306, The download of the User List Cfg Data in Restore-Mode is not allowed in the state II
- 3307, The activation of the TwinSAFE Restore Project is not allowed in the state II
- 3308, The Restore Mode is not supported in EtherCAT state 0xXX
- 3310, The FSoE-Slave on the II. connection is in Restore-Mode
- 3311, The FSoE-Master on the II. connection is in Restore-Mode
- 3400, The II. group has no more errors
- 3401, The Analog Input at word offset II of the analog input process image has expired maximum allowed deviation to the last stored value, received value: II, last stored value: II
- 3402, The Wait-Com-Error-Timeout has not been expired when the group II should be deactivated in passivate mode
- 3403, A module fault happened in group II
- 3404, The assigned connection reported an error when the group II was deactivated in passivate mode
- 3405, The connection has been successfully restarted when the group II was deactivated in passivate mode
- 3410, All groups will enter the ERROR-state because the safe logic program has been restarted
- 3411, All groups will enter the ERROR-state because the CRC of the Change Group Activation Data was wrong
- 3412, All groups will enter the ERROR-state because the CRC of the Change FB Parameter Data was wrong
- 3413, All groups will enter the ERROR-state because the CRC of the Project CRC Data was wrong
- 3414, All groups will enter the ERROR-state because the CRC of the Power-On Analog Value Check Data was wrong
- 3415, The TwinSAFE Logic Program was not loaded on C1 because of an inconsistency
- 3416, The TwinSAFE Logic Program was not loaded on C2 because of an inconsistency
- 3420, No more EtherCAT size error (EtherCAT Output Size=II, EtherCAT Input Size=II)
- 3421, The EtherCAT Output Data sizes of the Safety Logic Program (II) and the EtherCAT Configuration (II) are unequal
- 3422, The EtherCAT Input Data sizes of the Safety Logic Program (II) and the EtherCAT Configuration (II) are unequal
- 3423, The EtherCAT Output Data sizes for PROFIsafe of the Safety Logic Program (II) and the EtherCAT Configuration (II) are unequal
- 3424, The EtherCAT Input Data sizes for PROFIsafe of the Safety Logic Program (II) and the EtherCAT Configuration (II) are unequal
- 3425, The needed EtherCAT Process data buffer size (II) exceeded the maximum available size of II
- 3501, On the II. connection the changeable FSoE Address of II already exists
- 3502, On the II. connection the changeable FSoE Address is zero
- 3800, FB II (ESTOP): An EDM-fault (0xXX) was detected in state SAFE
- 3802, FB II (ESTOP): An EDM-fault (0xXX) was detected in state RESET
- 3803, FB II (ESTOP): An EDM-fault (0xXX) was detected in state START
- 3804, FB II (ESTOP): An DiscTime-Fault (0xXX) was detected in state SAFE, the actual EStopIn-values are 0xXX
- 3806, FB II (ESTOP): An DiscTime-Fault (0xXX) was detected in state RESET, the actual EStopIn-values are 0xXX
- 3807, FB II (ESTOP): An DiscTime-Fault (0xXX) was detected in state START, the actual EStopIn-values are 0xXX
- 3809, FB II (ESTOP): An DiscTime-Fault (0xXX) was detected in state DELAYOUT, the actual EStopIn-values are 0xXX
- 380F, FB II (ESTOP): At least one activated EDM-Input was not reset in RUN when the EDM Reset time had been expired (Diag-Code=0xXX)
- 3810, FB II (MON): An EDM-fault (0xXX) was detected in state SAFE
- 3812, FB II (MON): An EDM-fault (0xXX) was detected in state RESET
- 3813, FB II (MON): An EDM-fault (0xXX) was detected in state START
- 3814, FB II (MON): An DiscTime-Fault (0xXX) was detected in state SAFE, the actual MonIn/Secure-values are 0xXX
- 3816, FB II (MON): An DiscTime-Fault (0xXX) was detected in state RESET, the actual MonIn/Secure-values are 0xXX
- 3817, FB II (MON): An DiscTime-Fault (0xXX) was detected in state START, the actual MonIn/Secure-values are 0xXX
- 3818, FB II (MON): An DiscTime-Fault (0xXX) was detected in state RUN, the actual MonIn/Secure-values are 0xXX
- 3819, FB II (MON): An DiscTime-Fault (0xXX) was detected in state DELAYOUT, the actual MonIn/Secure-values are 0xXX
- 381A, FB II (MON): An DiscTime-Fault (0xXX) was detected in state FUNCTEST, the actual MonIn/Secure-values are 0xXX
- 381F, FB II (MON): At least one activated EDM-Input was not reset in RUN when the EDM Reset time had been expired (Diag-Code=0xXX)
- 3820, FB II (TWOHAND): A Disc-Group-fault (0xXX) was detected in state 1BUTTON, the actual TwoHandIn-values are 0xXX
- 3821, FB II (TWOHAND): A Disc-Group-fault (0xXX) was detected in state 2BUTTON, the actual TwoHandIn-values are 0xXX
- 3823, FB II (TWOHAND): An DiscTime-Fault (0xXX) was detected in state SAFE, the actual TwoHandIn-values are 0xXX
- 3825, FB II (TWOHAND): An DiscTime-Fault (0xXX) was detected in state RESET, the actual TwoHandIn-values are 0xXX
- 382B, FB II (TWOHAND): An DiscTime-Fault (0xXX) was detected in state 1BUTTON, the actual TwoHandIn-values are 0xXX
- 382C, FB II (TWOHAND): An DiscTime-Fault (0xXX) was detected in state 2BUTTON, the actual TwoHandIn-values are 0xXX
- 382D, FB II (TWOHAND): An DiscTime-Fault (0xXX) was detected in state RELEASE, the actual TwoHandIn-values are 0xXX
- 3830, FB II (OPMODE): An DiscTime-Fault (0xXX) was detected, the actual OpIn-values are 0xXX
- 3831, FB II (OPMODE): An Input-Fault was detected in state RESET, the actual OpIn-values are 0xXX
- 3840, FB II (EDM): The SwitchOn-Time had been expired
- 3841, FB II (EDM): The SwitchOff-Time had been expired
- 3853, FB II (CS): An DiscTime-Fault (0xXX) was detected in state SAFE, the actual Deactivate-values are 0xXX
- 3855, FB II (CS): An DiscTime-Fault (0xXX) was detected in state RESET, the actual Deactivate-values are 0xXX
- 3881, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state RUN, the actual MuteIn/OssdIn-values are 0xXX
- 3883, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state SAFE, the actual MuteIn/OssdIn-values are 0xXX
- 3885, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state RESET, the actual MuteIn/OssdIn-values are 0xXX
- 3888, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state DELAYOUT, the actual MuteIn/OssdIn-values are 0xXX
- 3889, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING1, the actual MuteIn/OssdIn-values are 0xXX
- 388A, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING2, the actual MuteIn/OssdIn-values are 0xXX
- 388B, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING3, the actual MuteIn/OssdIn-values are 0xXX
- 388C, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING4, the actual MuteIn/OssdIn-values are 0xXX
- 388D, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING5, the actual MuteIn/OssdIn-values are 0xXX
- 388E, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING6, the actual MuteIn/OssdIn-values are 0xXX
- 388F, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING7, the actual MuteIn/OssdIn-values are 0xXX
- 3890, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING8, the actual MuteIn/OssdIn-values are 0xXX
- 3891, FB II (MUTING): An DiscTime-Fault (0xXX) was detected in state MUTING9, the actual MuteIn/OssdIn-values are 0xXX
- 3892, FB II (MUTING): State RUN, Sequential Inputs=TRUE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 3893, FB II (MUTING): State RUN, Sequential Inputs=FALSE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 3894, FB II (MUTING): State MUTING1, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 3895, FB II (MUTING): State MUTING1, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 3896, FB II (MUTING): State MUTING2, MutingEnable is set and the MuteIn-signals before the AOPD are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 3897, FB II (MUTING): State MUTING2, MutingEnable is set and the MuteIn-signals after the AOPD are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 3898, FB II (MUTING): State MUTING3, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 3899, FB II (MUTING): State MUTING3, Sequential Inputs=TRUE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 389A, FB II (MUTING): State MUTING3, Sequential Inputs=FALSE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 389B, FB II (MUTING): State MUTING4, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 389C, FB II (MUTING): State MUTING4, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 389D, FB II (MUTING): State MUTING5, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 389E, FB II (MUTING): State MUTING5, Sequential Inputs=TRUE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 389F, FB II (MUTING): State MUTING5, Sequential Inputs=FALSE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A0, FB II (MUTING): State MUTING6, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A1, FB II (MUTING): State MUTING6, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A2, FB II (MUTING): State MUTING7, MutingEnable is set and the MuteIn-signals before the AOPD are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A3, FB II (MUTING): State MUTING7, MutingEnable is set and the MuteIn-signals after the AOPD are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A4, FB II (MUTING): State MUTING8, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A5, FB II (MUTING): State MUTING8, Sequential Inputs=TRUE, CheckOssdOptional=TRUE: MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A6, FB II (MUTING): State MUTING8, Sequential Inputs=TRUE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A7, FB II (MUTING): State MUTING8, Sequential Inputs=FALSE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A8, FB II (MUTING): State MUTING9, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38A9, FB II (MUTING): State MUTING9, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38AA, FB II (MUTING): State MUTING5, Sequential Inputs=TRUE, MuteIn3 and MuteIn4 are inactive: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38AB, FB II (MUTING): State MUTING6, Sequential Inputs=TRUE, MuteIn3 and MuteIn4 are inactive: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38AC, FB II (MUTING): State MUTING1, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0xXX
- 38B0, FB II (MUTING): At least one activated EDM-Input was not reset in RUN when the EDM Reset time had been expired (Diag-Code=0xXX)
- 38C1, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING1 (Digital Inputs=0xXX)
- 38C2, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING2 (Digital Inputs=0xXX)
- 38C3, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING3 (Digital Inputs=0xXX)
- 38C4, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING4 (Digital Inputs=0xXX)
- 38C5, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING5 (Digital Inputs=0xXX)
- 38C6, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING6 (Digital Inputs=0xXX)
- 38C7, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING7 (Digital Inputs=0xXX)
- 38C8, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING8 (Digital Inputs=0xXX)
- 38C9, FB II (MUTING): The Max-Muting-Time had been expired in state MUTING9 (Digital Inputs=0xXX)
- 4001, FB II (CAMMON): The TDC2UpperLimit (II) is lower or equal than the maximum position jitter (II)
- 4002, FB II (CAMMON): The Position (II) is bigger than the maximum position (plus the maximum position jitter) (II)
- 4003, FB II (CAMMON): The input OverrunCAM was FALSE in the top dead center area, the actual position is II
- 4004, FB II (CAMMON): The input OverrunCAM changed from FALSE to TRUE outside the area between BDCUpperLimit and TDCLowerLimit, the actual position is II
- 4005, FB II (CAMMON): The input OverrunCAM was TRUE in the area between OverrunMax and BDCUpperLimit, the actual position is II
- 4006, FB II (CAMMON): The input OverrunCAM changed from TRUE to FALSE outside the area between OverrunMax and BDCLowerLimit, the actual position is II
- 4007, FB II (CAMMON): The input UpwardsCAM was FALSE in the area between BDCUpperLimit and TDCLowerLimit, the actual position is II
- 4008, FB II (CAMMON): The input UpwardsCAM changed from FALSE to TRUE outside the area between BDCLowerLimit and TDCLowerLimit, the actual position is II
- 4009, FB II (CAMMON): The input UpwardsCAM changed from TRUE to FALSE outside the area between TDCLowerLimit and OverrunMax, the actual position is II
- 400A, FB II (CAMMON): The Position was moving while waiting for a rising edge of the input Reset in the state MOVE-STOP
- 400B, FB II (CAMMON): The Position was moving while waiting for a falling edge of the input Reset in the state MOVE-START
- 400C, FB II (CAMMON): The Position II in the area between OverrunMax and BDCLowerLimit was detected in the state MOVE-UP
- 400D, FB II (CAMMON): The Position has left the top dead center while waiting for a stop, the actual position is II
- 400E, FB II (CAMMON): The Position has been changed negative
- 400F, FB II (CAMMON): The input UpwardsCAM was TRUE in the area between OverrunMax and BDCLowerLimit
- 4010, FB II (CAMMON): The Position has a circle overflow in Pendulum Mode, actual position=II, last position=II
- 4011, FB II (CAMMON): The Position has moved while waiting for a rising edge of the input Reset in Pendulum Mode, actual position=II, compare position=II
- 4012, FB II (CAMMON): The Input BackwardsMove is TRUE while the Position is between 180� and 360�, the actual position is II
- 4013, FB II (CAMMON): The Input BackwardsMove is TRUE while the moving is clockwise
- 4014, FB II (CAMMON): The Position has moved while waiting for a falling edge of the input Reset in Pendulum Mode, actual position=II, last position=II
- 4015, FB II (CAMMON): The value of TDCLowerLimit (plus maximum position jitter) (II) is bigger or equal the configured position of 360� (II)
- 4016, FB II (CAMMON): The value of BDCUpperLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of TDCLowerLimit (II)
- 4017, FB II (CAMMON): The value of BDCUpperLimit (II) is smaller or equal the configured value of 180� (plus maximum position jitter) (II)
- 4018, FB II (CAMMON): The value of BDCLowerLimit (plus maximum position jitter) (II) is greater or equal the configured value of 180� (II)
- 4019, FB II (CAMMON): The value of OverrunMax (plus twice the maximum position jitter) (II) is bigger or equal the value of BDCLowerLimit (II)
- 401A, FB II (CAMMON): The value of TDCUpperLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of OverrunMax (II)
- 401B, FB II (CAMMON): The value of TDC1UpperLimit (plus the maximum position jitter) (II) is bigger or equal the configured position of 360� (II)
- 401C, FB II (CAMMON): The value of TDC1LowerLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of TDC1UpperLimit (5d)
- 401D, FB II (CAMMON): The value of TDC2LowerLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of BDCLowerLimit (II)
- 401E, FB II (CAMMON): The value of TDC2UpperLimit (plus twice the maximum position jitter) (II) is bigger or equal the value of TDC2LowerLimit (II)
- 401F, FB II (CAMMON): The input PressStarted is TRUE and the position did not move after the PressStartedDelayTime
- 4020, FB II (CAMMON): The input PressStarted is TRUE and the position has stopped after moving before
- 4021, FB II (CAMMON): The input PressStarted is TRUE and the position has not moved enough, the actual position is II, the compare position is II
- 4022, FB II (CAMMON), Pendulum Mode: The Position has changed contra clockwise while moving up clockwise (actual Position=II, old Position=II)
- 4023, FB II (CAMMON), Pendulum Mode: The Position has changed clockwise while moving up contra clockwise (actual Position=II, old Position=II)
- 4024, FB II (CAMMON): The Position was moving while waiting for a falling edge of the input Reset in the state WAIT-FOR_RESET
- 4025, FB II (CAMMON): The TDCUpperLimit (II) is lower or equal than the maximum position jitter (II)
- 4080, FB II (ADD/SUB): an underflow was detected, AnalogIn1=II, AnalogIn2=II
- 4081, FB II (ADD/SUB): an overflow was detected, AnalogIn1=II, AnalogIn2=II
- 4088, FB II (SPEED): an underflow was detected, actual Position=II, old Position=II
- 4089, FB II (SPEED): an overflow was detected, actual Position=II, old Position=II
- 4090, FB II (LIMIT): the minimum value (II) is bigger than the maximum value (II)
- 4098, FB II (COMPARE): an underflow was detected on CompOut (II), the minimum allowed value is II
- 4099, FB II (COMPARE): an overflow was detected on CompOut (II), the maximum allowed value is II
- 40A0, FB II (MUL): an underflow was detected, AnalogIn1=II, AnalogIn2=II
- 40A1, FB II (MUL): an overflow was detected, AnalogIn1=II, AnalogIn2=II
- 40A8, FB II (DIV): an underflow was detected, AnalogIn1=II, AnalogIn2=II
- 40A9, FB II (DIV): an overflow was detected, AnalogIn1=II, AnalogIn2=II
- 40B0, FB II (SCALE): an underflow was detected, AnalogIn=II
- 40B1, FB II (SCALE): an overflow was detected, AnalogIn=II
- 40B2, FB II (SCALE): an overflow was detected after multiplication, AnalogIn=II
- 40B3, FB II (SCALE): an overflow was detected before division when rounding up the value, AnalogIn=II
- 40B8, FB II (COUNT): an underflow was detected on ActValue (II)
- 40B9, FB II (COUNT): an overflow was detected on ActValue (II)
- 40C0, FB II (SLI): an underflow was detected on ActValue (II), the minimum allowed value is II
- 40C1, FB II (SLI): an overflow was detected on ActValue (II), the maximum allowed value is II
- 40C8, FB II (ENVELOPE): an underflow was detected on InValue (II), the minimum allowed value is II
- 40C9, FB II (ENVELOPE): an overflow was detected on InValue (II), the maximum allowed value is II
- 40CA, FB II (ENVELOPE): an overflow error was detected on InValue (II), InValue+Offset is bigger than the maximum allowed value
- 40CB, FB II (ENVELOPE): the MaxTime was expired (InValue=II)
- 40D0, FB II (SLP): MultiturnPos_LL (II) is bigger than MultiturnPos_UL (II)
- 40D1, FB II (SLP): MultiturnPos_LL=MultiturnPos_UL and SingleturnPos_LL (II) is bigger than SingleturnPos_UL (II)
- 40D8, FB II (SBT): Brake-Test failed in state II
- 40D9, FB II (SBT): Brake-Test Interval expired in state II
- 40DA, FB II (SBT): Brake-Test failed, Actual Position Deviation=II, Maximum Position Deviation=IIInterval expired in state II
- 6009, SAFEOUT:Initial-Parameter: MultiplierDiagTestPulse has to be greater zero. ModuleNr:0xXX
- 6010, SAFEOUT:Initial-Parameter: Number of Modules incorrect. ModuleNr:0xXX, Parameter:0xXX
- 6011, SAFEOUT:Initial-Parameter: Number of Channels incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 6012, SAFEOUT:Initial-Parameter: Number of Diagnosis active Module incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 6013, SAFEOUT:Initial-Parameter: Number of Diagnosis inactive Module incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 6014, SAFEOUT:Initial-Parameter: Number of Feedback active Module incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 6015, SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis active Module incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 6016, SAFEOUT:Initial-Parameter: Number of Feedback inactive Module incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 6017, SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis inactive Module incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 6018, SAFEOUT:Initial-Parameter: Number of Diagnosis active Channel incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 6019, SAFEOUT:Initial-Parameter: Number of Diagnosis inactive Channel incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 601A, SAFEOUT:Initial-Parameter: Number of Feedback active Channel incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 601B, SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis active Channel incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 601C, SAFEOUT:Initial-Parameter: Number of Feedback inactive Channel incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 601D, SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis inactive Channel incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 601E, SAFEOUT:Setup Hardware Fault: Module Switch. ReturnData:0xXX, ReturnState:0xXX
- 601F, SAFEOUT:Setup Hardware Fault: Diagnosis active Module. ReturnData:0xXX, ReturnState:0xXX
- 6020, SAFEOUT:Setup Hardware Fault: Diagnosis inactive Module. ReturnData:0xXX, ReturnState:0xXX
- 6021, SAFEOUT:Setup Hardware Fault: Feedback active Module. ReturnData:0xXX, ReturnState:0xXX
- 6022, SAFEOUT:Setup Hardware Fault: Feedback Diagnosis active Module. ReturnData:0xXX, ReturnState:0xXX
- 6023, SAFEOUT:Setup Hardware Fault: Feedback inactive Module. ReturnData:0xXX, ReturnState:0xXX
- 6024, SAFEOUT:Setup Hardware Fault: Feedback Diagnosis inactive Module. ReturnData:0xXX, ReturnState:0xXX
- 6025, SAFEOUT:Setup Hardware Fault: Channel Switch. ReturnData:0xXX, ReturnState:0xXX
- 6026, SAFEOUT:Setup Hardware Fault: Diagnosis active Channel. ReturnData:0xXX, ReturnState:0xXX
- 6027, SAFEOUT:Setup Hardware Fault: Diagnosis inactive Channel. ReturnData:0xXX, ReturnState:0xXX
- 6028, SAFEOUT:Setup Hardware Fault: Feedback active Channel. ReturnData:0xXX, ReturnState:0xXX
- 6029, SAFEOUT:Setup Hardware Fault: Feedback Diagnosis active Channel. ReturnData:0xXX, ReturnState:0xXX
- 602A, SAFEOUT:Setup Hardware Fault: Feedback inactive Channel. ReturnData:0xXX, ReturnState:0xXX
- 602B, SAFEOUT:Setup Hardware Fault: Feedback Diagnosis inactive Channel. ReturnData:0xXX, ReturnState:0xXX
- 6030, SAFEOUT:The Feedback of the active Module Switch is wrong. Module:0xXX
- 6031, SAFEOUT:The Feedback of the inactive Module Switch is wrong. Module:0xXX
- 6032, SAFEOUT:The Feedback of the active Channel Switch is wrong. Module:0xXX / Channel:0xXX
- 6033, SAFEOUT:The Feedback of the inactive Channel Switch is wrong. Module:0xXX / Channel:0xXX
- 6040, SAFEOUT:Diagnosis Test: Common Fault Module:0xXX / DiagChannel:0xXX
- 6041, SAFEOUT:Diagnosis Test: Unknown State local ModuleState:0xXX
- 6042, SAFEOUT:Diagnosis Test: Unknown State other ModuleState:0xXX
- 6050, SAFEOUT:Diagnosis Test: Feedback active Module Switch is wrong (Step1 - check current state). Module:0xXX
- 6051, SAFEOUT:Diagnosis Test: Feedback inactive Module Switch is wrong (Step1 - check current state). Module:0xXX
- 6052, SAFEOUT:Diagnosis Test: Feedback active Channel Switch is wrong (Step1 - check current state). Module:0xXX / DiagChannel:0xXX
- 6053, SAFEOUT:Diagnosis Test: Feedback inactive Channel Switch is wrong (Step1 - check current state). Module:0xXX / DiagChannel:0xXX
- 6060, SAFEOUT:Diagnosis Test: Feedback active Module Switch is wrong (Step2 - check test pulse). Module:0xXX
- 6061, SAFEOUT:Diagnosis Test: Feedback inactive Module Switch is wrong (Step2 - check test pulse). Module:0xXX
- 6062, SAFEOUT:Diagnosis Test: Feedback active Channel Switch is wrong (Step2 - check test pulse). Module:0xXX / DiagChannel:0xXX
- 6063, SAFEOUT:Diagnosis Test: Feedback inactive Channel Switch is wrong (Step2 - check test pulse). Module:0xXX / DiagChannel:0xXX
- 6080, SAFEOUT:Diagnosis Test:VendorData. ID: 0xXX Module:0xXX
- 6081, SAFEOUT:Diagnosis Test:VendorData. ID: 0xXX Module:0xXX
- 6082, SAFEOUT:Diagnosis Test:VendorData. ID: 0xXX Module:0xXX
- 6083, SAFEOUT:Diagnosis Test:VendorData. Channel: 0xXX Module:0xXX
- 6084, SAFEOUT:Diagnosis Test:VendorData. Channel: 0xXX Module:0xXX
- 6085, SAFEOUT:Diagnosis Test:VendorData. Channel: 0xXX Module:0xXX
- 6086, SAFEOUT:Diagnosis Test:VendorData. Channel: 0xXX Module:0xXX
- 6090, SAFEOUT:Module Switch FeedbackTest ViolationCounter incremented, Outputs active. Module:0xXX, Info:0xXX.
- 6091, SAFEOUT:Module Switch FeedbackTest ViolationCounter incremented, Outputs inactive. Module:0xXX, Info:0xXX.
- 6092, SAFEOUT:Channel Switch FeedbackTest ViolationCounter incremented, Outputs active. Module:0xXX, Channel:0xXX, Info:0xXX.
- 6093, SAFEOUT:Channel Switch FeedbackTest ViolationCounter incremented, Outputs inactive. Module:0xXX, Channel:0xXX, Info:0xXX.
- 6094, SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step1 - check current state). Module:0xXX, Info:0xXX.
- 6095, SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step1 - check current state). Module:0xXX, Info:0xXX.
- 6096, SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step1 - check current state). Module:0xXX, Channel:0xXX, Info:0xXX.
- 6097, SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step1 - check current state). Module:0xXX, Channel:0xXX, Info:0xXX.
- 6098, SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step2 - check test pulse). Module:0xXX, Info:0xXX.
- 6099, SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step2 - check test pulse). Module:0xXX, Info:0xXX.
- 609A, SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step2 - check test pulse). Module:0xXX, Channel:0xXX, Info:0xXX.
- 609B, SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step2 - check test pulse). Module:0xXX, Channel:0xXX, Info:0xXX.
- 60A0, SAFEOUT:Sercom Fault 0. Cmd/State:0xXX
- 60A1, SAFEOUT:Sercom Fault 1. Cmd/State:0xXX
- 60B0, SAFEOUT:Unknown Sercom Command Request 1. Cmd/State:0xXX
- 60B1, SAFEOUT:Unknown Sercom Command Answer 1. Cmd/State:0xXX
- 60B2, SAFEOUT:Unknown Sercom Command Request 2. Cmd/State:0xXX
- 60B3, SAFEOUT:Unknown Sercom Command Answer 2. Cmd/State:0xXX
- 60C0, SAFEOUT:Module Switch too fast Switching OFF detected Fault (see technical data). Module:0xXX
- 60C1, SAFEOUT:Channel Switch too fast Switching OFF detected Fault (see technical data). Module:0xXX / Channel:0xXX
- 60C2, SAFEOUT:Module Switch too fast Switching ON detected Fault (see technical data). Module:0xXX
- 60C3, SAFEOUT:Channel Switch too fast Switching ON detected Fault (see technical data). Module:0xXX / Channel:0xXX
- 60C4, SAFEOUT:Module Error Acknowledge is not possible. Module:0xXX
- 60E0, SAFEOUT:HAL Read Fault. ReturnData:0xXX
- 60E1, SAFEOUT:Init Fault. Module:0xXX
- 8009, SAFEIN:Initial-Parameter: MultiplierDiagTestPulse has to be greater zero. ModuleNr:0xXX
- 8010, SAFEIN:Initial-Parameter: Number of Modules incorrect. ModuleNr:0xXX, Parameter:0xXX
- 8011, SAFEIN:Initial-Parameter: Number of Channels incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 8018, SAFEIN:Initial-Parameter: Number of Diagnosis active Channel incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 801B, SAFEIN:Initial-Parameter: Number of Feedback Diagnosis active Channel incorrect. Parameter0:0xXX, Parameter1:0xXX, Parameter2:0xXX
- 8025, SAFEIN:Setup Hardware Fault: Channel Switch. ReturnData:0xXX, ReturnState:0xXX
- 8026, SAFEIN:Setup Hardware Fault: Diagnosis active Channel. ReturnData:0xXX, ReturnState:0xXX
- 8029, SAFEIN:Setup Hardware Fault: Feedback Diagnosis active Channel. ReturnData:0xXX, ReturnState:0xXX
- 8040, SAFEIN:Diagnosis Test: Common Fault Module:0xXX / DiagChannel:0xXX
- 8041, SAFEIN:Diagnosis Test: Unknown State local ModuleState:0xXX
- 8042, SAFEIN:Diagnosis Test: Unknown State Other ModuleState:0xXX
- 8043, SAFEIN Pulse Detection: Wrong pulse was detected at . Module:0xXX / DiagChannel:0xXX
- 8044, SAFEIN Pulse Detection: Detected pulse from Module:0xXX / DiagChannel:0xXX
- 8052, SAFEIN:Diagnosis Test: Feedback in Step1 active Channel is wrong. Module:0xXX / DiagChannel:0xXX
- 8062, SAFEIN:Diagnosis Test: Feedback in Step2 active Channel is wrong. Module:0xXX / DiagChannel:0xXX
- 8080, SAFEIN:Diagnosis Test:VendorData. ID: 0xXX Module:0xXX
- 8081, SAFEIN:Diagnosis Test:VendorData. ID: 0xXX Module:0xXX
- 8084, SAFEIN:Diagnosis Test:VendorData. Channel: 0xXX Module:0xXX
- 8085, SAFEIN:Diagnosis Test:VendorData. Channel: 0xXX Module:0xXX
- 8086, SAFEIN:Diagnosis Test:VendorData. Channel: 0xXX Module:0xXX
- 8096, SAFEIN:DiagnosisTest ViolationCounter incremented, Inputs active (Step1 - check current state). Module:0xXX, Channel:0xXX, Info:0xXX.
- 809A, SAFEIN:DiagnosisTest ViolationCounter incremented, Inputs active (Step2 - check test pulse). Module:0xXX, Channel:0xXX, Info:0xXX.
- 80A0, SAFEIN:Sercom Fault 0. Cmd/State:0xXX
- 80A1, SAFEIN:Sercom Fault 1. Cmd/State:0xXX
- 80B0, SAFEIN:Unknown Sercom Command Request 1. Cmd/State:0xXX
- 80B1, SAFEIN:Unknown Sercom Command Answer 1. Cmd/State:0xXX
- 80B2, SAFEIN:Unknown Sercom Command Request 2. Cmd/State:0xXX
- 80B3, SAFEIN:Unknown Sercom Command Answer 2. Cmd/State:0xXX
- 80C0, SAFEIN:Error Acknowledge is not possible. Module:0xXX
- 80C1, SAFEIN:Diagnosis Test: Implausible Inputs detected. Module:0xXX
- 80C2, SAFEIN:Diagnosis Test: Implausible Inputs detected (INFO). Parameter1:0xXX / Parameter2:0xXX
- 80E0, SAFEIN:Init HAL Fault.ReturnState:0xXX
- 80E1, SAFEIN:Init Fault. Module:0xXX
- 80F0, SAFEIN: Testpulse is parametrized but not enabled (Diag Testpulse for Inputs active). Module:0xXX / Channel:0xXX
- 80F1, SAFEIN: Testpulse is parametrized but not enabled (Diag TestPulse active). Module:0xXX / Channel:0xXX
- 80F2, SAFEIN: Testfilter-Time too long. Parameter1:0xXX / Parameter2:0xXX
- 80F3, SAFEIN: Inputfilter-Time too short. Parameter1:0xXX / Parameter2:0xXX
- 80F4, SAFEIN: Wrong parameters detected for Module:0xXX / Channel:0xXX. Please check parameters!
- A081, Transition Pre-Op to Safe-Op not successful. Safetycard not detected.
- D000, ENCODER: Module: 0xXX. No Error
- D010, ENCODER: Module: 0xXX in State 0xXX. Microcontroller async detected. Info: 0xXX.
- D020, ENCODER: Module: 0xXX in State 0xXX. Encoder is in State 'Enabled' and Voltage is too low. Info: 0xXX.
- D021, ENCODER: Module: 0xXX in State 0xXX. Encoder is in State 'To Enabled' and Voltage is too low. Info: 0xXX.
- D070, ENCODER: Module: 0xXX in State 0xXX. Encoder is in State 'Disabled' and Voltage is too high. Info: 0xXX.
- D071, ENCODER: Module: 0xXX in State 0xXX. Encoder is in State 'To Disabled' and Voltage is too high. Info: 0xXX.
- D072, ENCODER: Module: 0xXX in State 0xXX. Encoder is in State 'To Enable' and Voltage is too high. Info: 0xXX.
- D073, ENCODER: Module: 0xXX in State 0xXX. Encoder is in State 'Enabled' and Voltage is too high. Info: 0xXX.
- D180, Primary MC: SAFETY FEEDBACK Module: 0xXX in State 0xXX. No Error
- D181, Primary MC: SAFETY FEEDBACK Module: 0xXX in State 0xXX. No new Position received
- D182, Primary MC: SAFETY FEEDBACK Module: 0xXX. Invalid Position. Errorcode: 0xXX Info: 0xXX
- D183, Primary MC: SAFETY FEEDBACK Module: 0xXX in State 0xXX. DriveApplication reports Feedback Error 0xXX
- D184, Primary MC: SAFETY FEEDBACK Module: 0xXX. Safety OCT Feedback not supported by Hardware
- D185, Primary MC: SAFETY FEEDBACK Module: 0xXX. EnDat2.2 Feedback not supported by Hardware
- D186, Primary MC: SAFETY FEEDBACK Invalid drive application data received. Invalid CRC. Module Id: II Calculated CRC: 0xXX Received CRC: 0xXX
- D187, Primary MC: SAFETY FEEDBACK Invalid drive application data received. Invalid Command: 0xXX Module Id: II type: 0xXX
- D188, Primary MC: SAFETY FEEDBACK Module: 0xXX. configured Safety User Parameter CRC (0xXX) did not match with Feedback Parameter CRC
- D189, Primary MC: SAFETY FEEDBACK Module: 0xXX. Module state sync error. local: 0xXX other: 0xXX
- D18A, Primary MC: SAFETY FEEDBACK: FPGA is not validated with this firmware. Elapsed time: II seconds
- D18B, Primary MC: SAFETY FEEDBACK Module: 0xXX. Stored Feedback Parameter CRC (0xXX) and Safety User Parameter CRC (0xXX) did not match
- D18C, Primary MC: SAFETY FEEDBACK Module: 0xXX. Encoder Safety User Parameter CRC configured but Drive Application (Slot Configuration) not set
- D18D, Primary MC: SAFETY FEEDBACK Module: 0xXX. Cannot enable because module is not configured. State: 0xXX DriveAppl: 0xXX
- D18E, Primary MC: SAFETY FEEDBACK Module: 0xXX. Double used Parameter CRC (0xXX). Info: 0xXX
- D18F, Primary MC: SAFETY FEEDBACK Module: 0xXX. Encoder Voltage not enabled. State: 0xXX
- D190, Primary MC: SAFETY FEEDBACK Module: 0xXX. Encoder data buffer overrun. State: 0xXX
- D191, Primary MC: SAFETY FEEDBACK Module: 0xXX. Cannot read Encoder info block. Return Code: 0xXX Info: II
- D192, Primary MC: SAFETY FEEDBACK Invalid drive application data received. Module Id exceeded: II Expected max: II
- D193, Primary MC: SAFETY FEEDBACK Invalid drive application data received. Data length too long: II Expected max: II
- D194, Primary MC: SAFETY FEEDBACK Invalid drive application data received. Data length too short: II Expected min: II
- D195, Primary MC: SAFETY FEEDBACK Module: 0xXX. Invalid drive application data received. Not allowed in this state: II Command: II
- D196, Primary MC: SAFETY FEEDBACK Module: 0xXX. Error during position calculation. Info: 0xXX
- D197, Primary MC: SAFETY FEEDBACK Invalid Safety FPGA interface version. Info: 0xXX
- D198, Primary MC: SAFETY FEEDBACK Module: 0xXX. Invalid Safedrive Settings Parameter II. value: 0xXX
- D199, Primary MC: SAFETY FEEDBACK Module: 0xXX. Not supported by this firmware. CRC: 0xXX
- D19A, Primary MC: SAFETY FEEDBACK Module: 0xXX. Safe user parameter position shift value is too large. SingleturnPositionBits: II PositionShiftValue: II
- D19B, Primary MC: SAFETY FEEDBACK Module: 0xXX. Motor exchange cannot performed. Stored and current Encoder Parameter mismatch (Subidx: II). Current Encoder Index: II
- D19C, Primary MC: SAFETY FEEDBACK Module: 0xXX. Motor exchange cannot performed because other module II is in fault state with errorcode 0xXX
- D19D, Primary MC: SAFETY FEEDBACK Module: 0xXX. Motor exchange detected and successfully done.
- D19E, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: EnableForSetReferencingPosition is disabled but reference position is not zero. Ref SingleturnPos: II RefMultiturnPos: II
- D19F, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: MinimumReferencePostion (Singleturn:0xXX Multiturn:II) is larger than MaximumReferencePosition
- D1A0, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: ReferenceSafePosition (Singleturn:0xXX Multiturn:II) is too small. Position exceeded minimum Range
- D1A1, Primary MC: SAFETY FEEDBACK SafeUserParameter: Cyclic FRAM data size is not large enough. Allocated size: II Requested size: II
- D1A2, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: Difference between minimal and maximal configured position is too large. Difference: Singleturn:0xXX Multiturn:II
- D1A3, Primary MC: SAFETY FEEDBACK Module: 0xXX. Referencing of position in automatic mode is required. No stored position found.
- D1A4, Primary MC: SAFETY FEEDBACK Module: 0xXX. Referencing of position cannot be achieved because motor speed is too high. current Speed: II configured limit: II
- D1A5, Primary MC: SAFETY FEEDBACK Module: 0xXX. Position deviation on startup is too large. Difference: Singleturn:0xXX Multiturn:II
- D1A6, Primary MC: SAFETY FEEDBACK Module: 0xXX. Referenced position exceeded configured minimum range. Current position: Singleturn:0xXX Multiturn:II
- D1A7, Primary MC: SAFETY FEEDBACK Module: 0xXX. Referenced position exceeded configured maximum range. Current position: Singleturn:0xXX Multiturn:II
- D1A8, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: ReferenceSafePosition (Singleturn:0xXX Multiturn:II) is too large. Position exceeded maximum Range
- D1A9, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: Referencing Optional Parameter size is invaild. Info: 0xXX. 0xXX.
- D1AA, Primary MC: SAFETY FEEDBACK Module: 0xXX. Invalid feedback configuration. Same encoder type on primary and secondary feedback is not permitted. Other Module: II type:II
- D1AB, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: Invalid referencing operation mode selected: II
- D1AC, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: ManualReferencing option and SpeedatReferencePosition is not zero. value: II
- D1AD, Primary MC: SAFETY FEEDBACK Module: 0xXX. Position Referencing is not supported because no Multiturn Feedback detected.
- D1AE, Primary MC: SAFETY FEEDBACK Module: 0xXX. Shifted Singleturn Position exceeds 32bit. SingleturnPosBits: II PositionShiftBits: II
- D1AF, Primary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: Online change of Referencing mode is not permitted. Current: II New: II
- D1B0, Primary MC: SAFETY FEEDBACK Module: 0xXX. Manual Referencing requires download of new Safe User Parameter because position range exceeded.
- D280, Secondary MC: SAFETY FEEDBACK Module: 0xXX in State 0xXX. No Error
- D281, Secondary MC: SAFETY FEEDBACK Module: 0xXX in State 0xXX. No new Position received
- D282, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Invalid Position. Errorcode: 0xXX Info: 0xXX
- D283, Secondary MC: SAFETY FEEDBACK Module: 0xXX in State 0xXX. DriveApplication reports Feedback Error 0xXX
- D284, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Safety OCT Feedback not supported by Hardware
- D285, Secondary MC: SAFETY FEEDBACK Module: 0xXX. EnDat2.2 Feedback not supported by Hardware
- D286, Secondary MC: SAFETY FEEDBACK Invalid drive application data received. Invalid Command. Module Id: II type: 0xXX Command: 0xXX
- D287, Secondary MC: SAFETY FEEDBACK Invalid drive application data received. Invalid Command: 0xXX Module Id: II type: 0xXX
- D288, Secondary MC: SAFETY FEEDBACK Module: 0xXX. configured Safety User Parameter CRC (0xXX) did not match with Feedback Parameter CRC
- D289, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Module state sync error. local: 0xXX other: 0xXX
- D28A, Secondary MC: SAFETY FEEDBACK: FPGA is not validated with this firmware. Elapsed time: II seconds
- D28B, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Stored Feedback Parameter CRC (0xXX) and Safety User Parameter CRC (0xXX) did not match
- D28C, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Encoder Safety User Parameter CRC configured but Drive Application (Slot Configuration) not set
- D28D, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Cannot enable because module is not configured. State: 0xXX DriveAppl: 0xXX
- D28E, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Double used Parameter CRC (0xXX). Info: 0xXX
- D28F, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Encoder Voltage not enabled. State: 0xXX
- D290, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Encoder data buffer overrun. State: 0xXX
- D291, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Cannot read Encoder info block. Return Code: 0xXX Info: II
- D292, Secondary MC: SAFETY FEEDBACK Invalid drive application data received. Module Id exceeded: II Expected max: II
- D293, Secondary MC: SAFETY FEEDBACK Invalid drive application data received. Data length too long: II Expected max: II
- D294, Secondary MC: SAFETY FEEDBACK Invalid drive application data received. Data length too short: II Expected min: II
- D295, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Invalid drive application data received. Not allowed in this state: II Command: II
- D296, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Error during position calculation. Info: 0xXX
- D297, Secondary MC: SAFETY FEEDBACK Invalid Safety FPGA interface version. Info: 0xXX
- D298, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Invalid Safedrive Settings Parameter II. value: 0xXX
- D299, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Not supported by this firmware. CRC: 0xXX
- D29A, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Safe user parameter position shift value is too large. SingleturnPositionBits: II PositionShiftValue: II
- D29B, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Motor exchange cannot performed. Stored and current Encoder Parameter mismatch (Subidx: II). Current Encoder Index: II
- D29C, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Motor exchange cannot performed because other module II is in fault state with errorcode 0xXX
- D29D, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Motor exchange detected and successfully done.
- D29E, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: EnableForSetReferencingPosition is disabled but reference position is not zero. Ref SingleturnPos: II RefMultiturnPos: II
- D29F, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: MinimumReferencePostion (Singleturn:0xXX Multiturn:II) is larger than MaximumReferencePosition
- D2A0, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: ReferenceSafePosition (Singleturn:0xXX Multiturn:II) is too small. Position exceeded minimum Range
- D2A1, Secondary MC: SAFETY FEEDBACK SafeUserParameter: Cyclic FRAM data size is not large enough. Allocated size: II Requested size: II
- D2A2, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: Difference between minimal and maximal configured position is too large. Difference: Singleturn:0xXX Multiturn:II
- D2A3, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Referencing of position in automatic mode is required. No stored position found.
- D2A4, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Referencing of position cannot be achieved because motor speed is too high. current Speed: II configured limit: II
- D2A5, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Position deviation on startup is too large. Difference: Singleturn:0xXX Multiturn:II
- D2A6, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Referenced position exceeded configured minimum range. Current position: Singleturn:0xXX Multiturn:II
- D2A7, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Referenced position exceeded configured maximum range. Current position: Singleturn:0xXX Multiturn:II
- D2A8, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: ReferenceSafePosition (Singleturn:0xXX Multiturn:II) is too large. Position exceeded maximum Range
- D2A9, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: Referencing Optional Parameter size is invaild. Info: 0xXX. 0xXX.
- D2AA, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Invalid feedback configuration. Same encoder type on primary and secondary feedback is not permitted. Other Module: II type:II
- D2AB, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: Invalid referencing operation mode selected: II
- D2AC, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: ManualReferencing option and SpeedatReferencePosition is not zero. value: II
- D2AD, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Position Referencing is not supported because no Multiturn Feedback detected.
- D2AE, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Shifted Singleturn Position exceeds 32bit. SingleturnPosBits: II PositionShiftBits: II
- D2AF, Secondary MC: SAFETY FEEDBACK Module: 0xXX. SafeUserParameter: Online change of Referencing mode is not permitted. Current: II New: II
- D2B0, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Manual Referencing requires download of new Safe User Parameter because position range exceeded.
- D300, SafeMotion Axis A Diag Message 1
- D301, SafeMotion Axis A Diag Message 2
- D302, SafeMotion Axis A Diag Message 3
- D303, SafeMotion Axis A Diag Message 4
- D304, SafeMotion Axis A Diag Message 5
- D305, SafeMotion Axis A Diag Message 6
- D306, SafeMotion Axis A Diag Message 7
- D307, SafeMotion Axis A Diag Message 8
- D308, SafeMotion Axis A Diag Message 9
- D309, SafeMotion Axis A Diag Message 10
- D30A, SafeMotion Axis A Diag Message 11
- D30B, SafeMotion Axis A Diag Message 12
- D30C, SafeMotion Axis A Diag Message 13
- D30D, SafeMotion Axis A Diag Message 14
- D30E, SafeMotion Axis A Diag Message 15
- D30F, SafeMotion Axis A Diag Message 16
- D310, SafeMotion Axis B Diag Message 1
- D311, SafeMotion Axis B Diag Message 2
- D312, SafeMotion Axis B Diag Message 3
- D313, SafeMotion Axis B Diag Message 4
- D314, SafeMotion Axis B Diag Message 5
- D315, SafeMotion Axis B Diag Message 6
- D316, SafeMotion Axis B Diag Message 7
- D317, SafeMotion Axis B Diag Message 8
- D318, SafeMotion Axis B Diag Message 9
- D319, SafeMotion Axis B Diag Message 10
- D31A, SafeMotion Axis B Diag Message 11
- D31B, SafeMotion Axis B Diag Message 12
- D31C, SafeMotion Axis B Diag Message 13
- D31D, SafeMotion Axis B Diag Message 14
- D31E, SafeMotion Axis B Diag Message 15
- D31F, SafeMotion Axis B Diag Message 16
- D320, The Safety Control Task watchdog has bveen expired
- 00B1, Safety reports a 'Global Shutdown Error'
- 0115, Controller II: Maximum temperature exceeded. Temperature is 0xXX, should be <= 0xXX.
- 0117, Controller II: Temperature difference too high. Difference is II, should be <= II.
- 0118, Controller II: Maximum voltage alert (Partner_VCC). Voltage is 0xXX, should be <= 0xXX.
- 011A, Controller II: Maximum voltage alert (ECAT_VCC). Voltage is 0xXX, should be <= 0xXX.
- 102C, Unallowed Safe User Parameter Size for the requested features, Received=II Expected=II
- 3112, The activating or deactivating of groups is not allowed in PREOP
- 3115, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of TDCLowerLimit (plus maximum position jitter) (II) is bigger or equal the configured position of 360° (II)
- 3117, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of BDCUpperLimit (II) is smaller or equal the configured value of 180° (plus maximum position jitter) (II)
- 3118, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of BDCLowerLimit (plus maximum position jitter) (II) is greater or equal the configured value of 180° (II)
- 311B, FB CAMMON (Word-Offset 0xXX of the CfgData): The value of TDC1UpperLimit (plus the maximum position jitter) (II) is bigger or equal the configured position of 360° (II)
- 3122, The Download of the Project CRC is not allowed in PREOP
- 3123, The Download of the Change Group Activation data is not allowed if customizing is not supported
- 3414, All groups will enter the ERROR-state because the CRC of the Cyclic FRAM Data was wrong
- 3417, All groups will enter the ERROR-state because the initialization of Cyclic FRAM Data was wrong
- 3418, Safe User Parameter from FRAM are not correct
- 38D0, FB II (ADVPOSMON): The referenced SafeDriveFeedback module (II) is not configured or has no Position Referencing enabled.
- 38D1, FB II (ADVPOSMON): The referenced SafeDriveFeedback module (II) reports error 0xXX.
- 4012, FB II (CAMMON): The Input BackwardsMove is TRUE while the Position is between 180° and 360°, the actual position is II
- 4015, FB II (CAMMON): The value of TDCLowerLimit (plus maximum position jitter) (II) is bigger or equal the configured position of 360° (II)
- 4017, FB II (CAMMON): The value of BDCUpperLimit (II) is smaller or equal the configured value of 180° (plus maximum position jitter) (II)
- 4018, FB II (CAMMON): The value of BDCLowerLimit (plus maximum position jitter) (II) is greater or equal the configured value of 180° (II)
- 401B, FB II (CAMMON): The value of TDC1UpperLimit (plus the maximum position jitter) (II) is bigger or equal the configured position of 360° (II)
- D1B0, Primary MC: SAFETY FEEDBACK Module: 0xXX. Manual Referencing requires download of new Safe User Parameter.
- D1B1, Primary MC: SAFETY FEEDBACK Module: 0xXX. FPGA type is not supported by current Firmware. Protocol reported: II II
- D1B2, Primary MC: SAFETY FEEDBACK Module: 0xXX. EnDat3 Feedback is not supported by Hardware.
- D1B3, Primary MC: SAFETY FEEDBACK Module: 0xXX. The stored encoder Id (II) did not match with the expected id (II). Maybe the axis is reversed.
- D1B4, Primary MC: SAFETY FEEDBACK Module: 0xXX. 64bit calculation is needed for position verification and may result in long safety cycle execution time (Return Code: 0xXX).
- D2B0, Secondary MC: SAFETY FEEDBACK Module: 0xXX. Manual Referencing requires download of new Safe User Parameter.
- D2B1, Secondary MC: SAFETY FEEDBACK Module: 0xXX. FPGA type is not supported by current Firmware. Protocol reported: II II
- D2B2, Secondary MC: SAFETY FEEDBACK Module: 0xXX. EnDat3 Feedback is not supported by Hardware.
- D2B3, Secondary MC: SAFETY FEEDBACK Module: 0xXX. The stored encoder Id (II) did not match with the expected id (II). Maybe the axis is reversed.
- D2B4, Secondary MC: SAFETY FEEDBACK Module: 0xXX. 64bit calculation is needed for position verification and may result in long safety cycle execution time (Return Code: 0xXX).
- D320, The Safety Control Task watchdog has been expired