meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
simatic:errorcodes [2024/11/17 23:01] – [Simatic Modbus S7 error- and statuscodes] vamsansimatic:errorcodes [2024/11/18 00:07] (current) – vamsan
Line 79: Line 79:
 |80C8..80CF|DP slave or module reports a manufacturer-specific error regarding its resources. Please refer to the documentation provided by the manufacturer of the DP slave or module.|| |80C8..80CF|DP slave or module reports a manufacturer-specific error regarding its resources. Please refer to the documentation provided by the manufacturer of the DP slave or module.||
 |80C8|No response OF the server in the defined period. \\ Value at the ID parameter is already being used by a connection that was created via the user program. The connection uses the same ID but different connection settings on the CONNECT parameter.|| |80C8|No response OF the server in the defined period. \\ Value at the ID parameter is already being used by a connection that was created via the user program. The connection uses the same ID but different connection settings on the CONNECT parameter.||
 +|80C8|The slave does not respond within the set time \\ **Solution:** Check the data transmission rate, parity and wiring of the slave.||
 |80C9|Connection partner validation failed. The connection partner who wants to establish a connection does not correspond to the partner defined in the structure at the CONNECT parameter.|| |80C9|Connection partner validation failed. The connection partner who wants to establish a connection does not correspond to the partner defined in the structure at the CONNECT parameter.||
 |80C9|The length of the receive area is smaller than the length of the sent data.|| |80C9|The length of the receive area is smaller than the length of the sent data.||
 +|80C9|The slave does not respond within the time set by Blocked_Proc_Timeout. \\ **Solution:** Check the setting for Blocked_Proc_Timeout. \\ Check if the module has been configured with the Modbus_Comm_Load instruction. The module may possibly need to be reconfigured using Modbus_Comm_Load after a pull/plug or after voltage recovery.||
 |80CE|The IP address of the local interface is 0.0.0.0|| |80CE|The IP address of the local interface is 0.0.0.0||
 |80D0|Related to TCP and the active connection endpoint: The remote_qdn parameter is an empty string. In this case no connection can be established.|| |80D0|Related to TCP and the active connection endpoint: The remote_qdn parameter is an empty string. In this case no connection can be established.||
 |80D1|The remote_qdn parameter is not a fully qualified domain name. Possibly the dot is missing at the end.|| |80D1|The remote_qdn parameter is not a fully qualified domain name. Possibly the dot is missing at the end.||
 +|80D1|The wait time for XON or CTS = ON has expired. \\ **Solution:** The communication partner has a fault, is too slow or is offline. Check the communication partner or change the parameters, if necessary.||
 |80D2|There is no DNS server address configured.|| |80D2|There is no DNS server address configured.||
 +|80D2|"Hardware RTS always ON": Send job canceled due to change from DSR = ON to OFF \\ **Solution:** Check the communication partner. Make sure that DSR is ON for the entire duration of transmission.||
 |80D3|The fully qualified domain name could not be resolved. Possible causes: \\  - The DNS server cannot be reached, e.g. B. because it is down or the remote port is unreachable. \\  - An error occurred while communicating with the DNS server. \\  - The DNS server returned a valid DNS response, but the response did not contain an IPv4 address.|| |80D3|The fully qualified domain name could not be resolved. Possible causes: \\  - The DNS server cannot be reached, e.g. B. because it is down or the remote port is unreachable. \\  - An error occurred while communicating with the DNS server. \\  - The DNS server returned a valid DNS response, but the response did not contain an IPv4 address.||
 |80E0|Inappropriate or bad message was received.|| |80E0|Inappropriate or bad message was received.||
 +|80E0|Frame aborted: Send buffer overflow / send frame too long \\ **Solution:** In the user program call the instruction more often or configure a communication with data flow control.||
 |80E1|Error during handshake. Possible causes: \\  - Canceled by user \\  - Security not high enough \\  - Renegotiation is not supported \\  - SSL/TLS version is not supported \\  - Hostname validation failed|| |80E1|Error during handshake. Possible causes: \\  - Canceled by user \\  - Security not high enough \\  - Renegotiation is not supported \\  - SSL/TLS version is not supported \\  - Hostname validation failed||
 +|80E1|Frame aborted: Parity error \\ **Solution:** Check the connection line of the communication partners, or verify that the same data transmission rate, parity and stop bit number are configured for both devices.||
 |80E2|Unsupported / Invalid Certificate \\ - Possible cause: The time of the module concerned has not been set or the module is not synchronized.|| |80E2|Unsupported / Invalid Certificate \\ - Possible cause: The time of the module concerned has not been set or the module is not synchronized.||
 +|80E2|Frame aborted: Character frame error \\ **Solution:** Check the settings for start bit, data bits, parity bit, data transmission rate, and stop bit(s).||
 |80E3|Certificate has been discarded.|| |80E3|Certificate has been discarded.||
 +|80E3|Frame aborted: Character overflow error \\ **Solution:** Check the number of data in the frame of the communication partner.||
 |80E4|No valid certificate authority was found.|| |80E4|No valid certificate authority was found.||
 +|80E4|Frame aborted: Maximum frame length reached \\ **Solution:** Select a shorter frame length at the communication partner. The following are valid (depending on the module): 1-1024/2048/4096 (bytes)||
 |80E5|Certificate expired.|| |80E5|Certificate expired.||
 |80E6|Integrity error in transport layer security protocol.|| |80E6|Integrity error in transport layer security protocol.||
