The following error messages may occur:
0 - no error
If the bit "Order ready with error" is set, the CP had to reinitialize the connection, e.g.
after a reboot or RESET.
1 - wrong Q/ZTYP at HTB
The order has been parameterized with the wrong type label.
2 - AG area not found
The order impulse had a wrong parameterized DB-No.
3 - AG area too small
Q/ZANF and Q/ZLAE overwrite the range boundaries. Handling with data blocks the
range boundary is defined by the block size. With flags, timers, counters etc. the
range size depends on the AG.
4 - QVZ-Error in the AG
This error message means, that you chose a source res. destination parameter of
the AG area, where there is either no block plugged in or the memory has a defect.
The QVZ error message can only occur with the type Q/ZTYP AS, PB, QB or
memory defects.
5 - Error at indicator word
The parameterized indicator word cannot be handled. This error occurs, if ANZW
declared a data word res. double word, that is not (any more) in the specified data
block, i.e. DB is too small or doesn’t exist.
6 - no valid ORG-Format
The data destination res. source isn’t declared, neither at the handling block (Q/
TYP="NN") nor at the coupler block.
7 - Reserved
8 - no available transfer connections
The capacity for transfer connections is at limit. Delete unnecessary connections.
9 - Remote error
There was an error at the communication partner during a READ/WRITE-order.
A - Connection error
The connection is not (yet) established. The message disappears as soon as the
connection is stable. If all connections are interrupted, please check the block itself
and the bus cable. Another possibility for the occurrence of this error is a wrong
parameterization, like e.g. inconsistent addressing.
B - Handshake error
This could be a system error or the size of the data blocks has been defined out of
range.
C - Initial error
The wrong handling block tried to initialize the order or the size of the given data
block was too large.
D - Cancel after RESET
This is a normal system message. With PRIO 1 and 2 the connection is interrupted
but will be established again, as soon as the communication partner is online. PRIO
3 connections are deleted, but can be initialized again.
E - Order with basic load function
VIPA SPEED7
System Blocks
Fetch/Write Communication > SFC 230 ... 238 - Page frame communication
HB00 | OPL_SP7 | Operation list | en | 18-30 891
To Next Page
Loading...
