User Manual

Page 24 of 90
CCT24
development by removing the need to dynamically update a database that matches system addresses to
MAC addresses for each router and remote. The task of manually assigning system addresses to all
routers and remotes in a tree-routing system can be somewhat tedious. Contact RFM’s module technical
support group for the latest support tools for manual address assignment. Table 2.12.4.1 summarizes
radio parameter settings for each assignment method.
Dynamic Router Parent Assignment and Dynamic Remote System Address Assignment
Radio
InitialParentNwkID
StaticNetAddress
BaseModeNetID
Router
0xFF (join any parent)
0xFF (assigned by parent)
0x01 - 0x3F (router NwkID)
Remote
0xFF (join any parent)
0xFF(assigned by parent)
0xFF (not used by remote)
Manual Router Parent Address Assignment with Dynamic Remote System Address Assignment
Radio
InitialParentNwkID
StaticNetAddress
BaseModeNetID
Router
0x00 - 0x3F (specifies parent)
0xFF (assigned by parent)
0x01 - 0x3F (router NwkID)
Remote
0xFF (join any parent)
0xFF(assigned by parent)
0xFF (not used by remote)
Manual Router Parent and Remote System Address Assignment
Radio
InitialParentNwkID
StaticNetAddress
BaseModeNetID
Router
0x00 - 0x3F (specifies parent)
0x01 - 0x7E (sent to parent)
0x01 - 0x3F (router NwkID)
Remote
0x00 - 0x3F (specifies parent)
0x01 - 0x07 (sent to parent)
0xFF (not used by remote)
Table 2.12.4.1
Tree-routing networks can support peer-to-peer communications. However, the value of the P2PReply-
Timeout parameter (see Section 4.2.2) is interpreted differently in a tree-routing system compared to a
point-to-multipoint network. In a point-to-multipoint network, the P2PReplyTimeout parameter is in units of
hops. In tree-routing systems, this parameter is in units of hop pairs, due to the system routers alternating
between remote mode and base mode hop-by-hop. Referring to Figure 2.12.1.2, the minimum useable
value for peer-to-peer communications between Remote 1 and Remote 7 is determined as follows:
Route Segment
Required Hops
Remote R1 to Router R2
1
Router R2 to Base
1
Base Turn Around
1
Base to Router R5
1
Router R5 to Router R6
1
Router R6 to Remote R7
1
Remote R7 Reply Turn Around
1
Remote R7 to Router R6
1
Router R6 to Router R5
1
Router R5 to Base
1
Base Turn Around
1
Base to Router R2
1
Router R2 to Remote R1
1
Total
13
Table 2.12.4.2
The minimum number of hops required is 13, so the minimum P2PReplyTimeout parameter value would
be 7 hop pairs. This minimum value provides no tolerance for transmission retries. Selecting a value 50%
to 100% larger is recommended, in the range of 11 to 14 hop pairs.