YASKAWA VIPA SPEED7 - Page 887

Value Block size Value Block size
0 Default (64byte) 4 128byte
1 16byte 5 256byte
2 32byte 6 512byte
3 64byte 255 512byte
n Parameter type: Integer
n Convenient range: 0 ... 255
Error indication at parameterization defects
n This "BYTE" (output, marker) is set if the block detects a parameterization error, e.g.
interface (plug-in) not detected or a non-valid parameterization of QUANF/ZANF.
– Parameter type: Byte
– Convenient range: AB 0 ... AB127, MB 0...MB 255
16.1.2.2 Parameter transfer
A handling block may be parameterized directly or indirectly. Only the "PAFE" parameter
must always been set directly. When using the direct parameterization, the handling block
works off the parameters given immediately with the block call. When using the indirect
parameterization, the handling block gets only pointers per block parameters. These are
pointing to other parameter fields (data blocks or data words). The parameters SSNR,
ANR, IND and BLGR are of the type "integer", so you may parameterize them indirectly.
CALL SFC 230
SSNR:=0
ANR :=3
IND :=0
QANF:=P#A 0.0 BYTE 16
PAFE:=MB79
ANZW:=MD44
CALL SFC 230
SSNR:=MW10
ANR :=MW12
IND :=MW14
QANF:=P#DB10.DBX0.0 BYTE 16
PAFE:=MB80
ANZW:=MD48
Please note that you have to load the bit memory words with the corresponding values
before.
16.1.2.3 Source res. destination definition
You have the possibility to set the entries for source, destination and ANZW directly or
store it indirectly in a block to which the QANF / ZANF res. ANZW pointer points. The
parameter IND is the switch criterion between direct and indirect parameterization.
PAFE
Direct/indirect parameteri-
zation
Example
Direct parameter transfer
Indirect parameter transfer
Overview
VIPA SPEED7
System Blocks
Fetch/Write Communication > SFC 230 ... 238 - Page frame communication
HB00 | OPL_SP7 | Operation list | en | 18-30 887