The "real error information" that is contained in the table "specific error information" and
others may be classified as follows:
Value Description
809xh Error on the CPU where the SFC is being executed
80Axh Permanent communication error
80Bxh Error on the communication partner
80Cxh Temporary error
Value Description
0000h REQ = 1 when the specified connection has not been established.
7000h Call issued with REQ = 0 (call without processing),
BUSY is set to 0, no data transfer is active.
7001h First call with REQ = 1: data transfer initiated;
BUSY is set to 1.
7002h Intermediate call with REQ = 1.
8090h The specified target address of the communication partners is not valid, e.g.:
n bad IOID
n bad base address exists
n bad MPI-address (> 126)
8095h The block is already being processed on a priority class that has a lower priority.
80A0h Error in the acknowledgement that was received.
80A1h Communication failures: SFC-call after an existing connection has been terminated.
80B1h ANY-pointer error. The length of the data block that must be transferred is wrong.
80B4h ANY-pointer data type error, or ARRAY of the specified data type is not permitted.
80B6h The received acknowledgement contains an unknown error code.
80BAh The answer of the communication partner does not fit into the communication telegram.
80C0h The specified connection is already occupied by another operation.
80C1h Lack of resources on the CPU where the SFC is being executed, e.g.:
n the module is already executing the maximum number of different send operations.
n connection resources may be occupied, e.g. by a receive operation.
RET_VAL (Return value)
Specific error information:
VIPA SPEED7
Integrated Standard
System Functions > SFC 69 - X_ABORT - Disconnect
HB00 | OPL_SP7 | Operation list | en | 18-30 715
To Next Page
Loading...
