![background image](http://html1.mh-extra.com/html/abb/ac-800m/ac-800m_library-object-style-manual_3371230038.webp)
Connections
Section 3 Parameter Interface
38
3BSE042835-600
Point-to-Point Connection using ControlConnection Data Type
In
Out
A
In
Out
B
Forward
Backward
Direction
A natural way to represent the main signal flow of Control Modules is by structured
connections. In this way a single connection, which preferably is done graphically,
handles the main signal flow between two adjacent objects.
Bidirectional connections should have components for each direction. The
substructures are preferably named Forward and Backward, but other names may be
used if they better fit the context they are used in, for example Previous and Next,
Upstream and Downstream, etc. This makes it easier for the programmer to handle
communication between objects. It also supports data communication over task and
system borders, since it is clear what components are sent in each direction.
Figure 4. Point-to-point connection between two objects. The node names reflect the
main direction of the signal. The blow-up shows in principle data flow.
In each of the directional substructures, for example Forward and Backward, a
component Connected should exist. All objects shall set the Connected component
true in the direction-component they are allowed writing to. The Connected
component can then be checked by the object on the other side and determine if
there is a connected object or not. This is useful when an object connection is
optional, thus may not be connected.
Point-to-Point Connection Using Reverse Attribute
In bi-directional data types, the components used to transfer data in backward
direction must have the
reverse
attribute. Otherwise the data type cannot be used for
parameters with direction defined.
The
reverse
components must be grouped in consecutive order at the end of the
data type. They can also be put in a sub structure at the end of the data type.
Summary of Contents for AC 800M
Page 2: ......
Page 3: ...AC 800M Library Object Style Guide System Version 6 0...
Page 12: ...Related Documentation About This User Manual 12 3BSE042835 600...
Page 18: ...Naming Convention Section 1 Libraries 18 3BSE042835 600...
Page 108: ...SIL Mark Restrictions Section 6 Program Code Issues 108 3BSE042835 600...
Page 116: ...Standard Library Parameters Appendix A Names and Abbreviations 116 3BSE042835 600...
Page 119: ......