Peer to peer configuration example 3, Figure 14 example 3 peer to peer configuration, Trusted – Rockwell Automation T8017 Trusted Peer to Peer Communications User Manual
Page 37: Communication software package t8017

Trusted
TM
Communication Software Package T8017
Issue 10 Mar 08
PD-T8017
37
2.5. Peer to Peer Configuration Example 3
Processor
Module
Comm
Interface
Module
Comm
Interface
Module
Comm
Interface
Module
Comm
Interface
Module
Processor
Module
Comm
Interface
Module
Comm
Interface
Module
Processor
Module
Processor
Module
Comm
Interface
Module
Comm
Interface
Module
Processor
Module
Comm
Interface
Module
Comm
Interface
Module
Controller 1
Controller 3
Controller 2
Controller 5
Controller 4
Peer
Network 1
Peer
Network 2
Subnet 1
Subnet 2
Subnet 1
Subnet 2
10.10.1.1
10.10.1.2
10.10.1.4
10.10.1.3
10.10.2.1
10.10.2.4
10.10.3.4
10.10.2.3
10.10.2.2
10.10.4.4
10.10.3.5
10.10.4.5
239.255.1.1*
239.255.1.1*
239.255.1.1*
239.255.2.1*
239.255.2.1*
239.255.2.1*
239.255.1.1 & 239.255.2.1
are Multicast addresses
Figure 14 Example 3 Peer to Peer Configuration.
Figure 14 shows an example configuration for a system using 5 controllers connected together
using two separate peer to peer networks, each having dual physical network paths.
In this example, Controller 4 will be the master of network 1 subnet 1 and network 2 subnet 1.
Controller 1 will be the master of network 1 subnet 2 and Controller 5 will be the master of
network 2 subnet 2.
• 16 digital points will be sent from controller 3 to controllers 1, 2 & 4 via a multicast
configuration.
• 16 analogue points will be sent from controller 1 to controller 2.
• A separate set of 16 analogue values will be sent from controller 1 to controller 3.
• 16 digital values will be sent from controller 2 to controller 5. Controller 5 is on a
different peer network than controller 2, therefore to achieve the data transfer 16
values will be sent from controller 2 to controller 4 and the application in controller 4
will connect the input signals to an output board which in turn will send the data to
controller 5.