Technical data

Table Of Contents
S7 Communication
System Software for S7-300/400 System and Standard Functions - Volume 2/2
A5E00739858-01
21-17
Error Information
The following table contains all the error information specific to SFB/FB 12 that can
be output with the parameters ERROR and STATUS.
ERROR
STATUS
(Decimal)
Explanation
0 11 Warning:
New job cannot take effect since previous job is not yet completed.
The job is now being processed in a priority class having lower priority.
0 25 Communication has started. The job is being processed.
1 1 Communication 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 Negative acknowledgement from the partner SFB/FB. The function cannot
be executed.
1 3 R_ID is unknown on the connection specified by the ID or the receive block
has not yet been called.
1 4 Error in the send area pointer SD_1 involving the data length or the data
type or the value 0 was transferred with LEN.
1 5 Reset request was executed.
1 6 Partner SFB/FB is in the DISABLED state (EN_R has the value 0). Also
check the input parameters of the BRCV block for consistency with the
BSEND block.
1 7 Partner SFB/FB is in the wrong state.
The receive block was not called again after the last data transmission.
1 8 Access to remote object in the user memory was rejected: The target area
for the corresponding SFB/FB 13 "BRCV" is too small.
The corresponding SFB/FB 13 "BRCV" reports ERROR = 1, STATUS = 4 or
ERROR = 1, STATUS = 10.
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 12
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.)