
Using the Ethernet Port
Network Design Considerations, Continued
I/O Networks | In an Ethernet I/O network architecture, an M1 Processor Adapter is used to control |
| Momentum I/O points equipped with an Ethernet Communication Adapter or other |
| Modbus over TCP/IP |
| devices should be isolated not only from MIS data traffic, but also from unrelated |
| communication between other control devices. |
| You may isolate communication by creating a separate network or by using |
| switches. |
Supervisory |
|
In a supervisory architecture, several intelligent processing devices share system | |
Networks | data with each other. Many kinds of devices may be part of the network. You should |
| be aware of each device’s requirement for access to the network and of the impact |
| each device will have on the timing of your network communication. |
Combined |
|
If your system requires both supervisory and I/O handling architectures, one | |
Supervisory and | solution is to use the I/OBus capabilities of the 171 CCC 960 20 Processor Adapter |
I/O Handling | for the I/O network and the Ethernet capabilities for the supervisory network. |
| If you intend to use Ethernet to handle both functions, use switches to isolate the |
| network traffic and supply additional buffering of network packets. |
Concurrent |
|
A maximum of 96 devices may be communicating with the Processor Adapter via | |
Communication | the Ethernet at any one time. This |
| λ up to 2 programming panels (one must be in monitor mode) |
| λ up to 14 general purpose Modbus server paths |
| λ up to 16 MSTR elements which support Modbus read, write or read/write |
| commands |
| λ up to 64 cyclic configured data slave paths |
|
|
| Continued on next page |
870 USE 101 10 V..2 | 145 |