RDC from Digital Barriers is a revolutionary unattended ground sensor (UGS) system for monitoring and securing wide-areas, remote assets and extended perimeters.
It combines an innovative rapid deployment design, exceptional power efficiency, accurate target detection/classification and intelligent mesh-based wireless networking. RDC Deploy is software supplied with RDC Multi-hop and RDC UltraMesh systems. It is used with a Master Node during the deployment of a RDC system to assist in an effective deployment.
This document provides detailed instructions for using RDC Deploy. It should be read in conjunction with:
RDC Setup and Deployment User Guide – this explains how to deploy and setup an RDC sensor network
Section 1: Overview of the application
RDC Deploy is a measurement tool that is used to provide information relating to the deployment of Sensor Nodes or ASNs within an RDC system. This document covers RDC Deploy version 3.0.1. RDC Deploy is used with a Master Node that is configured by the software to operate in a ‘listen’ mode. The Master Node then does not interact with the RDC network but listens to messages transmitted. When using the listening Master Node there must also be another Master Node in the network which would normally be connected to a separate computer running RDC Control. To avoid confusion this is referred to as the network Master Node. RDC Deploy has several distinct uses:
Signal strength: the strength of the RF signal from other Nodes. This is useful for determining whether the position of a Sensor Node (or ASN) will have good communications to other Nodes in the network.
GPS: the GPS co-ordinates of a Node location. A Node ID can be added to this data and then stored in a file that can be later used in RDC Control to plot the locations of the Nodes in the network on a map. Note that a USB GPS receiver must be connected to the laptop or tablet for this function to operate.
Events: reports any events from Nodes that it can receive a signal from. This can be useful for testing the detection performance of a RDC network or for close quarters monitoring of the network.
Background: reports the seismic background noise from Nodes that it can receive a signal from. This is useful for determining the likely detection conditions. In seismically noisy environments it may be difficult to detect people or vehicles or there may be a high false alarm rate.
Frequency Scan: performs a frequency scan of each band (865.3-868MHz and 903-927MHz). This can be useful for identifying any other RF activity in the vicinity that may affect communications performance.
1.1 Installation
RDC Deploy should be installed on a Windows laptop/tablet. A small ruggedised device will allow the device to be carried around the deployment site with a Master Node. To install the software, insert the supplied USB drive and navigate to it – then launch ‘RDC Deploy 3.0.1.XXXX setup.exe’ and follow the on-screen prompts.
1.2 Node firmware capabilities
All the functions described in this document are available with RDC UltraMesh. Some functions are not available with RDC Multi-hop and these are: Events, Background and Frequency Scan. The tabs for these functions are not shown when connected to a Master Node that is not on RDC UltraMesh firmware. RDC UltraMesh nodes are denoted by ‘UM’ on the brass place, while Multi-hop nodes are denoted by ‘MH’.
1.3 Equipment required
RDC Master Node (Multi-hop or UltraMesh)
Master Node USB cable
Windows Vista/7/8 laptop or tablet (ideally rugged such as Getac or Panasonic Toughbook/Toughpad)
USB GPS receiver (Globalsat BU-353 recommended)
1.4 Launch RDC Deploy
RDC Deploy can be launched by double-clicking on the shortcut on the desktop or by clicking on the shortcut in the start menu (All programs/Digital Barriers/RDC Deploy 3.0.1.XXXX)
Section 2: Starting and RDC Deploy session
The RDC Master Node should be connected to the laptop or tablet using the USB cable supplied. A session is defined as the period of time where RDC Deploy is connected to the Master Node.
2.1 Starting the session
To start a new session, click on the ‘Connect’ button. The Session configuration dialog box is shown:
In the session configuration dialog box, the type of connection to the Master Node must be selected. Select the ‘Serial’ option and the appropriate COM port. Note, do not use the WiFi option.
2.2 Initial communications with the Master Node
When the session is started, RDC Deploy sends messages to the Master Node to check its status. During this communication, RDC Deploy displays a ‘please wait’ dialog box with the option to abort. If RDC Deploy is unable to communicate with the Master Node, a ‘communication error’ message box is displayed. Communication can fail in the following cases:
If the wrong serial port is selected
If the Master Node is not connected to the serial cable
If the serial cable is not connected to the laptop/tablet
2.3 Stopping the session
To stop the session, click on the ‘disconnect’ button.
The session is automatically stopped when RDC Deploy is closed.
Section 3: Setting the role and configuration
When first used, the role of the Master Node is likely to be incorrect for use with the RDC Deploy software. When the session starts, the RDC Deploy software will generate a dialogue box stating that the Node has the wrong role – and the role will also be shown as ‘MH Master’ in the ‘Radio config’ pane.
It is possible to ‘Get’ or ‘Set’ the configuration. By pressing ‘Set’ the ‘Set Config’ dialogue box appears:
By pressing ‘OK’ the role will be changed so that the Master Node role has changed to ‘listening’. The ‘network ID’, ‘Band’ and ‘Frequency’ can be set. They should all be set to the same as the RDC network that is to be deployed. Note that RDC Deploy reports on Nodes that have any network ID when used with Ultramesh nodes but only those with the specified ID with Multi-hop nodes.
Section 4: Using the ‘Signal strength measurement’ function
RDC Deploy reports on the strength of the RF signal from other Nodes. This is useful for determining whether the position identified for a Sensor Node (or ASN) is likely to provide good communications to other Nodes in the network. To use the Signal Strength facility it is necessary to place the listening Master Node exactly where the Sensor Node (or ASN) will be located (using the ground spike) at the same height as the Sensor Node (or ASN). Selecting the Signal Strength tab will show a list of Nodes that can be received and their signal strength.
The list is updated every 5 seconds if the RDC network is in Commission mode and every 40 seconds if the RDC Network is in Normal Mode. The instructions for using the Signal Strength measurement tool for deploying nodes are contained in the RDC UltraMesh and Deployment User Guide but repeated here.
Carry the listening Master Node and laptop/tablet to the Node location closest to the network Master Node and secure it in the ground. Press the ‘Signal Strength’ tab. If it can see the network Master Node it will appear in the list. Ignore any other Nodes that appear in the list.
If the network Master Node cannot be seen or signal strength is less than 5, a Relay Node is required, or the network Master Node will need to be moved or raised. If a Relay Node is to be deployed it should also be placed as high as possible. Place the listening Master Node at the identified relay location and re-check the signal strength from the network Master Node. Further Relay Nodes may be required if the network Master Node is a long way from the detection area and/or the network Master Node and/or Relay Nodes are also on the ground. Note that Relay Nodes are SNs (or ASNs) with detection turned off.
If relay nodes are required it is advisable to use two for each hop at different locations to provide redundant paths for the communications between SNs (or ASNs) and the network Master Node. When the listening Master Node is at the SN (or ASN) location closest to the network relay nodes it must have a signal from both relay nodes with a strength not less than 5. 4. Continue deployment moving further from the network Master Node. At each SN (or ASN) location the signal strength must not be less than 5 to at least two other SNs (or ASNs) or Relay Nodes.
Note that during a deployment it is often the case that there will be a bag or case containing other SNs (or ASNs) that are powered on close to the user. If these have previously had a connection to the network they will appear in the list of Nodes. It is important that only the Nodes that have been deployed are considered when deciding whether a proposed Node location will provide a reliable connection to the RDC network.
Section 5: Using the ‘GPS positioning’ function
RDC Deploy reports the GPS co-ordinates of a Node location. A Node ID can be added to this data and then stored in a file that can be later used in RDC Control to plot the locations of all of the Nodes in the network. Note that a USB GPS receiver must be connected to the laptop or tablet for this to work. Install a driver if required by the GPS receiver then connect RDC Deploy to the GPS receiver by pressing the ‘Connect’ button.
Select the COM port and the Baud rate for the GPS receiver.
When the GPS receiver has obtained a fix, RDC Deploy will report the current location and the ‘Add’ and ‘Clear’ buttons will become available.
The GPS location of a Node is usually recorded after a Node has been deployed. Place the RDC Deploy Probe close to this Node and press the ‘Add’ button. A list of Node IDs will be made available. Select the ID of the nearby Node. When the list of locations for all Nodes has been compiled, the list can be exported as a KML file.
The KML file can be used in RDC Control (see RDC Control User Guide for details). It can also be used in Google Earth or Google Maps to show the positions of the Nodes. Note that using the ‘Options’ button, the GPS co-ordinates can be selected as one of the following units: degrees, minutes and seconds or decimal degrees.
Section 6 Using the ‘Events reporting’ function
RDC Deploy reports any events from Nodes that the listening Master Node can receive a signal from. This can be useful for testing the detection performance of an RDC Network or for close quarters monitoring of the network. The Events are only reported for those Nodes from which the listening Master Node can receive a signal and those which are relayed by those nodes from which it can receive a signal. It does not report the events reported by all the Nodes in the network. The Events reporting is only available with RDC UltraMesh Nodes – the tab is not shown when connected to a Multi-hop Master Node.
Event Message | ICON (Same as in RDC Control) | NOTES |
Person | 
| Detection of a person walking or running. May also be triggered by a person crawling. 2-3 people walking will generate person alerts. Large groups walking at the same time may also generate vehicle alerts if enabled. |
Vehicle | 
| Detection of a vehicle. Vehicle size ranges from motorbike to truck. The detection range is usually greater for large vehicles. Detection range will also be affected by the road surface. Vehicles on rough road surfaces can usually be detected further than those on a smooth road. |
Digging | 
| Detection of digging activity with a shovel or pick axe. (Only available with RDC UltraMesh nodes.) |
External sensor 1 event | 
| Generated by an external sensor (e.g. PIR) connected to an Alternative Sensor Node (ASN). |
External sensor 2 event | 
| Generated by an external sensor (e.g. PIR) connected to an Alternative Sensor Node (ASN). |
Large seismic event | 
| Generated when there is an unusually large seismic event such as a Node being moved. (Only available with RDC UltraMesh nodes). |
Loss of comms | 
| Generated when 3 'alive' messages in succession have not been received by the Master Node from a Sensor Node. (Only available with RDC UltraMesh nodes). |
Section 7: Using the ‘Background noise’ function
RDC Deploy reports the seismic background noise from nodes that the listening Master Node can receive a signal from. The ‘Background’ window provides information about the likely detection conditions. Three environmental factors will typically affect the detection performance of RDC:
Nature of the stimulus i.e. type of stimulus (person or vehicle) and its weight, movement and speed
The ground conditions: detection is greatly affected by the type of ground (detection in sandy, rocky ground is often very good, while detection in chalk is often very poor)
Background noise: there are various environmental and man-made factors that can affect detection performance and false alarms (rain, wind, vehicles on nearby roads, heavy machinery, nearby aircraft)
The ‘Background’ window indicates whether background noise is likely to have on detection performance, shown as a bar chart. A full green bar indicates that the background noise is low and therefore detection conditions are likely to be good for that particular ground type and stimulus. An almost empty red chart for a node indicates that the detection conditions are likely to be very poor due to a high level of background noise.
The Background is only reported for those nodes from which the listening Master Node can receive a signal and those which are relayed by those nodes from it can receive. It does not report the events reported by all the nodes in the network.
The Background function is not available with RDC Multi-hop nodes.
Section 8: Using the ‘Frequency scan’ function
RDC Deploy can perform a frequency scan of each frequency band (865.3-868MHz and 903-927MHz). This can be useful for identifying whether there is other RF activity in the vicinity that may affect the communications performance of the RDC network.
To start the frequency scan press the ‘Scan’ button. The frequency scan repeats until the ‘Stop’ button is pressed or the user switches to another window. The blue bar shows the average signal measured and the yellow bar shows the peak signal energy measured since the scan was started. To refresh the display press ‘Stop’ and then ‘Scan’.
Note that if this is used with a live RDC network it will detect the network transmissions. Due to the wide bandwidth of the receiver (approx. 1MHz) they will appear in the graph +/-500kHz from the network centre frequency. For example if a network has been set to 866.3MHz there will be signals appearing in the chart from 865.8 to 866.8MHz.