7 Distributed Event Binding Protocol / Redundancy Binding Communication
7.1 General
The Distributed Event Binding protocol is a proprietary protocol for fast time stamped event based data transfer directly from one
Brodersen RTU runtime to another. The Binding protocol is communicating directly from one RTU32 to another RTU32 in a LAN/WAN
network. It can run regardless of any other application. In a network with several Brodersen RTUs you can use the Global Binding Editor
to bind any global declared variables together. Binding can be used between any type of RTU32 Series product and even with STRATON
PC runtimes (soft PLCs).
Redundancy Binding is used in a redundancy network connection using 2-6 separate network segments. Both the unit publishing
variables (producer) and the unit subscribing variables (consumer) has to be equipped with 2-6 Ethernet network interfaces. Each
network connection must be setup on the units as separate network segments using different TCP/IP subnet masks. The compiler also
takes care of handling the sorting out of timing issues of any changes in values. This means that you on the subscriber side always will
get the correct value. The first received event will be reported at the subscriber side and the same event with the same time stamp
received on other network interfaces will be ignored.
7.2 Network settings in RTU32 (redundancy binding)
If you want to run redundancy Binding using the RTU32 you must configure all Ethernet interfaces. No additional settings are necessary
as the networks is seen as direct accessible parallel networks. Routing to the networks is done as default. If you ping an address on any
of the one of selected network segments, the ping request will find its way to the correct segment automatically.
7.3 Procedure for setting up binding/redundancy binding in WorkSuite
You need to configure all the RTU32 (and PCs with STRATON runtime) before starting to bind (link) I/Os together. I/Os and variables to
bind must be declared as Global variables. Use variable naming that makes sense for you. You could for example call all input variables
published for binding BindInput_DI0 and BindInput_DI1, and you could call outputs BindOutput_DO0. After defining the variables for
use in both comms direction for all relevant projects (RTUs), you must start the Global Binding Editor (find it in WorkSuite under the
Tools menu). Note that in WorkSuite you will need all Projects used for binding in the same project list.
You assign the IP addresses to each project. If using redundancy Binding, you add up to maximum 6 x “IP:TCP port” to the address of
the RTU. If two network interfaces are used for binding (dual redundant binding), the two IP addresses are defined with a separator “|”
– like 192.168.1.222:9000|192.168.2.21:9000”
As shown above, the OUTPUTS from Publishing RTU project are linked to the subscribing RTUs INPUTS.
After configuration you download ALL projects to the relevant RTUs. Use the “Download All Projects…” in the Project menu,
To Next Page
Loading...
Need help?
General