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:45] – 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.||
Line 127: Line 129:
 |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. ||
 |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.|| |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.||
 |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. || |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. ||
Line 138: 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.|| 
 +|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.|| |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**||
Line 153: Line 156:
 |8455|MB_HOLD_REG points to a write-protected DB \\ **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.|| |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.||
-|**8500..85FF**|**Error in the 5st call 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.||