110
Exchanging Data with the CPU Unit Section 5-1
Using the CX-Integrator, set the Registered Slave Participation Monitoring
Time (1 to 600 s; default: 10 s at baud rate of other than 93.75 kbit/s and 30 s
at baud rate of 93.75 kbit/s) under Detailed Settings in the Master General
Tab Page, and then downloading the parameters to the CompoNet Master
Unit. This setting is disabled when the Registered Slave Participation Standby
Mode is enabled.
Registered Slave
Participation Standby
Mode
Registered Slave Participation Standby Mode can be used to not start remote
I/O communications until all registered Slave Units are participating in the net-
work (i.e., while the All Registered Slaves Participating Flag is OFF). Remote
I/O communications will start when the All Registered Slaves Participating
Flag turns ON. Using this mode will make it faster for all Slave Units to partici-
pate in the network.
Remote I/O communications will not start, however, unless all registered
Slave Units are participating.
When this mode is used, Registered Slave Unit Participation Monitoring Time
setting (including the default value of 10 s) is disabled.
On the CX-Integrator, go to the Detailed Settings on the Master General Tab
Page, and enable the Registered Slave Participation Standby Mode. Down-
load the parameters to the CompoNet Master Unit.
This function is enabled only in Registration Table Enable Mode, i.e., when
SW4 (REGS) is turned ON on the Master Unit when the power is turned ON,
and the Registration Table data is normal. It can be used with any communi-
cations mode number.
Slave Unit Address
Duplication Error
In any of the following cases, a Slave Unit address duplication error will occur
and the Address Duplication Error Flag (status bit 03) will turn ON for the
Slave Unit that joined the network later. The NS indicator on the front of the
Master Unit will flash red and the seven-segment display will show d0.
Remote I/O communications will stop.
• There is already a Slave Unit for which the same node address is set.
(For example, both Slave Units are set for node address N.)
Note An address duplication error will occur if the same node address is
set for two Slave Units in the same allocation area. This applies
only if both are Input Slave Units or both are Output Slave Units.
• Different node addresses are set, but the allocated memory areas over-
lap.
(For example, a Slave Unit set for node address 0 has 24 inputs and a
Slave Unit set for node address 1 has 16 inputs, in which case both Slave
Units will be set to use the Input 1 Area.)
Note As long as the allocated areas themselves are not duplicated be-
tween nodes, Slave Units set for different node addresses can be
allocated the Input Area and Output Area at the same node ad-
dress area. (For example, a Slave Unit set for node address 1 can
be allocated 16 outputs in the Output 1 Area, while an Expansion
Slave Unit set for node address 0 can be allocated 16 inputs in the
Input 1 Area.)
• A Slave Unit was removed and then a Slave Unit of a different class
started participating at the same node address.
Illegal Configuration
Error
If the permitted number of Repeater Unit segments is exceeded, the NS indi-
cator on the front of the Master Unit will flash red and the seven-segment dis-
play will show E5.
To Next Page
Loading...
