VIPA SSM-BG41, Manual

Page: 150 / 286

Handling with VIPA data handling blocks Manual BG41/BG42/BG43
4-34 Rev. 99/49
Example: FB31 (RECEIVE ) by direct parametrizing:
:SPA FB31
NAME :RECEIVE
ADRE : KH F080
The address set by the DIL switches
SSNR : KF +1 Interface number 1,2,3
A-NR : KF +3 Order number (1...255)
ZTYP : KC DB Target type
DBNR : KY 0,5 DB no. by target type DB
BWNR : KY 0,20 Telegram filed from DW 20
MXBW : KF +100 Incoming telegrams may have a maximum length of 100 words
ANZW : MW 30 In this word the display word is filed
PAFE : MB 32 In this byte error messages in relation to parametrizing are
filed
NEUS : M 1.0 New start bit
Example: FB31 (RECEIVE ) by indirect parametrizing:
If the operands are to be indirectly transferred, it is possible in the following form. XX is to be
parametrized on the operand ZTYP. This is the identifier for indirect parametrizing. The DB
number, in which the operands lie, are to given on the operand DBNR. The data word number, from
where the operands lie, is to be given on the operand BWNR. The operands ADRE, SSNR, A-NR,
MXBW have in this case no meaning. The operands ANZW, NEUS and PAFE can not be indirectly
parametrized. They must still be given directly to the formal operands.
:SPA FB31
NAME :RECEIVE
ADRE : KH 0000
Irrelevant
SSNR : KF +0 Irrelevant
A-NR : KF +0 Irrelevant
ZTYP : KC XX Identifier: indirect parametrizing
DBNR : KY 0,6 Parameter lies in DB 6
BWNR : KY 0,50 from DW 50
MXBW : KF +0 Irrelevant
ANZW : MW 30 The display word is filed in this word
PAFE : MB 32 Error messages in relation to parametrizing are filed under
this byte
NEUS : M 1.0 New start bit
Allocation of the given DBs:
DB 6:
DW 50 KH ADRE
DW 51 KF SSNR
DW 52 KF A-NR
DW 53 KC ZTYP
DW 54 KY DBNR
DW 55 KY BWNR
DW 56 KF MXBW