meta data for this page
  •  

Differences

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

Link to this comparison view

simatic:errorcodes [2026/04/21 20:46] – created - external edit 127.0.0.1simatic:errorcodes [2026/06/16 12:17] (current) vamsan
Line 45: Line 45:
 |8094|"Length" is greater than the maximum permitted value. For an S7-1500 CPU, for example, the maximum value permitted is 16 MB, i.e. 16,777,216 bytes. (FileWriteC) \\ "Length" + "Offset" is greater than the maximum permitted value. (FileWriteC)|| |8094|"Length" is greater than the maximum permitted value. For an S7-1500 CPU, for example, the maximum value permitted is 16 MB, i.e. 16,777,216 bytes. (FileWriteC) \\ "Length" + "Offset" is greater than the maximum permitted value. (FileWriteC)||
 |809A|The structure at the CONNECT parameter is not supported on an integrated interface or the length is invalid.|| |809A|The structure at the CONNECT parameter is not supported on an integrated interface or the length is invalid.||
-|809B|The InterfaceId element within the TCON_xxx structure does not reference a hardware ID of a CPU or CM/CP interface or has the value "0".||+|809B|The InterfaceId element within the TCON_xxx structure does not reference a hardware ID of a CPU or CM/CP interface or has the value "0"\\ \\ <color red> - You have forget set Unit ID: device & networks -> click to communication unit (PLC or comm card) -> Properties -> System constants -> example: Local~CP_1543-1~Ethernet_interface_1 (259). Com.block settings InterfaceID (HW_ANY) <- 259. </color>||
 |80A0|Negative acknowledgment when reading from the module|| |80A0|Negative acknowledgment when reading from the module||
 |80A1|The specified connection or port is already in use. \\ Communication error: \\  - The specified connection has not yet been established. \\  - The specified connection is being terminated. Transmission via this connection is not possible. \\  - The interface is reinitialized. \\  - Negative acknowledgment when writing to the module \\ - Write error; the data in the file on the memory card may be partly overwritten. (FileWriteC) \\ \\ <color red>This errors are often caused by conflicting IDs (CONN_OUC). Ensure each connection has a unique ID! After fixing the error, it's advisable to recompile the entire program (//compile -> software (rebuild all)//) and then download it (//PLC restart!//). - Vamsan </color>|| |80A1|The specified connection or port is already in use. \\ Communication error: \\  - The specified connection has not yet been established. \\  - The specified connection is being terminated. Transmission via this connection is not possible. \\  - The interface is reinitialized. \\  - Negative acknowledgment when writing to the module \\ - Write error; the data in the file on the memory card may be partly overwritten. (FileWriteC) \\ \\ <color red>This errors are often caused by conflicting IDs (CONN_OUC). Ensure each connection has a unique ID! After fixing the error, it's advisable to recompile the entire program (//compile -> software (rebuild all)//) and then download it (//PLC restart!//). - Vamsan </color>||
Line 75: 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, clears down the connection, or actively ends it. \\ - Connection terminated by the communication partner. \\ - LSAP of the remote connection partner not released \\ \\ <color red> - This error often points to an incorrect firewall setting. You should verify that, in addition to IP release, port release is also configured properly. When port release is involved, ports 502 and 503 need to be enabled. \\ \\ - In many cases, this error occurs when a Modbus RTU network is connected behind a Modbus-TCP media converter. In this scenario, the station ID must also be included with the call (0..255). Without it, the converter "loses" the telegram. \\ [vamsan] </color>||+|80C5|DP slave or module not available. \\ The connection partner refuses to establish the connection, clears down the connection, or actively ends it. \\ - Connection terminated by the communication partner. \\ - LSAP of the remote connection partner not released \\ \\ <color red> - This error often points to an incorrect firewall setting. You should verify that, in addition to IP release, port release is also configured properly. When port release is involved, ports 502 and 503 need to be enabled. \\ - can u try to change 502 <-> 503 (local <-> remote) \\ - In many cases, this error occurs when a Modbus RTU network is connected behind a Modbus-TCP media converter. In this scenario, the station ID 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.||