Handling with VIPA data handling blocks Manual BG41/BG42/BG43
4-82 Rev. 99/49
Coordination flag:
The protocol 3964(R) supports the usage of a coordination flag. This flag is used for blocking
access to the source area or to allow the reading of the source area. The coordination flag is given by
the sender of the request telegram in the telegram header. On receiving a new request telegram the
data handling block SEND-ALL examines, if the parametrized flag in the telegram header is set. If
this is the case, reading access is denied. The sender receives a response telegram with the
information, that the area for the job was blocked.
If the given flag is at 0, the requested data is sent. If it is at 1, the reading access is denied.
If, for some reason, the data can not be sent to the receiver, he receives a response telegram with a
corresponding error number. The user is supplied with this error number in the display word.
Error codes of the response telegrams:
12 Invalid bit number in the coordination flags given (allowed 0...7)
or invalid byte number in the coordination flags given (allowed 0...199)
16 Invalid area type, from where the data is requested
(allowed DB,DX,AB,EB,MB,T,Z)
20 Invalid area, from where the data is to be read
(i.e. e.g. Block is not available or DB too short or access at MD255)
50 Area is blocked by coordination flag (Flag = 1)
The data handling block examines the parametrized values at the following limits:
ADRE F080...F1FC
SSNR 1...2 (3)
PAFE not examined
NEUS not examined
Example: FB22, (SEND-ALL)
:
:SPA FB22
NAME :SEND-ALL
ADRE : KH F080 Address set with DIL switches
SSNR : KF +1 Interface number 1,2 (3)
PAFE : MB 32 Error messages in relation to parametrizing are filed in this
byte
NEUS : M 1.0 New start bit
To Next Page
Loading...
