Basic instructions
8.8 Program control operations
S7-1200 Programmable controller
System Manual, V4.2, 09/2016, A5E02486680-AK
313
Table 8- 149 Error_ID values
Program block execution error
2520 9504 Corrupted string
Operand out of range read error
Operand out of range write error
Data alignment read error (incorrect bit alignment)
Data alignment write error (incorrect bit alignment)
Uninitialized pointer error
Access error: DB does not exist
Access error: Wrong DB used
Wrong version or FC does not exist
Instruction does not exist
Wrong version or FB does not exist
Instruction does not exist
Access error: DB does not exist
Program nesting depth error
2576 9590 Local data allocation error
Physical input point does not exist
Physical output point does not exist
By default, the CPU responds to a block execution error by logging an error in the
diagnostics buffer. However, if you place one or more GET_ERROR or GET_ERROR_ID
instructions within a code block, this block is now set to handle errors within the block. In this
case, the CPU does not log an error in the diagnostics buffer. Instead, the error information
is reported in the output of the GET_ERROR or GET_ERROR_ID instruction. You can read
the detailed error information with the GET_ERROR instruction, or read just the error
identifier with GET_ERROR_ID instruction. Normally the first error is the most important, with
the following errors only consequences of the first error.
The first execution of a GET_ERROR or GET_ERROR_ID instruction within a block returns
the first error detected during block execution. This error could have occurred anywhere
between the start of the block and the execution of either GET_ERROR or GET_ERROR_ID.
Subsequent executions of either GET_ERROR or GET_ERROR_ID return the first error
since the previous execution of GET_ERROR or GET_ERROR_ID. The history of errors is
not saved, and execution of either instruction will re-arm the PLC system to catch the next
error.
To Next Page
Loading...
