{28111931-0002-0000-5230-B61700001300} EL6070 1K. Lizenzierungs-Klemme EL6070 1Ch. Licensing-Terminal 4736 File {0} erased successfully File {0} erased successfully 17037 Challenge is not Random 33409 Ownership failed: {0,X} 33410 Too many Keys founded Too many Keys founded 33411 Key Creation failed: {0,X} Key Creation failed: {0,X} 33412 Key loading failed: {0,X} Key loading failed: {0,X} 33413 Reading Public Key failed: {0,X} Reading Public Key failed: {0,X} 33414 Reading Public EK failed: {0,X} Reading Public EK failed: {0,X} 33415 Reading PCR Value failed: {0,X} 33416 Reading Certificate EK failed: {0,X} 33417 Challenge could not be hashed: {0,X} Challenge could not be hashed: {0,X} 33418 Tickstamp Process failed: {0,X} Tickstamp Process failed: {0,X} 33419 PCR Process failed: {0,X} PCR Process failed: {0,X} 33420 Quote Process failed: {0,X} 33535 No Boot Mode No Boot Mode 34561 Operatingtime was manipulated Operatingtime was manipulated DisplayTxtId true {28111931-0002-0000-5230-7E0700001000} EL1918, 8K. Safety Eingang 24V, TwinSAFE EL1918, 8Ch. Safety Input 24V, TwinSAFE 1 Primary MC: GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x} 2 Primary MC: GLOBAL_Shutdown with Code 0x{0,x} and Additional Code 0x{1,x} 3 Secondary MC: GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x} 4 Secondary MC: GLOBAL_Shutdown with Code 0x{0,x} and Additional Code 0x{1,x} 5 Primary MC: Stored GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x} 6 Secondary MC: Stored GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x} 7 Diag-Message-Overflow: {0} messages got lost 8 Primary MC: the CRC of the FRAM Data was wrong (Diag-Code={0}) 9 Secondary MC: the CRC of the FRAM Data was wrong (Diag-Code={0}) 16 Reserved CfgData has to be zero st offset {0} 17 The password is wrong 18 The user was not found 19 The CRC of the login data does not match 20 The serial number of the login data does not match 21 The login watchdog has been expired 22 The user was logged out before 23 The user has not sufficient access rights 24 The reserved area of the CfgData was not 0 25 The CRC of the CfgData was wrong 26 The user name is wrong at word offset 0x{0,x} when changing the password 27 The requested number of users is too big 29 The user update flags are wrong at word offset 0x{0,x} when changing the password 30 The wrong user (user {0}) is logged in when changing the password (user {1} found in the received data) 33 the maximum Global-Shutdown counter was exceeded in the Vendor Data (maximu value: {0}, actual value: {1}) 48 Sync Manager 2 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 49 Sync Manager 3 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 50 Sync Manager 4 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 51 Sync Manager 5 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 52 Sync Manager 2 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 53 Sync Manager 3 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 54 Sync Manager 4 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 55 Sync Manager 5 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 56 Sync Manager {0} Settings (Offset 4-7) are invalid, expected values = 0x{1,x}, 0x{2,x} 68 Sync Manager 6 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 69 Sync Manager 7 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 72 Sync Manager 6 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 73 Sync Manager 7 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 257 Primary MC: Completed RAM TEST: Starttime: 0x{0,x} and Stoptime: 0x{1,x} . The calculated timediff is 0x{2,x}. 258 Secondary MC: Completed RAM TEST: Starttime: 0x{0,x} and Stoptime: 0x{1,x} . The calculated timediff is 0x{2,x}. 259 C1 MCTEST Info: Arg1: 0x{0,x}, Arg2: 0x{1,x}, Arg3: 0x{2,x}. 260 C2 MCTEST Info: Arg1: 0x{0,x}, Arg2: 0x{1,x}, Arg3: 0x{2,x}. 277 278 = 0x{2,x}.]]> 279 280 281 = 0x{2,x}.]]> 282 283 = 0x{2,x}.]]> 286 = 0x{2,x}.]]> 287 Controller {0}: Minimum value alert (Individual ADC Check). Channel parameter = {1}. Actual value is 0x{2,x}. 288 Controller {0}: Maximum value alert (Individual ADC Check). Channel parameter = {1}. Actual value is 0x{2,x}. 289 Module Shutdown due to minimum value alert (Individual ADC Check). Channel parameter = {0}. 4096 The size of the safe User Parameter is too small ({0}), the expected size is {1} 4097 The Vendor-ID ({0}) is unequal the expected value of {1} 4098 The Product-Code ({0}) is unequal the expected value of {1} 4099 The reserved data of the SafeOut User Parameter of module {0} at byte offset 0x{1,x} has to be 0 4100 The reserved data of the SafeIn User Parameter of module {0} at byte offset 0x{1,x} has to be 0 4101 The standard outputs of module {0} should be enabled but the Sync-Manager 6 is not configured or enabled correctly 4102 The FASTSTDOUT mode of the standard outputs of module {0} is not supported 4103 The SAFEOUT-Module-Number ({0}) for the ExternalPulseDetection of the SAFEIN-Module {1} is wrong, the allowed range is 1-{2} 4104 The SAFEOUT-Channel-Number ({0}) for the ExternalPulseDetection of the SAFEIN-Module {1} is wrong, the allowed range is 1-{2} 4105 The Bumper-Mode {0} is not supported for SAFEIN-Module {1} 4106 The version of the Product-Code (0x{0,x}) is unequal the expected value of 0x{1,x} 4112 The default Project CRC is wrong, the received value is 0x{0,x} 4128 The watchdog for the Standard Outputs was expired 4144 The size of the safe User Parameter is too big ({0}), the expected size is {1} 5569 SAFEIN-Module {0}: Module Fault due to Fault Link 8193 The {0}. connection has received an invalid FSoE-Cmd in state CONNECTION 8194 The {0}. connection has received an unknown FSoE-Cmd in state CONNECTION 8195 The {0}. connection has received an invalid FSoE-ConnID in state CONNECTION 8196 The {0}. connection has received an invalid FSoE-CRC in state CONNECTION 8197 The FSoE-Watchdog of the {0}. connection has been expired in state CONNECTION 8198 On the {0}. connection the received FSoE-Address (0x{1,x}) does not match with the expected FSoE-Address (0x{2,x}) 8199 On the {0}. connection the received connection data do not match with the sent values 8206 A Module fault was detected on the {0}. connection in state CONNECTION 8209 On 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-Cmd 8210 On 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-Cmd 8211 On 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-ConnID 8212 On 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-CRC 8213 On 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 partner 8214 On 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-Address 8215 On 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 values 8216 On 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 length 8217 On 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 Watchdog 8218 On 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 length 8219 On 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 data 8220 On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 12 was received 8221 On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 13 was received 8222 On 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 fault 8223 On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 0x{1,x} was received 8257 The {0}. connection has received an invalid FSoE-Cmd in state PARAMETER 8258 The {0}. connection has received an unknown FSoE-Cmd in state PARAMETER 8259 The {0}. connection has received an invalid FSoE-ConnID in state PARAMETER 8260 The {0}. connection has received an invalid FSoE-CRC in state PARAMETER 8261 The FSoE-Watchdog of the {0}. connection has been expired in state PARAMETER 8263 On the {0}. connection the received parameter data do not match with the sent values 8264 On the {0}. connection the received communication parameter length ({1}) does not match with the expected value of 2 8265 On the {0}. connection the received FSoE Watchdog ({1}) is outside the allowed area from 2 to 60000 8266 On the {0}. connection the received application parameter length ({1}) is unequal the expected length of {2} 8267 On the {0}. connection the received application parameter data are wrong 8270 A Module fault was detected on the {0}. connection in state PARAMETER 8273 On 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-Cmd 8274 On 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-Cmd 8275 On 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-ConnID 8276 On 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-CRC 8277 On 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 partner 8278 On 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-Address 8279 On 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 values 8280 On 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 length 8281 On 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 Watchdog 8282 On 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 length 8283 On 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 data 8284 On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 12 was received 8285 On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 13 was received 8286 On 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 fault 8287 On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 0x{1,x} was received 8289 On 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}) 8321 The {0}. connection has received an invalid FSoE-Cmd in state DATA 8322 The {0}. connection has received an unknown FSoE-Cmd in state DATA 8323 The {0}. connection has received an invalid FSoE-ConnID in state DATA 8324 The {0}. connection has received an invalid FSoE-CRC in state DATA 8325 The FSoE-Watchdog of the {0}. connection has been expired in state DATA 8333 The FailSafeData command was received on the {0}. connection in state DATA 8334 A Module fault was detected on the {0}. connection in state DATA 8337 On 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-Cmd 8338 On 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-Cmd 8339 On 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-ConnID 8340 On 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-CRC 8341 On 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 partner 8342 On 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-Address 8343 On 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 values 8344 On 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 length 8345 On 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 Watchdog 8346 On 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 length 8347 On 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 data 8348 On the {0}. connection in state DATA a FSoE-Reset with Error-Code 12 was received 8349 On the {0}. connection in state DATA a FSoE-Reset with Error-Code 13 was received 8350 On 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 fault 8351 On the {0}. connection in state DATA a FSoE-Reset with Error-Code 0x{1,x} was received 8385 The {0}. connection has received an invalid FSoE-Cmd in state SHUTDOWN 8386 The {0}. connection has received an unknown FSoE-Cmd in state SHUTDOWN 8388 The {0}. connection has received an invalid FSoE-CRC in state SHUTDOWN 8419 The {0}. connection has received the invalid FSoE-ConnID 0 in state SESSION 8449 On the {0}. connection the PROFIsafe-Slave reports a communication error 8450 On the {0}. connection the PROFIsafe-Slave reports a watchdog error 8451 On the {0}. connection the PROFIsafe-Slave reports a device fault 8452 On the {0}. connection a CRC2-Error was detected locally on the PROFIsafe Host 8453 On the {0}. connection the Watchdog has been expired locally on the PROFIsafe Host 8468 On the {0}. connection a CRC2-Error was detected locally on the PROFIsafe Slave 8469 On the {0}. connection the Watchdog has been expired locally on the PROFIsafe Slave 8471 On 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 outputs 8476 On the {0}. connection the PROFIsafe Slave has been restarted locally 12288 The received number of groups ({0}) was too big, the maximum allowed value is {1} 12289 The received number of FBs ({0}) was too big, the maximum allowed value is {1} 12290 The received number of Connections ({0}) was too big, the maximum allowed value is {1} 12291 The received number of Output Mappings was too big, the maximum allowed value is {0} 12292 The received number of Input Mappings was too big, the maximum allowed value is {0} 12293 The received size of Standard Inputs ({0}) was too big, the maximum allowed value is {1} 12294 The received size of Standard Outputs ({0}) was too big, the maximum allowed value is {1} 12295 The received number of Restore Slaves ({0}) was too big, the maximum allowed value is {1} 12296 The SafeCfgData type was unexpected: {0} found and {1} expected 12297 The SafeCfgData type 2 (Connection) was expected at offset {0} 12298 The SafeCfgData type 3 (FB) was expected at offset {0} 12299 The SafeCfgData type 15 (GAP) was expected at offset {0} 12300 The Bit-Mask in the SafeCfgData was wrong at offset {0} 12301 The address in the SafeCfgData was wrong at offset {0} 12302 The Signal number in the SafeCfgData was wrong at offset {0} 12303 The number of connections was wrong in the SafeCfgData of the Group at offset {0} 12304 The number of FBs was wrong in the SafeCfgData of the Group at offset {0} 12305 The size of the SafeCfgData was wrong at offset {0} 12306 The complete size of the SafeCfgData related to the Group {0} was wrong 12307 If the RUN-Signal should be mapped internally, it has to be activated at offset {0} 12308 The message size at offset {0} is invalid 12309 The connection parameter at offset {0} is invalid 12310 If the ERRACK-Signal should be mapped internally, it has to be activated at offset {0} 12311 The connection type at offset {0} is invalid 12312 The value at offset {0} of the SafeCfgData is invalid 12313 The value at offset {0} of the SafeCfgData is invalid because at least one of the related signals is not active 12314 The number of mappings ({0}) is wrong because it is not the last Mapping SafeCfgData 12315 The Safe Logic Cfg Data were downloaded in the wrong download state ({0}) 12316 The number of mappings ({0}) is too great in the Mapping SafeCfgData 12317 The Mapping-Size in the SafeCfgData was wrong at offset {0} 12318 A Group-Input Mapping was expected at offset {0} 12319 A Connection-Input Mapping was expected at offset {0} 12320 A FB-Input Bit-Mapping was expected at offset {0} 12321 A FB-Input Byte-Mapping was expected at offset {0} 12322 No more mapping was expected at offset {0} 12323 Invalid Safe User Parameter size at byte offset 0x{0,x} (Found={1}, Expected={2}) 12324 The SafeCfgData type 4 (Safe User Parameter) was expected at offset {0} 12325 The download of the Input Mapping Cfg Data was refused because {0} groups were missing in the Safe Logic Cfg Data 12326 The download of the Input Mapping Cfg Data was refused because {0} connections were missing in the Safe Logic Cfg Data 12327 The download of the Input Mapping Cfg Data was refused because {0} FBs were missing in the Safe Logic Cfg Data 12328 At least one group has to be defined in the SafeCfgData 12329 The download of the Input Mapping Cfg Data was refused because no safe Logic Cfg Data were downloaded before 12330 The Subindex {0} was expected to be downloaded 12331 When loading CfgData a user has to be logged in before 12332 The Input Mapping Cfg Data were downloaded in the wrong download state ({0}) 12333 The download of theSafe Logic CfgData is refused because the old Safe Logic Cfg Data were not deleted before 12334 The user was logged out before 12335 The user has not sufficient access rights 12336 The reserved area of the CfgData was not 0 12337 The CRC of the CfgData was wrong 12338 All needed CfgData pages were downloaded before, no more pages are expected 12339 The mapping code buffer is too small for the mapping 12340 The maximum allowed subindex is {0} 12341 The download of the Output Mapping Cfg Data was refused because {0} mappings of the Input Mapping Cfg Data were missing 12342 {0} input mappings of the groups were missing in the Input Mapping Cfg Data 12343 {0} input mappings of the connections were missing in the Input Mapping Cfg Data 12344 {0} input bit mappings of the FBs were missing in the Input Mapping Cfg Data 12345 {0} input byte mappings of the FBs were missing in the Input Mapping Cfg Data 12346 The Output Mapping Cfg Data were downloaded in the wrong download state ({0}) 12347 The mapping code buffer is too small for the local mapping 12348 The download of the Safe Parameter was refused because no Output Mapping Cfg Data were downloaded before 12349 The download of the Safe User Parameter was refused because {0} mappings of the Output Mapping Cfg Data were missing 12350 The Safe User Parameter Cfg Data were downloaded in the wrong download state ({0}) 12351 The download of the Activate Project Cfg Data was refused because no Safe User Parameter Cfg Data were downloaded before 12352 The download of the Activate Project Cfg Data was refused because {0} bytes of the Safe Parameter Cfg Data were missing 12353 The received activate code (0x{0,x}) was wrong in the Project Cfg Data 12354 The TwinSAFE Address ({0}) in the Project Cfg Data does not match with the DIP switch ({1}) 12355 At least one Cfg Data page has to be defined in the Safe Logic Cfg Data 12356 The maximum number ({0}) of Cfg Data pages was exceeded in the Safe Logic Cfg Data 12357 The received number of Safe Logic Cfg Data pages ({0}) has exceeded the configured value at offset 0 of the Safe Logic Cfg Data ({1}) 12358 The download of the Input Mapping Cfg Data was refused because {0} pages were missing in the Safe Logic Cfg Data 12359 The Safe Logic Cfg Data CRC does not match in the Safe Project Cfg Data 12360 When checking the Mapping Code a fault has detected at offset 0x{0,x} 12361 The Mapping Cfg Data CRC does not match in the Safe Project Cfg Data 12362 The number of Input Mappings is too small in the Safe Project Cfg Data (Code-Offset=0x{0,x}) 12363 The number of Output Mappings is too small in the Safe Project Cfg Data (Code-Offset=0x{0,x}) 12364 The number of Input Mappings is too great in the Safe Project Cfg Data, ({0} mappings too much, Code-Offset=0x{1,x}) 12365 The number of Output Mappings is too great in the Safe Project Cfg Data, ({0} mappings too much, Code-Offset=0x{1,x}) 12366 The maximum number ({0}) of Cfg Data pages was exceeded in the Safe User Parameter Cfg Data 12367 At least one Cfg Data page has to be defined in the Safe User Parameter Cfg Data 12368 The Safe User Parameter Cfg Data CRC does not match in the Safe Project Cfg Data 12370 The caluculated local process image size ({0}) exceeded the maximum local process image size of {1} 12371 The Activate Project Cfg Data were downloaded in the wrong download state ({0}) 12372 The Delete Project Cfg Data were downloaded in the wrong download state ({0}) 12373 The TwinSAFE Address ({0}) does not match with the DIP switch ({1}) in the Delete Project Cfg Data 12374 The Delete Code ({0}) is too high in the Delete Project Cfg Data 12375 Unexpected connection index in the Safe User Parameter Cfg Data at byte offset 0x{0,x} 12376 The received number of Local Safety Inputs ({0}) was wrong, the expected value is {1} 12377 The received number of Local Safety Outputs ({0}) was wrong, the expected value is {1} 12378 The received number of Local Standard Inputs ({0}) was wrong, the expected value is {1} 12379 The received number of Local Standard Outputs ({0}) was wrong, the expected value is {1} 12380 The received Safety Input Message size at word offset 15 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12381 The received Safety Output Message size at word offset 16 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12382 The received Safety Input size at word offset 7 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12383 The received Safety Output size at word offset 8 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12384 The received PROFIsafe Input Message size at word offset 9 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12385 The received PROFIsafe Output Message size at word offset 10 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12386 At word offset 0x{0,x} the configured number of CRCs of {1} exceeds the maximum number of CRCs ({2}) 12388 The received FB Analog Input size at word offset 13 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12389 The received FB Analog Output size at word offset 14 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12390 The received Connection Status Data size at word offset 21 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12391 The received FB Status Data size at word offset 22 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12392 The number of active signals in the FB is invalid at offset {0} 12393 The local map code size in the FB is invalid at offset {0} 12394 The analog output size in the Group Cfg Data is invalid at offset {0} 12395 The analog output offset in the Group Cfg Data is invalid at offset {0} 12396 The 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}) 12397 The caluculated end of the analog output area ({0}) is unequal the calculated analog output offset over all the Group Cfg Data ({1}) 12398 The value of the FB Cfg Data at offset {0} is invalid 12399 At least one FB input has to be deactivated in this operation mode at offset {0} 12400 At least the level of one FB input is wrong in this operation mode at offset {0} 12401 The value of the FB Cfg Data at word offset {0} is invalid in this operation mode 12402 The number ({0}) of Cfg Data pages was exceeded in the Info Data Cfg Data at offset 0 12403 The received number of FBs ({0}) at word offset 1 was unequal the configured number of FBs of {1} 12404 The 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} 12405 The 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} 12406 The received number of Connections ({0}) in the Info Data Cfg Data at word offset {1} was unequal the configured number of connections of {2} 12407 The received Connection Type ({0}) in the Info Data Map Cfg Data at byte offset {1} is unequal the configured Connection Type of {2} 12408 The 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) 12409 The received number of Groups ({0}) in the Info Data Cfg Data at word offset {1} was unequal the configured number of Groups of {2} 12410 The FB-Type is unknown at offet 0x{0,x} 12411 The value at offset {0} of the SafeCfgData is too great 12412 The value at offset {0} of the SafeCfgData is too small 12413 FB-Muting: if SequentialInputs is TRUE, all MuteIn signals have to be active at offset 0x{0,x} 12414 The type of the analog inputs has to be the same at offet 0x{0,x} 12415 The received size of the local safe user parameter ({0}) was wrong, the expected size is {1} 12416 The value at offset {0} of the SafeCfgData is invalid in combination with the value {1} words before in the SafeCfgData 12417 The 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} 12418 The FB-Type in the Change FB Parameter Data (FB {0}) is unequal, the expected FB-type is {1} 12419 The size in the Change FB Parameter Data (FB {0}) is unequal, the expected size is {1} 12420 The Setting Mode of the FB CAMMON (FB {0}) in the Change FB Parameter Data is not activated 12421 The actual Logic State ({0}) is unequal RUN (1) when changing FB Parameter Data 12422 The FB-Number ({0}) in the Change FB Parameter Data is invalid 12423 The FRAM data size ({0}) has exceeded, the maximum allowed value is {1} 12436 The size 0 is not allowed for the safe user parameter at word offset {0} 12437 The download of the Activate Project Cfg Data was refused because no Output Mapping Cfg Data were downloaded before 12438 The download of the Activate Project Cfg Data was refused because {0} mappings of the Output Mapping Cfg Data were missing 12439 The re-converted FB-Mapping-Code was not matching to the FB Cfg Data (FB: {0}, Code-Address: 0x{1,x}, Offset: 0x{2,x}) 12440 a destination was mapped twice in the bit mapping code (page: 0x{0,x}, Code-Address: 0x{1,x}) 12441 a destination was mapped twice in the byte mapping code (Page: 0x{0,x}, Code-Address: 0x{1,x}) 12442 the number of groups was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12443 the number of FBs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12444 the number of Connections was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12445 the number of Standard Inputs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12446 the number of Standard Outputs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12447 the FSoE message size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12448 the FSoE safe user parameter size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12449 the PROFIsafe message size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12450 the EtherCAT Output size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12451 the EtherCAT Input size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12452 the EtherCAT Output size was exceeded in the project (calculated value: {0}, maximum value: {1}) 12453 the EtherCAT Input size was exceeded in the project (calculated value: {0}, maximum value: {1}) 12454 when 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}) 12455 when 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}) 12456 when 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}) 12457 when 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}) 12458 when 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}) 12459 when re-converting the local FB mapping code (FB {0}) the generated mapping data size was wrong (Code-Offset: 0x{1,x}) 12460 the Project CRC in the Activate Project Cfg Data was wrong 12461 when re-converting the local FB mapping code the source bit address was wrong (FB: {0}, Code-Offset: 0x{1,x}) 12462 when re-converting the local FB mapping code the source byte address was wrong (FB: {0}, Code-Offset: 0x{1,x}) 12465 wrong subindex order when reading the input mapping cfg data, the expected subindex is {0} 12466 subindex exceeded when reading the cfg data 12467 the offset in the Replacement Values cfg data is wrong in the Group cfg data at word-offset 0x{0,x} 12468 the deactivation mode passivate is enabled and the number of connections is unequal 1 in the Group cfg data at word-offset 0x{0,x} 12469 the RUN-signal has to be active in the Group cfg data at word-offset 0x{0,x} 12470 in the Change FB-Parameter (FB {0}) the FB-type {1} is not supported 12471 the Subindex exceeds the number of connections ({0}) when writing the PROFIsafe F-Parameter 12472 the Connection-Type {0} does not support PROFIsafe F-Parameter 12473 the Subindex exceeds the number of connections ({0}) when writing the Store Slave Project CRC Parameter 12474 the Connection-Type {0} does not support Store Slave Project CRC Parameter 12475 if there are no Muting sensors behind the AOPD, the Backwards-Mode and optional Check of the OSSD inputs are not allowed 12476 when optional Check of the OSSD inputs is activated, the Sequential Inputs mode has to be activated too 12477 The number of Connections ({0}) is unequal the calculated number of connections over all groups ({1}) 12478 The number of FBs ({0}) is unequal the calculated number of FBs over all groups ({1}) 12479 The caluculated local near process image size ({0}) exceeded the maximum near local process image size of {1} 12480 the EtherCAT Output size was exceeded in the connection cfg data at word offset 0x{0,x} (calculated value: {1}, maximum value: {2}) 12481 the EtherCAT Input size was exceeded in the connection cfg data at word offset 0x{0,x} (calculated value: {1}, maximum value: {2}) 12482 the reserved bits in the flags of the Vendor Data were set (actual value: 0x{0,x}, reserved flags: 0x{1,x}) 12483 FB CAMMON: if the Setting Mode is enabled, at least one position marker has to be configured in the cfg data 12484 Connection Type is not supported at word-offset 0x{0,x} of the cfg data 12485 writing the PROFIsafe F-Parameter is not allowed in this logic state ({0}), the logic state has to be 1 (RUN) 12486 The ConnId 0x{0,x} is used at least twice 12487 The PROFIsafe Address 0x{0,x} is used at least twice 12488 The FSoE Address 0x{0,x} is used at least twice 12489 The TwinSAFE SC type {0} is used at least twice 12490 The TwinSAFE SC CRC 0x{0,x} is used at least twice 12491 The Connection Index {0} in a FB Connection Shutdown is used at least twice 12492 It is not allowed that the number of FBs and the number of Connections is zero inside the Group Cfg Data 12493 the storing of the Store Slave Project CRC Parameter is not supported in connection {0} 12494 The received size of Safety Input Messages ({0}) was too big, the maximum allowed value is {1} 12495 The received size of Safety Output Messages ({0}) was too big, the maximum allowed value is {1} 12496 The received size of PROFIsafe Input Messages ({0}) was too big, the maximum allowed value is {1} 12497 The received size of PROFIsafe Output Messages ({0}) was too big, the maximum allowed value is {1} 12498 The Restore Mode is supported on a TwinSAFE SC connection at word-offset 0x{0,x} 12499 The FB {0} (Connection Shutdown) is assigned to a non FSoE-connection 12500 The download of the TwinSAFE IO-Project failed because {0} FBs are configured (no FBs allowed) 12501 When the TwinSAFE-Address in the Project Cfg data should be used, it has to be uneual zero 12502 When the TwinSAFE-Address in the Project Cfg data should be used, the DIP-switch has to be zero (0x{0,x} found) 12503 Read aborted because of invalid code buffer offset (Calculated=0x{0,x}, Expected=0x{1,x}) 12504 Invalid Safe User Parameter Offset at word offset 0x{0,x} (Calculated=0x{1,x}, Expected=0x{2,x}) 12505 The Standard Inputs Size of zero is not allowed 12506 The download of the Replacement Values is not allowed after the download before (download state={0}) 12507 The Info Data Map Cfg Data were downloaded in the wrong download state ({0}) 12508 The offset for the safety-Timer has to be inside the safety Output Area from 0x{0,x} to 0x{1,x} 12509 The 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 Data 12510 The 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 Data 12511 No more safe user parameter expected at byte-offset 0x{0,x} of the Safe User Parameter Cfg Data 12512 The TwinSAFE Address 0 is not allowed in the Project Cfg Data 12513 The download of the TwinSAFE IO-Project failed because {0} Groups are configured (only 1 Group allowed) 12514 The download of the Delete Project Cfg Data is not allowed in this state ({0}) 12515 The destination bit address (0x{0,x}, Bit {1}) already exists in the same mapping code 12516 Local Inputs cannot be mapped in the Info data because no local inputs are existing 12517 Local Outputs cannot be mapped in the Info data because no local outputs are existing 12518 The destination bit address (0x{0,x}, Bit {1}) already exists in the same mapping code 12519 the input mapping cfg data has to be read before the output mapping cfg data 12520 wrong subindex order when reading the mapping cfg data, the expected subindex is {0} 12521 when reading the input mapping cfg data, it has to be started with subindex 1 12522 invalid CRC when checking the Page {0} of the Safe Logic Cfg Data 12523 invalid CRC when checking the Page {0} of the Safe User Parameter Cfg Data 12524 invalid CRC when checking the Page {0} of the Replacement values Cfg Data 12544 No groups defined when trying to activate or deactive groups 12545 The reserved bits are set in value {0} at offset {1} when trying to activate or deactive groups 12546 The operation mode at offset {0} is not supported when trying to activate or deactive groups 12547 The deactiving of groups is not enabled for any group so no replacement values should be downloaded 12548 The maximum number ({0}) of Cfg Data pages was exceeded in the Replacement Values Cfg Data 12549 Invalid FB output size size at offset {0} of the Replacement Values Cfg Data 12550 Unexpected groupindex in the Replacement values Cfg Data at offset 0x{0,x} 12551 The download of the Activate Project Cfg Data was refused because {0} bytes of the Replacement Values Cfg Data were missing 12552 To 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 in 12553 No more definitions of individual replace values for analog FB Outputs in case of Group State unequal RUN are expected at offset {0} 12554 The offset in the definitions of individual replace values for analog FB Outputs in case of Group State unequal RUN was wrong at offset {0} 12555 The source process image offset of the Cyclic FRAM Data is outside the FB analog input area at offset {0} 12556 The source process image offset of the Cyclic FRAM Data has to even at offset {0} 12557 The size of the Cyclic FRAM Data was exceeding at offset {0} 12558 The 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} 12559 The size of the Cyclic FRAM CfgData in the GroupCfgData was not dividable by 4 at offset {0} 12560 The offset of the Cyclic FRAM Data in the GroupCfgData was wrong at offset {0} 12561 The value of {0} at offset {1} is not allowed when trying to activate or deactive groups 12563 FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The TDC2UpperLimit ({1}) is lower or equal than the maximum position jitter ({2}) 12564 FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The TDCUpperLimit ({1}) is lower or equal than the maximum position jitter ({2}) 12565 FB 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}) 12566 FB 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}) 12567 FB 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}) 12568 FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of BDCLowerLimit (plus maximum position jitter) ({1}) is grealer or equal the configured value of 180° ({2}) 12569 FB 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}) 12570 FB 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}) 12571 FB 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}) 12572 FB 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) 12573 FB 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}) 12574 FB 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}) 12575 The maximum size of the Replacement Values was exceeded at Word-Offset 0x{0,x} of the Group Cfg Data 12576 If no deactivation mode is enabled the offset of the replacement values shall be zero at Word-Offset 0x{0,x} of the Group Cfg Data 12577 No more replacement values expected at byte-offset 0x{0,x} of the Replacement Values Cfg Data 12800 The PROFIsafe-protocol is not supported on this device 12801 The F_ParVersion in the F_Prm_Flag2 of the F-Parameter at Word-Offset 0x{0,x} is unequal 1 (PROFIsafe V2) 12802 The F_CRC1 of the F-Parameter at Word-Offset 0x{0,x} is wrong 12803 The 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) 12806 The I-Parameter CRC in the F-Parameter is wrong at Word-Offset 0x{0,x} 12807 The 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) 12808 The F_Source_Address in the F-Parameter at Word-Offset 0x{0,x} is outside the allowed area of 1-0xFFFE 12809 The F_Destination_Address in the F-Parameter at Word-Offset 0x{0,x} is outside the allowed area of 1-0xFFFE 12810 The F_WD_Time in the F-parameter at Word-Offset 0x{0,x} is outside the allowed range from 2-60000 12811 The F_Destination_Address in the F-Parameter at Word-Offset 0x{0,x} is wrong, the expected value is {1} 13056 The State OPERATIONAL was left in Restore Mode 13057 Only {0} CRCs were matching in Restore Mode 13058 The CRC of the Activate Project Cfg Data in Restore Mode does not match, the expected value was 0x{0,x} 13059 No RestoreMode Slaves configured when trying to start the Restore Mode 13060 The CRC of the User List Cfg Data was not matching in Restore Mode, the expected value was 0x{0,x} 13061 The download of the User List Cfg Data is not activated in Restore Mode 13062 The download of the User List Cfg Data in Restore-Mode is not allowed in the state {0} 13063 The activation of the TwinSAFE Restore Project is not allowed in the state {0} 13064 The Restore Mode is not supported in EtherCAT state 0x{0,x} 13072 The FSoE-Slave on the {0}. connection is in Restore-Mode 13073 The FSoE-Master on the {0}. connection is in Restore-Mode 13312 The {0}. group has no more errors 13313 The 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} 13314 The Wait-Com-Error-Timeout has not been expired when the group {0} should be deactivated in passivate mode 13315 A module fault happened in group {0} 13316 The assigned connection reported an error when the group {0} was deactivated in passivate mode 13317 The connection has been successfully restarted when the group {0} was deactivated in passivate mode 13328 All groups will enter the ERROR-state because the safe logic program has been restarted 13329 All groups will enter the ERROR-state because the CRC of the Change Group Activation Data was wrong 13330 All groups will enter the ERROR-state because the CRC of the Change FB Parameter Data was wrong 13331 All groups will enter the ERROR-state because the CRC of the Project CRC Data was wrong 13332 All groups will enter the ERROR-state because the CRC of the Power-On Analog Value Check Data was wrong 13333 The TwinSAFE Logic Program was not loaded on C1 because of an inconsistency 13334 The TwinSAFE Logic Program was not loaded on C2 because of an inconsistency 13344 No more EtherCAT size error (EtherCAT Output Size={0}, EtherCAT Input Size={1}) 13345 The EtherCAT Output Data sizes of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal 13346 The EtherCAT Input Data sizes of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal 13347 The EtherCAT Output Data sizes for PROFIsafe of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal 13348 The EtherCAT Input Data sizes for PROFIsafe of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal 13349 The needed EtherCAT Process data buffer size ({0}) exceeded the maximum available size of {1} 13569 On the {0}. connection the changeable FSoE Address of {1} already exists 13570 On the {0}. connection the changeable FSoE Address is zero 14336 FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state SAFE 14338 FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state RESET 14339 FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state START 14340 FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual EStopIn-values are 0x{2,x} 14342 FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual EStopIn-values are 0x{2,x} 14343 FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state START, the actual EStopIn-values are 0x{2,x} 14345 FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual EStopIn-values are 0x{2,x} 14351 FB {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}) 14352 FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state SAFE 14354 FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state RESET 14355 FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state START 14356 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual MonIn/Secure-values are 0x{2,x} 14358 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual MonIn/Secure-values are 0x{2,x} 14359 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state START, the actual MonIn/Secure-values are 0x{2,x} 14360 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state RUN, the actual MonIn/Secure-values are 0x{2,x} 14361 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual MonIn/Secure-values are 0x{2,x} 14362 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state FUNCTEST, the actual MonIn/Secure-values are 0x{2,x} 14367 FB {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}) 14368 FB {0} (TWOHAND): A Disc-Group-fault (0x{1,x}) was detected in state 1BUTTON, the actual TwoHandIn-values are 0x{2,x} 14369 FB {0} (TWOHAND): A Disc-Group-fault (0x{1,x}) was detected in state 2BUTTON, the actual TwoHandIn-values are 0x{2,x} 14371 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual TwoHandIn-values are 0x{2,x} 14373 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual TwoHandIn-values are 0x{2,x} 14379 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state 1BUTTON, the actual TwoHandIn-values are 0x{2,x} 14380 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state 2BUTTON, the actual TwoHandIn-values are 0x{2,x} 14381 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state RELEASE, the actual TwoHandIn-values are 0x{2,x} 14384 FB {0} (OPMODE): An DiscTime-Fault (0x{1,x}) was detected, the actual OpIn-values are 0x{2,x} 14385 FB {0} (OPMODE): An Input-Fault was detected in state RESET, the actual OpIn-values are 0x{1,x} 14400 FB {0} (EDM): The SwitchOn-Time had been expired 14401 FB {0} (EDM): The SwitchOff-Time had been expired 14419 FB {0} (CS): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual Deactivate-values are 0x{2,x} 14421 FB {0} (CS): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual Deactivate-values are 0x{2,x} 14465 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state RUN, the actual MuteIn/OssdIn-values are 0x{2,x} 14467 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual MuteIn/OssdIn-values are 0x{2,x} 14469 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual MuteIn/OssdIn-values are 0x{2,x} 14472 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual MuteIn/OssdIn-values are 0x{2,x} 14473 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING1, the actual MuteIn/OssdIn-values are 0x{2,x} 14474 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING2, the actual MuteIn/OssdIn-values are 0x{2,x} 14475 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING3, the actual MuteIn/OssdIn-values are 0x{2,x} 14476 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING4, the actual MuteIn/OssdIn-values are 0x{2,x} 14477 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING5, the actual MuteIn/OssdIn-values are 0x{2,x} 14478 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING6, the actual MuteIn/OssdIn-values are 0x{2,x} 14479 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING7, the actual MuteIn/OssdIn-values are 0x{2,x} 14480 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING8, the actual MuteIn/OssdIn-values are 0x{2,x} 14481 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING9, the actual MuteIn/OssdIn-values are 0x{2,x} 14482 FB {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} 14483 FB {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} 14484 FB {0} (MUTING): State MUTING1, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14485 FB {0} (MUTING): State MUTING1, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14486 FB {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} 14487 FB {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} 14488 FB {0} (MUTING): State MUTING3, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14489 FB {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} 14490 FB {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} 14491 FB {0} (MUTING): State MUTING4, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14492 FB {0} (MUTING): State MUTING4, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14493 FB {0} (MUTING): State MUTING5, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14494 FB {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} 14495 FB {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} 14496 FB {0} (MUTING): State MUTING6, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14497 FB {0} (MUTING): State MUTING6, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14498 FB {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} 14499 FB {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} 14500 FB {0} (MUTING): State MUTING8, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14501 FB {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} 14502 FB {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} 14503 FB {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} 14504 FB {0} (MUTING): State MUTING9, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14505 FB {0} (MUTING): State MUTING9, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14506 FB {0} (MUTING): State MUTING5, Sequential Inputs=TRUE, MuteIn3 and MuteIn4 are deactive: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14507 FB {0} (MUTING): State MUTING6, Sequential Inputs=TRUE, MuteIn3 and MuteIn4 are deactive: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14508 FB {0} (MUTING): State MUTING1, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14512 FB {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}) 14529 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING1 (Digital Inputs=0x{1,x}) 14530 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING2 (Digital Inputs=0x{1,x}) 14531 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING3 (Digital Inputs=0x{1,x}) 14532 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING4 (Digital Inputs=0x{1,x}) 14533 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING5 (Digital Inputs=0x{1,x}) 14534 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING6 (Digital Inputs=0x{1,x}) 14535 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING7 (Digital Inputs=0x{1,x}) 14536 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING8 (Digital Inputs=0x{1,x}) 14537 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING9 (Digital Inputs=0x{1,x}) 16385 FB {0} (CAMMON): The TDC2UpperLimit ({1}) is lower or equal than the maximum position jitter ({2}) 16386 FB {0} (CAMMON): The Position ({1}) is bigger than the maximum position (plus the maximum position jitter) ({2}) 16387 FB {0} (CAMMON): The input OverrunCAM was FALSE in the top dead center area, the actual position is {1} 16388 FB {0} (CAMMON): The input OverrunCAM changed from FALSE to TRUE outside the area between BDCUpperLimit and TDCLowerLimit, the actual position is {1} 16389 FB {0} (CAMMON): The input OverrunCAM was TRUE in the area between OverrunMax and BDCUpperLimit, the actual position is {1} 16390 FB {0} (CAMMON): The input OverrunCAM changed from TRUE to FALSE outside the area between OverrunMax and BDCLowerLimit, the actual position is {1} 16391 FB {0} (CAMMON): The input UpwardsCAM was FALSE in the area between BDCUpperLimit and TDCLowerLimit, the actual position is {1} 16392 FB {0} (CAMMON): The input UpwardsCAM changed from FALSE to TRUE outside the area between BDCLowerLimit and TDCLowerLimit, the actual position is {1} 16393 FB {0} (CAMMON): The input UpwardsCAM changed from TRUE to FALSE outside the area between TDCLowerLimit and OverrunMax, the actual position is {1} 16394 FB {0} (CAMMON): The Position was moving while waiting for a rising edge of the input Reset in the state MOVE-STOP 16395 FB {0} (CAMMON): The Position was moving while waiting for a falling edge of the input Reset in the state MOVE-START 16396 FB {0} (CAMMON): The Position {1} in the area between OverrunMax and BDCLowerLimit was detected in the state MOVE-UP 16397 FB {0} (CAMMON): The Position has left the top dead center while wating for a stop, the actual position is {1} 16398 FB {0} (CAMMON): The Position has been changed negative 16399 FB {0} (CAMMON): The input UpwardsCAM was TRUE in the area between OverrunMax and BDCLowerLimit 16400 FB {0} (CAMMON): The Position has a circle overflow in Pendulum Mode, actual position={1}, last position={2} 16401 FB {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} 16402 FB {0} (CAMMON): The Input BackwardsMove is TRUE while the Position is between 180° and 360°, the actual position is {1} 16403 FB {0} (CAMMON): The Input BackwardsMove is TRUE while the moving is clockwise 16404 FB {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} 16405 FB {0} (CAMMON): The value of TDCLowerLimit (plus maximum position jitter) ({1}) is bigger or equal the configured position of 360° ({2}) 16406 FB {0} (CAMMON): The value of BDCUpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDCLowerLimit ({2}) 16407 FB {0} (CAMMON): The value of BDCUpperLimit ({1}) is smaller or equal the configured value of 180° (plus maximum position jitter) ({2}) 16408 FB {0} (CAMMON): The value of BDCLowerLimit (plus maximum position jitter) ({1}) is greater or equal the configured value of 180° ({2}) 16409 FB {0} (CAMMON): The value of OverrunMax (plus twice the maximum position jitter) ({1}) is bigger or equal the value of BDCLowerLimit ({2}) 16410 FB {0} (CAMMON): The value of TDCUpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of OverrunMax ({2}) 16411 FB {0} (CAMMON): The value of TDC1UpperLimit (plus the maximum position jitter) ({1}) is bigger or equal the configured position of 360° ({2}) 16412 FB {0} (CAMMON): The value of TDC1LowerLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDC1UpperLimit (5d) 16413 FB {0} (CAMMON): The value of TDC2LowerLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of BDCLowerLimit ({2}) 16414 FB {0} (CAMMON): The value of TDC2UpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDC2LowerLimit ({2}) 16415 FB {0} (CAMMON): The input PressStarted is TRUE and the position did not move after the PressStartedDelayTime 16416 FB {0} (CAMMON): The input PressStarted is TRUE and the position has stopped after moving before 16417 FB {0} (CAMMON): The input PressStarted is TRUE and the position has not moved enough, the actual position is {1}, the compare position is {2} 16418 FB {0} (CAMMON), Pendulum Mode: The Position has changed contra clockwise while moving up clockwise (actual Position={1}, old Position={2}) 16419 FB {0} (CAMMON), Pendulum Mode: The Position has changed clockwise while moving up contra clockwise (actual Position={1}, old Position={2}) 16420 FB {0} (CAMMON): The Position was moving while waiting for a falling edge of the input Reset in the state WAIT-FOR_RESET 16421 FB {0} (CAMMON): The TDCUpperLimit ({1}) is lower or equal than the maximum position jitter ({2}) 16512 FB {0} (ADD/SUB): an underflow was detected, AnalogIn1={1}, AnalogIn2={2} 16513 FB {0} (ADD/SUB): an overflow was detected, AnalogIn1={1}, AnalogIn2={2} 16520 FB {0} (SPEED): an underflow was detected, actual Position={1}, old Position={2} 16521 FB {0} (SPEED): an overflow was detected, actual Position={1}, old Position={2} 16528 FB {0} (LIMIT): the minimum value ({1}) is bigger than than the maximum value ({2}) 16536 FB {0} (COMPARE): an underflow was detected on CompOut ({1}), the minimum allowed value is {2} 16537 FB {0} (COMPARE): an overflow was detected on CompOut ({1}), the maximum allowed value is {2} 16544 FB {0} (MUL): an underflow was detected, AnalogIn1={1}, AnalogIn2={2} 16545 FB {0} (MUL): an overflow was detected, AnalogIn1={1}, AnalogIn2={2} 16552 FB {0} (DIV): an underflow was detected, AnalogIn1={1}, AnalogIn2={2} 16553 FB {0} (DIV): an overflow was detected, AnalogIn1={1}, AnalogIn2={2} 16560 FB {0} (SCALE): an underflow was detected, AnalogIn={1} 16561 FB {0} (SCALE): an overflow was detected, AnalogIn={1} 16562 FB {0} (SCALE): an overflow was detected after multiplication, AnalogIn={1} 16563 FB {0} (SCALE): an overflow was detected before division when rounding up the value, AnalogIn={1} 16568 FB {0} (COUNT): an underflow was detected on ActValue ({1}), the minimum allowed value is {2} 16569 FB {0} (COUNT): an overflow was detected on ActValue ({1}), the maximum allowed value is {2} 16576 FB {0} (SLI): an underflow was detected on ActValue ({1}), the minimum allowed value is {2} 16577 FB {0} (SLI): an overflow was detected on ActValue ({1}), the maximum allowed value is {2} 16584 FB {0} (ENVELOPE): an underflow was detected on InValue ({1}), the minimum allowed value is {2} 16585 FB {0} (ENVELOPE): an overflow was detected on InValue ({1}), the maximum allowed value is {2} 16586 FB {0} (ENVELOPE): an overflow error was detected on InValue ({1}), InValue+Offset is bigger than the maximum allowed value 16587 FB {0} (ENVELOPE): the MaxTime was expired (InValue={1}) 24585 SAFEOUT:Initial-Parameter: MultiplierDiagTestPulse has to be greater zero. ModuleNr:0x{0,x} 24592 SAFEOUT:Initial-Parameter: Number of Modules incorrect. ModuleNr:0x{0,x}, Parameter:0x{1,x} 24593 SAFEOUT:Initial-Parameter: Number of Channels incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24594 SAFEOUT:Initial-Parameter: Number of Diagnosis active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24595 SAFEOUT:Initial-Parameter: Number of Diagnosis inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24596 SAFEOUT:Initial-Parameter: Number of Feedback active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24597 SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24598 SAFEOUT:Initial-Parameter: Number of Feedback inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24599 SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24600 SAFEOUT:Initial-Parameter: Number of Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24601 SAFEOUT:Initial-Parameter: Number of Diagnosis inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24602 SAFEOUT:Initial-Parameter: Number of Feedback active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24603 SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24604 SAFEOUT:Initial-Parameter: Number of Feedback inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24605 SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24606 SAFEOUT:Setup Hardware Fault: Module Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24607 SAFEOUT:Setup Hardware Fault: Diagnosis active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24608 SAFEOUT:Setup Hardware Fault: Diagnosis inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24609 SAFEOUT:Setup Hardware Fault: Feedback active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24610 SAFEOUT:Setup Hardware Fault: Feedback Diagnosis active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24611 SAFEOUT:Setup Hardware Fault: Feedback inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24612 SAFEOUT:Setup Hardware Fault: Feedback Diagnosis inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24613 SAFEOUT:Setup Hardware Fault: Channel Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24614 SAFEOUT:Setup Hardware Fault: Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24615 SAFEOUT:Setup Hardware Fault: Diagnosis inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24616 SAFEOUT:Setup Hardware Fault: Feedback active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24617 SAFEOUT:Setup Hardware Fault: Feedback Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24618 SAFEOUT:Setup Hardware Fault: Feedback inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24619 SAFEOUT:Setup Hardware Fault: Feedback Diagnosis inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24624 SAFEOUT:The Feedback of the active Module Switch is wrong. Module:0x{0,x} 24625 SAFEOUT:The Feedback of the inactive Module Switch is wrong. Module:0x{0,x} 24626 SAFEOUT:The Feedback of the active Channel Switch is wrong. Module:0x{0,x} / Channel:0x{1,x} 24627 SAFEOUT:The Feedback of the inactive Channel Switch is wrong. Module:0x{0,x} / Channel:0x{1,x} 24640 SAFEOUT:Diagnosis Test: Common Fault Module:0x{0,x} / DiagChannel:0x{1,x} 24641 SAFEOUT:Diagnosis Test: Unknown State local ModuleState:0x{0,x} 24642 SAFEOUT:Diagnosis Test: Unknown State other ModuleState:0x{0,x} 24656 SAFEOUT:Diagnosis Test: Feedback active Module Switch is wrong (Step1 - check current state). Module:0x{0,x} 24657 SAFEOUT:Diagnosis Test: Feedback inactive Module Switch is wrong (Step1 - check current state). Module:0x{0,x} 24658 SAFEOUT:Diagnosis Test: Feedback active Channel Switch is wrong (Step1 - check current state). Module:0x{0,x} / DiagChannel:0x{1,x} 24659 SAFEOUT:Diagnosis Test: Feedback inactive Channel Switch is wrong (Step1 - check current state). Module:0x{0,x} / DiagChannel:0x{1,x} 24672 SAFEOUT:Diagnosis Test: Feedback active Module Switch is wrong (Step2 - check test pulse). Module:0x{0,x} 24673 SAFEOUT:Diagnosis Test: Feedback inactive Module Switch is wrong (Step2 - check test pulse). Module:0x{0,x} 24674 SAFEOUT:Diagnosis Test: Feedback active Channel Switch is wrong (Step2 - check test pulse). Module:0x{0,x} / DiagChannel:0x{1,x} 24675 SAFEOUT:Diagnosis Test: Feedback inactive Channel Switch is wrong (Step2 - check test pulse). Module:0x{0,x} / DiagChannel:0x{1,x} 24704 SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 24705 SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 24706 SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 24707 SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 24708 SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 24709 SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 24710 SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 24720 SAFEOUT:Module Switch FeedbackTest ViolationCounter incremented, Outputs active. Module:0x{0,x}, Info:0x{1,x}. 24721 SAFEOUT:Module Switch FeedbackTest ViolationCounter incremented, Outputs inactive. Module:0x{0,x}, Info:0x{1,x}. 24722 SAFEOUT:Channel Switch FeedbackTest ViolationCounter incremented, Outputs active. Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24723 SAFEOUT:Channel Switch FeedbackTest ViolationCounter incremented, Outputs inactive. Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24724 SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step1 - check current state). Module:0x{0,x}, Info:0x{1,x}. 24725 SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step1 - check current state). Module:0x{0,x}, Info:0x{1,x}. 24726 SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24727 SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24728 SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step2 - check test pulse). Module:0x{0,x}, Info:0x{1,x}. 24729 SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step2 - check test pulse). Module:0x{0,x}, Info:0x{1,x}. 24730 SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24731 SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24736 SAFEOUT:Sercom Fault 0. Cmd/State:0x{0,x} 24737 SAFEOUT:Sercom Fault 1. Cmd/State:0x{0,x} 24752 SAFEOUT:Unknown Sercom Command Request 1. Cmd/State:0x{0,x} 24753 SAFEOUT:Unknown Sercom Command Answer 1. Cmd/State:0x{0,x} 24754 SAFEOUT:Unknown Sercom Command Request 2. Cmd/State:0x{0,x} 24755 SAFEOUT:Unknown Sercom Command Answer 2. Cmd/State:0x{0,x} 24768 SAFEOUT:Module Switch too fast Switching OFF detected Fault (see technical data). Module:0x{0,x} 24769 SAFEOUT:Channel Switch too fast Switching OFF detected Fault (see technical data). Module:0x{0,x} / Channel:0x{1,x} 24770 SAFEOUT:Module Switch too fast Switching ON detected Fault (see technical data). Module:0x{0,x} 24771 SAFEOUT:Channel Switch too fast Switching ON detected Fault (see technical data). Module:0x{0,x} / Channel:0x{1,x} 24772 SAFEOUT:Module Error Acknowledge is not possible. Module:0x{0,x} 24800 SAFEOUT:HAL Read Fault. ReturnData:0x{0,x} 24801 SAFEOUT:Init Fault. Module:0x{0,x} 32777 SAFEIN:Initial-Parameter: MultiplierDiagTestPulse has to be greater zero. ModuleNr:0x{0,x} 32784 SAFEIN:Initial-Parameter: Number of Modules incorrect. ModuleNr:0x{0,x}, Parameter:0x{1,x} 32785 SAFEIN:Initial-Parameter: Number of Channels incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 32792 SAFEIN:Initial-Parameter: Number of Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 32795 SAFEIN:Initial-Parameter: Number of Feedback Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 32805 SAFEIN:Setup Hardware Fault: Channel Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x} 32806 SAFEIN:Setup Hardware Fault: Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 32809 SAFEIN:Setup Hardware Fault: Feedback Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 32832 SAFEIN:Diagnosis Test: Common Fault Module:0x{0,x} / DiagChannel:0x{1,x} 32833 SAFEIN:Diagnosis Test: Unknown State local ModuleState:0x{0,x} 32834 SAFEIN:Diagnosis Test: Unknown State Other ModuleState:0x{0,x} 32835 SAFEIN Pulse Detection: Wrong pulse was detected at . Module:0x{0,x} / DiagChannel:0x{1,x} 32836 SAFEIN Pulse Detection: Detected pulse from Module:0x{0,x} / DiagChannel:0x{1,x} 32850 SAFEIN:Diagnosis Test: Feedback in Step1 active Channel is wrong. Module:0x{0,x} / DiagChannel:0x{1,x} 32866 SAFEIN:Diagnosis Test: Feedback in Step2 active Channel is wrong. Module:0x{0,x} / DiagChannel:0x{1,x} 32896 SAFEIN:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 32897 SAFEIN:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 32900 SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 32901 SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 32902 SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 32918 SAFEIN:DiagnosisTest ViolationCounter incremented, Inputs active (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 32922 SAFEIN:DiagnosisTest ViolationCounter incremented, Inputs active (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 32928 SAFEIN:Sercom Fault 0. Cmd/State:0x{0,x} 32929 SAFEIN:Sercom Fault 1. Cmd/State:0x{0,x} 32944 SAFEIN:Unknown Sercom Command Request 1. Cmd/State:0x{0,x} 32945 SAFEIN:Unknown Sercom Command Answer 1. Cmd/State:0x{0,x} 32946 SAFEIN:Unknown Sercom Command Request 2. Cmd/State:0x{0,x} 32947 SAFEIN:Unknown Sercom Command Answer 2. Cmd/State:0x{0,x} 32960 SAFEIN:Error Acknowledge is not possible. Module:0x{0,x} 32961 SAFEIN:Diagnosis Test: Implausible Inputs detected. Module:0x{0,x} 32962 SAFEIN:Diagnosis Test: Implausible Inputs detected (INFO). Parameter1:0x{0,x} / Parameter2:0x{1,x} 32992 SAFEIN:Init HAL Fault.ReturnState:0x{0,x} 32993 SAFEIN:Init Fault. Module:0x{0,x} 33008 SAFEIN: Testpulse is parametrized but not enabled (Diag Testpulse for Inputs active). Module:0x{0,x} / Channel:0x{1,x} 33009 SAFEIN: Testpulse is parametrized but not enabled (Diag TestPulse active). Module:0x{0,x} / Channel:0x{1,x} 33010 SAFEIN: Testfilter-Time too long. Parameter1:0x{0,x} / Parameter2:0x{1,x} 33011 SAFEIN: Inputfilter-Time too short. Parameter1:0x{0,x} / Parameter2:0x{1,x} 33012 SAFEIN: Wrong parameters detected for Module:0x{0,x} / Channel:0x{1,x}. Please check parameters! DisplayTxtId true {28111931-0002-0000-5230-5F0B00001000} EL2911, Potential supply terminal (10 A) with 4 Ch. Safety Inputs, TwinSAFE EL2911, Potential supply terminal (10 A) with 4 Ch. Safety Inputs, TwinSAFE 1 Primary MC: GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x} 2 Primary MC: GLOBAL_Shutdown with Code 0x{0,x} and Additional Code 0x{1,x} 3 Secondary MC: GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x} 4 Secondary MC: GLOBAL_Shutdown with Code 0x{0,x} and Additional Code 0x{1,x} 5 Primary MC: Stored GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x} 6 Secondary MC: Stored GLOBAL_Fault with Code 0x{0,x} and Additional Code 0x{1,x} 7 Diag-Message-Overflow: {0} messages got lost 8 Primary MC: the CRC of the FRAM Data was wrong (Diag-Code={0}) 9 Secondary MC: the CRC of the FRAM Data was wrong (Diag-Code={0}) 16 Reserved CfgData has to be zero st offset {0} 17 The password is wrong 18 The user was not found 19 The CRC of the login data does not match 20 The serial number of the login data does not match 21 The login watchdog has been expired 22 The user was logged out before 23 The user has not sufficient access rights 24 The reserved area of the CfgData was not 0 25 The CRC of the CfgData was wrong 26 The user name is wrong at word offset 0x{0,x} when changing the password 27 The requested number of users is too big 29 The user update flags are wrong at word offset 0x{0,x} when changing the password 30 The wrong user (user {0}) is logged in when changing the password (user {1} found in the received data) 33 the maximum Global-Shutdown counter was exceeded in the Vendor Data (maximu value: {0}, actual value: {1}) 48 Sync Manager 2 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 49 Sync Manager 3 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 50 Sync Manager 4 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 51 Sync Manager 5 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 52 Sync Manager 2 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 53 Sync Manager 3 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 54 Sync Manager 4 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 55 Sync Manager 5 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 56 Sync Manager {0} Settings (Offset 4-7) are invalid, expected values = 0x{1,x}, 0x{2,x} 68 Sync Manager 6 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 69 Sync Manager 7 Address (0x{0,x}) is invalid, minimum value = 0x{1,x}, maximum value = 0x{2,x} 72 Sync Manager 6 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 73 Sync Manager 7 Size ({0}) is invalid, minimum value = {1}, maximum value = {2} 257 Primary MC: Completed RAM TEST: Starttime: 0x{0,x} and Stoptime: 0x{1,x} . The calculated timediff is 0x{2,x}. 258 Secondary MC: Completed RAM TEST: Starttime: 0x{0,x} and Stoptime: 0x{1,x} . The calculated timediff is 0x{2,x}. 259 C1 MCTEST Info: Arg1: 0x{0,x}, Arg2: 0x{1,x}, Arg3: 0x{2,x}. 260 C2 MCTEST Info: Arg1: 0x{0,x}, Arg2: 0x{1,x}, Arg3: 0x{2,x}. 277 278 = 0x{2,x}.]]> 279 280 281 = 0x{2,x}.]]> 282 283 = 0x{2,x}.]]> 286 = 0x{2,x}.]]> 287 Controller {0}: Minimum value alert (Individual ADC Check). Channel parameter = {1}. Actual value is 0x{2,x}. 288 Controller {0}: Maximum value alert (Individual ADC Check). Channel parameter = {1}. Actual value is 0x{2,x}. 289 Module Shutdown due to minimum value alert (Individual ADC Check). Channel parameter = {0}. 4096 The size of the safe User Parameter is too small ({0}), the expected size is {1} 4097 The Vendor-ID ({0}) is unequal the expected value of {1} 4098 The Product-Code ({0}) is unequal the expected value of {1} 4099 The reserved data of the SafeOut User Parameter of module {0} at byte offset 0x{1,x} has to be 0 4100 The reserved data of the SafeIn User Parameter of module {0} at byte offset 0x{1,x} has to be 0 4101 The standard outputs of module {0} should be enabled but the Sync-Manager 6 is not configured or enabled correctly 4102 The FASTSTDOUT mode of the standard outputs of module {0} is not supported 4103 The SAFEOUT-Module-Number ({0}) for the ExternalPulseDetection of the SAFEIN-Module {1} is wrong, the allowed range is 1-{2} 4104 The SAFEOUT-Channel-Number ({0}) for the ExternalPulseDetection of the SAFEIN-Module {1} is wrong, the allowed range is 1-{2} 4105 The Bumper-Mode {0} is not supported for SAFEIN-Module {1} 4106 The version of the Product-Code (0x{0,x}) is unequal the expected value of 0x{1,x} 4112 The default Project CRC is wrong, the received value is 0x{0,x} 4128 The watchdog for the Standard Outputs was expired 4144 The size of the safe User Parameter is too big ({0}), the expected size is {1} 5393 Module - Overcurrent,UP- Reverse Polarity or Output Voltage Injection for SAFEOUT-Module:0x{0,x} detected; Counter:0x{1,x} 8193 The {0}. connection has received an invalid FSoE-Cmd in state CONNECTION 8194 The {0}. connection has received an unknown FSoE-Cmd in state CONNECTION 8195 The {0}. connection has received an invalid FSoE-ConnID in state CONNECTION 8196 The {0}. connection has received an invalid FSoE-CRC in state CONNECTION 8197 The FSoE-Watchdog of the {0}. connection has been expired in state CONNECTION 8198 On the {0}. connection the received FSoE-Address (0x{1,x}) does not match with the expected FSoE-Address (0x{2,x}) 8199 On the {0}. connection the received connection data do not match with the sent values 8206 A Module fault was detected on the {0}. connection in state CONNECTION 8209 On 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-Cmd 8210 On 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-Cmd 8211 On 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-ConnID 8212 On 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-CRC 8213 On 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 partner 8214 On 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-Address 8215 On 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 values 8216 On 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 length 8217 On 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 Watchdog 8218 On 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 length 8219 On 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 data 8220 On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 12 was received 8221 On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 13 was received 8222 On 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 fault 8223 On the {0}. connection in state CONNECTION a FSoE-Reset with Error-Code 0x{1,x} was received 8257 The {0}. connection has received an invalid FSoE-Cmd in state PARAMETER 8258 The {0}. connection has received an unknown FSoE-Cmd in state PARAMETER 8259 The {0}. connection has received an invalid FSoE-ConnID in state PARAMETER 8260 The {0}. connection has received an invalid FSoE-CRC in state PARAMETER 8261 The FSoE-Watchdog of the {0}. connection has been expired in state PARAMETER 8263 On the {0}. connection the received parameter data do not match with the sent values 8264 On the {0}. connection the received communication parameter length ({1}) does not match with the expected value of 2 8265 On the {0}. connection the received FSoE Watchdog ({1}) is outside the allowed area from 2 to 60000 8266 On the {0}. connection the received application parameter length ({1}) is unequal the expected length of {2} 8267 On the {0}. connection the received application parameter data are wrong 8270 A Module fault was detected on the {0}. connection in state PARAMETER 8273 On 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-Cmd 8274 On 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-Cmd 8275 On 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-ConnID 8276 On 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-CRC 8277 On 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 partner 8278 On 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-Address 8279 On 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 values 8280 On 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 length 8281 On 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 Watchdog 8282 On 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 length 8283 On 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 data 8284 On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 12 was received 8285 On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 13 was received 8286 On 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 fault 8287 On the {0}. connection in state PARAMETER a FSoE-Reset with Error-Code 0x{1,x} was received 8289 On 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}) 8321 The {0}. connection has received an invalid FSoE-Cmd in state DATA 8322 The {0}. connection has received an unknown FSoE-Cmd in state DATA 8323 The {0}. connection has received an invalid FSoE-ConnID in state DATA 8324 The {0}. connection has received an invalid FSoE-CRC in state DATA 8325 The FSoE-Watchdog of the {0}. connection has been expired in state DATA 8333 The FailSafeData command was received on the {0}. connection in state DATA 8334 A Module fault was detected on the {0}. connection in state DATA 8337 On 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-Cmd 8338 On 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-Cmd 8339 On 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-ConnID 8340 On 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-CRC 8341 On 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 partner 8342 On 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-Address 8343 On 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 values 8344 On 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 length 8345 On 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 Watchdog 8346 On 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 length 8347 On 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 data 8348 On the {0}. connection in state DATA a FSoE-Reset with Error-Code 12 was received 8349 On the {0}. connection in state DATA a FSoE-Reset with Error-Code 13 was received 8350 On 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 fault 8351 On the {0}. connection in state DATA a FSoE-Reset with Error-Code 0x{1,x} was received 8385 The {0}. connection has received an invalid FSoE-Cmd in state SHUTDOWN 8386 The {0}. connection has received an unknown FSoE-Cmd in state SHUTDOWN 8388 The {0}. connection has received an invalid FSoE-CRC in state SHUTDOWN 8419 The {0}. connection has received the invalid FSoE-ConnID 0 in state SESSION 8449 On the {0}. connection the PROFIsafe-Slave reports a communication error 8450 On the {0}. connection the PROFIsafe-Slave reports a watchdog error 8451 On the {0}. connection the PROFIsafe-Slave reports a device fault 8452 On the {0}. connection a CRC2-Error was detected locally on the PROFIsafe Host 8453 On the {0}. connection the Watchdog has been expired locally on the PROFIsafe Host 8468 On the {0}. connection a CRC2-Error was detected locally on the PROFIsafe Slave 8469 On the {0}. connection the Watchdog has been expired locally on the PROFIsafe Slave 8471 On 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 outputs 8476 On the {0}. connection the PROFIsafe Slave has been restarted locally 12288 The received number of groups ({0}) was too big, the maximum allowed value is {1} 12289 The received number of FBs ({0}) was too big, the maximum allowed value is {1} 12290 The received number of Connections ({0}) was too big, the maximum allowed value is {1} 12291 The received number of Output Mappings was too big, the maximum allowed value is {0} 12292 The received number of Input Mappings was too big, the maximum allowed value is {0} 12293 The received size of Standard Inputs ({0}) was too big, the maximum allowed value is {1} 12294 The received size of Standard Outputs ({0}) was too big, the maximum allowed value is {1} 12295 The received number of Restore Slaves ({0}) was too big, the maximum allowed value is {1} 12296 The SafeCfgData type was unexpected: {0} found and {1} expected 12297 The SafeCfgData type 2 (Connection) was expected at offset {0} 12298 The SafeCfgData type 3 (FB) was expected at offset {0} 12299 The SafeCfgData type 15 (GAP) was expected at offset {0} 12300 The Bit-Mask in the SafeCfgData was wrong at offset {0} 12301 The address in the SafeCfgData was wrong at offset {0} 12302 The Signal number in the SafeCfgData was wrong at offset {0} 12303 The number of connections was wrong in the SafeCfgData of the Group at offset {0} 12304 The number of FBs was wrong in the SafeCfgData of the Group at offset {0} 12305 The size of the SafeCfgData was wrong at offset {0} 12306 The complete size of the SafeCfgData related to the Group {0} was wrong 12307 If the RUN-Signal should be mapped internally, it has to be activated at offset {0} 12308 The message size at offset {0} is invalid 12309 The connection parameter at offset {0} is invalid 12310 If the ERRACK-Signal should be mapped internally, it has to be activated at offset {0} 12311 The connection type at offset {0} is invalid 12312 The value at offset {0} of the SafeCfgData is invalid 12313 The value at offset {0} of the SafeCfgData is invalid because at least one of the related signals is not active 12314 The number of mappings ({0}) is wrong because it is not the last Mapping SafeCfgData 12315 The Safe Logic Cfg Data were downloaded in the wrong download state ({0}) 12316 The number of mappings ({0}) is too great in the Mapping SafeCfgData 12317 The Mapping-Size in the SafeCfgData was wrong at offset {0} 12318 A Group-Input Mapping was expected at offset {0} 12319 A Connection-Input Mapping was expected at offset {0} 12320 A FB-Input Bit-Mapping was expected at offset {0} 12321 A FB-Input Byte-Mapping was expected at offset {0} 12322 No more mapping was expected at offset {0} 12323 Invalid Safe User Parameter size at byte offset 0x{0,x} (Found={1}, Expected={2}) 12324 The SafeCfgData type 4 (Safe User Parameter) was expected at offset {0} 12325 The download of the Input Mapping Cfg Data was refused because {0} groups were missing in the Safe Logic Cfg Data 12326 The download of the Input Mapping Cfg Data was refused because {0} connections were missing in the Safe Logic Cfg Data 12327 The download of the Input Mapping Cfg Data was refused because {0} FBs were missing in the Safe Logic Cfg Data 12328 At least one group has to be defined in the SafeCfgData 12329 The download of the Input Mapping Cfg Data was refused because no safe Logic Cfg Data were downloaded before 12330 The Subindex {0} was expected to be downloaded 12331 When loading CfgData a user has to be logged in before 12332 The Input Mapping Cfg Data were downloaded in the wrong download state ({0}) 12333 The download of theSafe Logic CfgData is refused because the old Safe Logic Cfg Data were not deleted before 12334 The user was logged out before 12335 The user has not sufficient access rights 12336 The reserved area of the CfgData was not 0 12337 The CRC of the CfgData was wrong 12338 All needed CfgData pages were downloaded before, no more pages are expected 12339 The mapping code buffer is too small for the mapping 12340 The maximum allowed subindex is {0} 12341 The download of the Output Mapping Cfg Data was refused because {0} mappings of the Input Mapping Cfg Data were missing 12342 {0} input mappings of the groups were missing in the Input Mapping Cfg Data 12343 {0} input mappings of the connections were missing in the Input Mapping Cfg Data 12344 {0} input bit mappings of the FBs were missing in the Input Mapping Cfg Data 12345 {0} input byte mappings of the FBs were missing in the Input Mapping Cfg Data 12346 The Output Mapping Cfg Data were downloaded in the wrong download state ({0}) 12347 The mapping code buffer is too small for the local mapping 12348 The download of the Safe Parameter was refused because no Output Mapping Cfg Data were downloaded before 12349 The download of the Safe User Parameter was refused because {0} mappings of the Output Mapping Cfg Data were missing 12350 The Safe User Parameter Cfg Data were downloaded in the wrong download state ({0}) 12351 The download of the Activate Project Cfg Data was refused because no Safe User Parameter Cfg Data were downloaded before 12352 The download of the Activate Project Cfg Data was refused because {0} bytes of the Safe Parameter Cfg Data were missing 12353 The received activate code (0x{0,x}) was wrong in the Project Cfg Data 12354 The TwinSAFE Address ({0}) in the Project Cfg Data does not match with the DIP switch ({1}) 12355 At least one Cfg Data page has to be defined in the Safe Logic Cfg Data 12356 The maximum number ({0}) of Cfg Data pages was exceeded in the Safe Logic Cfg Data 12357 The received number of Safe Logic Cfg Data pages ({0}) has exceeded the configured value at offset 0 of the Safe Logic Cfg Data ({1}) 12358 The download of the Input Mapping Cfg Data was refused because {0} pages were missing in the Safe Logic Cfg Data 12359 The Safe Logic Cfg Data CRC does not match in the Safe Project Cfg Data 12360 When checking the Mapping Code a fault has detected at offset 0x{0,x} 12361 The Mapping Cfg Data CRC does not match in the Safe Project Cfg Data 12362 The number of Input Mappings is too small in the Safe Project Cfg Data (Code-Offset=0x{0,x}) 12363 The number of Output Mappings is too small in the Safe Project Cfg Data (Code-Offset=0x{0,x}) 12364 The number of Input Mappings is too great in the Safe Project Cfg Data, ({0} mappings too much, Code-Offset=0x{1,x}) 12365 The number of Output Mappings is too great in the Safe Project Cfg Data, ({0} mappings too much, Code-Offset=0x{1,x}) 12366 The maximum number ({0}) of Cfg Data pages was exceeded in the Safe User Parameter Cfg Data 12367 At least one Cfg Data page has to be defined in the Safe User Parameter Cfg Data 12368 The Safe User Parameter Cfg Data CRC does not match in the Safe Project Cfg Data 12370 The caluculated local process image size ({0}) exceeded the maximum local process image size of {1} 12371 The Activate Project Cfg Data were downloaded in the wrong download state ({0}) 12372 The Delete Project Cfg Data were downloaded in the wrong download state ({0}) 12373 The TwinSAFE Address ({0}) does not match with the DIP switch ({1}) in the Delete Project Cfg Data 12374 The Delete Code ({0}) is too high in the Delete Project Cfg Data 12375 Unexpected connection index in the Safe User Parameter Cfg Data at byte offset 0x{0,x} 12376 The received number of Local Safety Inputs ({0}) was wrong, the expected value is {1} 12377 The received number of Local Safety Outputs ({0}) was wrong, the expected value is {1} 12378 The received number of Local Standard Inputs ({0}) was wrong, the expected value is {1} 12379 The received number of Local Standard Outputs ({0}) was wrong, the expected value is {1} 12380 The received Safety Input Message size at word offset 15 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12381 The received Safety Output Message size at word offset 16 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12382 The received Safety Input size at word offset 7 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12383 The received Safety Output size at word offset 8 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12384 The received PROFIsafe Input Message size at word offset 9 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12385 The received PROFIsafe Output Message size at word offset 10 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12386 At word offset 0x{0,x} the configured number of CRCs of {1} exceeds the maximum number of CRCs ({2}) 12388 The received FB Analog Input size at word offset 13 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12389 The received FB Analog Output size at word offset 14 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12390 The received Connection Status Data size at word offset 21 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12391 The received FB Status Data size at word offset 22 of the Safe Logic Cfg Data ({0}) is unequal the calculated value of {1} 12392 The number of active signals in the FB is invalid at offset {0} 12393 The local map code size in the FB is invalid at offset {0} 12394 The analog output size in the Group Cfg Data is invalid at offset {0} 12395 The analog output offset in the Group Cfg Data is invalid at offset {0} 12396 The 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}) 12397 The caluculated end of the analog output area ({0}) is unequal the calculated analog output offset over all the Group Cfg Data ({1}) 12398 The value of the FB Cfg Data at offset {0} is invalid 12399 At least one FB input has to be deactivated in this operation mode at offset {0} 12400 At least the level of one FB input is wrong in this operation mode at offset {0} 12401 The value of the FB Cfg Data at word offset {0} is invalid in this operation mode 12402 The number ({0}) of Cfg Data pages was exceeded in the Info Data Cfg Data at offset 0 12403 The received number of FBs ({0}) at word offset 1 was unequal the configured number of FBs of {1} 12404 The 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} 12405 The 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} 12406 The received number of Connections ({0}) in the Info Data Cfg Data at word offset {1} was unequal the configured number of connections of {2} 12407 The received Connection Type ({0}) in the Info Data Map Cfg Data at byte offset {1} is unequal the configured Connection Type of {2} 12408 The 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) 12409 The received number of Groups ({0}) in the Info Data Cfg Data at word offset {1} was unequal the configured number of Groups of {2} 12410 The FB-Type is unknown at offet 0x{0,x} 12411 The value at offset {0} of the SafeCfgData is too great 12412 The value at offset {0} of the SafeCfgData is too small 12413 FB-Muting: if SequentialInputs is TRUE, all MuteIn signals have to be active at offset 0x{0,x} 12414 The type of the analog inputs has to be the same at offet 0x{0,x} 12415 The received size of the local safe user parameter ({0}) was wrong, the expected size is {1} 12416 The value at offset {0} of the SafeCfgData is invalid in combination with the value {1} words before in the SafeCfgData 12417 The 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} 12418 The FB-Type in the Change FB Parameter Data (FB {0}) is unequal, the expected FB-type is {1} 12419 The size in the Change FB Parameter Data (FB {0}) is unequal, the expected size is {1} 12420 The Setting Mode of the FB CAMMON (FB {0}) in the Change FB Parameter Data is not activated 12421 The actual Logic State ({0}) is unequal RUN (1) when changing FB Parameter Data 12422 The FB-Number ({0}) in the Change FB Parameter Data is invalid 12423 The FRAM data size ({0}) has exceeded, the maximum allowed value is {1} 12436 The size 0 is not allowed for the safe user parameter at word offset {0} 12437 The download of the Activate Project Cfg Data was refused because no Output Mapping Cfg Data were downloaded before 12438 The download of the Activate Project Cfg Data was refused because {0} mappings of the Output Mapping Cfg Data were missing 12439 The re-converted FB-Mapping-Code was not matching to the FB Cfg Data (FB: {0}, Code-Address: 0x{1,x}, Offset: 0x{2,x}) 12440 a destination was mapped twice in the bit mapping code (page: 0x{0,x}, Code-Address: 0x{1,x}) 12441 a destination was mapped twice in the byte mapping code (Page: 0x{0,x}, Code-Address: 0x{1,x}) 12442 the number of groups was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12443 the number of FBs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12444 the number of Connections was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12445 the number of Standard Inputs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12446 the number of Standard Outputs was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12447 the FSoE message size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12448 the FSoE safe user parameter size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12449 the PROFIsafe message size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12450 the EtherCAT Output size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12451 the EtherCAT Input size was exceeded in the Vendor Data (actual value: {0}, minimum: {1}, maximum: {2}) 12452 the EtherCAT Output size was exceeded in the project (calculated value: {0}, maximum value: {1}) 12453 the EtherCAT Input size was exceeded in the project (calculated value: {0}, maximum value: {1}) 12454 when 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}) 12455 when 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}) 12456 when 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}) 12457 when 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}) 12458 when 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}) 12459 when re-converting the local FB mapping code (FB {0}) the generated mapping data size was wrong (Code-Offset: 0x{1,x}) 12460 the Project CRC in the Activate Project Cfg Data was wrong 12461 when re-converting the local FB mapping code the source bit address was wrong (FB: {0}, Code-Offset: 0x{1,x}) 12462 when re-converting the local FB mapping code the source byte address was wrong (FB: {0}, Code-Offset: 0x{1,x}) 12465 wrong subindex order when reading the input mapping cfg data, the expected subindex is {0} 12466 subindex exceeded when reading the cfg data 12467 the offset in the Replacement Values cfg data is wrong in the Group cfg data at word-offset 0x{0,x} 12468 the deactivation mode passivate is enabled and the number of connections is unequal 1 in the Group cfg data at word-offset 0x{0,x} 12469 the RUN-signal has to be active in the Group cfg data at word-offset 0x{0,x} 12470 in the Change FB-Parameter (FB {0}) the FB-type {1} is not supported 12471 the Subindex exceeds the number of connections ({0}) when writing the PROFIsafe F-Parameter 12472 the Connection-Type {0} does not support PROFIsafe F-Parameter 12473 the Subindex exceeds the number of connections ({0}) when writing the Store Slave Project CRC Parameter 12474 the Connection-Type {0} does not support Store Slave Project CRC Parameter 12475 if there are no Muting sensors behind the AOPD, the Backwards-Mode and optional Check of the OSSD inputs are not allowed 12476 when optional Check of the OSSD inputs is activated, the Sequential Inputs mode has to be activated too 12477 The number of Connections ({0}) is unequal the calculated number of connections over all groups ({1}) 12478 The number of FBs ({0}) is unequal the calculated number of FBs over all groups ({1}) 12479 The caluculated local near process image size ({0}) exceeded the maximum near local process image size of {1} 12480 the EtherCAT Output size was exceeded in the connection cfg data at word offset 0x{0,x} (calculated value: {1}, maximum value: {2}) 12481 the EtherCAT Input size was exceeded in the connection cfg data at word offset 0x{0,x} (calculated value: {1}, maximum value: {2}) 12482 the reserved bits in the flags of the Vendor Data were set (actual value: 0x{0,x}, reserved flags: 0x{1,x}) 12483 FB CAMMON: if the Setting Mode is enabled, at least one position marker has to be configured in the cfg data 12484 Connection Type is not supported at word-offset 0x{0,x} of the cfg data 12485 writing the PROFIsafe F-Parameter is not allowed in this logic state ({0}), the logic state has to be 1 (RUN) 12486 The ConnId 0x{0,x} is used at least twice 12487 The PROFIsafe Address 0x{0,x} is used at least twice 12488 The FSoE Address 0x{0,x} is used at least twice 12489 The TwinSAFE SC type {0} is used at least twice 12490 The TwinSAFE SC CRC 0x{0,x} is used at least twice 12491 The Connection Index {0} in a FB Connection Shutdown is used at least twice 12492 It is not allowed that the number of FBs and the number of Connections is zero inside the Group Cfg Data 12493 the storing of the Store Slave Project CRC Parameter is not supported in connection {0} 12494 The received size of Safety Input Messages ({0}) was too big, the maximum allowed value is {1} 12495 The received size of Safety Output Messages ({0}) was too big, the maximum allowed value is {1} 12496 The received size of PROFIsafe Input Messages ({0}) was too big, the maximum allowed value is {1} 12497 The received size of PROFIsafe Output Messages ({0}) was too big, the maximum allowed value is {1} 12498 The Restore Mode is supported on a TwinSAFE SC connection at word-offset 0x{0,x} 12499 The FB {0} (Connection Shutdown) is assigned to a non FSoE-connection 12500 The download of the TwinSAFE IO-Project failed because {0} FBs are configured (no FBs allowed) 12501 When the TwinSAFE-Address in the Project Cfg data should be used, it has to be uneual zero 12502 When the TwinSAFE-Address in the Project Cfg data should be used, the DIP-switch has to be zero (0x{0,x} found) 12503 Read aborted because of invalid code buffer offset (Calculated=0x{0,x}, Expected=0x{1,x}) 12504 Invalid Safe User Parameter Offset at word offset 0x{0,x} (Calculated=0x{1,x}, Expected=0x{2,x}) 12505 The Standard Inputs Size of zero is not allowed 12506 The download of the Replacement Values is not allowed after the download before (download state={0}) 12507 The Info Data Map Cfg Data were downloaded in the wrong download state ({0}) 12508 The offset for the safety-Timer has to be inside the safety Output Area from 0x{0,x} to 0x{1,x} 12509 The 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 Data 12510 The 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 Data 12511 No more safe user parameter expected at byte-offset 0x{0,x} of the Safe User Parameter Cfg Data 12512 The TwinSAFE Address 0 is not allowed in the Project Cfg Data 12513 The download of the TwinSAFE IO-Project failed because {0} Groups are configured (only 1 Group allowed) 12514 The download of the Delete Project Cfg Data is not allowed in this state ({0}) 12515 The destination bit address (0x{0,x}, Bit {1}) already exists in the same mapping code 12516 Local Inputs cannot be mapped in the Info data because no local inputs are existing 12517 Local Outputs cannot be mapped in the Info data because no local outputs are existing 12518 The destination bit address (0x{0,x}, Bit {1}) already exists in the same mapping code 12519 the input mapping cfg data has to be read before the output mapping cfg data 12520 wrong subindex order when reading the mapping cfg data, the expected subindex is {0} 12521 when reading the input mapping cfg data, it has to be started with subindex 1 12522 invalid CRC when checking the Page {0} of the Safe Logic Cfg Data 12523 invalid CRC when checking the Page {0} of the Safe User Parameter Cfg Data 12524 invalid CRC when checking the Page {0} of the Replacement values Cfg Data 12544 No groups defined when trying to activate or deactive groups 12545 The reserved bits are set in value {0} at offset {1} when trying to activate or deactive groups 12546 The operation mode at offset {0} is not supported when trying to activate or deactive groups 12547 The deactiving of groups is not enabled for any group so no replacement values should be downloaded 12548 The maximum number ({0}) of Cfg Data pages was exceeded in the Replacement Values Cfg Data 12549 Invalid FB output size size at offset {0} of the Replacement Values Cfg Data 12550 Unexpected groupindex in the Replacement values Cfg Data at offset 0x{0,x} 12551 The download of the Activate Project Cfg Data was refused because {0} bytes of the Replacement Values Cfg Data were missing 12552 To 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 in 12553 No more definitions of individual replace values for analog FB Outputs in case of Group State unequal RUN are expected at offset {0} 12554 The offset in the definitions of individual replace values for analog FB Outputs in case of Group State unequal RUN was wrong at offset {0} 12555 The source process image offset of the Cyclic FRAM Data is outside the FB analog input area at offset {0} 12556 The source process image offset of the Cyclic FRAM Data has to even at offset {0} 12557 The size of the Cyclic FRAM Data was exceeding at offset {0} 12558 The 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} 12559 The size of the Cyclic FRAM CfgData in the GroupCfgData was not dividable by 4 at offset {0} 12560 The offset of the Cyclic FRAM Data in the GroupCfgData was wrong at offset {0} 12561 The value of {0} at offset {1} is not allowed when trying to activate or deactive groups 12563 FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The TDC2UpperLimit ({1}) is lower or equal than the maximum position jitter ({2}) 12564 FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The TDCUpperLimit ({1}) is lower or equal than the maximum position jitter ({2}) 12565 FB 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}) 12566 FB 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}) 12567 FB 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}) 12568 FB CAMMON (Word-Offset 0x{0,x} of the CfgData): The value of BDCLowerLimit (plus maximum position jitter) ({1}) is grealer or equal the configured value of 180° ({2}) 12569 FB 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}) 12570 FB 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}) 12571 FB 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}) 12572 FB 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) 12573 FB 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}) 12574 FB 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}) 12575 The maximum size of the Replacement Values was exceeded at Word-Offset 0x{0,x} of the Group Cfg Data 12576 If no deactivation mode is enabled the offset of the replacement values shall be zero at Word-Offset 0x{0,x} of the Group Cfg Data 12577 No more replacement values expected at byte-offset 0x{0,x} of the Replacement Values Cfg Data 12800 The PROFIsafe-protocol is not supported on this device 12801 The F_ParVersion in the F_Prm_Flag2 of the F-Parameter at Word-Offset 0x{0,x} is unequal 1 (PROFIsafe V2) 12802 The F_CRC1 of the F-Parameter at Word-Offset 0x{0,x} is wrong 12803 The 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) 12806 The I-Parameter CRC in the F-Parameter is wrong at Word-Offset 0x{0,x} 12807 The 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) 12808 The F_Source_Address in the F-Parameter at Word-Offset 0x{0,x} is outside the allowed area of 1-0xFFFE 12809 The F_Destination_Address in the F-Parameter at Word-Offset 0x{0,x} is outside the allowed area of 1-0xFFFE 12810 The F_WD_Time in the F-parameter at Word-Offset 0x{0,x} is outside the allowed range from 2-60000 12811 The F_Destination_Address in the F-Parameter at Word-Offset 0x{0,x} is wrong, the expected value is {1} 13056 The State OPERATIONAL was left in Restore Mode 13057 Only {0} CRCs were matching in Restore Mode 13058 The CRC of the Activate Project Cfg Data in Restore Mode does not match, the expected value was 0x{0,x} 13059 No RestoreMode Slaves configured when trying to start the Restore Mode 13060 The CRC of the User List Cfg Data was not matching in Restore Mode, the expected value was 0x{0,x} 13061 The download of the User List Cfg Data is not activated in Restore Mode 13062 The download of the User List Cfg Data in Restore-Mode is not allowed in the state {0} 13063 The activation of the TwinSAFE Restore Project is not allowed in the state {0} 13064 The Restore Mode is not supported in EtherCAT state 0x{0,x} 13072 The FSoE-Slave on the {0}. connection is in Restore-Mode 13073 The FSoE-Master on the {0}. connection is in Restore-Mode 13312 The {0}. group has no more errors 13313 The 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} 13314 The Wait-Com-Error-Timeout has not been expired when the group {0} should be deactivated in passivate mode 13315 A module fault happened in group {0} 13316 The assigned connection reported an error when the group {0} was deactivated in passivate mode 13317 The connection has been successfully restarted when the group {0} was deactivated in passivate mode 13328 All groups will enter the ERROR-state because the safe logic program has been restarted 13329 All groups will enter the ERROR-state because the CRC of the Change Group Activation Data was wrong 13330 All groups will enter the ERROR-state because the CRC of the Change FB Parameter Data was wrong 13331 All groups will enter the ERROR-state because the CRC of the Project CRC Data was wrong 13332 All groups will enter the ERROR-state because the CRC of the Power-On Analog Value Check Data was wrong 13333 The TwinSAFE Logic Program was not loaded on C1 because of an inconsistency 13334 The TwinSAFE Logic Program was not loaded on C2 because of an inconsistency 13344 No more EtherCAT size error (EtherCAT Output Size={0}, EtherCAT Input Size={1}) 13345 The EtherCAT Output Data sizes of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal 13346 The EtherCAT Input Data sizes of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal 13347 The EtherCAT Output Data sizes for PROFIsafe of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal 13348 The EtherCAT Input Data sizes for PROFIsafe of the Safety Logic Program ({0}) and the EtherCAT Configuration ({1}) are unequal 13349 The needed EtherCAT Process data buffer size ({0}) exceeded the maximum available size of {1} 13569 On the {0}. connection the changeable FSoE Address of {1} already exists 13570 On the {0}. connection the changeable FSoE Address is zero 14336 FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state SAFE 14338 FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state RESET 14339 FB {0} (ESTOP): An EDM-fault (0x{1,x}) was detected in state START 14340 FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual EStopIn-values are 0x{2,x} 14342 FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual EStopIn-values are 0x{2,x} 14343 FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state START, the actual EStopIn-values are 0x{2,x} 14345 FB {0} (ESTOP): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual EStopIn-values are 0x{2,x} 14351 FB {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}) 14352 FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state SAFE 14354 FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state RESET 14355 FB {0} (MON): An EDM-fault (0x{1,x}) was detected in state START 14356 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual MonIn/Secure-values are 0x{2,x} 14358 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual MonIn/Secure-values are 0x{2,x} 14359 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state START, the actual MonIn/Secure-values are 0x{2,x} 14360 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state RUN, the actual MonIn/Secure-values are 0x{2,x} 14361 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual MonIn/Secure-values are 0x{2,x} 14362 FB {0} (MON): An DiscTime-Fault (0x{1,x}) was detected in state FUNCTEST, the actual MonIn/Secure-values are 0x{2,x} 14367 FB {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}) 14368 FB {0} (TWOHAND): A Disc-Group-fault (0x{1,x}) was detected in state 1BUTTON, the actual TwoHandIn-values are 0x{2,x} 14369 FB {0} (TWOHAND): A Disc-Group-fault (0x{1,x}) was detected in state 2BUTTON, the actual TwoHandIn-values are 0x{2,x} 14371 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual TwoHandIn-values are 0x{2,x} 14373 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual TwoHandIn-values are 0x{2,x} 14379 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state 1BUTTON, the actual TwoHandIn-values are 0x{2,x} 14380 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state 2BUTTON, the actual TwoHandIn-values are 0x{2,x} 14381 FB {0} (TWOHAND): An DiscTime-Fault (0x{1,x}) was detected in state RELEASE, the actual TwoHandIn-values are 0x{2,x} 14384 FB {0} (OPMODE): An DiscTime-Fault (0x{1,x}) was detected, the actual OpIn-values are 0x{2,x} 14385 FB {0} (OPMODE): An Input-Fault was detected in state RESET, the actual OpIn-values are 0x{1,x} 14400 FB {0} (EDM): The SwitchOn-Time had been expired 14401 FB {0} (EDM): The SwitchOff-Time had been expired 14419 FB {0} (CS): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual Deactivate-values are 0x{2,x} 14421 FB {0} (CS): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual Deactivate-values are 0x{2,x} 14465 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state RUN, the actual MuteIn/OssdIn-values are 0x{2,x} 14467 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state SAFE, the actual MuteIn/OssdIn-values are 0x{2,x} 14469 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state RESET, the actual MuteIn/OssdIn-values are 0x{2,x} 14472 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state DELAYOUT, the actual MuteIn/OssdIn-values are 0x{2,x} 14473 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING1, the actual MuteIn/OssdIn-values are 0x{2,x} 14474 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING2, the actual MuteIn/OssdIn-values are 0x{2,x} 14475 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING3, the actual MuteIn/OssdIn-values are 0x{2,x} 14476 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING4, the actual MuteIn/OssdIn-values are 0x{2,x} 14477 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING5, the actual MuteIn/OssdIn-values are 0x{2,x} 14478 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING6, the actual MuteIn/OssdIn-values are 0x{2,x} 14479 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING7, the actual MuteIn/OssdIn-values are 0x{2,x} 14480 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING8, the actual MuteIn/OssdIn-values are 0x{2,x} 14481 FB {0} (MUTING): An DiscTime-Fault (0x{1,x}) was detected in state MUTING9, the actual MuteIn/OssdIn-values are 0x{2,x} 14482 FB {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} 14483 FB {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} 14484 FB {0} (MUTING): State MUTING1, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14485 FB {0} (MUTING): State MUTING1, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14486 FB {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} 14487 FB {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} 14488 FB {0} (MUTING): State MUTING3, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14489 FB {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} 14490 FB {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} 14491 FB {0} (MUTING): State MUTING4, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14492 FB {0} (MUTING): State MUTING4, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14493 FB {0} (MUTING): State MUTING5, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14494 FB {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} 14495 FB {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} 14496 FB {0} (MUTING): State MUTING6, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14497 FB {0} (MUTING): State MUTING6, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14498 FB {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} 14499 FB {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} 14500 FB {0} (MUTING): State MUTING8, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14501 FB {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} 14502 FB {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} 14503 FB {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} 14504 FB {0} (MUTING): State MUTING9, MutingEnable is set and the OssdIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14505 FB {0} (MUTING): State MUTING9, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14506 FB {0} (MUTING): State MUTING5, Sequential Inputs=TRUE, MuteIn3 and MuteIn4 are deactive: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14507 FB {0} (MUTING): State MUTING6, Sequential Inputs=TRUE, MuteIn3 and MuteIn4 are deactive: MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14508 FB {0} (MUTING): State MUTING1, MutingEnable is set and the MuteIn-signals are invalid, the actual MuteIn/OssdIn-values are 0x{1,x} 14512 FB {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}) 14529 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING1 (Digital Inputs=0x{1,x}) 14530 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING2 (Digital Inputs=0x{1,x}) 14531 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING3 (Digital Inputs=0x{1,x}) 14532 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING4 (Digital Inputs=0x{1,x}) 14533 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING5 (Digital Inputs=0x{1,x}) 14534 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING6 (Digital Inputs=0x{1,x}) 14535 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING7 (Digital Inputs=0x{1,x}) 14536 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING8 (Digital Inputs=0x{1,x}) 14537 FB {0} (MUTING): The Max-Muting-Time had been expired in state MUTING9 (Digital Inputs=0x{1,x}) 16385 FB {0} (CAMMON): The TDC2UpperLimit ({1}) is lower or equal than the maximum position jitter ({2}) 16386 FB {0} (CAMMON): The Position ({1}) is bigger than the maximum position (plus the maximum position jitter) ({2}) 16387 FB {0} (CAMMON): The input OverrunCAM was FALSE in the top dead center area, the actual position is {1} 16388 FB {0} (CAMMON): The input OverrunCAM changed from FALSE to TRUE outside the area between BDCUpperLimit and TDCLowerLimit, the actual position is {1} 16389 FB {0} (CAMMON): The input OverrunCAM was TRUE in the area between OverrunMax and BDCUpperLimit, the actual position is {1} 16390 FB {0} (CAMMON): The input OverrunCAM changed from TRUE to FALSE outside the area between OverrunMax and BDCLowerLimit, the actual position is {1} 16391 FB {0} (CAMMON): The input UpwardsCAM was FALSE in the area between BDCUpperLimit and TDCLowerLimit, the actual position is {1} 16392 FB {0} (CAMMON): The input UpwardsCAM changed from FALSE to TRUE outside the area between BDCLowerLimit and TDCLowerLimit, the actual position is {1} 16393 FB {0} (CAMMON): The input UpwardsCAM changed from TRUE to FALSE outside the area between TDCLowerLimit and OverrunMax, the actual position is {1} 16394 FB {0} (CAMMON): The Position was moving while waiting for a rising edge of the input Reset in the state MOVE-STOP 16395 FB {0} (CAMMON): The Position was moving while waiting for a falling edge of the input Reset in the state MOVE-START 16396 FB {0} (CAMMON): The Position {1} in the area between OverrunMax and BDCLowerLimit was detected in the state MOVE-UP 16397 FB {0} (CAMMON): The Position has left the top dead center while wating for a stop, the actual position is {1} 16398 FB {0} (CAMMON): The Position has been changed negative 16399 FB {0} (CAMMON): The input UpwardsCAM was TRUE in the area between OverrunMax and BDCLowerLimit 16400 FB {0} (CAMMON): The Position has a circle overflow in Pendulum Mode, actual position={1}, last position={2} 16401 FB {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} 16402 FB {0} (CAMMON): The Input BackwardsMove is TRUE while the Position is between 180° and 360°, the actual position is {1} 16403 FB {0} (CAMMON): The Input BackwardsMove is TRUE while the moving is clockwise 16404 FB {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} 16405 FB {0} (CAMMON): The value of TDCLowerLimit (plus maximum position jitter) ({1}) is bigger or equal the configured position of 360° ({2}) 16406 FB {0} (CAMMON): The value of BDCUpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDCLowerLimit ({2}) 16407 FB {0} (CAMMON): The value of BDCUpperLimit ({1}) is smaller or equal the configured value of 180° (plus maximum position jitter) ({2}) 16408 FB {0} (CAMMON): The value of BDCLowerLimit (plus maximum position jitter) ({1}) is greater or equal the configured value of 180° ({2}) 16409 FB {0} (CAMMON): The value of OverrunMax (plus twice the maximum position jitter) ({1}) is bigger or equal the value of BDCLowerLimit ({2}) 16410 FB {0} (CAMMON): The value of TDCUpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of OverrunMax ({2}) 16411 FB {0} (CAMMON): The value of TDC1UpperLimit (plus the maximum position jitter) ({1}) is bigger or equal the configured position of 360° ({2}) 16412 FB {0} (CAMMON): The value of TDC1LowerLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDC1UpperLimit (5d) 16413 FB {0} (CAMMON): The value of TDC2LowerLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of BDCLowerLimit ({2}) 16414 FB {0} (CAMMON): The value of TDC2UpperLimit (plus twice the maximum position jitter) ({1}) is bigger or equal the value of TDC2LowerLimit ({2}) 16415 FB {0} (CAMMON): The input PressStarted is TRUE and the position did not move after the PressStartedDelayTime 16416 FB {0} (CAMMON): The input PressStarted is TRUE and the position has stopped after moving before 16417 FB {0} (CAMMON): The input PressStarted is TRUE and the position has not moved enough, the actual position is {1}, the compare position is {2} 16418 FB {0} (CAMMON), Pendulum Mode: The Position has changed contra clockwise while moving up clockwise (actual Position={1}, old Position={2}) 16419 FB {0} (CAMMON), Pendulum Mode: The Position has changed clockwise while moving up contra clockwise (actual Position={1}, old Position={2}) 16420 FB {0} (CAMMON): The Position was moving while waiting for a falling edge of the input Reset in the state WAIT-FOR_RESET 16421 FB {0} (CAMMON): The TDCUpperLimit ({1}) is lower or equal than the maximum position jitter ({2}) 16512 FB {0} (ADD/SUB): an underflow was detected, AnalogIn1={1}, AnalogIn2={2} 16513 FB {0} (ADD/SUB): an overflow was detected, AnalogIn1={1}, AnalogIn2={2} 16520 FB {0} (SPEED): an underflow was detected, actual Position={1}, old Position={2} 16521 FB {0} (SPEED): an overflow was detected, actual Position={1}, old Position={2} 16528 FB {0} (LIMIT): the minimum value ({1}) is bigger than than the maximum value ({2}) 16536 FB {0} (COMPARE): an underflow was detected on CompOut ({1}), the minimum allowed value is {2} 16537 FB {0} (COMPARE): an overflow was detected on CompOut ({1}), the maximum allowed value is {2} 16544 FB {0} (MUL): an underflow was detected, AnalogIn1={1}, AnalogIn2={2} 16545 FB {0} (MUL): an overflow was detected, AnalogIn1={1}, AnalogIn2={2} 16552 FB {0} (DIV): an underflow was detected, AnalogIn1={1}, AnalogIn2={2} 16553 FB {0} (DIV): an overflow was detected, AnalogIn1={1}, AnalogIn2={2} 16560 FB {0} (SCALE): an underflow was detected, AnalogIn={1} 16561 FB {0} (SCALE): an overflow was detected, AnalogIn={1} 16562 FB {0} (SCALE): an overflow was detected after multiplication, AnalogIn={1} 16563 FB {0} (SCALE): an overflow was detected before division when rounding up the value, AnalogIn={1} 16568 FB {0} (COUNT): an underflow was detected on ActValue ({1}), the minimum allowed value is {2} 16569 FB {0} (COUNT): an overflow was detected on ActValue ({1}), the maximum allowed value is {2} 16576 FB {0} (SLI): an underflow was detected on ActValue ({1}), the minimum allowed value is {2} 16577 FB {0} (SLI): an overflow was detected on ActValue ({1}), the maximum allowed value is {2} 16584 FB {0} (ENVELOPE): an underflow was detected on InValue ({1}), the minimum allowed value is {2} 16585 FB {0} (ENVELOPE): an overflow was detected on InValue ({1}), the maximum allowed value is {2} 16586 FB {0} (ENVELOPE): an overflow error was detected on InValue ({1}), InValue+Offset is bigger than the maximum allowed value 16587 FB {0} (ENVELOPE): the MaxTime was expired (InValue={1}) 24585 SAFEOUT:Initial-Parameter: MultiplierDiagTestPulse has to be greater zero. ModuleNr:0x{0,x} 24592 SAFEOUT:Initial-Parameter: Number of Modules incorrect. ModuleNr:0x{0,x}, Parameter:0x{1,x} 24593 SAFEOUT:Initial-Parameter: Number of Channels incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24594 SAFEOUT:Initial-Parameter: Number of Diagnosis active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24595 SAFEOUT:Initial-Parameter: Number of Diagnosis inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24596 SAFEOUT:Initial-Parameter: Number of Feedback active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24597 SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis active Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24598 SAFEOUT:Initial-Parameter: Number of Feedback inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24599 SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis inactive Module incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24600 SAFEOUT:Initial-Parameter: Number of Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24601 SAFEOUT:Initial-Parameter: Number of Diagnosis inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24602 SAFEOUT:Initial-Parameter: Number of Feedback active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24603 SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24604 SAFEOUT:Initial-Parameter: Number of Feedback inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24605 SAFEOUT:Initial-Parameter: Number of Feedback Diagnosis inactive Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 24606 SAFEOUT:Setup Hardware Fault: Module Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24607 SAFEOUT:Setup Hardware Fault: Diagnosis active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24608 SAFEOUT:Setup Hardware Fault: Diagnosis inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24609 SAFEOUT:Setup Hardware Fault: Feedback active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24610 SAFEOUT:Setup Hardware Fault: Feedback Diagnosis active Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24611 SAFEOUT:Setup Hardware Fault: Feedback inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24612 SAFEOUT:Setup Hardware Fault: Feedback Diagnosis inactive Module. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24613 SAFEOUT:Setup Hardware Fault: Channel Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24614 SAFEOUT:Setup Hardware Fault: Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24615 SAFEOUT:Setup Hardware Fault: Diagnosis inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24616 SAFEOUT:Setup Hardware Fault: Feedback active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24617 SAFEOUT:Setup Hardware Fault: Feedback Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24618 SAFEOUT:Setup Hardware Fault: Feedback inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24619 SAFEOUT:Setup Hardware Fault: Feedback Diagnosis inactive Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 24624 SAFEOUT:The Feedback of the active Module Switch is wrong. Module:0x{0,x} 24625 SAFEOUT:The Feedback of the inactive Module Switch is wrong. Module:0x{0,x} 24626 SAFEOUT:The Feedback of the active Channel Switch is wrong. Module:0x{0,x} / Channel:0x{1,x} 24627 SAFEOUT:The Feedback of the inactive Channel Switch is wrong. Module:0x{0,x} / Channel:0x{1,x} 24640 SAFEOUT:Diagnosis Test: Common Fault Module:0x{0,x} / DiagChannel:0x{1,x} 24641 SAFEOUT:Diagnosis Test: Unknown State local ModuleState:0x{0,x} 24642 SAFEOUT:Diagnosis Test: Unknown State other ModuleState:0x{0,x} 24656 SAFEOUT:Diagnosis Test: Feedback active Module Switch is wrong (Step1 - check current state). Module:0x{0,x} 24657 SAFEOUT:Diagnosis Test: Feedback inactive Module Switch is wrong (Step1 - check current state). Module:0x{0,x} 24658 SAFEOUT:Diagnosis Test: Feedback active Channel Switch is wrong (Step1 - check current state). Module:0x{0,x} / DiagChannel:0x{1,x} 24659 SAFEOUT:Diagnosis Test: Feedback inactive Channel Switch is wrong (Step1 - check current state). Module:0x{0,x} / DiagChannel:0x{1,x} 24672 SAFEOUT:Diagnosis Test: Feedback active Module Switch is wrong (Step2 - check test pulse). Module:0x{0,x} 24673 SAFEOUT:Diagnosis Test: Feedback inactive Module Switch is wrong (Step2 - check test pulse). Module:0x{0,x} 24674 SAFEOUT:Diagnosis Test: Feedback active Channel Switch is wrong (Step2 - check test pulse). Module:0x{0,x} / DiagChannel:0x{1,x} 24675 SAFEOUT:Diagnosis Test: Feedback inactive Channel Switch is wrong (Step2 - check test pulse). Module:0x{0,x} / DiagChannel:0x{1,x} 24704 SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 24705 SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 24706 SAFEOUT:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 24707 SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 24708 SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 24709 SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 24710 SAFEOUT:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 24720 SAFEOUT:Module Switch FeedbackTest ViolationCounter incremented, Outputs active. Module:0x{0,x}, Info:0x{1,x}. 24721 SAFEOUT:Module Switch FeedbackTest ViolationCounter incremented, Outputs inactive. Module:0x{0,x}, Info:0x{1,x}. 24722 SAFEOUT:Channel Switch FeedbackTest ViolationCounter incremented, Outputs active. Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24723 SAFEOUT:Channel Switch FeedbackTest ViolationCounter incremented, Outputs inactive. Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24724 SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step1 - check current state). Module:0x{0,x}, Info:0x{1,x}. 24725 SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step1 - check current state). Module:0x{0,x}, Info:0x{1,x}. 24726 SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24727 SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24728 SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step2 - check test pulse). Module:0x{0,x}, Info:0x{1,x}. 24729 SAFEOUT:Module Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step2 - check test pulse). Module:0x{0,x}, Info:0x{1,x}. 24730 SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs active (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24731 SAFEOUT:Channel Switch DiagnosisTest ViolationCounter incremented, Outputs inactive (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 24736 SAFEOUT:Sercom Fault 0. Cmd/State:0x{0,x} 24737 SAFEOUT:Sercom Fault 1. Cmd/State:0x{0,x} 24752 SAFEOUT:Unknown Sercom Command Request 1. Cmd/State:0x{0,x} 24753 SAFEOUT:Unknown Sercom Command Answer 1. Cmd/State:0x{0,x} 24754 SAFEOUT:Unknown Sercom Command Request 2. Cmd/State:0x{0,x} 24755 SAFEOUT:Unknown Sercom Command Answer 2. Cmd/State:0x{0,x} 24768 SAFEOUT:Module Switch too fast Switching OFF detected Fault (see technical data). Module:0x{0,x} 24769 SAFEOUT:Channel Switch too fast Switching OFF detected Fault (see technical data). Module:0x{0,x} / Channel:0x{1,x} 24770 SAFEOUT:Module Switch too fast Switching ON detected Fault (see technical data). Module:0x{0,x} 24771 SAFEOUT:Channel Switch too fast Switching ON detected Fault (see technical data). Module:0x{0,x} / Channel:0x{1,x} 24772 SAFEOUT:Module Error Acknowledge is not possible. Module:0x{0,x} 24800 SAFEOUT:HAL Read Fault. ReturnData:0x{0,x} 24801 SAFEOUT:Init Fault. Module:0x{0,x} 32777 SAFEIN:Initial-Parameter: MultiplierDiagTestPulse has to be greater zero. ModuleNr:0x{0,x} 32784 SAFEIN:Initial-Parameter: Number of Modules incorrect. ModuleNr:0x{0,x}, Parameter:0x{1,x} 32785 SAFEIN:Initial-Parameter: Number of Channels incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 32792 SAFEIN:Initial-Parameter: Number of Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 32795 SAFEIN:Initial-Parameter: Number of Feedback Diagnosis active Channel incorrect. Parameter0:0x{0,x}, Parameter1:0x{1,x}, Parameter2:0x{2,x} 32805 SAFEIN:Setup Hardware Fault: Channel Switch. ReturnData:0x{0,x}, ReturnState:0x{1,x} 32806 SAFEIN:Setup Hardware Fault: Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 32809 SAFEIN:Setup Hardware Fault: Feedback Diagnosis active Channel. ReturnData:0x{0,x}, ReturnState:0x{1,x} 32832 SAFEIN:Diagnosis Test: Common Fault Module:0x{0,x} / DiagChannel:0x{1,x} 32833 SAFEIN:Diagnosis Test: Unknown State local ModuleState:0x{0,x} 32834 SAFEIN:Diagnosis Test: Unknown State Other ModuleState:0x{0,x} 32835 SAFEIN Pulse Detection: Wrong pulse was detected at . Module:0x{0,x} / DiagChannel:0x{1,x} 32836 SAFEIN Pulse Detection: Detected pulse from Module:0x{0,x} / DiagChannel:0x{1,x} 32850 SAFEIN:Diagnosis Test: Feedback in Step1 active Channel is wrong. Module:0x{0,x} / DiagChannel:0x{1,x} 32866 SAFEIN:Diagnosis Test: Feedback in Step2 active Channel is wrong. Module:0x{0,x} / DiagChannel:0x{1,x} 32896 SAFEIN:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 32897 SAFEIN:Diagnosis Test:VendorData. ID: 0x{0,x} Module:0x{1,x} 32900 SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 32901 SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 32902 SAFEIN:Diagnosis Test:VendorData. Channel: 0x{0,x} Module:0x{1,x} 32918 SAFEIN:DiagnosisTest ViolationCounter incremented, Inputs active (Step1 - check current state). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 32922 SAFEIN:DiagnosisTest ViolationCounter incremented, Inputs active (Step2 - check test pulse). Module:0x{0,x}, Channel:0x{1,x}, Info:0x{2,x}. 32928 SAFEIN:Sercom Fault 0. Cmd/State:0x{0,x} 32929 SAFEIN:Sercom Fault 1. Cmd/State:0x{0,x} 32944 SAFEIN:Unknown Sercom Command Request 1. Cmd/State:0x{0,x} 32945 SAFEIN:Unknown Sercom Command Answer 1. Cmd/State:0x{0,x} 32946 SAFEIN:Unknown Sercom Command Request 2. Cmd/State:0x{0,x} 32947 SAFEIN:Unknown Sercom Command Answer 2. Cmd/State:0x{0,x} 32960 SAFEIN:Error Acknowledge is not possible. Module:0x{0,x} 32961 SAFEIN:Diagnosis Test: Implausible Inputs detected. Module:0x{0,x} 32962 SAFEIN:Diagnosis Test: Implausible Inputs detected (INFO). Parameter1:0x{0,x} / Parameter2:0x{1,x} 32992 SAFEIN:Init HAL Fault.ReturnState:0x{0,x} 32993 SAFEIN:Init Fault. Module:0x{0,x} 33008 SAFEIN: Testpulse is parametrized but not enabled (Diag Testpulse for Inputs active). Module:0x{0,x} / Channel:0x{1,x} 33009 SAFEIN: Testpulse is parametrized but not enabled (Diag TestPulse active). Module:0x{0,x} / Channel:0x{1,x} 33010 SAFEIN: Testfilter-Time too long. Parameter1:0x{0,x} / Parameter2:0x{1,x} 33011 SAFEIN: Inputfilter-Time too short. Parameter1:0x{0,x} / Parameter2:0x{1,x} 33012 SAFEIN: Wrong parameters detected for Module:0x{0,x} / Channel:0x{1,x}. Please check parameters! DisplayTxtId true {BB2A9999-102E-421A-8D3D-B0660E07B1FE} TcSystemEventClass 1 Interner Fehler. Internal error. 2 Keine Echtzeit. No real-time. 3 Zuweisung gesperrt - Speicherfehler. Allocation locked – memory error. 4 Postfach voll – Es konnte die ADS Nachricht nicht versendet werden. Reduzieren der Anzahl der ADS Nachrichten pro Zyklus bringt Abhilfe. Mailbox full – the ADS message could not be sent. Reducing the number of ADS messages per cycle will help. 5 Falsches HMSG. Wrong HMSG. 6 Ziel-Port nicht gefunden – ADS Server ist nicht gestartet oder erreichbar. Target port not found – ADS server is not started or is not reachable. 7 Target computer not found – AMS route was not found. 8 Unbekannte Befehl-ID. Unknown command ID. 9 Ungültige Task-ID. Invalid task ID. 10 Kein IO. No IO. 11 Unbekannter AMS-Befehl. Unknown AMS command. 12 Win32 Fehler. Win32 error. 13 Port nicht verbunden. Port not connected. 14 Ungültige AMS-Länge. Invalid AMS length. 15 Ungültige AMS Net ID. Invalid AMS Net ID. 16 Installations-Level ist zu niedrig – TwinCAT 2 Lizenzfehler. Low installation level – TwinCAT 2 license error. 17 Kein Debugging verfügbar. No debugging available. 18 Port deaktiviert – TwinCAT System Service nicht gestartet. Port disabled – TwinCAT system service not started. 19 Port bereits verbunden. Port already connected. 20 AMS Sync Win32 Fehler. AMS Sync Win32 error. 21 AMS Sync Timeout. AMS Sync Timeout. 22 AMS Sync Fehler. AMS Sync error. 23 Keine Index-Map für AMS Sync vorhanden. No index map for AMS Sync available. 24 Ungültiger AMS-Port. Invalid AMS port. 25 Kein Speicher. No memory. 26 TCP Sendefehler. TCP send error. 27 Host nicht erreichbar. Host unreachable. 28 Ungültiges AMS Fragment. Invalid AMS fragment. 29 TLS Sendefehler – Secure ADS Verbindung fehlgeschlagen. TLS send error – secure ADS connection failed. 30 Zugriff Verweigert – Secure ADS Zugriff verweigert. Access denied – secure ADS access denied. {7D760066-D373-4A0C-B0F1-328B1620B0F0} TcGeneralAdsEventClass 1792 Allgemeiner Gerätefehler. General device error. 1793 Service wird vom Server nicht unterstützt. Service is not supported by the server. 1794 Ungültige Index-Gruppe. Invalid index group. 1795 Ungültiger Index-Offset. Invalid index offset. 1796 Lesen oder Schreiben ist nicht gestattet. Reading or writing is not permitted. 1797 Parametergröße ist nicht korrekt. Parameter size is not correct. 1798 Ungültige Daten-Werte. Invalid data value(s). 1799 Gerät ist nicht betriebsbereit. Device is not ready to operate. 1800 Gerät ist beschäftigt. Device is busy. 1801 Ungültiger Kontext vom Betriebssystem. Kann durch Verwendung von ADS Bausteinen in unterschiedlichen Tasks auftreten. Invalid operating system context. This can result from use of ADS function blocks in different tasks. 1802 Nicht genügend Speicher. Insufficient memory. 1803 Ungültige Parameter-Werte. Invalid parameter value(s). 1804 Nicht gefunden (Dateien,...). Not found (files, ...). 1805 Syntax-Fehler in Datei oder Befehl. Syntax error in file or command. 1806 Objekte stimmen nicht überein. Objects do not match. 1807 Objekt ist bereits vorhanden. Object already exists. 1808 Symbol nicht gefunden. Symbol was not found. 1809 Symbol-Version ist ungültig. Kann durch einen Online-Change auftreten. Erzeuge einen neuen Handle. Invalid symbol version. This can occur due to an online change. Create a new handle. 1810 Gerät (Server) ist im ungültigen Zustand. Device (server) is in invalid state. 1811 AdsTransMode wird nicht unterstützt. AdsTransMode is not supported. 1812 Notification Handle ist ungültig. Notification handle is invalid. 1813 Notification-Client nicht registriert. Notification client is not registered. 1814 Keine weiteren Notification Handles. No further notification handles. 1815 Größe der Notification zu groß. Notification size too large. 1816 Gerät ist nicht initialisiert. Device is not initialized. 1817 Gerät hat einen Timeout. Device has a timeout. 1818 Interface Abfrage fehlgeschlagen. Interface query failed. 1819 Falsches Interface angefordert. Wrong interface is requested. 1820 Class-ID ist ungültig. Class ID is invalid. 1821 Object-ID ist ungültig. Object ID is invalid. 1822 Anforderung steht aus. Request pending. 1823 Anforderung wird abgebrochen. Request is aborted. 1824 Signal-Warnung. Signal warning. 1825 Ungültiger Array-Index. Invalid array index. 1826 Symbol ist nicht aktiv. Symbol is not active. 1827 Zugriff verweigert. Access denied. 1828 Fehlende Lizenz. Missing license. 1829 Lizenz abgelaufen. License is expired. 1830 Lizenz überschritten. License is exceeded. 1831 Lizenz ungültig. License is invalid. 1832 Lizenzproblem: System-ID ist ungültig. License problem: System ID is invalid. 1833 Lizenz nicht zeitlich begrenzt. License not limited in time. 1834 Lizenzproblem: Zeitpunkt in der Zukunft. License problem: Time in the future. 1835 Lizenz-Zeitraum ist zu lang. License time period is too long. 1836 Exception beim Systemstart. Exception at system startup. 1837 Lizenz-Datei zweimal gelesen. License file is read twice. 1838 Ungültige Signatur. Invalid signature. 1839 Zertifikat ungültig. Invalid certificate. 1840 Public Key vom OEM nicht bekannt. Public key not known from OEM. 1841 Lizenz nicht gültig für diese System-ID. License not valid for this system ID. 1842 Demo-Lizenz untersagt. Demo license prohibited. 1843 Funktions-ID ungültig. Invalid function ID. 1844 Außerhalb des gültigen Bereiches. Outside the valid range. 1845 Ungültiges Alignment. Invalid alignment. 1846 Ungültiger Plattform Level. Invalid platform level. 1847 Kontext – Weiterleitung zum Passiv-Level. Context – forward to passive level. 1848 Kontext – Weiterleitung zum Dispatch-Level. Context – forward to dispatch level. 1849 Kontext – Weiterleitung zur Echtzeit. Context – forward to real-time. 1857 Dienst enthält einen ungültigen Parameter. Service contains an invalid parameter. 1858 Polling-Liste ist leer. Polling list is empty. 1859 Variablen-Verbindung bereits im Einsatz. Variable connection is already in use. 1860 Die Invoke-ID ist bereits in Benutzung. Invoke ID is already in use. 1861 Timeout ist aufgetreten – Die Gegenstelle antwortet nicht im vorgegebenen ADS Timeout. Timeout has occurred – the remote terminal is not responding in the specified ADS timeout. 1862 Fehler im Win32 Subsystem. Error in Win32 subsystem 1863 Ungültiger Client Timeout-Wert. Invalid client timeout value. 1864 Port nicht geöffnet. Port is not open. 1865 Keine AMS Adresse. No AMS address. 1872 Interner Fehler in Ads-Sync. Internal error in Ads sync. 1873 Überlauf der Hash-Tabelle. Hash table overflow. 1874 Schlüssel in der Hash-Tabelle nicht gefunden. Key not found in hash table. 1875 Keine Symbole im Cache. No symbols in the cache. 1876 Ungültige Antwort erhalten. Invalid response received 1877 Sync Port ist verriegelt. Sync port is locked. {E759605A-2341-48FC-9F3F-C8FA405C4B24} TcRouterEventClass 1280 Lockierter Speicher kann nicht zugewiesen werden. Locked memory cannot be allocated. 1281 Die Größe des Routerspeichers konnte nicht geändert werden. The router memory size could not be changed. 1282 Das Postfach hat die maximale Anzahl der möglichen Meldungen erreicht. The mailbox has reached the maximum number of possible messages. 1283 Das Debug Postfach hat die maximale Anzahl der möglichen Meldungen erreicht. The debug mailbox has reached the maximum number of possible messages. 1284 Der Porttyp ist unbekannt. The port type is unknown. 1285 Der TwinCAT Router ist nicht initialisiert. TwinCAT Router is not initialised. 1286 Die Portnummer ist bereits vergeben. The port number is already assigned. 1287 Der Port ist nicht registriert. The port is not registered. 1288 Die maximale Portanzahl ist erreicht. The maximum number of ports has been reached. 1289 Der Port ist ungültig. The port is invalid. 1290 Der TwinCAT Router ist nicht aktiv. TwinCAT Router is not active. 1291 Das Postfach hat die maximale Anzahl für fragmentierte Nachrichten erreicht. The mailbox has reached the maximum number for fragmented messages. 1292 Fragment Timeout aufgetreten. A fragment timeout has occurred. 1293 Port wird entfernt. The port is removed. {1D0C4BAC-ECF3-4F33-8F20-A12E77AB6387} Win32EventClass 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 8 Not enough storage is available to process this command. 13 The data is invalid. 21 The device is not ready. 22 The device does not recognize the command. 23 Data error (cyclic redundancy check). 24 The program issued a command but the command length is incorrect. 29 The system cannot write to the specified device. 30 The system cannot read from the specified device. 31 A device attached to the system is not functioning. 50 The request is not supported. 51 The remote computer is not available. 52 A duplicate name exists on the network. 53 The network path was not found. 54 The network is busy. 55 The specified network resource or device is no longer available. 80 The file exists. 82 The directory or file cannot be created. 85 The local device name is already in use. 86 The specified network password is not correct. 87 The parameter is incorrect. 110 The system cannot open the device or file specified. 183 Cannot create a file when that file already exists. 186 The flag passed is not correct. 258 The wait operation timed out. 259 No more data is available. 487 Attempt to access invalid address. 534 Arithmetic result exceeded 32 bits. 995 The I/O operation has been aborted because of either a thread exit or an application request. 996 Overlapped I/O event is not in a signaled state. 997 Overlapped I/O operation is in progress. {CC929187-3970-4CF4-8F39-946BEC12422D} TcIPCDiagEventClass #x0001 Fail - unspecified error. #x0100 Invalid index. #x0101 Invalid access. #x0102 Buffer is too small. #x0103 Type is not supported. #x0104 Out of memory. #x0105 No data available. #x0106 Invalid data. #x0107 Invalid argument. #x0108 Value is out of range. #x0200 Server is busy. #x0201 MDP API is not initialized. #x0F00 Not implemented. #x1000 Not supported. {20226F4C-54BA-479F-BA48-FBE52D0E9CD5} TcIPCDiagPlcApiEventClass 1 Invalid module list (initialization of IPCDiag required). #x2 Module of parameter is unavailable (not existing). #x3 Parameter is unavailable (not existing). #x4 No valid parameter value available (reading is pending or failed). #x5 Allocated buffer is invalid (pointer is zero or buffer size is too small). #x6 Allocated index is invalid. 7 Error that some of the requested parameter values returned an error (use GetParameterByIdx). #x8 Info that some of the requested parameter values returned an error (use GetParameterByIdx). {229BB0F3-F9CA-475F-8753-FABF4E988AA0} My message event 999666 {0} {1} {2} {52901D69-F975-4949-BB4F-7F9B31186576} Project specific events 2 {0,x} Emergency stop {1} {2} activated #x012014 {0,x} Crane HPU - External shutdown #x012015 {0,x} Crane HPU - Oil Level shutdown #x030001 {0,x} Sensor Error {1} #x030002 {0,x} Position failure {1} #x030003 {0,x} PWM card failure {1} #x003018 {0,x} Loadcell tension limit exceeded {2} #x004433 {0,x} Oil level switch alarm {2} ID {1} {16A8F721-FD4A-4ED1-B8BC-9994F334F362} NewEventClass_DisplayText #x013001 {0,x} Oil filter clogged {2} ID {1} #x013002 {0,x} Gate Valve Closed {2} ID {1} #x013003 {0,x} Oil level switch alarm {2} ID {1} #x013004 {0,x} Limitl switch alarm {2} ID {1} #x013005 {0,x} Return filter clogged {2} ID {1} #x013006 {0,x} Servo pressure too low {2} ID {1} #x013007 {0,x} High oil temperature {2} ID {1} #x013008 {0,x} Oil temperature Critical {2} ID {1} #x013009 {0,x} Drain filter clogged {2} ID {1} #x01300A {0,x} Pump overload {2} ID {1} {69C78348-F660-42E2-88B9-1C9A9130BA21} Event Class for the power lib #x010001 {0,x} The power usage is too high. Power Usage {3} #x010002 {0,x} Power Regneration is too high. Power Regeneration {3} #x010003 {0,x} AFE {1} Ethercat communication lost #x012001 {0,x} The time for building up pressure was too high - Brake HPU {1} #x012002 {0,x} The pressure for the brake HPU {1} is too low to operate #x012003 {0,x} The oil level for brake HPU {1} is too low #x012004 {0,x} The oil temperature for brake HPU {1} is too high #x010004 #x010005 {0,x} AFE {1} is not operational #x000001 {0,x} Ground Fault {1} {2} #x010006 {0,x} The IGBT #{1} has a charge overload. Wait 5 minutes #x012005 {0,x} The pressure for the crane HPU is too low to operate #x012006 {0,x} The limit switch is indicating a low oil level in the crane HPU #x012007 {0,x} The oil level in the crane HPU is low #x012008 {0,x} The crane HPU drain filter is clogged #x012009 {0,x} The crane HPU return filter is clogged #x012010 {0,x} Error with crane HPU servo filter #x012011 {0,x} Hight temperature on crane HPU #x012012 {0,x} Crane HPU Motor overload #x012013 {0,x} Crane HPU has not enough power #x010007 {0,x} AFE {1} {2} has tripped #x010008 {0,x} AFE {1} {2} is in local control #x014001 {0,x} HPU {1} Pump1 overload #x014002 {0,x} HPU {1} Pump2 overload #x014003 {0,x} HPU {1} Oil level low #x014004 {0,x} HPU {1} oil level extreme low #x014005 {0,x} HPU {1} Oil temperature high #x010009 {0,x} Brake Chopper {1} Error #x01000A {0,x} Brake Chopper {1} High temperature #x012014 {0,x} The HPU Brake oil filter is clogged #x012015 {0,x} The brake HPU has a too high oil temperature {5D86E790-FC5D-402F-B030-59EA298C46A8} NewEventClass_DisplayText #x001000 {0,x} The inverter #{1} has no power (#{2}) #x001001 {0,x} The inverter #{1} has tripped (#{2}) #x001002 #x001003 #x001004 {0,x} The inverter #{1} has received a reset request (#{2}) #x001005 {0,x} The inverter #{1} has a fieldbus problem (#{2}) #x001006 {0,x} The inverter #{1} is now local (#{2}) #x001007 {0,x} The inverter #{1} misses encoder 1 (#{2}) #x001008 {0,x} The inverter #{1} misses encoder 2 (#{2}) #x003000 has not enough motors (#{2})]]> {C6898F4C-D78A-444D-BE11-5D97C208E6E4} NewEventClass_DisplayText #x003001 {0,x} Spooling #{1} {2} has a high spool deviation #x003002 {0,x} Spooling drive #{1} {2} has lost the motor for spooling #x003003 {0,x} Winch #{1} the follow up sensor is defect #x003017 {0,x} Spooling drive #{1} {2} auto mode disabled - position error too high. #x003004 {0,x} Fishpump #{1} has a high oil temperature {3} #x003005 {0,x} Fishpump #{1} has a defect oil temperature sensor #x003006 {0,x} Fishpump #{1} has a defect environment pressure sensor #x003007 {0,x} Fishpump #{1} has a defect housing pressure sensor #x003008 {0,x} #{1} A gear cooling oil filter is clocked. #x003009 {0,x} #{1} The motor cooling oil pressure is not OK #x00300A {0,x} #{1} The motor cooling oil level is low #x00300B {0,x} #{1} The motor cooling oil temperature is high #x00300C {0,x} #{1} Motor cooling HPU missing pump #{3} #x00300D {0,x} Winch #{1} one of the motors has a high temperature {3} #x00300E {0,x} Winch #{1} one of the gear temperatures is high ({3}) #x00300F {0,x} {2} temperature sensor # {1} is defect #x003010 {0,x} Purseseine Winch #{1} has a defect brake on sensor #x003011 {0,x} Purseseine Winch #{1} has a defect brake off sensor #x003012 {0,x} The difference of the trawset is high #x003013 {0,x} The max distance of a sounder winch to the master length is too high #x003014 {0,x} {2} temperature sensor {1} is defect #x003015 {0,x} Winches have lost pumps for cooling #x3016 {0,x} Fishpump #{1} has to low difference pressure inside housing. Value is {2} bar #x003018 {0,x} Gear cooling selector valve {1} Feedback Error