Technical data

Table Of Contents
S7 Communication
System Software for S7-300/400 System and Standard Functions - Volume 2/2
21-14
A5E00739858-01
ERROR
STATUS
(Decimal)
Explanation
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 19 The corresponding SFB/FB "USEND" is sending data faster than the SFB/FB
"URCV" can copy them to the receive areas ."
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
1 27 There is no function code in the CPU for this block.
Data Consistency
The data are received consistently if you remember the following points:
S7-300: After the status parameter NDR has changed to the value 1, you must
immediately
call FB 9 "URCV" again with the value 0 at EN_R. This ensures
that the receive area is not overwritten before you have evaluated it.
Evaluate the receive area (RD_1) completely before you call the block with the
value 1 at control input EN_R).
S7-400: After the status parameter NDR has changed to the value 1, there are new
receive data in your receive areas (RD_i). A new block call may cause these data
to be overwritten with new receive data. If you want to prevent this, you must call
SFB 9 "URCV" (such as with cyclic block processing) with the value 0 at EN_R
until you have finished processing the receive data.