Line 103: Line 112:
 |**8100..81FF**|**Error in the 1st call parameter**|| |**8100..81FF**|**Error in the 1st call parameter**||
 |8152|The WSTRING, WCHAR, BOOL, ARRAY of STRING, ARRAY of WSTRING and ARRAY of WCHAR data types are not supported at the SRCBLK parameter. (//Error in the 1st call parameter//)|| |8152|The WSTRING, WCHAR, BOOL, ARRAY of STRING, ARRAY of WSTRING and ARRAY of WCHAR data types are not supported at the SRCBLK parameter. (//Error in the 1st call parameter//)||
 +|8180|Invalid value for MB_DB parameter  \\ **Solution:** The value configured for MB_DB (instance data DB) at the Modbus_Comm_Load instruction is not valid. Check the interconnection of the Modbus_Comm_Load instruction and its error messages.||
 |8181|The module does not support this data transmission rate. \\ **Solution:** Select a valid data transmission rate for the module at the BAUD parameter.|| |8181|The module does not support this data transmission rate. \\ **Solution:** Select a valid data transmission rate for the module at the BAUD parameter.||
-|8182|the length OF the Modbus frame in the frame header does NOT match the number OF received bytes. (//Error in the 1st call parameter//)|| +|8182|The module does not support this parity setting. \\ **Solution:** Select a suitable value for "Parity" at the PARITY parameter. The following are valid: \\ • None (1) \\ • Even (2) \\ • Odd (3) \\ • Mark (4) \\ • Space (5) \\ • Any (6)|| 
-|8183|#error reading OR writing data OR access outside the address area (//Error in the 1st call parameter//)|| +|8183|The module does not support this type of data flow control. \\ **Solution:** Select a valid data flow control for the module at the FLOW_CTRL parameter.|| 
-|8184|Invalid exception code received. (//Error in the 1st call parameter//)||+|8184|Invalid value for "Response timeout" \\ **Solution:**  Select a suitable value for "Response timeout" at the RESP_TO parameter. Valid range of values: 1 to 65535 (ms)||
 |8185|Diagnostics code NOT supported. (//Error in the 1st call parameter//)|| |8185|Diagnostics code NOT supported. (//Error in the 1st call parameter//)||
-|8186|received function code does NOT match the one sent originally. (//Error in the 1st call parameter//)|| +|8186|Invalid slave address \\ **Solution:** Select a suitable slave address at the MB_ADDR parameter. \\ The following are valid: 1-247 at standard address area; \\ 1-65535 at extended address area (0 is reserved for Broadcast)|| 
-|8187|The MB_HOLD_REG parameter has an Invalid Pointer. Data area is too small. (//Error in the 1st call parameter//)|| +|8187|Invalid value at MB_HOLD_REG parameter \\ **Solution:** Select a suitable value for the hold register at the MB_HOLD_REG parameter.|| 
-|8188|The MB_MODE parameter has an Invalid value. (//Error in the 1st call parameter//)|| +|8188|Invalid operating mode or broadcast (MB_ADDR = 0) and MODE parameter ≠ 1 \\ **Solution:** Select the value 1 for MODE in Broadcast mode or select a different operating mode.|| 
-|8189|An invalid data used in MB_DATA_ADDR (//Error in the 1st call parameter//)|| +|8189|Invalid data address \\ **Solution:** Select a suitable value for the data address at the DATA_ADDR parameter.|| 
-|818A|Invalid data length at the MB_DATA_LEN parameter. (//Error in the 1st call parameter//)|| +|818A|Invalid length \\ **Solution:** Select a suitable data length at the DATA_LEN parameter.|| 
-|818B|The MB_DATA_PTR parameter has an Invalid Pointer. (//Error in the 1st call parameter//)|| +|818B|Invalid value for DATA_PTR \\ **Solution:** Select a suitable value for the data pointer at the DATA_PTR parameter (M or DB address).|| 
-|818C|Timeout at parameter BLOCKED_PROC_TIMEOUT OR RCV_TIMEOUT (//Error in the 1st call parameter//)||+|818C|The pointer to a MB_HOLD_REG area must be a data block or a bit memory address area. \\ **Solution:** Select a suitable value for the pointer to the MB_HOLD_REG area. || 
 +|818C|Interconnection error of the DATA_PTR parameter \\ **Solution:** Check the interconnection of the instruction.|| 
 +|818D|The area addressed by DATA_PTR is longer than the DB, or the area addressed is too small for the number of data bytes to be read or written. \\ **Solution:** Check the DATA_PTR pointer||
 |8189|Invalid addressing OF data at the MB_DATA_ADDR parameter. (//Error in the 1st call parameter//)|| |8189|Invalid addressing OF data at the MB_DATA_ADDR parameter. (//Error in the 1st call parameter//)||
 |**8200..82FF**|**Error in the 2nd call parameter**|| |**8200..82FF**|**Error in the 2nd call parameter**||
-|8200|A different Modbus request is currently being processed via the PORT. (//Error in the 2nd call parameter//)|| +|8200|The interface is busy with an ongoing request. \\ **Solution:** Repeat the command later. Make sure that there are no commands still running before you start a new one. || 
-|8281|Function code is NOT supported. (//Error in the 2nd call parameter//)|| +|8280|Negative acknowledgment when reading module \\ **Solution:** Check the input at the PORT parameter. \\ You can find more detailed information on error causes in the Send_Config.RDREC.STATUS or Receive_Config.RDREC.STATUS static parameters or RDREC.STATUS and in the description of the SFB RDREC.|| 
-|8282|the length OF the Modbus frame in the frame header does NOT match the number OF received bytes. (//Error in the 2nd call parameter//)||+|8281|Negative acknowledgment when writing module \\ **Solution:** Check the input at the PORT parameter. \\ You can find more detailed information on error causes in the Send_Config.WRREC.STATUS or Receive_Config.WRREC.STATUS static parameters or WRREC.STATUS and in the description of the SFB WRREC. || 
 +|8282|Module not available \\ **Solution:** Check the input at the PORT parameter and ensure that the module can be reached.||
 |8283|#error reading OR writing data OR access outside the address area. (//Error in the 2nd call parameter//)|| |8283|#error reading OR writing data OR access outside the address area. (//Error in the 2nd call parameter//)||
 |8284|Invalid exception code received. (//Error in the 2nd call parameter//)|| |8284|Invalid exception code received. (//Error in the 2nd call parameter//)||
Line 127: Line 140:
 |8352|The WSTRING, WCHAR, BOOL, ARRAY of STRING, ARRAY of WSTRING and ARRAY of WCHAR data types are not supported at the DSTBLK parameter. (//Error in the 3st call parameter//)|| |8352|The WSTRING, WCHAR, BOOL, ARRAY of STRING, ARRAY of WSTRING and ARRAY of WCHAR data types are not supported at the DSTBLK parameter. (//Error in the 3st call parameter//)||
 |8380|received Modbus frame has incorrect format OR too few bytes were received.(//Error in the 3st call parameter//)|| |8380|received Modbus frame has incorrect format OR too few bytes were received.(//Error in the 3st call parameter//)||
-|8381|Function code is NOT supported.(//Error in the 3st call parameter//)|| +|8380|CRC error \\ Solution: Checksum error of the Modbus frame. Check the communication partner.|| 
-|8382|the length OF the Modbus frame in the frame header does NOT match the number OF received bytes.(//Error in the 3st call parameter//)|| +|8381|The function code is not supported or is not supported for broadcast. \\ **Solution:** Check the communication partner and make sure that a valid function code is sent.|| 
-|8383|#error reading OR writing data OR access outside the address area. (//Error in the 3st call parameter//)|| +|8382|Invalid length information in the request frame \\ **Solution:** Select a suitable data length at the DATA_LEN parameter.|| 
-|8384|Invalid exception code received. (//Error in the 3st call parameter//)|| +|8383|Invalid data address in the request frame \\ **Solution:** Select a suitable value for the data address at the DATA_ADDR parameter.|| 
-|8385|Diagnostics code NOT supported. (//Error in the 3st call parameter//)|| +|8384|Invalid data value error in the request frame \\ **Solution:** Check the data value in the request frame of the Modbus master|| 
-|8386|received function code does NOT match the one sent originally. (//Error in the 3st call parameter//)|| +|8385|The diagnostic value is not supported by the Modbus slave (function code 08) \\ **Solution:** The Modbus slave only supports the diagnostic values 16#0000 and 16#000A.|| 
-|8387|the protocol ID OF the Modbus TCP frame received BY the server is NOT "0". (//Error in the 3st call parameter//)|| +|8386|The returned function code does not match the requested function code. \\ **Solution:** Check the response frame and the addressing of the slave.|| 
-|8388|the Modbus server sent a different data length than was requested. (//Error in the 3st call parameter//)|| +|8387|A slave that was not requested answers \\ **Solution:** Check the response frame of the device. Check the address settings of the slave.|| 
-|8389|Invalid data area definition. (//Error in the 3st call parameter//)||+|8388|Error in the response of the slave to a write request. \\ **Solution:** Check the response frame of the slave.|| 
 +|8389|Invalid data area definition: \\ • Illegal value of data_type \\ • DB number not permitted or not available:– Invalid value of db– DB number does not exist–DB number is already being used by another data area– DB with optimized access– DB is not in work memory \\ • Illegal valid for length \\ • Overlapping of MODBUS address areas that belong to the same MODBUS data type \\ **Solution:** Check the definition of the data areas.||
 |**8400..84FF**|**Error in the 4st call parameter**|| |**8400..84FF**|**Error in the 4st call parameter**||
-|**8500..85FF**|**Error in the 5st call parameter**||+|8452|MB_HOLD_REG is not a pointer to a DB or a bit memory area \\ **Solution:** Check the MB_HOLD_REG pointer|| 
 +|8453|MB_HOLD_REG is not a pointer of type BOOL or WORD \\ **Solution:** Check the MB_HOLD_REG pointer|| 
 +|8454| The area addressed by MB_HOLD_REG is longer than the DB, or the area addressed is too small for the number of data bytes to be read or written. \\ **Solution:** Check the MB_HOLD_REG pointer|| 
 +|8455|MB_HOLD_REG points to a write-protected DB \\ **Solution:** Check the MB_HOLD_REG pointer|| 
 +|8456| Error during instruction execution. The cause of the error is shown in the STATUS parameter \\ **Solution:** Determine the value of the SFCSTATUS parameter. Check what this means in the description for SFC51, STATUS parameter.|| 
 +|8852|**Error in the 5st call parameter**||
 |**8600..86FF**|**Error in the 6st call parameter**|| |**8600..86FF**|**Error in the 6st call parameter**||
 |**8700..87FF**|**Error in the 7st call parameter**|| |**8700..87FF**|**Error in the 7st call parameter**||
 |**8800..88FF**|**Error in the 8st call parameter**|| |**8800..88FF**|**Error in the 8st call parameter**||
 +|8828|DATA_PTR points to a bit address that is not equal to n * 8 \\ **Solution:** Check the DATA_PTR pointer||
 +|8852|DATA_PTR is not a pointer to a DB or a bit memory area \\ **Solution:** Check the DATA_PTR pointer||
 +|8853|DATA_PTR is not a pointer of type BOOL or WORD \\ **Solution:** Check the DATA_PTR pointer||
 +|8855|DATA_PTR points to a write-protected DB \\ **Solution:** Check the DATA_PTR pointer||
 +|8856|Error during call of SFC51 \\ **Solution:**  Call the Modbus_Master instruction again||
 |**8900..89FF**|**Error in the 9st call parameter**|| |**8900..89FF**|**Error in the 9st call parameter**||
 |8A24|The "Data" points to an impermissible area, for example to the load memory or the local data. (FileWriteC)|| |8A24|The "Data" points to an impermissible area, for example to the load memory or the local data. (FileWriteC)||
 |8A51|Invalid data type of the "Data" parameter. (FileWriteC)|| |8A51|Invalid data type of the "Data" parameter. (FileWriteC)||
 |8A52|The tag at the Data parameter is insufficient. A part of the source area data may have been written. (FileWriteC)|| |8A52|The tag at the Data parameter is insufficient. A part of the source area data may have been written. (FileWriteC)||
 +|8FFF|The module is not ready temporarily due to a reset. \\ **Solution:** Repeat the request.||