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
simatic:errorcodes [2025/09/02 08:58] – vamsansimatic:errorcodes [2025/10/17 14:31] (current) – vamsan
Line 8: Line 8:
  
 \\ \\
-List of error codes related to Simatic communication (especially Modbus communication). I added a little to the list based on my own experience (red entries).+List of error codes related to Simatic communication, especially Modbus communication. I added a few entries based on my own experience (marked in red).
 \\ \\  \\ \\ 
-//If you have more information about Modbus error signals, or if you found any error in the table, let me know!//+//If you have more information about Modbus error signals, or if you found any errors in the table, let me know!//
 \\ \\ \\ \\
-I am constantly expanding and improving the table based on my own experience.+I continually expand and improve the table based on my own experience.
 \\ \\ \\ \\ \\ \\
 +**Simatic Modbus error codes:**
 \\ \\
 ^Status codes^Text^notes and example call functions| ^Status codes^Text^notes and example call functions|
Line 23: Line 24:
 |7002|Intermediate call. Connection is being established, \\ BUSY has the value "1".|| |7002|Intermediate call. Connection is being established, \\ BUSY has the value "1".||
 |7003|Connection is being terminated|| |7003|Connection is being terminated||
-|7004|Connection established AND monitored. No job processing active.|| +|7004|Connection established AND monitored. No job processing is active.|| 
-|7005|data is being sent.|| +|7005| Data is being sent. \\ \\ <color red>In a properly functioning client system, signal 7005 will only "flash" briefly, indicating that the query telegram has been sent. Signal 7006 should then be received shortly thereafter, confirming receipt of the response.\\ [vamsan]</color>|| 
-|7006|data is being received. \\ \\  <color red> If this status "freezes", i.e. the #busy signal is not followed by #done, the unit does not respond, but is technically available. In the case of Modbus communication, it is worth checking the unit address and setting it. This is especially valid if the TCP/RTU converter is used, in this case //"MB_CLIENT_DB".MB_Unit_ID := address;// may be important. It is worth testing the operation of the converter beforehand on a PC with the modbus client test program. - vamsan</color>||+|7006|data is being received. \\ \\  <color red>If a properly functioning client function causes this status to "freeze," meaning the #busy signal is not followed by #done, the unit does not respond but remains technically available. For Modbus communication, it is advisable to verify the unit address and set it correctly. This is especially important if a TCP/RTU converter is used; in that case, //"MB_CLIENT_DB".MB_Unit_ID := address;// might be significant. It is recommended to test the converter's operation in advance using a PC with a Modbus client test program. \\ \\ For a server, a persistent 7006 signal usually indicates the "stand by, everything is fine" status. \\ [vamsan]</color>||
 |00 .. 7Fxx|CPU Kein Fehler oder keine Warnung|| |00 .. 7Fxx|CPU Kein Fehler oder keine Warnung||
 |8x3A|Invalid pointer at parameter x.|| |8x3A|Invalid pointer at parameter x.||
Line 74: Line 75:
 |80C3| - A block with this ID is already being processed in another priority group. \\ - Internal lack of resources. \\ The maximum number of simultaneously active FileWriteC instructions has already been reached.|| |80C3| - A block with this ID is already being processed in another priority group. \\ - Internal lack of resources. \\ The maximum number of simultaneously active FileWriteC instructions has already been reached.||
 |80C4|Temporary communication error: \\  - The connection cannot be established at the moment. \\  - The connection cannot be established because firewalls on the connection path are not enabled for the required ports. \\  - The interface is receiving new parameters. \\  - The configured connection is currently being removed by a "TDISCON" instruction. \\ \\ <color red> Most often, the solution to this error is to recompile the entire program (//compile -> software (rebuild all)// and download it (//PLC newstart!//) - vamsan </color>|| |80C4|Temporary communication error: \\  - The connection cannot be established at the moment. \\  - The connection cannot be established because firewalls on the connection path are not enabled for the required ports. \\  - The interface is receiving new parameters. \\  - The configured connection is currently being removed by a "TDISCON" instruction. \\ \\ <color red> Most often, the solution to this error is to recompile the entire program (//compile -> software (rebuild all)// and download it (//PLC newstart!//) - vamsan </color>||
-|80C5|DP slave or module not available. \\ The connection partner refuses to establish the connection, cleared down the connection or actively ended it. \\ - Connection terminated by the communication partner. \\ - LSAP of the remote connection partner not released \\ ||+|80C5|DP slave or module not available. \\ The connection partner refuses to establish the connection, cleared down the connection or actively ended it. \\ - Connection terminated by the communication partner. \\ - LSAP of the remote connection partner not released \\ \\ <color red> - This error very often indicates a bad firewall setting. You need to check that in addition to IP-release, port-release is also set correctly. In the event of port release, ports 502 and 503 must also be enabled. \\ \\ - In many cases, this error happens when a Modbus RTU network is connected behind the Modbus-TCP media converter. In this situation, the stationID must also be included with the call (0..255). Without it, the converter "loses" the telegram. \\ [vamsan] </color>||
 |80C6|**Network error** - The connection partner cannot be reached. \\ Record transfer aborted due to priority class abort.|| |80C6|**Network error** - The connection partner cannot be reached. \\ Record transfer aborted due to priority class abort.||
 |80C7|Execution timed out. \\ Job aborted due to restart (warm start) or cold start of the DP master.|| |80C7|Execution timed out. \\ Job aborted due to restart (warm start) or cold start of the DP master.||