Technical data

Table Of Contents
Communication SFCs for Non-Configured S7 Connections
System Software for S7-300/400 System and Standard Functions - Volume 2/2
A5E00739858-01
22-5
Error Code
(W#16# ...)
Explanation (General)
Explanation (for Specific SFC)
80B2 Hardware error: module
does not exist
The configured slot
is
not occupied.
Actual module type
does not match
expected type
Distributed
peripheral
I/Os not available.
No entry for the
module in the
corresponding SDB.
Possible with SFC 67 "X_GET" and SFC 68 "X_PUT" and
SFC 72 "I_GET" and SFC 73 "I_PUT"
80B3 Data may either only be
read or only written, for
example, write-protected
DB
Possible with SFC 67 "X_GET" and SFC 68 "X_PUT" and
SFC 72 "I_GET" and SFC 73 "I_PUT"
80B4 Data type error in the
ANY pointer, or ARRAY
of the specified type not
allowed.
SFC 67 "X_GET" and SFC 68 "X_PUT" and SFC 72 "I_GET"
and SFC 73 "I_PUT": The data type specified in VAR_ADDR is
not supported by the communication partner.
80B5 Execution rejected due
to illegal mode
Possible with SFC 65 "X_SEND"
80B6 The received
acknowledgment
contains an unknown
error code.
-
80B7 Data type and/or length
of the transferred data
does not fit in the area
on the partner CPU to
which it should be
written.
Possible with SFC 68 "X_PUT" and SFC 73 "I_PUT"
80B8 - SFC 65 "X_SEND":
The SFC 66 "X_RCV" of the communication partner did not
allow data acceptance (RD=NIL).
80B9 - SFC 65 "X_SEND":
The block of data was identified by the communication partner
(SFC 66 "X_RCV" call with EN_DT=0), it has not yet been
entered in the user program because the partner is in the
STOP mode.
80BA The response of the
communication partner
does not fit in the
communication frame.
-
80C0 The specified connection
is being used by another
job.
-