Technical data

Table Of Contents
S7 Communication
System Software for S7-300/400 System and Standard Functions - Volume 2/2
21-40
A5E00739858-01
Parameter Declaration Data Type Memory Area Description
IO_STATE IN_OUT BYTE I, Q, M, D, L Not currently relevant. Do not assign a
value to this parameter if your
communication partner is an S7
programmable controller.
Error Information
The following table contains all the error information specific to SFB 20 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 Communications problems, for example
Connection description not loaded (local or remote)
Connection interrupted (for example, cable, CPU off, CP in STOP mode)
1 2 Negative acknowledgement from the partner device. The function cannot be
executed.
1 3 The program name entered for PI_NAME is unknown.
1 4 Error in the pointer PI_NAME involving the data length or the data type.
1 7 The partner device is already in the STOP state.
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 20
No instance DB was specified, but rather a shared DB.
No instance DB found (loading a new instance DB from the PG).
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.
21.13 Initiating a Hot Restart on a Remote Device with
SFB 21 "RESUME"
Description
If there is a rising edge at control input REQ, SFB 21 "RESUME" activates a hot
restart on the remote device selected with the ID.
The following conditions must be met if the remote device is a CPU: