Section 2:
Configuration
Revision 1.0a
29
© 2006 Intuicom, Inc.
In typical applications this approach works very well, however there are scenarios where
you want to force communications to follow a specific path. For example, you may want
to ensure that two repeaters in the system are communicating in series instead of in
parallel, or it may be desirable to force slaves to communicate to specific repeaters for
load balancing purposes.
There are two components to the Subnet ID:
Rcv Subnet ID
. This setting identifies who a repeater or slave will listen to.
Xmit Subnet ID
. This setting identifies the sub network this device transmits on,
and in turn which devices will listen to it.
The Xmit Subnet ID parameter is
relevant for multipoint repeaters only.
To disable the Subnet ID both Rcv Subnet ID and Xmit Subnet ID should be set to ‘F’.
Note: The Subnet ID settings are irrelevant for the Master.
Note: The Master always transmits on Subnet ID=0, regardless of the setting. To force
communications directly through the Master the Slave or Repeater's Rcv SubnetID must
be set to 0.
Note: The Subnet ID works only in Multipoint Networks using NetworkID.
Note: In typical multipoint networks the Freq Key must be at the same setting for all
transceivers. If the SubnetID is used the sub network may be set to a different Freq Key.
Note: If both Rcv SubnetID and Xmit SubnetID are set to 0 the SubnetID will show
Roaming in the menu. This setting will allow a mobile slave to roam from subnet to
subnet within a network.
Figure 2-15
below depicts a point-to-multipoint network in which the Subnet ID is used
to force communications along specific paths. In this example Repeater1
must
talk
directly to the Master, and Repeater2
must
talk directly to Repeater1. Communications
for Slaves 1, 2, and 3 are forced along the direction of the solid lines, and Slave4 may
link to the first master or repeater it hears.