EasyManua.ls Logo

YASKAWA VIPA SPEED7 - Page 157

YASKAWA VIPA SPEED7
1007 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
ERROR STATUS
(decimal)
Description
1 1 Communication failures, e.g.
n Connection parameters not loaded (local or remote)
n Connection interrupted
(e.g. cable, CPU turned off, CP in STOP)
1 4 Error in receive buffer pointer RD_i with respect to the
length or the data type.
1 10 Access to local application memory not possible (e.g.
access to deleted DB).
1 12 The call to the FB/SFB
n contains an instance DB that does not belong to the
FB/SFB 9
n contains a global DB instead of an instance DB
n could not locate an instance DB
(load a new instance DB from the PG)
1 18 R_ID already exists in the connection ID.
1 19 The respective FB/SFB USEND transmits data quicker
than FB/SFB URCV can copy the data into the receive
buffers.
1 20 Not enough memory.
The data are received consistently if you remember the following points:
n Siemens S7-300 Communication:
After the status parameter NDR has changed to the value 1, you must immedi-
ately call FB 9 URCV again with the value 0 at EN_R. This ensures that the
receive area is not overwritten before you have evaluated it. Evaluate the receive
area (RD_1) completely before you call the block with the value 1 at control input
EN_R).
n Siemens S7-400 Communication:
After the status parameter NDR has changed to the value 1, there are new
receive data in your receive areas (RD_i). A new block call may cause these data
to be overwritten with new receive data. If you want to prevent this, you must call
SFB 9 URCV (such as with cyclic block processing) with the value 0 at EN_R until
you have finished processing the receive data.
Data consistency
VIPA SPEED7
Network Communication
Ethernet Communication > FB/SFB 9 - URCV - Uncoordinated data reception
HB00 | OPL_SP7 | Operation list | en | 18-30 157

Table of Contents

Related product manuals