Chapter 11 Integrated OBs SFBs SFCs Manual VIPA CPU 21x
11-38 HB103E - Rev. 05/45
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
This is a normal system message. This order is a READ/WRITE-
PASSIV and can not be started from the AG.
F
Order not found
The called order is not parameterized on the CP. This error may occur
when the SSNR/A-No. combination in the handling block is wrong or no
connection block is entered.
The bits 4 to 7 of Byte 2 are reserved for extensions.
Here you may see if an order has already been started, if an error occurred
or if this order is blocked, e.g. a virtual connection doesn’t exist any longer.
Handshake convenient
Set: Per plug-in according to the „delete“-announcement in the
order status bit: Handshake convenient (=1) is used at
the RECEIVE block (telegram exists at PRIO 1 or
RECEIVE impulse is possible at PRIO 2/3)
Analyze: Per RECEIVE block: The RECEIVE initializes the hand-
shake with the CP only if this bit is set.
Per application: for RECEIVE request (request a telegram
at PRIO 1).
Order is running
Set: Per plug-in: when the CP received the order.
Delete: Per plug-in: when an order has been commissioned (e.g.
receipt received).
Analyze: Per handling blocks: A new order is only send, when the
order before is completely commissioned.
Per user: when you want to know, if triggering a new
order is convenient.
Order ready without errors
Set: Per plug-in: when the according order has been
commissioned without errors.
Delete: Per plug-in: when the according order is triggered for a
second time.
Analyze: Per user: to proof that the order has been commissioned
without errors.
Status management
Byte 1,
Bit 0 to Bit 3
Bit 0
Bit 1
Bit 2