{28111931-0002-0000-5230-7E0700001100}EL1918, 8K. Safety Eingang 24V, TwinSAFEEL1918, 8Ch. Safety Input 24V, TwinSAFE1Primary MC: GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x}2Primary MC: GLOBAL_Shutdown with Code 0x{0,x} and Additional Code 0x{1,x}3Secondary MC: GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x}4Secondary MC: GLOBAL_Shutdown with Code 0x{0,x} and Additional Code 0x{1,x}5Primary MC: Stored GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x}6Secondary MC: Stored GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x}7Diag-Message-Overflow: {0} messages got lost8Primary MC: the CRC of the FRAM Data was wrong (Diag-Code={0})9Secondary MC: the CRC of the FRAM Data was wrong (Diag-Code={0})16Reserved CfgData has to be zero st offset {0}17The password is wrong18The user was not found19The CRC of the login data does not match20The serial number of the login data does not match21The login watchdog has been expired22The user was logged out before23The user has not sufficient access rights24The reserved area of the CfgData was not 025The CRC of the CfgData was wrong26The user name is wrong at word offset 0x{0,x} when changing the password27The requested number of users is too big29The user update flags are wrong at word offset 0x{0,x} when changing the password30The wrong user (user {0}) is logged in when changing the password (user {1} found in the received data)33the maximum Global-Shutdown counter was exceeded in the Vendor Data (maximum value: {0}, actual value: {1})48Sync Manager 2 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x}49Sync Manager 3 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x}50Sync Manager 4 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x}51Sync Manager 5 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x}52Sync Manager 2 Size ({0}) is invalid, minimum value = {1}, maximum value = {2}53Sync Manager 3 Size ({0}) is invalid, minimum value = {1}, maximum value = {2}54Sync Manager 4 Size ({0}) is invalid, minimum value = {1}, maximum value = {2}55Sync Manager 5 Size ({0}) is invalid, minimum value = {1}, maximum value = {2}56Sync Manager {0} Settings (Offset 4-7) are invalid, expected values = 0x{1,x}, 0x{2,x}68Sync Manager 6 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x}69Sync Manager 7 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x}72Sync Manager 6 Size ({0}) is invalid, minimum value = {1}, maximum value = {2}73Sync Manager 7 Size ({0}) is invalid, minimum value = {1}, maximum value = {2}257Primary MC: Completed RAM TEST: Starttime: 0x{0,x} and Stoptime: 0x{1,x} . The calculated timediff is 0x{2,x}.258Secondary MC: Completed RAM TEST: Starttime: 0x{0,x} and Stoptime: 0x{1,x} . The calculated timediff is 0x{2,x}.259C1 MCTEST Info: Arg1: 0x{0,x}, Arg2: 0x{1,x}, Arg3: 0x{2,x}.260C2 MCTEST Info: Arg1: 0x{0,x}, Arg2: 0x{1,x}, Arg3: 0x{2,x}.277278= 0x{2,x}.]]>279280281= 0x{2,x}.]]>282283= 0x{2,x}.]]>286= 0x{2,x}.]]>287Controller {0}: Minimum value alert (Individual ADC Check). Channel parameter = {1}. Actual value is 0x{2,x}.288Controller {0}: Maximum value alert (Individual ADC Check). Channel parameter = {1}. Actual value is 0x{2,x}.289Module Shutdown due to minimum value alert (Individual ADC Check). Channel parameter = {0}.4096The size of the safe User Parameter is too small ({0}), the expected size is {1}4097The Vendor-ID ({0}) is unequal the expected value of {1}4098The Product-Code ({0}) is unequal the expected value of {1}4099The reserved data of the SafeOut User Parameter of module {0} at byte offset 0x{1,x} has to be 04100The reserved data of the SafeIn User Parameter of module {0} at byte offset 0x{1,x} has to be 04101The standard outputs of module {0} should be enabled but the Sync-Manager 6 is not configured or enabled correctly4102The FASTSTDOUT mode of the standard outputs of module {0} is not supported4103The SAFEOUT-Module-Number ({0}) for the ExternalPulseDetection of the SAFEIN-Module {1} is wrong, the allowed range is 1-{2}4104The SAFEOUT-Channel-Number ({0}) for the ExternalPulseDetection of the SAFEIN-Module {1} is wrong, the allowed range is 1-{2}4105The Bumper-Mode {0} is not supported for SAFEIN-Module {1}4106The version of the Product-Code (0x{0,x}) is unequal the expected value of 0x{1,x}4112The default Project CRC is wrong, the received value is 0x{0,x}4128The watchdog for the Standard Outputs was expired4144The size of the safe User Parameter is too big ({0}), the expected size is {1}5569SAFEIN-Module {0}: Module Fault due to Fault Link5601SAFEOUT-Module:{0}: Overcurrent detected; Counter:0x{1,x}8193The {0}. connection has received an invalid FSoE-Cmd in state CONNECTION8194The {0}. connection has received an unknown FSoE-Cmd in state CONNECTION8195The {0}. connection has received an invalid FSoE-ConnID in state CONNECTION8196The {0}. connection has received an invalid FSoE-CRC in state CONNECTION8197The FSoE-Watchdog of the {0}. connection has been expired in state CONNECTION8198On the {0}. connection the received FSoE-Address (0x{1,x}) does not match with the expected FSoE-Address (0x{2,x})8199On the {0}. connection the received connection data do not match with the sent values8204On the {0}. connection in state CONNECTION the Connection was restarted from the FSoE-Master8206A Module fault was detected on the {0}. connection in state CONNECTION8209On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 1 was received which means that the communication partner has received an invalid FSoE-Cmd8210On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 2 was received which means that the communication partner has received an unknown FSoE-Cmd8211On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 3 was received which means that the communication partner has received an invalid FSoE-ConnID8212On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 4 was received which means that the communication partner has received an invalid FSoE-CRC8213On the {0}. 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 partner8214On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 6 was received which means that the communication partner has received an invalid FSoE-Address8215On the {0}. 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 values8216On the {0}. 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 length8217On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 9 was received which means that the communication partner has received an invalid FSoE Watchdog8218On the {0}. 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 length8219On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 11 was received which means that the communication partner has received invalid application parameter data8220On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 12 was received8221On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 13 was received8222On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 14 was received which means that the communication partner has detected a module fault8223On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 0x{1,x} was received8257The {0}. connection has received an invalid FSoE-Cmd in state PARAMETER8258The {0}. connection has received an unknown FSoE-Cmd in state PARAMETER8259The {0}. connection has received an invalid FSoE-ConnID in state PARAMETER8260The {0}. connection has received an invalid FSoE-CRC in state PARAMETER8261The FSoE-Watchdog of the {0}. connection has been expired in state PARAMETER8263On the {0}. connection the received parameter data do not match with the sent values8264On the {0}. connection the received communication parameter length ({1}) does not match with the expected value of 28265On the {0}. connection the received FSoE Watchdog ({1}) is outside the allowed area from 2 to 600008266On the {0}. connection the received application parameter length ({1}) is unequal the expected length of {2}8267On the {0}. connection the received application parameter data are wrong8268On the {0}. connection in state PARAMETER the Connection was restarted from the FSoE-Master8270A Module fault was detected on the {0}. connection in state PARAMETER8273On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 1 was received which means that the communication partner has received an invalid FSoE-Cmd8274On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 2 was received which means that the communication partner has received an unknown FSoE-Cmd8275On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 3 was received which means that the communication partner has received an invalid FSoE-ConnID8276On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 4 was received which means that the communication partner has received an invalid FSoE-CRC8277On the {0}. 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 partner8278On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 6 was received which means that the communication partner has received an invalid FSoE-Address8279On the {0}. 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 values8280On the {0}. 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 length8281On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 9 was received which means that the communication partner has received an invalid FSoE Watchdog8282On the {0}. 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 length8283On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 11 was received which means that the communication partner has received invalid application parameter data8284On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 12 was received8285On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 13 was received8286On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 14 was received which means that the communication partner has detected a module fault8287On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 0x{1,x} was received8289On the {0}. connection in state PARAMETER a wrong Command was received, which means that the Safe-Parameter size is wrong (Expected size: {1}, Received size: {2})8321The {0}. connection has received an invalid FSoE-Cmd in state DATA8322The {0}. connection has received an unknown FSoE-Cmd in state DATA8323The {0}. connection has received an invalid FSoE-ConnID in state DATA8324The {0}. connection has received an invalid FSoE-CRC in state DATA8325The FSoE-Watchdog of the {0}. connection has been expired in state DATA8332On the {0}. connection in state DATA the Connection was restarted from the FSoE-Master8333The FailSafeData command was received on the {0}. connection in state DATA8334A Module fault was detected on the {0}. connection in state DATA8337On the {0}. connection in state DATA a FSoE-Reset with Error-Code 1 was received which means that the communication partner has received an invalid FSoE-Cmd8338On the {0}. connection in state DATA a FSoE-Reset with Error-Code 2 was received which means that the communication partner has received an unknown FSoE-Cmd8339On the {0}. connection in state DATA a FSoE-Reset with Error-Code 3 was received which means that the communication partner has received an invalid FSoE-ConnID8340On the {0}. connection in state DATA a FSoE-Reset with Error-Code 4 was received which means that the communication partner has received an invalid FSoE-CRC8341On the {0}. 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 partner8342On the {0}. connection in state DATA a FSoE-Reset with Error-Code 6 was received which means that the communication partner has received an invalid FSoE-Address8343On the {0}. 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 values8344On the {0}. 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 length8345On the {0}. connection in state DATA a FSoE-Reset with Error-Code 9 was received which means that the communication partner has received an invalid FSoE Watchdog8346On the {0}. 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 length8347On the {0}. connection in state DATA a FSoE-Reset with Error-Code 11 was received which means that the communication partner has received invalid application parameter data8348On the {0}. connection in state DATA a FSoE-Reset with Error-Code 12 was received8349On the {0}. connection in state DATA a FSoE-Reset with Error-Code 13 was received8350On the {0}. connection in state DATA a FSoE-Reset with Error-Code 14 was received which means that the communication partner has detected a module fault8351On the {0}. connection in state DATA a FSoE-Reset with Error-Code 0x{1,x} was received8385The {0}. connection has received an invalid FSoE-Cmd in state SHUTDOWN8386The {0}. connection has received an unknown FSoE-Cmd in state SHUTDOWN8388The {0}. connection has received an invalid FSoE-CRC in state SHUTDOWN8419The {0}. connection has received the invalid FSoE-ConnID 0 in state SESSION8449On the {0}. connection the PROFIsafe-Slave reports a communication error8450On the {0}. connection the PROFIsafe-Slave reports a watchdog error8451On the {0}. connection the PROFIsafe-Slave reports a device fault8452On the {0}. connection a CRC2-Error was detected locally on the PROFIsafe Host8453On the {0}. connection the Watchdog has been expired locally on the PROFIsafe Host8468On the {0}. connection a CRC2-Error was detected locally on the PROFIsafe Slave8469On the {0}. connection the Watchdog has been expired locally on the PROFIsafe Slave8471On the {0}. connection the Bit 7 of the F_Control is reset, which is not allowed on a PROFIsafe Slave connection with the same message size for inputs and outputs8476On the {0}. connection the PROFIsafe Slave has been restarted locally12288The received number of groups ({0}) was too big, the maximum allowed value is {1}12289The received number of FBs ({0}) was too big, the maximum allowed value is {1}12290The received number of Connections ({0}) was too big, the maximum allowed value is {1}12291The received number of Output Mappings was too big, the maximum allowed value is {0}12292The received number of Input Mappings was too big, the maximum allowed value is {0}12293The received size of Standard Inputs ({0}) was too big, the maximum allowed value is {1}12294The received size of Standard Outputs ({0}) was too big, the maximum allowed value is {1}12295The received number of Restore Slaves ({0}) was too big, the maximum allowed value is {1}12296The SafeCfgData type was unexpected: {0} found and {1} expected12297The SafeCfgData type 2 (Connection) was expected at offset {0}12298The SafeCfgData type 3 (FB) was expected at offset {0}12299The SafeCfgData type 15 (GAP) was expected at offset {0}12300The Bit-Mask in the SafeCfgData was wrong at offset {0}12301The address in the SafeCfgData was wrong at offset {0}12302The Signal number in the SafeCfgData was wrong at offset {0}12303The number of connections was wrong in the SafeCfgData of the Group at offset {0}12304The number of FBs was wrong in the SafeCfgData of the Group at offset {0}12305The size of the SafeCfgData was wrong at offset {0}12306The complete size of the SafeCfgData related to the Group {0} was wrong12307If the RUN-Signal should be mapped internally, it has to be activated at offset {0}12308The message size at offset {0} is invalid12309The connection parameter at offset {0} is invalid12310If the ERRACK-Signal should be mapped internally, it has to be activated at offset {0}12311The connection type at offset {0} is invalid12312The value at offset {0} of the SafeCfgData is invalid12313The value at offset {0} of the SafeCfgData is invalid because at least one of the related signals is not active12314The number of mappings ({0}) is wrong because it is not the last Mapping SafeCfgData12315The Safe Logic Cfg Data were downloaded in the wrong download state ({0})12316The number of mappings ({0}) is too great in the Mapping SafeCfgData12317The Mapping-Size in the SafeCfgData was wrong at offset {0}12318A Group-Input Mapping was expected at offset {0}12319A Connection-Input Mapping was expected at offset {0}12320A FB-Input Bit-Mapping was expected at offset {0}12321A FB-Input Byte-Mapping was expected at offset {0}12322No more mapping was expected at offset {0}12323Invalid Safe User Parameter size at byte offset 0x{0,x} (Found={1}, Expected={2})12324The SafeCfgData type 4 (Safe User Parameter) was expected at offset {0}12325The download of the Input Mapping Cfg Data was refused because {0} groups were missing in the Safe Logic Cfg Data12326The download of the Input Mapping Cfg Data was refused because {0} connections were missing in the Safe Logic Cfg Data12327The download of the Input Mapping Cfg Data was refused because {0} FBs were missing in the Safe Logic Cfg Data12328At least one group has to be defined in the SafeCfgData12329The download of the Input Mapping Cfg Data was refused because no safe Logic Cfg Data were downloaded before12330The Subindex {0} was expected to be downloaded12331When loading CfgData a user has to be logged in before12332The Input Mapping Cfg Data were downloaded in the wrong download state ({0})12333The download of theSafe Logic CfgData is refused because the old Safe Logic Cfg Data were not deleted before12334The user was logged out before12335The user has not sufficient access rights12336The reserved area of the CfgData was not 012337The CRC of the CfgData was wrong12338All needed CfgData pages were downloaded before, no more pages are expected12339The mapping code buffer is too small for the mapping (Offset: 0x{0,x}, Size: {1})12340The maximum allowed subindex is {0}12341The download of the Output Mapping Cfg Data was refused because {0} mappings of the Input Mapping Cfg Data were missing12342{0} input mappings of the groups were missing in the Input Mapping Cfg Data12343{0} input mappings of the connections were missing in the Input Mapping Cfg Data12344{0} input bit mappings of the FBs were missing in the Input Mapping Cfg Data12345{0} input byte mappings of the FBs were missing in the Input Mapping Cfg Data12346The Output Mapping Cfg Data were downloaded in the wrong download state ({0})12347The mapping code buffer is too small for the local mapping12348The download of the Safe Parameter was refused because no Output Mapping Cfg Data were downloaded before12349The download of the Safe User Parameter was refused because {0} mappings of the Output Mapping Cfg Data were missing12350The Safe User Parameter Cfg Data were downloaded in the wrong download state ({0})12351The download of the Activate Project Cfg Data was refused because no Safe User Parameter Cfg Data were downloaded before12352The download of the Activate Project Cfg Data was refused because {0} bytes of the Safe Parameter Cfg Data were missing12353The received activate code (0x{0,x}) was wrong in the Project Cfg Data12354The TwinSAFE Address ({0}) in the Project Cfg Data does not match with the DIP switch ({1})12355At least one Cfg Data page has to be defined in the Safe Logic Cfg Data12356The maximum number ({0}) of Cfg Data pages was exceeded in the Safe Logic Cfg Data12357The received number of Safe Logic Cfg Data pages ({0}) has exceeded the configured value at offset 0 of the Safe Logic Cfg Data ({1})12358The download of the Input Mapping Cfg Data was refused because {0} pages were missing in the Safe Logic Cfg Data12359The Safe Logic Cfg Data CRC does not match in the Safe Project Cfg Data12360When checking the Mapping Code a fault has detected at offset 0x{0,x}12361The Mapping Cfg Data CRC does not match in the Safe Project Cfg Data12362The number of Input Mappings is too small in the Safe Project Cfg Data (Code-Offset=0x{0,x})12363The number of Output Mappings is too small in the Safe Project Cfg Data (Code-Offset=0x{0,x})12364The number of Input Mappings is too great in the Safe Project Cfg Data, ({0} mappings too much, Code-Offset=0x{1,x})12365The number of Output Mappings is too great in the Safe Project Cfg Data, ({0} mappings too much, Code-Offset=0x{1,x})12366The maximum number ({0}) of Cfg Data pages was exceeded in the Safe User Parameter Cfg Data12367At least one Cfg Data page has to be defined in the Safe User Parameter Cfg Data12368The Safe User Parameter Cfg Data CRC does not match in the Safe Project Cfg Data12370The calculated local process image size ({0}) exceeded the maximum local process image size of {1}12371The Activate Project Cfg Data were downloaded in the wrong download state ({0})12372The Delete Project Cfg Data were downloaded in the wrong download state ({0})12373The TwinSAFE Address ({0}) does not match with the DIP switch ({1}) in the Delete Project Cfg Data12374The Delete Code ({0}) is too high in the Delete Project Cfg Data12375Unexpected connection index in the Safe User Parameter Cfg Data at byte offset 0x{0,x}12376The received number of Local Safety Inputs ({0}) was wrong, the expected value is {1}12377The received number of Local Safety Outputs ({0}) was wrong, the expected value is {1}12378The received number of Local Standard Inputs ({0}) was wrong, the expected value is {1}12379The received number of Local Standard Outputs ({0}) was wrong, the expected value is {1}12380The received Safety Input Message size at word offset 15 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12381The received Safety Output Message size at word offset 16 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12382The received Safety Input size at word offset 7 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12383The received Safety Output size at word offset 8 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12384The received PROFIsafe Input Message size at word offset 9 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12385The received PROFIsafe Output Message size at word offset 10 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12386At word offset 0x{0,x} the configured number of CRCs of {1} exceeds the maximum number of CRCs ({2})12387The received SafeUserParameterSizeInFrame ({0}) was wrong, the expected value is {1}12388The received FB Analog Input size at word offset 13 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12389The received FB Analog Output size at word offset 14 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12390The received Connection Status Data size at word offset 21 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12391The received FB Status Data size at word offset 22 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12392The number of active signals in the FB is invalid at offset {0}12393The local map code size in the FB is invalid at offset {0}12394The analog output size in the Group Cfg Data is invalid at offset {0}12395The analog output offset in the Group Cfg Data is invalid at offset {0}12396The received FB Analog Output size at word offset 14 of the Safe Logic Cfg Data ({0}) is unequal the calculated value over all the Group Cfg Data ({1})12397The calculated end of the analog output area ({0}) is unequal the calculated analog output offset over all the Group Cfg Data ({1})12398The value of the FB Cfg Data at offset {0} is invalid12399At least one FB input has to be deactivated in this operation mode at offset {0}12400At least the level of one FB input is wrong in this operation mode at offset {0}12401The value of the FB Cfg Data at word offset {0} is invalid in this operation mode12402The number ({0}) of Cfg Data pages was exceeded in the Info Data Cfg Data at offset 012403The received number of FBs ({0}) at word offset 1 was unequal the configured number of FBs of {1}12404The received FB Status Data Size ({0}) in the Info Data Map Cfg Data at byte offset {1} is unequal the calculated FB Status Data size of {2}12405The received FB Diag Data Size ({0}) in the Info Data Map Cfg Data at byte offset {1} is unequal the calculated FB Diag Data size of {2}12406The received number of Connections ({0}) in the Info Data Cfg Data at word offset {1} was unequal the configured number of connections of {2}12407The received Connection Type ({0}) in the Info Data Map Cfg Data at byte offset {1} is unequal the configured Connection Type of {2}12408The FB Diag Data Map in the Info Data Map Cfg Data was wrong at byte offset {0} (bit 7=1 and bit 6=0 is not allowed)12409The received number of Groups ({0}) in the Info Data Cfg Data at word offset {1} was unequal the configured number of Groups of {2}12410The FB-Type is unknown at offset 0x{0,x}12411The value at offset {0} of the SafeCfgData is too great12412The value at offset {0} of the SafeCfgData is too small12413FB-Muting: if SequentialInputs is TRUE, all MuteIn signals have to be active at offset 0x{0,x}12414The type of the analog inputs has to be the same at offset 0x{0,x}12415The received size of the local safe user parameter ({0}) was wrong, the expected size is {1}12416The value at offset {0} of the SafeCfgData is invalid in combination with the value {1} words before in the SafeCfgData12417The received size of the FB Parameter Data at word offset 25 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12418The FB-Type in the Change FB Parameter Data (FB {0}) is unequal, the expected FB-type is {1}12419The size in the Change FB Parameter Data (FB {0}) is unequal, the expected size is {1}12420The Setting Mode of the FB CAMMON (FB {0}) in the Change FB Parameter Data is not activated12421The actual Logic State ({0}) is unequal RUN (1) when changing FB Parameter Data12422The FB-Number ({0}) in the Change FB Parameter Data is invalid12423The FRAM data size ({0}) has exceeded, the maximum allowed value is {1}12424The Safe User Parameter in the Change FB Parameter Data are not supported12425The size ({0}) of the Change FB Parameter Data is too small, {1} bytes are expected12426The type ({0}) of the Safe User Parameter in the Change FB Parameter Data is wrong12427The size ({0}) of the Safe User Parameter in the Change FB Parameter Data is wrong, the expected size is {1}12428The offset of the Cyclic FRAM Data was wrong at offset {0}12429No Local Input bytes configured for Extended Info Data Mapping12430No Local Output bytes configured for Extended Info Data Mapping12431Too much Local Input bytes configured for Info Data, only 31 bytes are allowed12432Too much Local Output bytes configured for Info Data, only 31 bytes are allowed12436The size 0 is not allowed for the safe user parameter at word offset {0}12437The download of the Activate Project Cfg Data was refused because no Output Mapping Cfg Data were downloaded before12438The download of the Activate Project Cfg Data was refused because {0} mappings of the Output Mapping Cfg Data were missing12439The re-converted FB-Mapping-Code was not matching to the FB Cfg Data (FB: {0}, Code-Address: 0x{1,x}, Offset: 0x{2,x})12440a destination was mapped twice in the bit mapping code (page: 0x{0,x}, Code-Address: 0x{1,x})12441a destination was mapped twice in the byte mapping code (Page: 0x{0,x}, Code-Address: 0x{1,x})12442the number of groups was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12443the number of FBs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12444the number of Connections was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12445the number of Standard Inputs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12446the number of Standard Outputs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12447the FSoE message size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12448the FSoE safe user parameter size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12449the PROFIsafe message size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12450the EtherCAT Output size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12451the EtherCAT Input size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2})12452the EtherCAT Output size was exceeded in the project (calculated value: {0}, maximum value: {1})12453the EtherCAT Input size was exceeded in the project (calculated value: {0}, maximum value: {1})12454when re-converting the local FB mapping code (FB {0}) the analog destination address was below the minimum value (Code-Offset: 0x{1,x}, Data-Offset: 0x{2,x})12455when re-converting the local FB mapping code (FB {0}) the analog destination address was above the maximum value (Code-Offset: 0x{1,x}, Data-Offset: 0x{2,x})12456when re-converting the local FB mapping code (FB {0}) the destination address was not found (Code-Offset: 0x{1,x}, Data-Offset: 0x{2,x})12457when re-converting the local FB mapping code (FB {0}) the digital destination address was below the minimum value (Code-Offset: 0x{1,x}, Data-Offset: 0x{2,x})12458when re-converting the local FB mapping code (FB {0}) the digital destination address was above the maximum value (Code-Offset: 0x{1,x}, Data-Offset: 0x{2,x})12459when re-converting the local FB mapping code (FB {0}) the generated mapping data size was wrong (Code-Offset: 0x{1,x})12460the Project CRC in the Activate Project Cfg Data was wrong12461when re-converting the local FB mapping code the source bit address was wrong (FB: {0}, Code-Offset: 0x{1,x})12462when re-converting the local FB mapping code the source byte address was wrong (FB: {0}, Code-Offset: 0x{1,x})12465wrong subindex order when reading the input mapping cfg data, the expected subindex is {0}12466subindex exceeded when reading the cfg data12467the offset in the Replacement Values cfg data is wrong in the Group cfg data at word-offset 0x{0,x}12468the deactivation mode passivate is enabled and the number of connections is unequal 1 in the Group cfg data at word-offset 0x{0,x}12469the RUN-signal has to be active in the Group cfg data at word-offset 0x{0,x}12470in the Change FB-Parameter (FB {0}) the FB-type {1} is not supported12471the Subindex exceeds the number of connections ({0}) when writing the PROFIsafe F-Parameter12472the Connection-Type {0} does not support PROFIsafe F-Parameter12473the Subindex exceeds the number of connections ({0}) when writing the Store Slave Project CRC Parameter12474the Connection-Type {0} does not support Store Slave Project CRC Parameter12475if there are no Muting sensors behind the AOPD, the Backwards-Mode and optional Check of the OSSD inputs are not allowed12476when optional Check of the OSSD inputs is activated, the Sequential Inputs mode has to be activated too12477The number of Connections ({0}) is unequal the calculated number of connections over all groups ({1})12478The number of FBs ({0}) is unequal the calculated number of FBs over all groups ({1})12479The calculated local near process image size ({0}) exceeded the maximum near local process image size of {1}12480the EtherCAT Output size was exceeded in the connection cfg data at word offset 0x{0,x} (calculated value: {1}, maximum value: {2})12481the EtherCAT Input size was exceeded in the connection cfg data at word offset 0x{0,x} (calculated value: {1}, maximum value: {2})12482the reserved bits in the flags of the Vendor Data were set (actual value: 0x{0,x}, reserved flags: 0x{1,x})12483FB CAMMON: if the Setting Mode is enabled, at least one position marker has to be configured in the cfg data12484Connection Type is not supported at word-offset 0x{0,x} of the cfg data12485writing the PROFIsafe F-Parameter is not allowed in this logic state ({0}), the logic state has to be 1 (RUN)12486The ConnId 0x{0,x} is used at least twice12487The PROFIsafe Address 0x{0,x} is used at least twice12488The FSoE Address 0x{0,x} is used at least twice12489The TwinSAFE SC type {0} is used at least twice12490The TwinSAFE SC CRC 0x{0,x} is used at least twice12491The Connection Index {0} in a FB Connection Shutdown is used at least twice12492It is not allowed that the number of FBs and the number of Connections is zero inside the Group Cfg Data12493the storing of the Store Slave Project CRC Parameter is not supported in connection {0}12494The received size of Safety Input Messages ({0}) was too big, the maximum allowed value is {1}12495The received size of Safety Output Messages ({0}) was too big, the maximum allowed value is {1}12496The received size of PROFIsafe Input Messages ({0}) was too big, the maximum allowed value is {1}12497The received size of PROFIsafe Output Messages ({0}) was too big, the maximum allowed value is {1}12498The Restore Mode is supported on a TwinSAFE SC connection at word-offset 0x{0,x}12499The FB {0} (Connection Shutdown) is assigned to a non FSoE-connection12500The download of the TwinSAFE IO-Project failed because {0} FBs are configured (no FBs allowed)12501When the TwinSAFE-Address in the Project Cfg data should be used, it has to be unequal zero12502When the TwinSAFE-Address in the Project Cfg data should be used, the DIP-switch has to be zero (0x{0,x} found)12503Read aborted because of invalid code buffer offset (Calculated=0x{0,x}, Expected=0x{1,x})12504Invalid Safe User Parameter Offset at word offset 0x{0,x} (Calculated=0x{1,x}, Expected=0x{2,x})12505The Standard Inputs Size of zero is not allowed12506The download of the Replacement Values is not allowed after the download before (download state={0})12507The Info Data Map Cfg Data were downloaded in the wrong download state ({0})12508The offset for the safety-Timer has to be inside the safety Output Area from 0x{0,x} to 0x{1,x}12509The safety input size of connection {0} is zero offset, the Safety Inputs cannot be mapped at byte offset 0x{1,x} of Info Data Map Cfg Data12510The safety output size of connection {0} is zero, the Safety Outputs cannot be mapped at byte offset 0x{1,x} of Info Data Map Cfg Data12511No more safe user parameter expected at byte-offset 0x{0,x} of the Safe User Parameter Cfg Data12512The TwinSAFE Address 0 is not allowed in the Project Cfg Data12513The download of the TwinSAFE IO-Project failed because {0} Groups are configured (only 1 Group allowed)12514The download of the Delete Project Cfg Data is not allowed in this state ({0})12515The destination bit address (0x{0,x}, Bit {1}) already exists in the same mapping code12516Local Inputs cannot be mapped in the Info data because no local inputs are existing12517Local Outputs cannot be mapped in the Info data because no local outputs are existing12518The destination bit address (0x{0,x}, Bit {1}) already exists in the same mapping code12519the input mapping cfg data has to be read before the output mapping cfg data12520wrong subindex order when reading the mapping cfg data, the expected subindex is {0}12521when reading the input mapping cfg data, it has to be started with subindex 112522invalid CRC when checking the Page {0} of the Safe Logic Cfg Data12523invalid CRC when checking the Page {0} of the Safe User Parameter Cfg Data12524invalid CRC when checking the Page {0} of the Replacement values Cfg Data12544No groups defined when trying to activate or deactivate groups12545The reserved bits are set in value {0} at offset {1} when trying to activate or deactivate groups12546The operation mode at offset {0} is not supported when trying to activate or deactivate groups12547The deactivation of groups is not enabled for any group so no replacement values should be downloaded12548The maximum number ({0}) of Cfg Data pages was exceeded in the Replacement Values Cfg Data12549Invalid FB output size size at offset {0} of the Replacement Values Cfg Data12550Unexpected groupindex in the Replacement values Cfg Data at offset 0x{0,x}12551The download of the Activate Project Cfg Data was refused because {0} bytes of the Replacement Values Cfg Data were missing12552To activate the Group {0} the user has to logged in with access rights Bit 0-15 unequal 0 that the Safe Logic Program will be stopped when logging in12553No more definitions of individual replace values for analog FB Outputs in case of Group State unequal RUN are expected at offset {0}12554The offset in the definitions of individual replace values for analog FB Outputs in case of Group State unequal RUN was wrong at offset {0}12555The source process image offset of the Cyclic FRAM Data is outside the FB analog input area at offset {0}12556The source process image offset of the Cyclic FRAM Data has to even at offset {0}12557The size of the Cyclic FRAM Data was exceeding at offset {0}12558The received size of the Cyclic FRAM Data at word offset 24 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1}12559The size of the Cyclic FRAM CfgData in the GroupCfgData was not dividable by 4 at offset {0}12560The offset of the Cyclic FRAM Data in the GroupCfgData was wrong at offset {0}12561The value of {0} at offset {1} is not allowed when trying to activate or deactivate groups12562The activating or deactivating of groups is not allowed in PREOP12563FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The TDC2UpperLimit ({1}) is lower or equal than the maximum position jitter ({2})12564FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The TDCUpperLimit ({1}) is lower or equal than the maximum position jitter ({2})12565FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of TDCLowerLimit (plus maximum position jitter) ({1}) is bigger or equal the configured position of 360° ({2})12566FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of BDCUpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDCLowerLimit ({2})12567FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of BDCUpperLimit ({1}) is smaller or equal the configured value of 180° (plus maximum position jitter) ({2})12568FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of BDCLowerLimit (plus maximum position jitter) ({1}) is greater or equal the configured value of 180° ({2})12569FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of OverrunMax (plus twice the maximum position jitter) ({1}) is bigger or equal the value of BDCLowerLimit ({2})12570FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of TDCUpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of OverrunMax ({2})12571FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of TDC1UpperLimit (plus the maximum position jitter) ({1}) is bigger or equal the configured position of 360° ({2})12572FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of TDC1LowerLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDC1UpperLimit (5d)12573FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of TDC2LowerLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of BDCLowerLimit ({2})12574FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of TDC2UpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDC2LowerLimit ({2})12575The maximum size of the Replacement Values was exceeded at Word-Offset 0x{0,x} of the Group Cfg Data12576If no deactivation mode is enabled the offset of the replacement values shall be zero at Word-Offset 0x{0,x} of the Group Cfg Data12577No more replacement values expected at byte-offset 0x{0,x} of the Replacement Values Cfg Data12578The Download of the Project CRC is not allowed in PREOP12800The PROFIsafe-protocol is not supported on this device12801The F_ParVersion in the F_Prm_Flag2 of the F-Parameter at Word-Offset 0x{0,x} is unequal 1 (PROFIsafe V2)12802The F_CRC1 of the F-Parameter at Word-Offset 0x{0,x} is wrong12803The F_CRC_Length in the F_Prm_Flag1 of the F-Parameter is wrong at Word-Offset 0x{0,x}, the expected value is 0 (3 Bytes CRC2)12806The I-Parameter CRC in the F-Parameter is wrong at Word-Offset 0x{0,x}12807The F_Block_ID in the F_Prm_Flag2 of the F-Parameter is wrong at Word-Offset 0x{0,x}, the expected value is 0 (No F_iPar_CRC, no F_WD_Time 2) or 1 (F_iPar_CRC, no F_WD_Time 2)12808The F_Source_Address in the F-Parameter at Word-Offset 0x{0,x} is outside the allowed area of 1-0xFFFE12809The F_Destination_Address in the F-Parameter at Word-Offset 0x{0,x} is outside the allowed area of 1-0xFFFE12810The F_WD_Time in the F-parameter at Word-Offset 0x{0,x} is outside the allowed range from 2-6000012811The F_Destination_Address in the F-Parameter at Word-Offset 0x{0,x} is wrong, the expected value is {1}13056The State OPERATIONAL was left in Restore Mode13057Only {0} CRCs were matching in Restore Mode13058The CRC of the Activate Project Cfg Data in Restore Mode does not match, the expected value was 0x{0,x}13059No RestoreMode Slaves configured when trying to start the Restore Mode13060The CRC of the User List Cfg Data was not matching in Restore Mode, the expected value was 0x{0,x}13061The download of the User List Cfg Data is not activated in Restore Mode13062The download of the User List Cfg Data in Restore-Mode is not allowed in the state {0}13063The activation of the TwinSAFE Restore Project is not allowed in the state {0}13064The Restore Mode is not supported in EtherCAT state 0x{0,x}13072The FSoE-Slave on the {0}. connection is in Restore-Mode13073The FSoE-Master on the {0}. connection is in Restore-Mode13312The {0}. group has no more errors13313The Analog Input at word offset {0} of the analog input process image has expired maximum allowed deviation to the last stored value, received value: {1}, last stored value: {2}13314The Wait-Com-Error-Timeout has not been expired when the group {0} should be deactivated in passivate mode13315A module fault happened in group {0}13316The assigned connection reported an error when the group {0} was deactivated in passivate mode13317The connection has been successfully restarted when the group {0} was deactivated in passivate mode13328All groups will enter the ERROR-state because the safe logic program has been restarted13329All groups will enter the ERROR-state because the CRC of the Change Group Activation Data was wrong13330All groups will enter the ERROR-state because the CRC of the Change FB Parameter Data was wrong13331All groups will enter the ERROR-state because the CRC of the Project CRC Data was wrong13332All groups will enter the ERROR-state because the CRC of the Cyclic FRAM Data was wrong13333The TwinSAFE Logic Program was not loaded on C1 because of an inconsistency13334The TwinSAFE Logic Program was not loaded on C2 because of an inconsistency13335All groups will enter the ERROR-state because the initialization of Cyclic FRAM Data was wrong13336Safe User Parameter from FRAM are not correct13344No more EtherCAT size error (EtherCAT Output Size={0}, EtherCAT Input Size={1})13345The EtherCAT Output Data sizes of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal13346The EtherCAT Input Data sizes of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal13347The EtherCAT Output Data sizes for PROFIsafe of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal13348The EtherCAT Input Data sizes for PROFIsafe of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal13349The needed EtherCAT Process data buffer size ({0}) exceeded the maximum available size of {1}13569On the {0}. connection the changeable FSoE Address of {1} already exists13570On the {0}. connection the changeable FSoE Address is zero14336FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state SAFE14338FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state RESET14339FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state START14340FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual EStopIn-values are 0x{2,x}14342FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual EStopIn-values are 0x{2,x}14343FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state START, the actual EStopIn-values are 0x{2,x}14345FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual EStopIn-values are 0x{2,x}14351FB {0} (ESTOP): At least one activated EDM-Input was not reset in RUN when the EDM Reset time had been expired (Diag-Code=0x{1,x})14352FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state SAFE14354FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state RESET14355FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state START14356FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual MonIn/Secure-values are 0x{2,x}14358FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual MonIn/Secure-values are 0x{2,x}14359FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state START, the actual MonIn/Secure-values are 0x{2,x}14360FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state RUN, the actual MonIn/Secure-values are 0x{2,x}14361FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual MonIn/Secure-values are 0x{2,x}14362FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state FUNCTEST, the actual MonIn/Secure-values are 0x{2,x}14367FB {0} (MON): At least one activated EDM-Input was not reset in RUN when the EDM Reset time had been expired (Diag-Code=0x{1,x})14368FB {0} (TWOHAND): A Disc-Group-fault (0x{1,x}) was detected in state 1BUTTON, the actual TwoHandIn-values are 0x{2,x}14369FB {0} (TWOHAND): A Disc-Group-fault (0x{1,x}) was detected in state 2BUTTON, the actual TwoHandIn-values are 0x{2,x}14371FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual TwoHandIn-values are 0x{2,x}14373FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual TwoHandIn-values are 0x{2,x}14379FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state 1BUTTON, the actual TwoHandIn-values are 0x{2,x}14380FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state 2BUTTON, the actual TwoHandIn-values are 0x{2,x}14381FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state RELEASE, the actual TwoHandIn-values are 0x{2,x}14384FB {0} (OPMODE): An DiscTime-Fault (0x{1,x}) was detected, the actual OpIn-values are 0x{2,x}14385FB {0} (OPMODE): An Input-Fault was detected in state RESET, the actual OpIn-values are 0x{1,x}14400FB {0} (EDM): The SwitchOn-Time had been expired14401FB {0} (EDM): The SwitchOff-Time had been expired14419FB {0} (CS): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual Deactivate-values are 0x{2,x}14421FB {0} (CS): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual Deactivate-values are 0x{2,x}14465FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state RUN, the actual MuteIn/OssdIn-values are 0x{2,x}14467FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual MuteIn/OssdIn-values are 0x{2,x}14469FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual MuteIn/OssdIn-values are 0x{2,x}14472FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual MuteIn/OssdIn-values are 0x{2,x}14473FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING1, the actual MuteIn/OssdIn-values are 0x{2,x}14474FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING2, the actual MuteIn/OssdIn-values are 0x{2,x}14475FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING3, the actual MuteIn/OssdIn-values are 0x{2,x}14476FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING4, the actual MuteIn/OssdIn-values are 0x{2,x}14477FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING5, the actual MuteIn/OssdIn-values are 0x{2,x}14478FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING6, the actual MuteIn/OssdIn-values are 0x{2,x}14479FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING7, the actual MuteIn/OssdIn-values are 0x{2,x}14480FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING8, the actual MuteIn/OssdIn-values are 0x{2,x}14481FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING9, the actual MuteIn/OssdIn-values are 0x{2,x}14482FB {0} (MUTING): State RUN, Sequential Inputs=TRUE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14483FB {0} (MUTING): State RUN, Sequential Inputs=FALSE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14484FB {0} (MUTING): State MUTING1, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14485FB {0} (MUTING): State MUTING1, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14486FB {0} (MUTING): State MUTING2, MutingEnable is set and the MuteIn-signals before the AOPD are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14487FB {0} (MUTING): State MUTING2, MutingEnable is set and the MuteIn-signals after the AOPD are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14488FB {0} (MUTING): State MUTING3, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14489FB {0} (MUTING): State MUTING3, Sequential Inputs=TRUE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14490FB {0} (MUTING): State MUTING3, Sequential Inputs=FALSE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14491FB {0} (MUTING): State MUTING4, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14492FB {0} (MUTING): State MUTING4, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14493FB {0} (MUTING): State MUTING5, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14494FB {0} (MUTING): State MUTING5, Sequential Inputs=TRUE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14495FB {0} (MUTING): State MUTING5, Sequential Inputs=FALSE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14496FB {0} (MUTING): State MUTING6, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14497FB {0} (MUTING): State MUTING6, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14498FB {0} (MUTING): State MUTING7, MutingEnable is set and the MuteIn-signals before the AOPD are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14499FB {0} (MUTING): State MUTING7, MutingEnable is set and the MuteIn-signals after the AOPD are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14500FB {0} (MUTING): State MUTING8, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14501FB {0} (MUTING): State MUTING8, Sequential Inputs=TRUE, CheckOssdOptional=TRUE: MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14502FB {0} (MUTING): State MUTING8, Sequential Inputs=TRUE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14503FB {0} (MUTING): State MUTING8, Sequential Inputs=FALSE: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14504FB {0} (MUTING): State MUTING9, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14505FB {0} (MUTING): State MUTING9, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14506FB {0} (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 0x{1,x}14507FB {0} (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 0x{1,x}14508FB {0} (MUTING): State MUTING1, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x}14512FB {0} (MUTING): At least one activated EDM-Input was not reset in RUN when the EDM Reset time had been expired (Diag-Code=0x{1,x})14529FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING1 (Digital Inputs=0x{1,x})14530FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING2 (Digital Inputs=0x{1,x})14531FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING3 (Digital Inputs=0x{1,x})14532FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING4 (Digital Inputs=0x{1,x})14533FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING5 (Digital Inputs=0x{1,x})14534FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING6 (Digital Inputs=0x{1,x})14535FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING7 (Digital Inputs=0x{1,x})14536FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING8 (Digital Inputs=0x{1,x})14537FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING9 (Digital Inputs=0x{1,x})16385FB {0} (CAMMON): The TDC2UpperLimit ({1}) is lower or equal than the maximum position jitter ({2})16386FB {0} (CAMMON): The Position ({1}) is bigger than the maximum position (plus the maximum position jitter) ({2})16387FB {0} (CAMMON): The input OverrunCAM was FALSE in the top dead center area, the actual position is {1}16388FB {0} (CAMMON): The input OverrunCAM changed from FALSE to TRUE outside the area between BDCUpperLimit and TDCLowerLimit, the actual position is {1}16389FB {0} (CAMMON): The input OverrunCAM was TRUE in the area between OverrunMax and BDCUpperLimit, the actual position is {1}16390FB {0} (CAMMON): The input OverrunCAM changed from TRUE to FALSE outside the area between OverrunMax and BDCLowerLimit, the actual position is {1}16391FB {0} (CAMMON): The input UpwardsCAM was FALSE in the area between BDCUpperLimit and TDCLowerLimit, the actual position is {1}16392FB {0} (CAMMON): The input UpwardsCAM changed from FALSE to TRUE outside the area between BDCLowerLimit and TDCLowerLimit, the actual position is {1}16393FB {0} (CAMMON): The input UpwardsCAM changed from TRUE to FALSE outside the area between TDCLowerLimit and OverrunMax, the actual position is {1}16394FB {0} (CAMMON): The Position was moving while waiting for a rising edge of the input Reset in the state MOVE-STOP16395FB {0} (CAMMON): The Position was moving while waiting for a falling edge of the input Reset in the state MOVE-START16396FB {0} (CAMMON): The Position {1} in the area between OverrunMax and BDCLowerLimit was detected in the state MOVE-UP16397FB {0} (CAMMON): The Position has left the top dead center while waiting for a stop, the actual position is {1}16398FB {0} (CAMMON): The Position has been changed negative16399FB {0} (CAMMON): The input UpwardsCAM was TRUE in the area between OverrunMax and BDCLowerLimit16400FB {0} (CAMMON): The Position has a circle overflow in Pendulum Mode, actual position={1}, last position={2}16401FB {0} (CAMMON): The Position has moved while waiting for a rising edge of the input Reset in Pendulum Mode, actual position={1}, compare position={2}16402FB {0} (CAMMON): The Input BackwardsMove is TRUE while the Position is between 180° and 360°, the actual position is {1}16403FB {0} (CAMMON): The Input BackwardsMove is TRUE while the moving is clockwise16404FB {0} (CAMMON): The Position has moved while waiting for a falling edge of the input Reset in Pendulum Mode, actual position={1}, last position={2}16405FB {0} (CAMMON): The value of TDCLowerLimit (plus maximum position jitter) ({1}) is bigger or equal the configured position of 360° ({2})16406FB {0} (CAMMON): The value of BDCUpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDCLowerLimit ({2})16407FB {0} (CAMMON): The value of BDCUpperLimit ({1}) is smaller or equal the configured value of 180° (plus maximum position jitter) ({2})16408FB {0} (CAMMON): The value of BDCLowerLimit (plus maximum position jitter) ({1}) is greater or equal the configured value of 180° ({2})16409FB {0} (CAMMON): The value of OverrunMax (plus twice the maximum position jitter) ({1}) is bigger or equal the value of BDCLowerLimit ({2})16410FB {0} (CAMMON): The value of TDCUpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of OverrunMax ({2})16411FB {0} (CAMMON): The value of TDC1UpperLimit (plus the maximum position jitter) ({1}) is bigger or equal the configured position of 360° ({2})16412FB {0} (CAMMON): The value of TDC1LowerLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDC1UpperLimit (5d)16413FB {0} (CAMMON): The value of TDC2LowerLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of BDCLowerLimit ({2})16414FB {0} (CAMMON): The value of TDC2UpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDC2LowerLimit ({2})16415FB {0} (CAMMON): The input PressStarted is TRUE and the position did not move after the PressStartedDelayTime16416FB {0} (CAMMON): The input PressStarted is TRUE and the position has stopped after moving before16417FB {0} (CAMMON): The input PressStarted is TRUE and the position has not moved enough, the actual position is {1}, the compare position is {2}16418FB {0} (CAMMON), Pendulum Mode: The Position has changed contra clockwise while moving up clockwise (actual Position={1}, old Position={2})16419FB {0} (CAMMON), Pendulum Mode: The Position has changed clockwise while moving up contra clockwise (actual Position={1}, old Position={2})16420FB {0} (CAMMON): The Position was moving while waiting for a falling edge of the input Reset in the state WAIT-FOR_RESET16421FB {0} (CAMMON): The TDCUpperLimit ({1}) is lower or equal than the maximum position jitter ({2})16512FB {0} (ADD/SUB): an underflow was detected, AnalogIn1={1}, AnalogIn2={2}16513FB {0} (ADD/SUB): an overflow was detected, AnalogIn1={1}, AnalogIn2={2}16520FB {0} (SPEED): an underflow was detected, actual Position={1}, old Position={2}16521FB {0} (SPEED): an overflow was detected, actual Position={1}, old Position={2}16528FB {0} (LIMIT): the minimum value ({1}) is bigger than the maximum value ({2})16536FB {0} (COMPARE): an underflow was detected on CompOut ({1}), the minimum allowed value is {2}16537FB {0} (COMPARE): an overflow was detected on CompOut ({1}), the maximum allowed value is {2}16544FB {0} (MUL): an underflow was detected, AnalogIn1={1}, AnalogIn2={2}16545FB {0} (MUL): an overflow was detected, AnalogIn1={1}, AnalogIn2={2}16552FB {0} (DIV): an underflow was detected, AnalogIn1={1}, AnalogIn2={2}16553FB {0} (DIV): an overflow was detected, AnalogIn1={1}, AnalogIn2={2}16560FB {0} (SCALE): an underflow was detected, AnalogIn={1}16561FB {0} (SCALE): an overflow was detected, AnalogIn={1}16562FB {0} (SCALE): an overflow was detected after multiplication, AnalogIn={1}16563FB {0} (SCALE): an overflow was detected before division when rounding up the value, AnalogIn={1}16568FB {0} (COUNT): an underflow was detected on ActValue ({1})16569FB {0} (COUNT): an overflow was detected on ActValue ({1})16576FB {0} (SLI): an underflow was detected on ActValue ({1}), the minimum allowed value is {2}16577FB {0} (SLI): an overflow was detected on ActValue ({1}), the maximum allowed value is {2}16584FB {0} (ENVELOPE): an underflow was detected on InValue ({1}), the minimum allowed value is {2}16585FB {0} (ENVELOPE): an overflow was detected on InValue ({1}), the maximum allowed value is {2}16586FB {0} (ENVELOPE): an overflow error was detected on InValue ({1}), InValue+Offset is bigger than the maximum allowed value16587FB {0} (ENVELOPE): the MaxTime was expired (InValue={1})16592FB {0} (SLP): MultiturnPos_LL ({1}) is bigger than MultiturnPos_UL ({2})16593FB {0} (SLP): MultiturnPos_LL=MultiturnPos_UL and SingleturnPos_LL ({1}) is bigger than SingleturnPos_UL ({2})16600FB {0} (SBT): Brake-Test failed in state {1}16601FB {0} (SBT): Brake-Test Interval expired in state {1}16602FB {0} (SBT): Brake-Test failed, Actual Position Deviation={1}, Maximum Position Deviation={2}Interval expired in state {3}24585SAFEOUT:Initial-Parameter: MultiplierDiagTestPulse has to be greater zero. ModuleNr:0x{0,x}24592SAFEOUT:Initial-Parameter: Number of Modules incorrect. ModuleNr:0x{0,x}, Parameter:0x{1,x}24593SAFEOUT:Initial-Parameter: Number of Channels incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24594SAFEOUT:Initial-Parameter: Number of Diagnosis active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24595SAFEOUT:Initial-Parameter: Number of Diagnosis inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24596SAFEOUT:Initial-Parameter: Number of Feedback active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24597SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24598SAFEOUT:Initial-Parameter: Number of Feedback inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24599SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24600SAFEOUT:Initial-Parameter: Number of Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24601SAFEOUT:Initial-Parameter: Number of Diagnosis inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24602SAFEOUT:Initial-Parameter: Number of Feedback active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24603SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24604SAFEOUT:Initial-Parameter: Number of Feedback inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24605SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}24606SAFEOUT:Setup Hardware Fault: Module Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x}24607SAFEOUT:Setup Hardware Fault: Diagnosis active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x}24608SAFEOUT:Setup Hardware Fault: Diagnosis inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x}24609SAFEOUT:Setup Hardware Fault: Feedback active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x}24610SAFEOUT:Setup Hardware Fault: Feedback Diagnosis active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x}24611SAFEOUT:Setup Hardware Fault: Feedback inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x}24612SAFEOUT:Setup Hardware Fault: Feedback Diagnosis inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x}24613SAFEOUT:Setup Hardware Fault: Channel Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x}24614SAFEOUT:Setup Hardware Fault: Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x}24615SAFEOUT:Setup Hardware Fault: Diagnosis inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x}24616SAFEOUT:Setup Hardware Fault: Feedback active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x}24617SAFEOUT:Setup Hardware Fault: Feedback Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x}24618SAFEOUT:Setup Hardware Fault: Feedback inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x}24619SAFEOUT:Setup Hardware Fault: Feedback Diagnosis inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x}24624SAFEOUT:The Feedback of the active Module Switch is wrong. Module:0x{0,x}24625SAFEOUT:The Feedback of the inactive Module Switch is wrong. Module:0x{0,x}24626SAFEOUT:The Feedback of the active Channel Switch is wrong. Module:0x{0,x} / Channel:0x{1,x}24627SAFEOUT:The Feedback of the inactive Channel Switch is wrong. Module:0x{0,x} / Channel:0x{1,x}24640SAFEOUT:Diagnosis Test: Common Fault Module:0x{0,x} / DiagChannel:0x{1,x}24641SAFEOUT:Diagnosis Test: Unknown State local ModuleState:0x{0,x}24642SAFEOUT:Diagnosis Test: Unknown State other ModuleState:0x{0,x}24656SAFEOUT:Diagnosis Test: Feedback active Module Switch is wrong (Step1 - check current state). Module:0x{0,x}24657SAFEOUT:Diagnosis Test: Feedback inactive Module Switch is wrong (Step1 - check current state). Module:0x{0,x}24658SAFEOUT:Diagnosis Test: Feedback active Channel Switch is wrong (Step1 - check current state). Module:0x{0,x} / DiagChannel:0x{1,x}24659SAFEOUT:Diagnosis Test: Feedback inactive Channel Switch is wrong (Step1 - check current state). Module:0x{0,x} / DiagChannel:0x{1,x}24672SAFEOUT:Diagnosis Test: Feedback active Module Switch is wrong (Step2 - check test pulse). Module:0x{0,x}24673SAFEOUT:Diagnosis Test: Feedback inactive Module Switch is wrong (Step2 - check test pulse). Module:0x{0,x}24674SAFEOUT:Diagnosis Test: Feedback active Channel Switch is wrong (Step2 - check test pulse). Module:0x{0,x} / DiagChannel:0x{1,x}24675SAFEOUT:Diagnosis Test: Feedback inactive Channel Switch is wrong (Step2 - check test pulse). Module:0x{0,x} / DiagChannel:0x{1,x}24704SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x}24705SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x}24706SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x}24707SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x}24708SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x}24709SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x}24710SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x}24720SAFEOUT:Module Switch FeedbackTest ViolationCounter incremented, Outputs active. Module:0x{0,x}, Info:0x{1,x}.24721SAFEOUT:Module Switch FeedbackTest ViolationCounter incremented, Outputs inactive. Module:0x{0,x}, Info:0x{1,x}.24722SAFEOUT:Channel Switch FeedbackTest ViolationCounter incremented, Outputs active. Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}.24723SAFEOUT:Channel Switch FeedbackTest ViolationCounter incremented, Outputs inactive. Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}.24724SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step1 - check current state). Module:0x{0,x}, Info:0x{1,x}.24725SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step1 - check current state). Module:0x{0,x}, Info:0x{1,x}.24726SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}.24727SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}.24728SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step2 - check test pulse). Module:0x{0,x}, Info:0x{1,x}.24729SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step2 - check test pulse). Module:0x{0,x}, Info:0x{1,x}.24730SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}.24731SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}.24736SAFEOUT:Sercom Fault 0. Cmd/State:0x{0,x}24737SAFEOUT:Sercom Fault 1. Cmd/State:0x{0,x}24752SAFEOUT:Unknown Sercom Command Request 1. Cmd/State:0x{0,x}24753SAFEOUT:Unknown Sercom Command Answer 1. Cmd/State:0x{0,x}24754SAFEOUT:Unknown Sercom Command Request 2. Cmd/State:0x{0,x}24755SAFEOUT:Unknown Sercom Command Answer 2. Cmd/State:0x{0,x}24768SAFEOUT:Module Switch too fast Switching OFF detected Fault (see technical data). Module:0x{0,x}24769SAFEOUT:Channel Switch too fast Switching OFF detected Fault (see technical data). Module:0x{0,x} / Channel:0x{1,x}24770SAFEOUT:Module Switch too fast Switching ON detected Fault (see technical data). Module:0x{0,x}24771SAFEOUT:Channel Switch too fast Switching ON detected Fault (see technical data). Module:0x{0,x} / Channel:0x{1,x}24772SAFEOUT:Module Error Acknowledge is not possible. Module:0x{0,x}24800SAFEOUT:HAL Read Fault. ReturnData:0x{0,x}24801SAFEOUT:Init Fault. Module:0x{0,x}32777SAFEIN:Initial-Parameter: MultiplierDiagTestPulse has to be greater zero. ModuleNr:0x{0,x}32784SAFEIN:Initial-Parameter: Number of Modules incorrect. ModuleNr:0x{0,x}, Parameter:0x{1,x}32785SAFEIN:Initial-Parameter: Number of Channels incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}32792SAFEIN:Initial-Parameter: Number of Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}32795SAFEIN:Initial-Parameter: Number of Feedback Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x}32805SAFEIN:Setup Hardware Fault: Channel Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x}32806SAFEIN:Setup Hardware Fault: Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x}32809SAFEIN:Setup Hardware Fault: Feedback Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x}32832SAFEIN:Diagnosis Test: Common Fault Module:0x{0,x} / DiagChannel:0x{1,x}32833SAFEIN:Diagnosis Test: Unknown State local ModuleState:0x{0,x}32834SAFEIN:Diagnosis Test: Unknown State Other ModuleState:0x{0,x}32835SAFEIN Pulse Detection: Wrong pulse was detected at . Module:0x{0,x} / DiagChannel:0x{1,x}32836SAFEIN Pulse Detection: Detected pulse from Module:0x{0,x} / DiagChannel:0x{1,x}32850SAFEIN:Diagnosis Test: Feedback in Step1 active Channel is wrong. Module:0x{0,x} / DiagChannel:0x{1,x}32866SAFEIN:Diagnosis Test: Feedback in Step2 active Channel is wrong. Module:0x{0,x} / DiagChannel:0x{1,x}32896SAFEIN:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x}32897SAFEIN:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x}32900SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x}32901SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x}32902SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x}32918SAFEIN:DiagnosisTest ViolationCounter incremented, Inputs active (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}.32922SAFEIN:DiagnosisTest ViolationCounter incremented, Inputs active (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}.32928SAFEIN:Sercom Fault 0. Cmd/State:0x{0,x}32929SAFEIN:Sercom Fault 1. Cmd/State:0x{0,x}32944SAFEIN:Unknown Sercom Command Request 1. Cmd/State:0x{0,x}32945SAFEIN:Unknown Sercom Command Answer 1. Cmd/State:0x{0,x}32946SAFEIN:Unknown Sercom Command Request 2. Cmd/State:0x{0,x}32947SAFEIN:Unknown Sercom Command Answer 2. Cmd/State:0x{0,x}32960SAFEIN:Error Acknowledge is not possible. Module:0x{0,x}32961SAFEIN:Diagnosis Test: Implausible Inputs detected. Module:0x{0,x}32962SAFEIN:Diagnosis Test: Implausible Inputs detected (INFO). Parameter1:0x{0,x} / Parameter2:0x{1,x}32992SAFEIN:Init HAL Fault.ReturnState:0x{0,x}32993SAFEIN:Init Fault. Module:0x{0,x}33008SAFEIN: Testpulse is parametrized but not enabled (Diag Testpulse for Inputs active). Module:0x{0,x} / Channel:0x{1,x}33009SAFEIN: Testpulse is parametrized but not enabled (Diag TestPulse active). Module:0x{0,x} / Channel:0x{1,x}33010SAFEIN: Testfilter-Time too long. Parameter1:0x{0,x} / Parameter2:0x{1,x}33011SAFEIN: Inputfilter-Time too short. Parameter1:0x{0,x} / Parameter2:0x{1,x}33012SAFEIN: Wrong parameters detected for Module:0x{0,x} / Channel:0x{1,x}. Please check parameters!DisplayTxtIdtrue{28111931-0002-0000-5230-B61721001300}EL6070-0033 1K. Licence-Key-Klemme, individuelle LizenzenEL6070-0033 1Ch. Licence key terminal, individual licences4736File {0} erased successfullyFile {0} erased successfully17037Challenge is not Random33409Ownership failed: {0,X}33410Too many Keys foundedToo many Keys founded33411Key Creation failed: {0,X}Key Creation failed: {0,X}33412Key loading failed: {0,X}Key loading failed: {0,X}33413Reading Public Key failed: {0,X}Reading Public Key failed: {0,X}33414Reading Public EK failed: {0,X}Reading Public EK failed: {0,X}33415Reading PCR Value failed: {0,X}33416Reading Certificate EK failed: {0,X}33417Challenge could not be hashed: {0,X}Challenge could not be hashed: {0,X}33418Tickstamp Process failed: {0,X}Tickstamp Process failed: {0,X}33419PCR Process failed: {0,X}PCR Process failed: {0,X}33420Quote Process failed: {0,X}33535No Boot ModeNo Boot Mode34561Operatingtime was manipulatedOperatingtime was manipulatedDisplayTxtIdtrue