Technical data

Table Of Contents
S7 Communication
System Software for S7-300/400 System and Standard Functions - Volume 2/2
A5E00739858-01
21-21
Error Information
The following table contains all the error information specific to SFB/FB 13 that can
be output with the parameters ERROR and STATUS.
ERROR
STATUS
(Decimal)
Explanation
0 11 Warning: The receive data are now being processed in a priority class having
lower priority.
0 17 Warning: block receiving data asynchronously. The LEN parameter shows the
amount of data already received in bytes.
1 1 Communications problems, for example:
Connection description not loaded (local or remote)
Connection interrupted (for example: cable, CPU off, CP in STOP mode)
Connection to partner not yet established
Additional for S7-300:
-
Maximum number of parallel jobs/instances exceeded
1 2 Function cannot be executed (protocol error).
1 4 Error in the receive area pointer RD_1 regarding the data length or data type.
The sent data field is longer than the receive area.
1 5 Reset request received, incomplete transfer.
1 8 Access error in the corresponding SFB/FB 12 "BSEND". After the last valid data
segment has been sent, ERROR = 1 and STATUS = 4 or ERROR = 1 and
STATUS = 10 is reported.
1 10 Access to the local user memory not possible (for example, access to a deleted
DB).
1 12 When the SFB was called
An instance DB was specified that does not belong to SFB 13
No instance DB was specified, but rather a global DB.
No instance DB found (loading a new instance DB from the PG).
1 18
R_ID already exists in the connection ID.
Additional for S7-300:
-
The instances were overloaded at CPU-RUN (STOP-RUN transition of
the CPU or CP required.)
1 20
S7-400: Not enough work memory available. If there is still enough total
work memory available, then the solution is to compress the work memory.
H system: a first call of SFB is not possible during an update since the
communication buffer in the work memory is being created. Measures that
change the work memory are not possible during an update.
S7-300:
-
Maximum number of parallel jobs/instances exceeded
-
The instances were overloaded at CPU-RUN (STOP-RUN transition of
the CPU or CP required.)
-
Possible when first called
-
Memory bottleneck in CP
1 27 There is no function code in the CPU for this block.