RDC from Digital Barriers is a revolutionary unattended ground sensor (UGS) system for intrusion detection and remote asset protection. It combines an innovative rapid deployment design, exceptional power efficiency, accurate target detection/classification and intelligent mesh-based two-way wireless networking. RDC Staging Tool is a Windows software application for creating RDC networks which sets the frequency and network ID so that all nodes in a network can communicate. It can also be used for adding nodes to an existing network or checking that nodes are working correctly before deploying them.

This document provides detailed instructions for using RDC Staging Tool. It should be read in conjunction with:

Often RDC networks will be provided as ‘kits’ with the frequency and network ID of each node already set, so the Nodes will connect as soon as power is applied. However, if this is not the case, then the Staging Tool can be used to set the frequency and network ID.
​
The frequency selected will be dependent upon the radio regulations that apply and also whether there are other devices using the same frequency band in the vicinity. There are two frequency bands:

The majority of the world has similar regulations to either Europe or the U.S. The Staging Tool provides assistance in selecting the correct band and frequency. However, it is necessary for the user to be aware of the relevant radio regulations in the country of operation.
​
For some defence and security applications, the national radio regulations may not apply.
​
The network ID allows multiple networks to operate in the same vicinity, even on the same frequency. However, it is advisable to use separate frequencies for each network with a minimum 400kHz separation to avoid congestion of the radio channel.
​
The Staging Tool has a ‘wizard-style’ user interface which guides the user through the Staging process.
​
​The Staging Tool does not set the detection configuration parameters of a Sensor Node. These are set using RDC Config. It also does not over-write previously set detection configuration parameters.
​
The Staging Tool can be used to create networks of either UM or UM+ Nodes or combinations of UM and UM+ Nodes. However, it is recommended to use only one type of Node in each network.

​

The Staging Tool can be used for several purposes:

For all of these uses, a Master Node should be connected to the PC/laptop on which the Staging Tool has been installed using the Master Node USB cable supplied.

When the Staging Tool is started, the user will be asked to supply a ‘Job reference’ and a ‘Description’. If there are several RDC networks to be configured, then set up of these networks is known as a ‘Job’. The ‘Job reference’ and ‘Description fields do not have to be filled in, but will provide a record of the details of the Job and network when the Staging Tool log file is created:

The next step is to select the appropriate frequency band from the drop-down list:

The Staging Tool then attempts to connect to a Master Node. It reports the Master Node’s current network ID, band and frequency (Figure 3). This can be useful when adding a node to an existing network because it is necessary to know the network’s radio parameters in order to set them correctly.

The default ‘Ultramesh Network ID’ shown is read from the Master Node. It is always the same as the Master Node ID (printed on the metal label). It is recommended that the Master Node ID is used as the network’s ID. Since the Master Node is unique, this ensures that the network ID is unique. Networks with the same ID in the same vicinity on the same frequency will have very poor radio performance and will potentially connect incorrectly.

It is possible, however, to set the network ID to any hexadecimal value from 0001 to FFFE. Pressing ‘Validate’ will confirm that the ID entered is valid. For instance, it might be necessary to set the network ID to something other than the default value when adding a Node to a network. A spare Master Node may be used to set the frequency and network ID of an operational network which already has an embedded Master Node:

The next step is to select the frequency. If multiple networks are being configured as part of the same Job, frequencies already allocated to networks within the same Job will be deleted from the drop-down list to avoid them being reused:

The user must provide the number of Nodes for which frequency and network ID is to be set. Unless the minimum number of Nodes specified are seen by the Staging Tool it will not move to the next step. This avoids user error and also identifies if Nodes have failed to start when power is applied. This may happen if the user failed to put a battery in the auger or there was a problem with the battery connection:

When power is applied to each Node they will appear in the Node list if they have started correctly. Note that UM Node (version 6769) may be reported as Node type: ‘Unknown’. The Node type of UM+ Nodes (version 8655) should be shown correctly:

The final stage is a check of each Node’s configuration, which is reported as status ‘configuring’.
​
UM nodes may take up to 3 mins to report that they have been configured correctly, whereas UM+ Nodes will report this almost immediately. Mixtures of UM and UM+ Nodes may also take 3 mins for all Nodes to report they are configured correctly.
​
Note that the detection parameters are not set and any previous detection parameter configuration is left unchanged:
​

The final window allows the user to export the results as a log file. They can then choose from one of three options:

​