CompoBus/D System Startup | Chapter 4 | |
|
|
|
•Slave remote I/O allocations providing the number of I/O words allocated to and the node address set for each Slave.
•Communications parameters providing the initial remote I/O communications status and the commu- nications cycle time settings.
HScan List Application
A scan list is not required for a Network with only one Master Unit and remote I/O that is allocated ac- cording to the fixed settings. The scan list is necessary, however, in the following cases.
•To confirm the increase or decrease of Slaves on the communications line, and to detect errors in a Network where the number of Slaves has increased or decreased, it is necessary to record the system status.
•For free allocation of remote I/O, it is necessary to record the number of I/O words allocated to each Slave.
•When using multiple Master Units to exchange information with the SYSMAC PC (CPU Unit), it is nec- essary for each Master Unit to record the node addresses for each Slave.
HCreating Scan Lists
DFixed Remote I/O Allocations
A scan list can be created by turning ON the Enable Scan List software switch when the CPU Unit is in PROGRAM mode, when communications are active and the scan list is disabled. All Slaves that are participating normally in the Network will be registered in the scan list.
DFree Remote I/O Allocations
The user creates the scan list using the Configurator and then registers it in the Master Unit. Settings for all Masters and Slaves participating normally in the Network are used as a basis for creating the scan list.
Scan List Enabled
Remote I/O communications
Scan list enabled
Fixed allocations
Scan list disabled
Free allocations |
| Scan list enabled |
|
Scan List Disabled
Scan list
Slave I/O allocations
Communications pa- rameters
Registered using | Fixed allocations | ||
software switch. |
| All Slaves participating | |
|
|
| |
|
|
| normally in the Network. |
|
|
|
|
|
|
| Free allocations |
|
|
| |
|
|
| |
|
|
|
|
|
|
| Set as required using |
|
|
| the Configurator. |
Registered as scan |
| ||
|
| ||
list in the Master Unit. |
|
Fixed allocations
All Slaves.
Note The scan lists created with the Configurator will be required again for registration in the Master Unit if the Master Unit is ever set to disable the scan list or if the Master Unit is replaced. Be sure to save any scan lists created with the Configurator as network files or master parameter files.