Communications configuring
System- and communication configuring D7-SYS - SIMADYN D 3-273
Edition 12.2003
Telegram structure of the connection name/data "!REC" from the
example:
Connection Virtual
connection
Data type Length
ANY_FB.X2 !REC.0003 R 4
ANY_FB.X1 !REC.0017 R 4
ANY_FB.X4/X5 !REC.0555 R 4
Total length = 12
bytes
Table 3-89 Telegram structure of the connection name/data "!REC"
Telegram structure of the connection name/data "!SEND" from the
example:
Connection Virtual
connection
Data type Length
ANY_FB.Y1 !SEND.0001 R 4
ANY_FB.Y3 !SEND.0004 R 4
ANY_FB.Y6 !SEND.0007 I 2
Total length = 10
bytes
Table 3-90 Telegram structure of the connection name/data "!SEND"
The structure of the configured telegram appears in similar form in the
CFC reference data in the view "cross-references, operands" or in the
CPU MAP listing (of the CFC) under "virtual connections". The
configuring can be checked using these lists.
NOTE
• The virtual connection names are known on the CPU. Data from
various function charts can be combined to form a telegram; however,
this is not possible from various CPUs.
• Data is processed by the receive/transmit blocks in their sampling
time. The sampling times of the blocks with virtual connections have
no influence on the telegram processing cycle.
• The configuring engineer is responsible in ensuring that the telegram
structure and length are compatible with that of the coupling partner
(refer to the chapter Mode of operation of the couplings). These
regulations are dependent on the secondary coupling. If an error
situation develops, the receive/transmit block disables itself and
makes an entry in the communications error field (e.g. PROFIBUS DP
or subrack coupling), or, communications are not established
(e.g. Industrial Ethernet).
To Next Page
Loading...
Need help?
General
