Master Operation Mode
114
05/01 AWB2700-1384GB
80B2 HW-error: module not available
* the configured slot is not
allocated.
* actual module type is not the
same as target module type.
* decentrallised periphery is not
available.
* there is no entry for the module
in the relevant SDB.
This is possible with SFC 67 „X_GET“ and
SFC 68
„X_PUT“ and SFC 72 „I_GET“ and SFC 73
„I_PUT“
80B3 Data may only be read or written,
e.g. write-protected DB
This is 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 for ANY pointer
or ARRAY of the specified data
type is 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 Processing rejected due to
invalid operating status.
This is possible with SFC 65 „X_SEND“
80B6 The received acknowledgement
contains an unknown error code.
80B7 Data type and/or length of the
transmitted data does not match
the area in the partner CPU into
which it is to be written.
This is possible with SFC 68 „X_PUT“ and
SFC 73 „I_PUT“
80B8 SFC 65 „X_SEND“: the „X_RCV“ of the
communication partner SFC 66 rejected data
transfer (RD=NIL).
80B9 SFC 65 „X_SEND“: the data block was
identified by the communication partner (call of
V“), however, due to STOP operating status, it
has not yet been loaded into the user program.
80BA The response of the
communication partner does not
fit into the communication
telegram.
Error code Explanations (general) Explanations (SFC-specific)
To Next Page
Loading...