YASKAWA VIPA SPEED7 - Ethernet Communication

8.2 Ethernet Communication
8.2.1 Communication - FC 5...6 for CP 343
The two blocks are used to process connection requests on the PLC side of an Ethernet
CP 343. Through integration of these blocks in the cycle block OB1 you may cyclically
send and receive data. Within these blocks, the SFCs 205 and 206 are called that are
stored as special function blocks in the CPU.
Please regard that you may only use the SEND/RECV-FCs from VIPA in
your user application for the communication with VIPA CPs. At a change
to VIPA CPs in an already existing project, the present AG_SEND /
AG_LSEND res. AG_RECV / AG_LRECV may be replaced by AG_SEND
res. AG_RECV from VIPA without adaptation. Due to the fact that the CP
automatically adjusts itself to the length of the data to transfer, the L var-
iant of SEND res. RECV is not required for VIPA CPs.
For the communication between CPU and Ethernet-CP 343, the following FCs are avail-
able:
n AG_SEND (FC 5)
– This block transfers the user data from the data area given in SEND to the CP
specified via ID and LADDR. As data area you may set a PI, bit memory or data
block area. When the data area has been transferred without errors, "job ready
without error" is returned.
n AG_RECV (FC 6)
– The block transfers the user data from the CP into a data area defined via RECV.
As data area you may set a PI, bit memory or data block area. When the data
area has been transferred without errors, "job ready without error" is returned.
The CP processes send and receive commands independently from the CPU cycle and
needs for this transfer time. The interface with the FC blocks to the user application is
here synchronized by means of acknowledgements/receipts. For status evaluation the
communication blocks return parameters that may be evaluated directly in the user appli-
cation. These status displays are updated at every block call.
Do not use cyclic calls of the communication blocks in OB 1. This causes a permanent
communication between CPU and CP. Program instead the communication blocks within
a time OB where the cycle time is higher OB 1 res. event controlled.
If a block is called a second time in the user application before the data of the last time is
already completely send res. received, the FC block interface reacts like this:
n AG_SEND
– No command is accepted until the data transfer has been acknowledged from the
partner via the connection. Until this you receive the message "Order running"
before the CP is able to receive a new command for this connection.
n AG_RECV
– The job is acknowledged with the message "No data available yet" as long as the
CP has not received the receive data completely.
The following illustration shows a possible sequence for the FC blocks together with the
organizations and program blocks in the CPU cycle:
Communication blocks
Status displays
Deployment at high com-
munication load
FC call is faster than CP
transfer time
AG_SEND, AG_RECV in
user application
VIPA SPEED7
Network Communication
Ethernet Communication > Communication - FC 5...6 for CP 343
HB00 | OPL_SP7 | Operation list | en | 18-30 137