
I/O Mapping an I/OBus Network with Concept
Supporting an I/O Map for an I/OBus Network
Introduction | Three Processor Adapters have an I/OBus communication port that enables them |
| to control and communicate with other network slave I/O: |
| λ 171 CCS 760 00 |
| λ 171 CCC 760 10 |
| λ 171 CCC 960 20 |
| λ 171 CCC 960 30 |
| If you are using I/OBus to control network I/O, you need to write an I/O Map in your |
| configuration. This section describes the configuration parameters required to |
| support an I/O Map for I/OBus. |
I/O Map |
|
Be sure that you have reserved enough words for I/O mapping to support your I/O | |
Reserved Words | Bus network. The default setting is 144 words. To estimate the number of words |
| you require, allow: |
λ16 words for overhead
λ10 words/module on the network (including both the local and the network I/O)
Allot sufficient memory to completely I/O Map your network, while preserving as much user memory as possible for your application program.
Number of | Be sure that the number of segments is set to 2. If you have changed this setting to |
Segments | 1, you will not be able to support an I/OBus network. |
Next Step |
|
Once you are sure that your Configuration Overview parameters are set properly, | |
| you can access an I/O Map screen for an I/OBus network. |
|
|
362 | 870 USE 101 10 V.2 |