
Configuring a Modbus Plus
Network in Concept with Peer
Cop
At a Glance
Purpose | Communication transactions over Modbus Plus are defined in Concept 2.1 by a | |||
| configuration tool called Peer Cop. This section uses examples to explain how to | |||
| use Peer Cop to configure the two types of network architecture: | |||
| λ An I/O network, where the Peer Cop of the CPU defines all the communication | |||
| transactions over the full network. |
|
|
|
| λ A supervisory network with two or more CPUs communicating with each other | |||
| and with additional devices on the network. |
|
| |
| Note: The 171 CCC 960 30 and 171 CCC 980 30 require Concept 2.2 with | |||
| service release 2. |
|
|
|
In This Chapter |
|
|
|
|
This chapter contains the following sections: |
|
|
| |
|
|
|
|
|
| For This Topic... | See Section... | On Page... |
|
|
|
|
|
|
| Getting Started | 1 | 370 |
|
|
|
|
|
|
| Using Modbus Plus to Handle I/O | 2 | 376 |
|
|
|
|
|
|
| Passing Supervisory Data over Modbus Plus | 3 | 387 |
|
|
|
|
|
|
|
|
|
|
|
870 USE 101 10 V.2 | 369 |