Ubiquiti XR5 User Manual

WAVE RELAY

®

USER MANUAL

03EN009 (English) VERSION 3.1

Copyright 2010 - 2015 Persistent Systems, LLC. Wave Relay® is a registered trademark of Persistent Systems, LLC. All rights reserved. This User Manual contains information that is the sole property of Persistent Systems, LLC and may not be excerpted, summarized, copied or published without the written permission of Persistent Systems, LLC.

This User Manual applies to Wave Relay

®

Firmware Version 18.4.0+. For

information on older ﬁrmware versions, contact Persistent Systems.

Issued: April 2015

03EN009 (English)

INTRODUCTION

Headquartered in New York City since 2007, Persistent Systems LLC is a global communications technology company which develops, manufactures and integrates a patented and secure Mobile Ad Hoc Networking (MANET) system: Wave Relay®. The company’s industry leading R&D team has designed wireless networking protocols to support their cutting edge Wave Relay® system and technology. Wave Relay® is capable of running real-time data, video, voice and other applications under the most difﬁcult and unpredictable conditions. Their suite of products is ﬁeld proven and utilized in Commercial, Military, Government, Industrial, Agriculture, Mining, Oil and Gas, Robotics, and Unmanned System markets.

The Wave Relay® System is a peer-to-peer wireless MANET networking solution in which there is no master node. If any device fails, the rest of the devices continue to commu nicate using any remaining connectivity. By eliminating master nodes, gateways, access points, and central coordinators from the design, Wave Relay® delivers high levels of fault tolerance regardless of which nodes might fail. The system is designed to maximize the capacity of the radio frequency (RF) spectrum and to minimize the network overhead. While optimizing efﬁciency, Wave Relay® also implements tech niques that increase multicast reliability. The advanced multicast functionality allows the system to support both multicast voice and video over IP.

Wave Relay® is designed to maintain high bandwidth con nectivity among devices that are on the move. The system is scalable, enabling it to incorporate unlimited meshed devices into the wireless network, where the devices themselves form the communication infrastructure. Even in high ly dynamic environments, the system is able to maintain connectivity by rapidly re-routing data. Wave Relay® “self-form” and “self-heal” as nodes move unpredictably throughout the network, and Wave Relay® routing adapts in less than a second to ﬂuctuations in topology and other environmental conditions, continuously maximizing the communication performance. Due to Wave Relay’s® architecture, deploying the system and establishing the network are as easy as plugging in an Ethernet cable. The system operates on the data link layer (OSI Layer 2) rather than the network layer (Layer 3), facilitating plugand-play operation.

Wave Relay® is a seamless wireless networking system offering a dynamic and reliable solution for all mobile networking needs. Wave Relay® offers all of these capabilities in an inte grated and cost-effective package.

TABLE OF CONTENTS

Introduction 5

Persistent Systems, LLC 5

Device Hardware Introduction 8

Man Portable Unit — Gen4 10 Man Portable Unit — Gen3 Single 11 Quad Radio Router 12 Man Portable Unit — Gen3 Dual 14 AID 15

Device Operation 16

Pushbutton/LED Operation 17 Conﬁguration 18

Web Management Overview 20

Web Management Introduction 21 Accessing the Web Management Interface

22 Conﬁguring Your Computer’s IP Address 23 Security Certiﬁcate Warnings 24

Initial Node Configuration 26

Steps for Conﬁguring the First Node 27 Steps for Conﬁguring Remaining Nodes 32 Node List 36 Network vs. Managed Nodes Deﬁned 36 Network Upgrade 37

TABLE OF CONTENTS

Web Management Interface Reference 38

Node Status 39 Node Conﬁguration 48 Creating a Master Conﬁguration File 61 Quick Setup 63 Reset to Factory Conﬁguration 64 Tracking Antenna Control 65 Push-To-Talk (PTT) 67 RS-232 71 Date/Time 75 Ampliﬁer Conﬁguration 77 Network Status 79 Network Conﬁguration 87 Network Node List 88 Network Defaults 89 Security 101 Wave Relay® API 104

Troubleshooting 106

Common Problems And Troubleshooting 107 Symptom 1: Nodes Are Unale To Communicate 109 Symptom 2: Poor/Low Throughput 110 Symptom 3: Multicast Trafﬁc Not Forwarding Correctly 110

Hardware Details 112

Man Portable Unit — Gen4 114 Man Portable Unit — Gen3 122 Quad Radio Router 130 Sector Array Kit 135 Tracking Antenna System 137

Regulatory Information 142

Change History --

Supporting Manuals

Cloud Relay™ Manual Android™ Manual Rapid Conﬁguration Tool Manual Quality Control Tool Manual All Available Upon Request

DEVICE

HARDWARE

INTRODUCTION

DEVICE HARDWARE INTRODUCTION

MAN PORTABLE UNIT — GEN4

GPS

3.3V Active Antenna only (SMA)

PUSHBUTTON/LED

ZEROIZE: PRESS 3X

IN < 2

SECONDS

POWER/DEVICE I/O

(19-PIN)

Ethernet 1: 10.3.1.254 Ethernet 2: 10.3.2.254

Serial RS-232

PTT Audio

PoE: 10-48 VDC

RADIO 1

ANTENNA

(RP-TNC)

BATTERY TWIST-LOCK

CONNECTION

Included: BAT-06

Battery Eliminator: CBL-054

Compatible With:

PRC-148 Battery PRC-152 Battery

POWER

10-48VDC

(48 VDC is PoE)

DEVICE HARDWARE INTRODUCTION

MAN PORTABLE UNIT — GEN3 SINGLE

RADIO 1

ANTENNA

(RP-TNC)

AUXILIARY

POWER (3-PIN)

10-48 VDC

POWER/DEVICE I/O

(19-PIN)

Ethernet 1: 10.3.1.254 Ethernet 2: 10.3.2.254

Serial RS-232

PTT Audio

PoE: 10 - 48 VDC

PUSHBUTTON/LED

ZEROIZE: PRESS 3X

IN < 2

SECONDS

GPS

3.3V Active Antenna only (SMA)

DEVICE HARDWARE INTRODUCTION

QUAD RADIO ROUTER

ETHERNET 2 SWITCH PORT

(RJ45)

CANNOT accept PoE

Ethernet 2 IP: 10.3.2.254

RADIO 2

ANTENNA

(N-type)

RADIO 1

ANTENNA

(N-type)

PUSH-TO-TALK (PTT) AU-

DIO (NATO 6-PIN CON-

NECTOR)

3.3V Active Antenna only

RADIO 3

ANTENNA

(N-type)

GPS

(SMA)

DEVICE HARDWARE INTRODUCTION

PUSHBUTTON/LED

ZEROIZE: PRESS 3X

IN < 2

SECONDS

RADIO 4

ANTENNA

(N-type)

ETHERNET 2 SWITCH PORT

(RJ45)

CANNOT accept PoE

Ethernet 2 IP: 10.3.2.254

POWER/ETHERNET 1

(RJ45)

Accepts PoE, 10-48 VDC Ethernet 1 IP: 10.3.1.254

AUXILIARY POWER/

SERIAL (4-PIN)

10-48 VDC

DEVICE HARDWARE INTRODUCTION

MAN PORTABLE UNIT — GEN3 DUAL

RADIO 1

ANTENNA

(RP-TNC)

AUXILIARY

POWER (3-PIN)

10-48 VDC

POWER/DEVICE I/O

(19-PIN)

Ethernet 1: 10.3.1.254 Ethernet 2: 10.3.2.254

Serial RS-232

PTT Audio

PoE: 10 - 48 VDC

RADIO 2

ANTENNA

(RP-TNC)

GPS

3.3V Active Antenna only (SMA)

PUSHBUTTON/LED

ZEROIZE: PRESS 3X

IN < 2

SECONDS

PUSH-TO-TALK

(PTT) AUDIO (NATO 6-PIN

CONNECTOR)

DEVICE HARDWARE INTRODUCTION

AID

ETHERNET 2

(RJ45)

PoE,

10-48 VDC

Factory Setup IP: 10.3.2.254

POWER/ETHERNET 1

(RJ45)

Accepts PoE, 10-48 VDC

Factory Setup IP: 10.3.1.254

TO MPU

(19-PIN)

DEVICE

OPERATION

DEVICE OPERATION

PUSHBUTTON/LED OPERATION

NOTE:

STATE LED STATUS OPERATION INSTRUCTION

OFF ON/OFF Power

OFF

Boot Up (30s - 2 mins)

ON

Fully Operational

Zeroize

HOLD

(1 second)

ON

Conﬁguration Required

TAP 3 TIMES

SLOW BLINK

Zeroize

FAST BLINK

Low Battery (MPU4 Only)

OFF 2 SEC,

ON .5 SEC

(< 2 sec)

DEVICE OPERATION

CONFIGURATION

When a node is shipped from the factory, it is in a state that requires conﬁguration. Nodes can be conﬁgured by using the Web Management Interface or through the Management API.

Follow the steps under “Initial Node Conﬁguration” to put the nodes into an operational state. The basic steps required to conﬁgure a node to an operational state are:

SET ENCRYPTION KEY

A key must be set in order for a node to communicate with other nodes in the network. In order for two nodes to communicate, they must share a matching encryption key and crytpo mode.

SET CHANNEL

Each radio module on a node should be assigned a center frequency and channel width. In order for two nodes to communicate, each node must have at least one radio that shares the same center frequency and channel width.

SET IP ADDRESS

During node conﬁguration, a node needs to be assigned a unique management IP address. This management IP address is used for monitoring, conﬁguration, and device services (PTT, Google™ Earth, Tracking, RS-232, etc.).

In the event that two nodes are unable to communicate after initial conﬁguration, refer to the “Troubleshooting” section starting on page 104.

WEB

MANAGEMENT

OVERVIEW

WEB MANAGEMENT OVERVIEW

WEB MANAGEMENT INTRODUCTION

The Wave Relay® Web Management Interface enables users to conﬁgure and monitor Wave Relay® units through a web browser. A navigation bar organizes the Management Interface. The “Node Status” and “Node Conﬁguration” tabs pertain only to the node to which the management computer is connected (either by Ethernet cable or by wireless), and the “Network Status” and “Network Conﬁguration” tabs pertain to the entire network of nodes.

WEB MANAGEMENT OVERVIEW

ACCESSING THE WEB MANAGEMENT INTERFACE

NODE CONNECTIVITY INFORMATION

Default Management Password Ethernet 1 Factory Setup IP Ethernet 2 Factory Setup IP

Password

10.3.1.254

10.3.2.254

•Factory Setup IP addresses are always accessible when directly connected to the radio. Use

Factory IPs any time you do not remember the management IP address of the radio.

•To connect to the Factory IP address, the management computer must be on the correct

IP subnet and wired to the correct Ethernet port on the node.

MANAGEMENT COMPUTER SETTINGS

IP Address Subnet Mask Default Gateway / Router

10.3.1.10

255.255.255.0

10.3.1.1

•To connect to the node using Ethernet 1, open a web browser and connect to

http://10.3.1.254.

•Each time you connect a new device, you may need to accept a security certiﬁcate before

you can enter the Web Management Interface.

•See next page for information on setting up the management computer.

WEB MANAGEMENT OVERVIEW

CONFIGURING YOUR COMPUTER’S IP ADDRESS

For your computer to be able to communicate with the Wave Relay®, it must have an IP address that is in the same IP subnet mask as the Wave Relay®’s IP address. A subnet mask of 255.255.255.0 means that the computer can communicate with another device that has an IP address matching the ﬁrst three numbers of its own IP address.

No Default Gateway or DNS server conﬁguration is required; however they can be conﬁgured if necessary. Most computers are capable of having more then one IP address conﬁgured on a single Ethernet adapter. It is recommended that you add all three addresses to your wired Ethernet adapter so that you can easily manage your network.

LINUX:

[sudo] ifconﬁg eth0 10.4.1.10/24 [sudo] ip addr add 10.3.1.10/24 dev eth0 [sudo] ip addr add 10.3.2.10/24 dev eth0

WINDOWS:

Start > Network (Right Click) > Properties Change Adapter Settings (Windows Vista / 7 only) Local Area Connection (Right Click) > Properties Select Internet Protocol Version 4 (TCP/ IPv4) Click Properties Select Use the following IP Address Click Advanced… Click Add… Enter IP Address and Subnet mask Click Add and repeat for all IP Addresses

WEB MANAGEMENT OVERVIEW

SECURITY CERTIFICATE WARNINGS

Recommended browsers are Firefox 3+, Internet Explorer 7+, and Google™ Chrome. Internet Explorer 6 is not compatible with the most recent Web Management Interface. If you are having difﬁculty connecting to the Web Management Interface, make sure you are using one of the recommended browsers.

When connecting to the Web Management Interface, Firefox and Internet Explorer may ask the user to accept a security certiﬁcate. Firefox and IE handle security certiﬁcates in different ways:

FIREFOX DISPLAYS A PAGE

Click “I understand the risks” > ”Add Exception” > ”Conﬁrm Security Exception.”

IE DISPLAYS A PAGE

Click the red X “Continue to this website (not recomended).”

WEB MANAGEMENT OVERVIEW

GOOGLE™ CHROME DISPLAYS A PAGE

1. Click the “Proceed anyway” button.

2. When the Web Management Interface loads, enter the management password and click “Authenticate.” The default management password is “password” which is set from the factory or after the key/conﬁguration is zeroized by pushing the on/off button 3 time in less than 2 seconds.

INITIAL

NODE

CONFIGURATION

INITIAL NODE CONFIGURATION

All nodes arrive set to factory default conﬁguration. This section details the recommended setup and custom conﬁguration procedure for a set of identical nodes, for example, a set of 50 MPU4s. In general, the procedure is completed as follows:

1. Conﬁgure an individual node

2. Save the individual node’s conﬁguration settings and key

3. Load key and the saved conﬁguration settings into remaining nodes

4. Verify communication among the nodes

QUICK CONFIGURATION

If the network administrator provides a node conﬁguration ﬁle, use it to facilitate quick device conﬁguration. Please refer to Section “Quick Setup.” If a node conﬁguration ﬁle has been provided, skip to the “Steps for Conﬁguring the Remaining Nodes” section.

STEPS FOR CONFIGURING THE FIRST NODE

1. Conﬁgure Network Defaults

2. Customize Node Name and IP Address To Be Unique

3. Conﬁgure Radio to Use Defaults

4. Setup Node List

5. Store Conﬁguration File

6. Set and Save Security Settings

INITIAL NODE CONFIGURATION

STEP 1: CONFIGURE NETWORK DEFAULTS

Network Defaults are settings that will be used to manage the conﬁguration of the network. Up to 16 different default Channel settings are able to be conﬁgured.

1. Click “Network Conﬁguration” > “Network Defaults.”

2. Choose the settings you would like to use for your network for each Channel.

3. Click the “Save to Network” button at the bottom of the page.

For more information on setting Network Defaults, refer to the section “Network Conﬁguration > Network Defaults.”

WARNING!

For units branded with an FCC label and FCC ID, only the provided antenna or equivalent type and gain can be used: this device must comply with Part 15 of the FCC rules.

FCC branded devices will be limited so users cannot set output power levels outside of those certiﬁed under the FCC rules.

FCC test results and reports can be provided by Persistent Systems, LLC upon request.

For more information, please contact Persistent Systems, LLC Quality/Compliance personnel.

STEP 2: CUSTOMIZE NODE NAME AND IP ADDRESS TO BE UNIQUE

Each node in the network should be assigned a unique node name and IP address to facilitate management and network operations.

1. Click “Node Conﬁguration” > “Node Conﬁguration.”

2. Insert the new name and IP Address in the indicated ﬁelds.

3. Set the gateway to match the subnet of the node’s IP address.

4. Click the “Save & Reconﬁgure Unit” button at the bottom of the page.

5. Load the key and saved conﬁguration ﬁle into remaining nodes. Customize the Node Name and IP address for each node, then click the “Save & Reconﬁgure Unit” button at the bottom of the page.

6. Ensure that node names and IP addresses of all nodes are unique.

INITIAL NODE CONFIGURATION

STEP 3: CONFIGURE RADIO TO USE DEFAULTS

The node must be conﬁgured to use the appropriate Network Defaults in order for the node to be managed by changes to the Network Conﬁguration.

1. Click “Node Conﬁguration” > “Node Conﬁguration.”

2. Select the appropriate Network Defaults in the drop down menus.

3. Click the “Save & Reconﬁgure Unit” button at the bottom of the page.

For more information, see section “Conﬁguring Radio to Use Defaults.”

STEP 4: SETUP NODE LIST

The Node List is a list of IP Addresses of nodes managed by the Web Management Interface.

1. Click “Network Conﬁguration” >

“Network Node List.”

2. Enter the IP Address of a node in the

“Manually Add IP(s)” ﬁeld and click “Add” to add the node associated with that IP Address to the Node List. Nodes may also be added from the “Other Nodes on Network” window if they are detected by the network. These nodes may be added individually with the “Selected IPs” button or all at once with the “All” button.

3. Repeat this process for every node to be managed.

4. With all new nodes programmed and on, ensure that all nodes are on the

Network Node List.

5. Click the “Push Management List to Network” button. This function will copy

the node list to each node in the network. Only nodes in the node list will be affected by Network Conﬁguration functions. Pushing the node list to the network allows network-wide settings to be managed from any node in the network.

STEP 5: STORE CONFIGURATION FILE

Device settings (both Node Conﬁguration and Network Conﬁguration settings) can be saved to a conﬁguration ﬁle. The conﬁguration ﬁle serves as a backup for device settings and provides the ability to easily transfer settings from one node to another.

1. Ensure Network Conﬁguration and Node Conﬁguration settings are set as

desired.

2. Click “Node Conﬁguration” > “Conﬁg Management.”

3. Click the “Store” button. A prompt will appear to choose where to save the

conﬁguration ﬁle. Note speciﬁcally that this ﬁle contains settings (both Network Conﬁguration and Node Conﬁguration settings) for the current device only.

INITIAL NODE CONFIGURATION

2

3

1

STEP 6: SET AND SAVE SECURITY SETTINGS

A node will not function properly unless it has a valid key. If the “Security” tab in the Web Management Interface is blinking red, then a proper key has not been set. All nodes in a network must use the same Crypto Mode AND Key in order to communicate.

1. Select the “Security” tab in the Web Management Interface.

2. Select a Crypto Mode to match your network requirements.

3. Once the Crypto Mode is set, enter a key value into the ﬁeld and click “Set” or click “Generate” to generate a random key. The new key information is stored to the node or the network based on the setting in the “Update” menu.

For more information on Security information and selecting Crypto Mode options, refer to the “Security” section.

The key will NOT be stored in the conﬁguration ﬁle. The key must be stored separately.

1. Click the “Display Key” button.

2. Select OK on the warning to open the key. Since the key is displayed in plaintext, only open the key in a secure environment.

3. Copy the key to a text ﬁle in a secure place on your management computer.

INITIAL NODE CONFIGURATION

1

Ensure all nodes are

using the same

Crypto Mode

Click here after

entering key

Enter your key

here

2

3

INITIAL NODE CONFIGURATION

STEPS FOR CONFIGURING THE REMAINING NODES

1. Load Conﬁguration File into All Other Nodes

2. Load Key into All Other Nodes

3. Verify Nodes are Communicating

4. Push Node List to Network

5. Set Management Password

INITIAL NODE CONFIGURATION

STEP 1: LOAD CONFIGURATION FILE INTO ALL OTHER NODES

When setting up a network of new nodes from the factory, use the conﬁguration ﬁle saved in the “Store Conﬁguration File” step to upload the settings from the previously conﬁgured node into the new node. During this process, node speciﬁc settings (including IP Address, Radio Name, and other radio speciﬁc settings) can be conﬁgured separately for each node while preserving all other settings from the conﬁguration ﬁle.

1. Click “Node Conﬁguration” > “Conﬁg Management.”

2. In the Load Conﬁguration menu, select “network (require all)” or “network (any

available)” to upload conﬁguration settings to all nodes in the network. The “network (require all)” setting will require all nodes in the network be available for any changes to be applied. If not all nodes are available, no changes will be applied. The “network (any available)” setting will apply changes to available nodes only.

3. Click the “Choose File” button to ﬁnd the the conﬁguration ﬁle saved in the

“Store Conﬁguration File” step.

4. Click the “Load” button to upload conﬁguration settings to other nodes in the

network.

STEP 2: LOAD KEY INTO ALL OTHER NODES

The security key is NOT stored in the conﬁguration ﬁle. You must load the key separately.

1. Select the “Security” tab in the Web Management Interface.

2. In the “Set Key” box, select “network (require all)” or “network (any available)”

to upload the security key to all nodes in the network. The “network (require all)” setting will require all nodes in the network be available for any changes to be applied. If not all nodes are available, no changes will be applied. The “network (any available)” setting will apply changes to available nodes only.

3. Select the Crypto Mode chosen in Step 6 of First Node Conﬁguration from the

drop-down menu.

4. Copy the security key from the text ﬁle saved in Step 6 of First Node Conﬁgura-

tion and paste the security into the “Enter key” ﬁeld. All nodes MUST have the same security key to communicate.

INITIAL NODE CONFIGURATION

STEP 3: VERIFY NODES ARE COMMUNICATING

After nodes have been conﬁgured, the connectivity of the nodes should be checked.

1. Ensure that all nodes are turned on, that at least one radio on each node has an antenna and is set to the same channel as the other nodes, and that each node has the same key.

2. Access one of the nodes and verify connectivity to all the nodes. Click “Node Status” > “Neighbor Status.” The ﬁgure below displays the Node Neighbor Status, which shows which of the node’s radios are communicating with other radios. This ﬁgure shows that Radio 1 is communicating with one other radio in a neighbor node.

STEP 4: PUSH NODE LIST TO NETWORK

To be able to control conﬁguration settings for the entire network from any node in the network rather than just this node, the user must push the Node List to all other nodes in the network.

1. Click “Network Conﬁguration” > “Network Node List” > “Push Management List to Network.” This function will share the Node List conﬁgured on this node with all nodes in the Node List.

INITIAL NODE CONFIGURATION

STEP 5: SET MANAGEMENT PASSWORD

After all nodes have been conﬁgured, the management password should be changed.

1. Click “Network Conﬁguration” > “Network Password.”

2. Enter the old password in the “Old Password” ﬁeld.

3. Enter the new password in both “New Password” ﬁelds.

4. Click the “Change” button to change the management password. The

management password will be changed on all nodes in the node list. The current node list is displayed at the bottom of the page.

INITIAL NODE CONFIGURATION

NODE LIST

The Node List contains a list of nodes speciﬁed by IP Address that are controlled by the Web Management Interface. Any function that resides under Network Status or Network Conﬁguration operates on, and only on, the nodes listed in the node list.

NETWORK VS MANAGED NODES DEFINED

®

In the context of Wave Relay routing is possible. These nodes do not need to be speciﬁed in the Node List. By contrast, the Node List deﬁnes a set of Managed Nodes that are managed by the network operations in the Web Management Interface. That list, however, does not restrict connectivity between nodes speciﬁed in the Node List and nodes not speciﬁed in the Node List. Therefore, the Node List is just a management tool that deﬁnes the list of nodes on which network management functions operate.

In general, the Node List should be updated whenever the network changes in order to ensure that every node has complete and current information and is able to be monitored and controlled by the network operations in the Web Management Interface.

, the network is deﬁned as the set of nodes for which

INITIAL NODE CONFIGURATION

NETWORK UPGRADE

Network Upgrade installs new ﬁrmware versions on large numbers of nodes with one operation. Since network upgrades function on all nodes in the Node List, make sure the Node List is complete and current before performing a Network Upgrade.

1. Click “Network Conﬁguration” > “Network Upgrade.”

2. Browse and select the appropriate upgrade ﬁle.

3. Check or uncheck “Require All.” If checked, the update will be installed if

and only if all the nodes in the Node List are accessible. If unchecked, the update will be installed to only those nodes in the Node List that are accessible. Network Upgrades will cause nodes to be reconﬁgured, an operation that causes a period of downtime. Do not perform Network Upgrades during mission critical operations that cannot tolerate such disruptions. Under such situations, perform Network Upgrades only during scheduled maintenance or other appropriate times.

4. Click the “Upload” button to upgrade ﬁrmware for all nodes in the Node List.

NOTE: When upgrading or downgrading a node’s ﬁrmware, it is normal for the LED to turn off for 30 seconds then turn on.

Do not unnecessarily disturb devices during a Network Upgrade. Loss of power during the Network Upgrade can permanently damage a device.

To receive the latest ﬁrmware update:

1. Connect to: http://www.persistentsystems.com/requestﬁrmwareupdate.php

2. Fill out all ﬁelds on the page.

3. Ensure the “Receive Firmware” box is checked.

4. Click the “Submit Query” button.

WEB

MANAGEMENT

INTERFACE

REFERENCE

WEB MANAGEMENT INTERFACE REFERENCE

NODE STATUS

The “Node Status” tab in the Web Management Interface contains node-speciﬁc information for the individual node that the user is connected to.

WEB MANAGEMENT INTERFACE REFERENCE

UNIT INFO

Unit Info displays a list of hardware and software information related to the node.

MENU ITEM MENU ITEM DESCRIPTION

Firmware Version Firmware version on node

Serial No. Serial number of node

Uptime Operating time since last node power on or reboot

Temperature Temperature of node

Input Power Voltage Voltage supplied to node

Real Time Clock Battery Voltage of real-time-clock keep-alive battery (on units with RTC)

Current System Time Current system time of node (in both UTC and current time zone

Management HW MAC Address

Radio X HW MAC Address

Ethernet X HW MAC Address

if not UTC)

MAC Address for Management Hardware of node

MAC Address and bandwidth for each radio installed in node (X will vary based on number of radios installed)

MAC Address for each ethernet port in node (X will vary based on number of Ethernet ports in node)

WEB MANAGEMENT INTERFACE REFERENCE

NEIGHBOR STATUS

Neighbor Status page displays a list of neighbor nodes that the current node has an RF connection with.

If the neighbor node is in the node list and the “Update Network” operation has been performed, the node’s name, IP address, and radio interface will be displayed. Otherwise, the neighbor node’s MAC address will be displayed.

MENU ITEM MENU ITEM DESCRIPTION

Interface Each interface in use on node

Neighbor Name, IP address, and interface of each neighbor node

Receive SNR Signal-to-Noise Ratio at which local node hears remote node

WEB MANAGEMENT INTERFACE REFERENCE

GPS STATUS

Position Update Status:

MENU ITEM MENU ITEM DESCRIPTION

Source GPS information source

Latitude Latitude of current node

Longitude Longitude of current node

Altitude Altitude above sea level of

System Clock Status:

When the system clock was set by GPS

Current system time

Internal GPS Status:

MENU ITEM MENU ITEM DESCRIPTION

Fix Type How node is connected (3D, 2D, or none)

Latitude Latitude of current node

Longitude Longitude of current node

Altitude Altitude above sea level of current node

Speed Speed of node (m/s) in the horizontal plane

Track Path of travel with respect to the Earth expressed in degrees - 000 degrees

Climb Speed of node (m/s) in the vertical plane

Fix Time When node obtained a satellite ﬁx

Number of satellites

ID/PRN ID/PRN of each satellite node is connected to

Signal Strength of the connection between node and each satellite

NTP Server Status of the NTP server (available or unavailable)

current node

is North (angle increases clockwise through 360 degrees)

Number of satellites node is connected to

WEB MANAGEMENT INTERFACE REFERENCE

TRAFFIC LOAD

Trafﬁc load monitors and analyzes the traffﬁc load on the wireless and wired networking interfaces on the node.

Channel Usage:

MENU ITEM

Sent Transmission duty cycle of wireless

Received Receiving transmission duty cycle of

Noise Duty cycle of wireless medium us-

Used Total duty cycle of wireless medium

Checking Trafﬁc Load:

MENU ITEM MENU ITEM DESCRIPTION

Mbps Total Total Mbps used on this interface

Mbps Wave Relay

Mbps Wave Relay® Sent Mbps used by Wave Relay® to send

Mbps Wave Relay

Mbps Control Total Mbps used for control functions

Mbps Control Ack Mbps used to control ACK

Mbps Control RTS/CTS Mbps used to control RTS/CTS

Mbps Other Mbps used for other functions

Mbps Sent Total Mbps used for all transmissions

Mbps Sent Unicast Mbps used for Unicast transmissions

Mbps Sent Broadcast/Multicast Mbps used for Broadcast/Multicast transmissions

Mbps Received Total Mbps used to receive all transmissions

Mbps Received Unicast Mbps used to receive Unicast transmissions

Mbps Received Broadcast/Multicast

MENU ITEM DESCRIPTION

medium usage

wireless medium usage

age: Occupied by noise

usage

®

Received Mbps used by Wave Relay® to receive

Total Mbps used by Wave Relay

Mbps used to receive Broadcast/Multicast transmissions

®

WEB MANAGEMENT INTERFACE REFERENCE

BANDWIDTH TEST

Bandwidth Test is a tool for testing the data throughput from the node to another node in the network. It is recommended to perform at least a 5 second throughput test.

Wave Relay® nodes run a TCP iPerf server. To perform a TCP throughput test through the iPerf server, use the command “iperf

-c X” (X is the IP address of the node) from the command line.

WARNING: Windows has known issues running iPerf and does not give true bandwidth readings. Contact Persistent Systems for more information.

TO PERFORM A THROUGHPUT TEST:

1. Select destination node for throughput test from drop-down menu. Desired destination node must be in Node List for it to appear on this menu.

2. Check or uncheck “Upload only test.” If this box is checked, throughput test will only test upload to destination node.

3. Enter desired throughput test duration (in seconds) into “Test Duration” ﬁeld. Caution: during tests of long duration, data will continue to be sent for the full speciﬁed duration even if a different data ﬂow is started or the web browser is exited.

WEB MANAGEMENT INTERFACE REFERENCE

TRACKING STATUS

Tracking Status displays relevant antenna tracking status and diagnostic information.

MENU ITEM MENU ITEM DESCRIPTION

Tracking Antenna Mode Tracking conﬁguration of node

Local Coordinates Coordinates of tracking node

Target Coordinates Coordinates of tracked node

Target Distance Distance of tracked node from tracking node

Target SNR Signal-to-Noise ratio between tracking node and tracked node

Target Azimuth Azimuth of tracked node

Target Elevation Elevation of tracked node

Target Antenna Pan Calculated necessary horizontal position of Tracking Antenna in

Target Antenna Tilt Calculated necessary vertical position of Tracking Antenna

Actual Antenna Pan Current horizontal position of Tracking Antenna in degrees

Actual Antenna Tilt Current vertical position of Tracking Antenna in degrees (will only

degrees clockwise from North

expressed in degrees

clockwise from North (will only pan when Target changes at least

0.5 degrees from Actual)

tilt when Target changes at least 0.5 degrees from Actual)

STATION LIST

Station List displays the list of 802.11 client stations currently connected to radios with the 802.11 access point feature enabled.

MENU ITEM

macaddr MAC Address of client device connected to access point

rssi Strength of signal to client device

last_rx Time (in seconds) since a packet was last received

MENU ITEM DESCRIPTION

WEB MANAGEMENT INTERFACE REFERENCE

IP FLOW LIST

IP Flow List lists IP data ﬂows passing through node sorted by measured throughput.

MENU ITEM MENU ITEM DESCRIPTION

Mbit/s Speed of each IP data ﬂow in Mbps

Pkt/s Number of packets transferred each second for each IP data ﬂow

Total bytes Number of bytes transferred for each IP data ﬂow

Destination IP IP address of destination node

Source IP IP address of source node

Direction/Interfaces Direction of and interfaces used by each IP data ﬂow (MANET, Ether-

IP MULTICAST STATUS

IP Multicast Status displays IGMP Snooping and IP Multicast Pruning status. This feature shows a table with a row for each multicast group, displaying an “F” if that group is forwarded over the MANET, or a “-” if it is not.

net X, or this node)

There are known issues with IGMP in Windows XP.

MENU ITEM MENU ITEM DESCRIPTION

Group Multicast address of nodes connected to managed node

Registered to receive packets for group

Interface used to receive data for each multicast address (Ethernet X or MANET)

WRoIP STATUS

WRoIP Status displays the Wave Relay® over IP gateway status.

WEB MANAGEMENT INTERFACE REFERENCE

MENU ITEM MENU ITEM DESCRIPTION

Gateway Which gateway the node is connected to as well as the priority of that gate-

Elected Whether the gateway is elected or not

Election Priority Election priority of the gateway over other gateways/number of other WRoIP

WRoIP gateways detected

When connected to a WRoIP-conﬁgured node, the Neighbor SNR status page for the node will NOT display other nodes connected over WRoIP. Instead, these nodes will be displayed on the MANET Monitor page with a SNR of “-” since they are not connected via radio.

For detailed information, see the Cloud RelayTM Manual

DYNAMIC LINK EXCHANGE PROTOCOL (DLEP) STATUS

The DLEP Status page shows if the DLEP services is running, what port, who it’s connected to and the status of it. It also contains the status of the associated neighbors.

way

gateways on the IP network.

Displays names of detected WRoIP gateway nodes

It is also possible to set the status of DLEP on the Cisco Router side.

SYSTEM LOG

The System Log page displays a history of node management operations. The “Refresh” button reloads the system log to add more recent operations. The “Download” button allows the user to download the log to the computer.

WEB MANAGEMENT INTERFACE REFERENCE

NODE CONFIGURATION

The “Node Conﬁguration” tab in the Web Management Interface contains conﬁguration options for managing an individual node. Click “Node Conﬁguration” > “Node Conﬁguration” to access basic Node Conﬁguration settings.

WEB MANAGEMENT INTERFACE REFERENCE

SHOW/HIDE ADVANCED FIELDS

For convenience, this button allows you to show (or hide) many of the less frequently used node conﬁguration ﬁelds. The default is to hide the advanced ﬁelds (and thus display a briefer page). If you choose to show the advanced ﬁelds, your choice will remain in effect when you revisit the page. Advanced ﬁelds are indicated as such in the descriptions below.

MANAGEMENT SETTINGS

MENU ITEM MENU ITEM DESCRIPTION

Node Name Nodes can be assigned a unique name which is displayed in all of the

IP Address A node IP address can be assigned to allow IP connectivity. The IP address is

Netmask This ﬁeld deﬁnes the netmask for the Web Management Interface.

Gateway This ﬁeld deﬁnes the default gateway if a default gateway is required. The

VLAN ID (advanced)

management status functions.

generally used for node management functions. An IP address is not required for actual network operation, only for management and conﬁguration.

gateway must be set to an IP address on the same subnet as the IP address for the node.

This setting conﬁgures this node’s management port VLAN ID. Management features will ONLY be accessible to the speciﬁed VLAN (trafﬁc to/from all other VLANs is blocked/ﬁltered).

WEB MANAGEMENT INTERFACE REFERENCE

MANET (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

IP Multicast Routing

Root Gateway Priority (advanced)

DHCP Server Filter (advanced)

SNAP OUI (advanced)

AUTO: Node will prune multicast packets that are not requested (default, most efﬁcient setting for network). PULL ALL MULTICAST: Node will accept all multicast packets it hears on the network. Note: Windows CE/XP computers do not respond to IGMP Multicast Group Queries sent by Wave Relay nodes. “Pull All Multicast” should be used in networks with Windows CE/XP computers to work around this issue.

HIGH: Any node in your network directly connected to wired infrastructure should have priority set to “HIGH.”

MEDIUM: All other non-mobile routers should be set to “MEDIUM.” LOW: Mobile routers should be set to “LOW.”

ALLOW: Device will pass DHCP messages FROM a DHCP server which

is bridged directly by one of its interfaces. Only the devices which are directly wired to the switch where the DHCP server resides need to be set to “ALLOW.” BLOCK: Device will not bridge any DHCP reply packets that it picks up off of any of its bridged interfaces. By setting all of the nodes in the network (except the nodes physically connected to the real DHCP server) to “BLOCK,” you will ensure that users of your system will always use the correct DHCP server.

Controls the Subnetwork Access Protocol Organizationally Unique Identiﬁer - The factory OUI, 0018A6, is registered to Persistent Systems, LLC with the IEEE. SNAP OUI is used to identify Wave Relay Changing this ﬁeld allows the user to obscure which protocol is being used by the system. All nodes must be set to the same value or they will not communicate.

®

packets.

RADIO CONFIGURATION (BASIC RADIO SETTINGS)

MENU ITEM MENU ITEM DESCRIPTION

Name Each radio can be assigned a name to be used in status functions.

WEB MANAGEMENT INTERFACE REFERENCE

Frequency Each radio should be a assigned a frequency. Two radios must be set to

Bandwidth Each radio should be assigned a bandwidth. Two radios must be set to

Max Link Distance

Channel Density The channel density setting controls how aggressively the radios compete

Radio Preference Radio Preference instructs the routing protocol to prefer links on a radio

the same frequency in order to communicate. If the radio is conﬁgured to use a “Network Default” channel, the radio’s channel assignment can be managed globally by clicking “Network Conﬁguration” > “Network Defaults.” Ensure that the frequency is set to match the radio installed in the unit. A warning will be displayed if the frequency setting does not match the radio hardware.

the same bandwidth in order to communicate. Bandwidth should be increased for shorter distances and decreased for increased distances.

The Max Link Distance should be set to the upper bound of how long any individual link in the network may need to be. All nodes on the network MUST be set to the same Max Link Distance.

for access to the shared medium. A number of nodes will be displayed in parentheses after each menu item. Choose the menu item that corresponds to the number of nodes in your network.

(consider them lower cost than normal). This can be used to help shift trafﬁc towards radios running on certain channels.

None: None is the default factory setting. All links are considered equally. Medium: Routing protocol is more likely to use this radio to forward

trafﬁc. High: Routing protocol is signiﬁcantly more likely to use this radio to forward trafﬁc.

RADIO CONFIGURATION (ADVANCED RADIO SETTINGS)

MENU ITEM MENU ITEM DESCRIPTION

Max Transmit Power (advanced)

MAC Address (advanced)

Max Transmit Power will control the radio’s maximum output power. In general, this conﬁguration is only used to reduce the output power of a radio for regulatory compliance reasons. The factory default setting should provide the best communication performance (highest power) in all other situations.

A custom MAC address may be used for this radio. The entered value MUST be different from ALL other radio MAC addresses used in the same network or with the same encryption key. All radios are factory conﬁgured with a globally unique MAC. Since the MAC address is unencrypted, using a custom MAC that is periodically changed can help prevent identiﬁcation and tracking of the same device across multiple uses.

WEB MANAGEMENT INTERFACE REFERENCE

ACCESS POINT SETTINGS (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

802.11 Access Point (advanced)

The following ﬁelds are only visible when the 802.11 Access Point is “Enabled.”

Mesh Routing (advanced)

ESSID (advanced) Sets the name of the network that the access point advertises to

ESSID Visibility (advanced)

AP Security (advanced) Enables or disables 802.11 security on the Access Point - Only

WPA2 Passphrase (advanced)

AP Broadcast Rate (advanced)

2.4GHz and 5.8GHz radios can be conﬁgured to function as an

802.11 access point. Standard clients such as laptops with built in 802.11 cards may access this system. If the AP is disabled, the ESSID and Beacon Interval conﬁguration options have no effect. For maximum performance, always disable the 802.11 AP unless it is required. To use a radio as a 802.11 Access Point, the radio MUST be set to a valid 802.11 frequency and the channel width MUST be set to 20MHz.

The Mesh Routing setting enables per radio selection of which radios participate in the multi-hop mesh routing process. In a multi-radio node where the user may only want the mesh running on the backhaul radios, this setting enables the user to speciﬁcally disable the mesh on the client access radios. Be aware that if a node is only accessible via the mesh and mesh routing is disabled, connection will be lost to that node.

clients.

The ESSID can be conﬁgured to be “Visible” or “Hidden.” Generally, the ESSID is conﬁgured to be “Visible” to make it easy for clients to connect to the access point. For additional security/ privacy the ESSID can be conﬁgured as “Hidden.”

WPA2-PSK (Wi-Fi Protected Access v2 with pre-shared keys) is supported.

Sets a shared passphrase when AP Security is set to WPA2 - The passphrase should be an ASCII string of length 8-63 characters, excluding these characters: ‘,”\&/<>

Controls the rate at which broadcasts are transmitted from an 802.11 Access Point - Increasing this rate can signiﬁcantly increase network capacity but will reduce the range of client connectivity. If the rate is set too high, client devices will have trouble receiving broadcast packets from the 802.11 access point.

WEB MANAGEMENT INTERFACE REFERENCE

AP Beacon Interval (advanced)

VLAN ID (advanced) Each 802.11 AP is a VLAN-aware bridge port. Each port is as-

VLAN Priority (advanced)

VLAN Trunking (advanced)

IP Mcast/Bcast Limit (advanced)

The 802.11 access point can send beacons at an interval between twice and ten times per second.

signed a VLAN ID. Untagged frames received by the port are tagged with the speciﬁed VLAN ID. Frames that are sent by the port which have a VLAN tag matching the speciﬁed VLAN ID will have their tags removed (i.e. they are sent by the port untagged).

Speciﬁes the 802.11 priority of the VLAN tag added to untagged frames received by this port

Controls the ﬁltering of VLAN tagged frames that do NOT match this port’s VLAN ID - Trunking enabled: ALL non-matching VLAN tagged frames are passed (no ﬁltering). Trunking disabled: all non-matching VLAN tagged frames are blocked (ﬁltered).

Deﬁnes the maximum bandwidth allowed for IP multicast or broadcast network trafﬁc received on the given interface and retransmitted onto the Wave Relay this limit will be dropped. Units are megabits/sec (Mbps). To disable the limit, set to zero.

®

network - Trafﬁc in excess of

ETHERNET CONFIGURATION (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

Name (advanced) A name can be assigned to each Ethernet interface.

MANET Access (advanced)

VLAN ID (advanced)

Controls whether MANET trafﬁc is available on a wired Ethernet port

- This setting is useful in cases where the node is physically situated in an insecure location, and you want to prevent casual passersby from eavesdropping on the MANET by physically plugging into the Ethernet port (in this case, be sure to disable access for all wired Ethernet interfaces on the node). The default setting is “Enabled,” i.e. the MANET trafﬁc is available on the Ethernet port. Note: the permanent factory IP address for the node is still available on the Ethernet port, regardless of this setting. In addition, two Wave Relay® nodes connected via wired Ethernet can still communicate via encrypted link regardless of this setting.

Each Ethernet interface is a VLAN-aware bridge port. Each port is assigned a VLAN ID. Untagged frames received by the port are tagged with the speciﬁed VLAN ID. Frames that are sent by the port which have a VLAN tag matching the speciﬁed VLAN ID will have their tags removed (i.e. they are sent by the port untagged).

WEB MANAGEMENT INTERFACE REFERENCE

VLAN Priority (advanced)

VLAN Trunking (advanced)

Speciﬁes the 802.11 priority of the VLAN tag added to untagged frames received by this port

Controls the ﬁltering of VLAN tagged frames that do NOT match this port’s VLAN ID - Trunking enabled: ALL non-matching VLAN tagged frames are passed (no ﬁltering). Trunking disabled: all non-matching VLAN tagged frames are blocked (ﬁltered).

IP Mcast/Bcast Limit (advanced)

Deﬁnes the maximum bandwidth allowed for IP multicast or broadcast network trafﬁc received on the given interface and retransmitted onto the Wave Relay

®

network - Trafﬁc in excess of this limit will be dropped.

Units are megabits/sec (Mbps). To disable the limit, set to zero.

Routing Metric (advanced)

Deﬁnes link capacity for the routing protocol - A value lower than the 100 Mbps default should be used when nodes are connected via non-switched Ethernet (e.g. a third-party point-to-point wireless link). The metric allows the routing protocol to make an intelligent decision whether it is better to route over this Ethernet port or use a faster alternate route.

USB ETHERNET (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

USB Ethernet Charging Power

Controls how an EUD connected via a USB Ethernet cable receives a charge from the node - Should be set to “Always On” for the Samsung Note/Note II/Note III, Motorola EUDs, and Nexus 7 and “Carrier Sense” for the Samsung Galaxy SII 9100G.

WEB MANAGEMENT INTERFACE REFERENCE

DHCP SERVER (ADVANCED)

If enabled, the DHCP server will serve IP addresses to devices connected to the node via the wired Ethernet or wireless 802.11 Access Point interfaces.

MENU ITEM MENU ITEM DESCRIPTION

DHCP Server Scope

Address Range Start

Address Range End

Netmask Netmask assigned to DHCP clients

Default Gateway Gateway assigned to DHCP clients

DNS Server 1 Primary DNS server assigned to DHCP clients

DNS Server 2 Secondary DNS server assigned to DHCP clients

WINS Server WINS server assigned to DHCP clients

Lease Time DHCP lease time (defaults to 1 hour)

Show Leases Displays the MAC and IP address of assigned DHCP leases

Selects which DHCP clients the DHCP server serves IP addresses to. “Local Ethernet/AP Only” serves IP addresses to nodes connected via Ethernet or a wireless 802.11 Access Point. “Entire Network” serves IP addresses to all nodes in the network. “Local Ethernet/AP Only” is the recommended setting.

Start of range of IP addresses assigned to DHCP clients

End of range of IP addresses assigned to DHCP clients

WEB MANAGEMENT INTERFACE REFERENCE

WAVE RELAY® OVER IP (WRoIP) (ADVANCED)

WRoIP allows the Wave Relay® network to extend over and seamlessly interact with a large routed IP network. In order to use this capability, one or more Wave Relay® nodes must be setup as WRoIP gateways. A WRoIP gateway must be directly connected to an appropriately conﬁgured IP router.

See Cloud RelayTM Manual

MENU ITEM MENU ITEM DESCRIPTION

WRoIP (advanced)

Multicast Routing Mode (advanced)

IP Address (advanced)

Netmask (advanced)

Gateway (advanced)

MTU (advanced)

Multicast Address (advanced)

UDP Port (advanced)

WRoIP gateway nodes must have the WRoIP protocol enabled on the interface directly connected to the IP router. All other nodes should have the WRoIP protocol disabled. When the WRoIP protocol is enabled on an interface, the interface will no longer function as a normal Wave Relay will only work for connecting the IP router.

Selects pruning options for multicast trafﬁc:

IP Router Controlled (default): All multicast packets travel to the cloud network Wave Relay Controlled: Only subscribed multicast feeds are passed to the cloud network to reduce network trafﬁc congestion.

Deﬁnes the IP address of the WRoIP gateway in the IP subnet speciﬁc to the directly connected IP router interface - WRoIP protocol packets will be sent over the IP network using this IP address.

Deﬁnes the netmask of the IP subnet speciﬁc to the directly connected IP router interface

Deﬁnes the IP address of the IP router in the IP subnet speciﬁc to the directly connected IP router interface - WRoIP protocol packets will be forwarded to this IP address in order to be sent over the IP network.

Deﬁnes the maximum transmissible unit size for the IP network - WRoIP protocol packets sent over the IP network will be limited to this MTU. All nodes that communicate over the IP network should be set to the same value.

Deﬁnes the multicast IP address used by the WRoIP protocol - The next higher IP multicast address will also be used by the WRoIP protocol. For example, if 239.255.90.67 is set as the multicast address, both 239.255.90.67 and 239.255.90.68 will be used.

Deﬁnes the UDP port used by WRoIP protocol packets

®

Ethernet port for connecting Ethernet devices: it

WEB MANAGEMENT INTERFACE REFERENCE

NODE CONFIGURATION FOR DLEP

Dynamic Link Exchange Protocol (DLEP) (advanced):

DLEP is used to transmit characteristics and metrics of the wireless network to a connected DLEP-capable router such as the Cisco 5915. This feature is available on all Wave Relay® versions. It supports DLEP Draft 00.

The Wave Relay® MANET operates at Layer 2 of the OSI mode. The DLEP protocol runs between a router and its attached Wave Relay device, allowing the Wave Relay® to communicate link characteristics as they change, and convergence events (acquisition and loss of potential Layer 3 (L3) routing neighbors). Upon receipt of the signal, the local router may take whatever action it deems appropriate, such as initiating L3 discovery protocols, and/or issuing HELLO messages to converge the network on L3. On a continuing, as-needed basis, the Wave Relay devices utilize DLEP to report any characteristics of the link (bandwidth, latency, etc)to the L3 router that have changed. DLEP is independent of the link type and topology supported by the Wave Relay.

•DLEP (advanced): Enable/disable the DLEP subsystem.

•Local UDP Port (advanced): UDP port on the Wave Relay to receive DLEP trafﬁc

from the router.

•Router IP Address (advanced): Network address of the DLEP-capable router.

•Router UDP Port (advanced): UDP port on the DLEP-capable router for receiving

DLEP packets.

WEB MANAGEMENT INTERFACE REFERENCE

POSITION

The node’s position must be speciﬁed in order to provide data to the visualization, CoT, and tracking features. The position may be speciﬁed via internal or external GPS, manually, or from an external feed.

Position Mode:

MENU ITEM MENU ITEM DESCRIPTION

Determines the source of local positioning information

Use Internal GPS Instructs node to receive GPS position information from the optional

Use External GPS

Manual Entry Allows manual entry of latitude, longitude, and altitude.

Use External Feed

Use ESD Feed Instructs node to receive positioning information over the network via a

Use CoT Feed Instructs node to receive positioning information over the network via a

Use CDF Feed Instructs node to receive positioning information over the network via

GPS Status Displays the current status of the GPS (only visible in “Use Internal GPS”

integrated GPS module - This control should not be enabled on a device that does not have an integrated GPS module or if a suitable GPS antenna with satellite connectivity is not attached.

Instructs node to receive GPS position information from an external GPS device connected via the node’s onboard serial port - A standard NMEA data stream is supported with the following RS-232 settings: 4800 baud, 8-N-1, no ﬂow control. Higher baud rates are also autodetected. Note that this option is disabled on Wave Relay units already using the serial port for other features (e.g. antenna tracking).

Instructs node to receive positioning information over the network via the external Wave Relay® ‘wr-update-gps’ command

ESD (Exploitation Support Data) feed

CoT (Cursor on Target) feed. This feature is not available on all ﬁrmware versions.

Shadow CDF (Common Data Feed)

mode)

®

units without serial connectors or

WEB MANAGEMENT INTERFACE REFERENCE

Latitude Allows the user to manually deﬁne the node’s latitude in decimal degrees

(only visible in “Manual Entry” mode)

Longitude Allows the user to manually deﬁne the node’s longitude in decimal de-

grees (only visible in “Manual Entry” mode)

Altitude Allows the user to manually deﬁne the node’s altitude in feet above GPS

ellipsoid - approximately equal to feet above mean sea level (MSL) (only visible in “Manual Entry” mode)

External Update UDP Port

Deﬁnes the port number to receive position updates via the external Wave Relay

®

‘wr-update-gps’ command (only visible in “Use External

Feed” mode)

ESD UDP Port Deﬁnes the port number to receive position updates via an external ESD

feed (only visible in “Use ESD Feed” mode)

CoT UDP Port Deﬁnes the port number to receive position updates via external CoT

feed (only visible in “Use CoT Feed” mode)

CDF UDP Port Deﬁnes the port number to receive position updates via an external CDF

feed (only visible in “Use CDF Feed” mode)

Update Interval Controls how often nodes report information back to visualiziation

server with visualization enabled - Smaller values allow ﬁner mobile node movements in Google

™

Earth. Shorter update intervals require more

bandwidth.

WEB MANAGEMENT INTERFACE REFERENCE

WAVE RELAY® SA (GOOGLE™ EARTH NETWORK VISUALIZATION)

MENU ITEM

Report to Server

Icon The user may select an icon that will be used to identify the node in Google

MENU ITEM DESCRIPTION

Sending visualization updates can be individually enabled or disabled on each node. Setting “Network Default,” allows visualization to be turned on and off for the entire network at once via the Network Default conﬁguration. Note that the selected server IP address is displayed here but is conﬁgured as part of the Network Default conﬁguration. Visualization is also used by the Tracking Antenna system and should be enabled on nodes that you wish to track.

™

Earth.

CURSOR ON TARGET (COT) SETTINGS

This feature enables transmission of local positioning information to a CoT server on the network. This feature is not available on all ﬁrmware versions.

MENU ITEM MENU ITEM DESCRIPTION

Send Position Enables or disables transmission of CoT packets to server

Server IP Deﬁnes the IP address of the CoT server - This IP address can be a unicast

Server Port Deﬁnes the UDP port of the CoT server

UID Deﬁnes the contents of the CoT “uid” attribute

Type Deﬁnes the contents of the CoT “type” attribute

Video Address Deﬁnes the contents of the CoT “Video Address” attribute

or multicast address

SIMPLE SA PACKET GENERATOR (SSPG) (ADVANCED)

These settings exist for backwards compatability with an outdated protocol. See earlier versions of the manual for more information.

WEB MANAGEMENT INTERFACE REFERENCE

CONFIGURATION MANAGEMENT

A Master Conﬁguration File allows the user to associate IP addresses, conﬁguration ﬁles, and names with speciﬁc nodes.

See RCT Tool Manul

CREATING A MASTER CONFIGURATION FILE

1. Create a temporary directory in an easy to ﬁnd location with a recognizable name.

2. Connect a node to the computer and set conﬁguration as desired.

3. Click “Node Conﬁguration” > “Conﬁg Management.”

4. Click the “Store” button. A prompt will appear to choose where to save the conﬁguration ﬁle. Save the conﬁguration ﬁle to the directory created in Step 1.

5. Repeat steps 2 - 4 for each conﬁguration ﬁle that will be uploaded to nodes. Ensure all conﬁguration ﬁle names are unique.

6. In Microsoft Excel, create a spreadsheet with 4 columns: Serial Number, IP address, Proﬁle, and Name.

7. For each node to be managed by the Master Conﬁguration File, enter that node’s Serial Number, IP address, the name of the conﬁguration ﬁle saved in Step 4 to be uploaded to the node, and the name of the node. Ensure all IP addresses and names are unique.

8. Click “File” > “Save As” and save the spreadsheet as a CSV (Comma delimited) .csv ﬁle with a recognizable name in the directory created in Step1.

9. Create a .zip ﬁle containing the CSV ﬁle created in Step 8 and ALL conﬁguration ﬁles created in Step 4.

WEB MANAGEMENT INTERFACE REFERENCE

UPLOADING A MASTER CONFIGURATION FILE

1. Ensure all nodes in the Master Conﬁguration File are in the node list.

2. Click “Node Conﬁguration” > “Conﬁg Management.”

3. In the Load Conﬁguration menu, select “network (require all)” or “network (any available)” to upload conﬁguration settings to all nodes in the network. The “network (require all)” setting will require all nodes in the network be available for any changes to be applied. If not all nodes are available, no changes will be applied. The “network (any available)” setting will apply changes to available nodes only.

4. Click the “Choose File” button to ﬁnd the the .zip ﬁle created in Step 9 above.

5. Click the “Load” button to upload conﬁguration settings to other nodes in the network.

STORE CONFIGURATION TO FILE

Clicking the “Store” button allows the web browser to download the node’s conﬁguration settings as an encrypted ﬁle. Environment variables, node lists, and network defaults are stored.

THE CRYPTO KEY IS NOT STORED IN THE CONFIGURATION FILE.

WEB MANAGEMENT INTERFACE REFERENCE

QUICK SETUP

Both “Load Conﬁguration from File” and “Quick Setup” load conﬁguration settings from a conﬁguration ﬁle. The difference between the functions is that “Quick Setup” loads all the conﬁguration settings from a ﬁle (except Node Identiﬁers), whereas “Load Conﬁguration from File” loads user-selected conﬁguration categories. Quick Setup facilitates the conﬁguration of a large number of nodes when the nodes share identical conﬁguration settings. Note speciﬁcally that the only conﬁguration categories that must be speciﬁed when using Quick Setup are Node Identiﬁers, which include IP Address, Node Name, and SSPG SA ID.

1. Click “Node Conﬁguration” > “Conﬁg Management.” Scroll down to the “Quick Setup” menu.

2. Click the “Base Conﬁguration File” ﬁeld or the “Browse...” button and select the conﬁguration ﬁle to load to the device. Note that the conﬁguration ﬁle should be from a device with the same ﬁrmware version and hardware setup (e.g. numbers and types of radios) as the device to which it is being uploaded.

3. Insert the IP Address, Node Name, SSPG SA ID, and SSPG SA Name to be set to the device.

4. Click the “Quick Setup” button. All settings from the conﬁguration ﬁle will be applied to the device except IP Address, Node Name, SSPG SA ID, and SSPG SA Name, which will populate from the values speciﬁed.

Select the conﬁguration

ﬁle to upload.

All settings from the conﬁguration ﬁle are written to

the device except Node Identiﬁers, which are speciﬁed

here.

WEB MANAGEMENT INTERFACE REFERENCE

RESET TO FACTORY CONFIGURATION

The Web Management Interface contains a “Reset to Factory Conﬁguration” feature to remove all custom conﬁguration and restore the node to its factory settings.

1. Click “Node Conﬁguration” > “Conﬁg Management.” Scroll to the bottom of the page. Resetting the node to its factory settings will remove all custom conﬁguration and will reset the IP address to 10.4.1.254.

2. To retain the node name and IP address after the reset, ensure that the box labelled “Keep node name and IP address” is checked. The node’s Crypto Key will NOT be zeroized. For instructions on how to zeroize the Crypto Key from the Security Conﬁguration page, refer to the “Security” section.

3. When you are ready to remove all custom conﬁguration and restore the node to its factory settings, click the “Reset” button.

WEB MANAGEMENT INTERFACE REFERENCE

TRACKING ANTENNA CONTROL

For information on setting up the Tracking Antenna Control system hardware, please refer to the Tracking Antenna Manual.

TRACKING CONFIGURATION

To enable the tracking antenna control system, go to the “Node Conﬁguration” tab and click on the “Tracking Conﬁguration” button. On the drop down menu, select “Enabled” next to the Tracking Antenna Control option.

MENU ITEM MENU ITEM DESCRIPTION

Tracking Antenna Mode

Home Position Returns the Pan/Tilt unit to its home position for storage

Track Node Instructs the node to track another Wave Relay

Track Node w/ Initial Coordinates

Track via ESD Feed

Track via CoT Feed

Track via CDF Feed

Track Node Selects a Wave Relay

ESD UDP Port Deﬁnes the port number to receive coordinate updates via an external ESD

Use this menu to choose the source of the coordinates to track or to return the Pan/Tilt unit to its home position for storage. Possible tracking sources include another Wave Relay®, a ESD (Exploitation Support Data) feed, a CoT (Cursor on Target) feed, or CDF (Common Data Feed).

®

function works by receiving Wave Relay® visualization packets from the chosen node. Be sure that the tracked node is conﬁgured to transmit Google™ Earth Network Visualization packets.

This setting is the same as the “Track Node” setting (instructs the node to track another Wave Relay® node position), but also allows manual entry of initial coordinates in cases where no position has yet been received from the tracked Wave Relay® node.

Points the antenna based on coordinate data received via an external ESD feed

Points the antenna based on coordinate data received via an external CoT feed

Points the antenna based on coordinate data received via an external CDF feed

®

node to track from the Node List

feed

node position - This

WEB MANAGEMENT INTERFACE REFERENCE

CoT UDP Port Deﬁnes the port number to receive coordinate updates via an external

CDF UDP Port Deﬁnes the port number to receive coordinate updates via an external

Compass Reading

CoT feed

CDF feed

Speciﬁes the heading of the Pan/Tilt unit - The heading is deﬁned as the compass reading taken when standing behind the Pan/Tilt unit while facing the large circular electrical connector. For more information, see the compass reading step of the setup procedure.

INITIAL COORDINATE SETTINGS

These ﬁelds allow speciﬁcation of the initial antenna target location in cases where coordinates have not yet been received from the tracked node.

MENU ITEM MENU ITEM DESCRIPTION

Initial Latitude Sets the tracked node’s initial latitude in decimal degrees

Initial Longitude

Initial Altitude Sets the tracked node’s initial altitude in feet above GPS ellipsoid, which is

Sets the tracked node’s initial longitude in decimal degrees

approximately equal to feet above mean sea level (MSL)

FINE TUNING SETTINGS

MENU ITEM MENU ITEM DESCRIPTION

Compass Tweak

Elevation Tweak

Deﬁnes the heading correction factor for tracking, speciﬁed in decimal degrees - Use a positive number for right/clockwise correction and a negative number for left/counterclockwise correction.

Deﬁnes the elevation correction factor for tracking, speciﬁed in decimal degrees - Use a positive number for upward correction and a negative number for downward correction.

WEB MANAGEMENT INTERFACE REFERENCE

PUSH-TO-TALK (PTT)

Push-to-Talk (PTT) voice is supported on all Wave Relay® nodes. By default, Wave Relay® supports single-channel PTT voice on a speciﬁed multicast IP address and port. You can “switch channels” by specifying an alternate IP address or port. Users can talk or listen (but cannot do both simultaneously). Transmissions from an individual user are broadcast to all other users on the network. Only one person can talk at a time. If a user tries to talk when another user is transmitting, a busy tone will be heard.

To conﬁgure Push-to-Talk settings, click “Node Conﬁguration” > “PTT Conﬁguration.”

WEB MANAGEMENT INTERFACE REFERENCE

PUSH-TO-TALK CONFIGURATION

MENU ITEM MENU ITEM DESCRIPTION

Run PTT subsystem

Volume Deﬁnes the default earpiece volume for headsets - Valid values are 0

Microphone Level Deﬁnes the default microphone level for headsets - Valid values are 0

Transmit Mode

Transmit on keypress

Transmit continuously

Tones on Transmit

Tones on Receive Enables or disables an audible checktone (either Beeps or Verbal) at

Advanced Features

Silynx PTT Headset

Microphone Voltage

Enables or disables push-to-talk voice

through 125 (Values above 100 are digitally ampliﬁed)

through 100 or “auto.” The “auto” conﬁguration uses automatic gain control for microphone input and is recommended for most users.

Audio is transmitted only when the PTT button is pressed on the headset.

Audio is continuously transmitted. Other nodes may monitor the channel only. Selected Channel audio transmissions will interrupt monitored continuously transmitted audio.

Enables or disables an audible checktone (either Beeps or Verbal) at

the beginning of each transmitted message

the beginning of each received message

If advanced features are able to be conﬁgured, a drop down menu will appear. If advanced features are not able to be conﬁgured, a string will appear displaying the current conﬁguration. Available features vary among Wave Relay® hardware versions.

Enables the serial port on the node (Silynx PTT Headsets require this setting be enabled)

Enables +5V power supply voltage on the center pin of the 6-pin headset connector (required for some headsets)

WEB MANAGEMENT INTERFACE REFERENCE

CHANNEL DEFINITIONS

The Wave Relay

®

Network has 16 channels numbered 0 through 15. Channel 0 is the Flash Override Channel and has priority over channels 1-15. The Flash Override Channel will always be enabled and is capable of both receiving and transmitting audio. Channels 1-15 are normal audio channels. Audio channels 1-15 may be conﬁgured to be either Selected Channels or Monitored Channels. Flash Override Channel audio will interrupt both Selected Channel audio and Monitored Channel audio. Each channel is deﬁned by a Multicast Address and a Multicast Port. To display the Multicast Address and Multicast Port ﬁelds, click the “Show Customization” button. After Channel Deﬁnition settings have been conﬁgured, click the “Set All” button.

MENU ITEM

Channel Displays the channel number to be conﬁgured

Selected A Selected Channel is capable of both receiving and transmitting PTT audio.

Monitor A Monitored Channel is only capable of receiving audio transmissions. Both

Name Deﬁnes the text name of the channel

Multicast Address

Multicast Port

MENU ITEM DESCRIPTION

Selected Channel audio will NOT interrupt Flash Override Channel audio. Selected Channel audio will interrupt Monitor Channel audio. A user MUST choose a Selected Channel from channels 1-15.

Flash Override Channel audio and Selected Channel audio will interrupt Monitored Channel audio. A user may select none to multiple channels to be Monitored Channels.

Deﬁnes the Multicast Address for the channel (Valid values are within the range of 224.0.0.0 through 239.255.255.255) - Note that each talk group must have a unique multicast address and port. This ﬁeld is only visible if the “Show Customization” button has been clicked

Deﬁnes the Multicast UDP port for audio trafﬁc (Valid values are within the range of 1 through 65534) - Note that each talk group must have a unique multicast address and port. This ﬁeld is only visible if the “Show Customization” button has been clicked.

FLASH OVERRIDE

Flash Override is a new feature which allows audio to be sent to all nodes even if those nodes have selected a different audio channel.

• A ﬂash override transmission is triggered by a “tap-tap-hold” of the PTT

button(button is pressed and released twice quickly in succession immediately preceding the normal hold for the duration of the transmission.)

• The user will hear a unique “triple” tone on TX and RX to indicate a ﬂash over-

ride.

WEB MANAGEMENT INTERFACE REFERENCE

AUDIBLE NOTIFICATIONS

MENU ITEM MENU ITEM DESCRIPTION

Low Battery Enables or disables audible notiﬁcation when the battery is depleted to

In-Net/Out-Net Enables or disables an audible notiﬁcation when a chosen node enters or

Node to Monitor Selects a node to monitor for In-Net/Out-Net audible notiﬁcations from

5% (notiﬁcation will occur every 5 minutes)

leaves the network

the node list (only visible when In-Net/Out-Net Audible Notiﬁcations are enabled)

WEB MANAGEMENT INTERFACE REFERENCE

RS-232

The RS-232 serial-over-Ethernet feature can be used for remote control of a distant serial device via the Wave Relay® network. A typical application is for a local PC to control a distant pan/tilt camera via a serial link. If the PC and camera cannot be colocated, then two Wave Relay® devices can be used to connect them (similar to an old-fashioned modem-to-modem link). Thus, the serial port on the local PC can be hardwired to a local Wave Relay® device and the serial port on the distant camera can be hardwired to a distant Wave Relay® device. Communication between the two devices is then relayed via the Wave Relay® network. This is called “serial-to-serial mode.”

Alternatively, the PC can run emulation software that allows it to create a local virtual COM port that is conﬁgured to communicate directly with a distant networkenabled serial port (e.g. as described in RFC 2217). Thus, the distant camera is hardwired to a distant Wave Relay® device and the local PC can then connect directly to the distant device via Ethernet. This is called “virtual-to-serial mode.”

To access RS-232 conﬁguration settings, click “Node Conﬁguration” > “RS-232 Conﬁguration.”

WEB MANAGEMENT INTERFACE REFERENCE

CONFIGURING SERIAL-TO-SERIAL MODE

1. Connect the serial device to be controlled (e.g. pan/tilt unit) to the serial port on the distant Wave Relay® device. Conﬁgure the RS-232 Conﬁguration Mode on the distant Wave Relay device to “Server” and set the Serial-over-Ethernet Port as desired. Set the Serial-over-Ethernet Protocol to “Raw.” Set the serial port parameters (Baud, Data Bits, Parity, Stop Bits, Flow Control) to match those of the connected serial device (factory defaults for the Wave Relay® device are 57600 baud, 8 data bits, no parity, 1 stop bit, no ﬂow control). Click “Save” to store the settings.

2. Connect the local serial device (e.g. PC) to the serial port on the local Wave Relay® device. Set the RS-232 Conﬁguration Mode on the local Wave Relay® device to “Client,” and set the Server IP Address and Serial-over-Ethernet Port to be those of the distant Wave Relay® device as conﬁgured in Step 1 above. Also set the serial parameters (Baud, Data Bits, Parity, Stop Bits, Flow Control) to match those of your local serial device. Click “Save” to store the settings.

CONFIGURING VIRTUAL-TO-SERIAL MODE

1. Connect and conﬁgure the serial device to be controlled (e.g. pan/tilt unit) as per Step 1 above for Conﬁguring Serial-to-Serial mode. Set the Serial-overEthernet Protocol to whichever protocol is supported by your virtual client (“Raw” or “Telnet RFC 2217”).

2. Install Virtual COM port software on the local PC (Eltima Serial to Ethernet Connector v5.0 for Windows has been tested and is known to work). Conﬁgure the virtual COM port in your software to connect to the distant serial port via the address/port as conﬁgured in Step 1.

SERIAL-TO-SERIAL MODE

WEB MANAGEMENT INTERFACE REFERENCE

VIRTUAL-TO-SERIAL MODE

CONFIRMING SERIAL CONNECTIVITY

Once you have conﬁgured the server and client as described above, the network connection status is displayed on the “Current Status” line. Statistics are displayed for transmitted and received bytes to/from the attached serial device, which can be used to debug the connection to your serial hardware. For example, if the “tx” byte count increases but the “rx” byte count remains zero, bytes are being sent out on the Wave Relay® serial port but no reply is being received (possibly due to reversed transmit and receive wires in your cable). To update the status and statistics, click the “Refresh” button.

WEB MANAGEMENT INTERFACE REFERENCE

RS-232 CONFIGURATION

MENU ITEM MENU ITEM DESCRIPTION

Mode

Disabled The serial-over-Ethernet feature is turned off.

Server Use this mode when the device to be controlled (e.g. pan/tilt unit) is

Client Use this mode when a controller (e.g. PC) is connected to a Wave

Echo Mode Instructs the serial port to retransmit any received serial data out

Serial Port Selects the primary or secondary RS-232 port on the Wave Relay®.

Serial-over-Ethernet TCP Port

Server IP Address Dﬁnes the default IP address of the serial-over-Ethernet server

Serial-over-Ethernet Protocol

Raw Serial messages are encapsulated into packets and are transmitted

Telnet - RFC2217 Serial messages are encapsulated into packets as per RFC2217,

Baud Valid settings are 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600,

Data Bits Valid settings are 7 or 8 bits.

Parity Valid settings are None, Even, or Odd.

Stop Bits Valid settings are 1 or 2 bits.

Flow Control Valid choices are XON/XOFF (a.k.a. software ﬂow control) or None.

connected to a Wave Relay® device serial port.

®

device serial port.

Relay

on its transmit pin (useful for debugging serial connections in cases where Rx/Tx pins might be accidentally reversed in the cable)

Deﬁnes the TCP port for serial-over-Ethernet trafﬁc

unaltered over the network. This setting requires that the RS232 parameters (baud, parity, etc.) be set correctly at both ends. This setting is typically used in serial-to-serial mode, e.g. when a hardware serial controller is used to control a remote serial device.

and baud settings are automatically controlled by the protocol. This setting is typically used in serial-to-virtual mode, e.g. when a PC with virtual COM ports is used to control a remote serial device.

or 115200.

Note that RTS/CTS (a.k.a. hardware ﬂow control) is not supported.

WEB MANAGEMENT INTERFACE REFERENCE

DATE/TIME

When possible, Wave Relay® will obtain the current date and time from its internal GPS hardware. However, in cases where the GPS is unlocked (or absent), you may alternatively specify an NTP server or manually set the current date and time. You may also set the local time zone. The default time zone is UTC (a.k.a. GMT or Zulu time). Note that some Wave Relay® device models do not contain a clock, and thus these settings may be unavailable.

Wave Relay® also supports a sleep feature that allows scheduling remote unit power down and power up in order to conserve battery life and/or maintain radio silence. Sleep can be performed as a one-time power cycle or can be scheduled for repetitive daily or hourly operation. The sleep feature is not available on all Wave Relay® device models.

To access Date/Time Conﬁguration, click “Node Conﬁguration” > “Date/Time.”

WEB MANAGEMENT INTERFACE REFERENCE

DATE/TIME SETTINGS

MENU ITEM MENU ITEM DESCRIPTION

Current System Time Displays the current system time (in both UTC and current time

Set local timezone Sets the local time zone as ±12 hours from UTC (settings also

Manually set time Manually sets the current local time

NTP Server Address Deﬁnes the address, if available, of the NTP (Network Time Proto-

Scheduled powerdown/powerup

One time only Instructs nodes to perform a one-time power down and power

Daily Instructs nodes to perform a daily powerdown and powerup as

Twice daily Instructs nodes to perform a twice-daily powerdown and powerup

Hourly Instructs nodes to perform hourly powerdowns and powerups as

Set powerdown time Selects the hour and minute (in local time zone) for unit power-

Set powerup time Selects the hour and minute (in local time zone) for unit powerup -

Set 2nd powerdown time

Set 2nd powerup time Selects the hour and minute (in local time zone) for second daily powerup

zone if not UTC)

include select US and other global time zones)

col) server for automatic clock synchronization

up at speciﬁed times as set in the Set powerdown time and Set powerup time ﬁelds

speciﬁed in the Set powerdown time and Set powerup time ﬁelds

as speciﬁed in the Set powerdown time, Set powerup time, Set 2nd powerdown time, and Set 2nd powerup time ﬁelds

speciﬁed in the Set powerdown time and Set powerup time ﬁelds

- powerdown and powerup times are speciﬁed as minutes past the hour (00 through 59)

down - If the powerdown/power up frequency is set to “Hourly,” then you may only set minutes past the hour.

If the powerdown/powerup frequency is set to “Hourly,” then you may only set minutes past the hour. If the powerup time is before the powerdown time, then the powerup happens the next day (or hour).

Selects the hour and minute (in local time zone) for second daily powerdown - This setting is valid only when power down/power up frequency is set to “Twice Daily.”

- If the powerup time is before the powerdown time, then the powerup happens the next day (or hour). This setting is valid only when powerdown/ powerup frequency is set to “Twice Daily.”

WEB MANAGEMENT INTERFACE REFERENCE

AMPLIFIER CONFIGURATION

Any Wave Relay® device (MPU4, MPU3 Single, MPU3 Dual, and Quad Radio Router) may be conﬁgured for use with an ampliﬁer. To access Ampliﬁer Conﬁguration settings, select the “Node Conﬁguration” tab, then click the “Ampliﬁer Conﬁguration” button. The page will display separate sections for each radio so that the ampliﬁer settings for each radio may be conﬁgured separately.

Depending on the radios installed in the node, several different options will appear. If the radio installed in the node does not support the use of an ampliﬁer, the section on the page corresponding to that radio will display the message “Ampliﬁer not supported on this Radio.”

If the radio installed in the node does support the use of an ampliﬁer, a drop-down menu titled “Ampliﬁer Setting” will appear. On the drop-down menu, select the ampliﬁer setting that matches the ampliﬁer being used with the radio.

WEB MANAGEMENT INTERFACE REFERENCE

VALID AMPLIFIER SETTINGS ARE:

• WR-AMP-0900 900 MHz Ampliﬁer

• WR-AMP-1370 1.3 GHz Ampliﬁer

• WR-AMP-2400 2.3 - 2.5 GHz Ampliﬁer

When the Ampliﬁer Conﬁguration page for a QAMP device is accessed from the Web Management Interface, the sections for some radios may display the message “Ampliﬁer Speciﬁed by Pelican Case.” The ampliﬁer settings for these radios have already been conﬁgured.

WARNING: WAVE RELAY® AMPLIFIERS REQUIRE REGULATED 28V DC POWER SUPPLY (DEVIATIONS WILL CAUSE DEGRADATION IN PERFORMANCE).

WEB MANAGEMENT INTERFACE REFERENCE

NETWORK STATUS

The “Network Status” tab in the Web Management Interface displays information about every node in the node list. Each time a network status feature is used, all nodes in the node list will attempt to be contacted and the combined results will be displayed on one page. This feature is useful for managing a network without having to individually connect to each node. Refer to the “Node Status” section for more detailed information about a speciﬁc feature.

WEB MANAGEMENT INTERFACE REFERENCE

UNIT INFO

MENU ITEM MENU ITEM DESCRIPTION

Node Node name and IP address

Uptime Operating time since last

Firmware Version

Temperature Temperature (in celsius) of

Supply Voltage Voltage supplied to node

RCT Battery Voltage

System Clock Current system time of node

NEIGHBOR STATUS

The Neighbor Status page displays a list of all neighboring nodes in the network.

of each node in the network

node power on or reboot

Firmware version on node

node

Voltage of real-time-clock keep-alive battery. 3 year shelf life when not powered

MENU ITEM MENU ITEM DESCRIPTION

Node Name and IP address of node

Result • Interface on managed node used

• Name of each neighbor node

• Interface on the neighbor node used

• Receive Signal to Noise Ratio of each connection to each

Interface on each neighbor node

WEB MANAGEMENT INTERFACE REFERENCE

MANET MONITOR

MANET Monitor displays information about active nodes heard on the MANET.

MENU ITEM MENU ITEM DESCRIPTION

Serial Serial number of all nodes active on MANET network

Node Node name and IP address of each neighbor node

Vector Distance and direction from local node to remote node (Only valid if both

Altitude Altitude (above sea level) of each node in MANET network

Neighbors Number of neighbor nodes (includes neighbors transmitting over the air

Battery Battery percentage remaining (Only valid when using a MPU4 with

Receive SNR Signal-to-Noise Ratio at which local node hears remote node

Reverse SNR Signal-to-Noise Ratio at which the local node is heard by the remote node

nodes have a GPS ﬁx or location)

and via Ethernet)

compatible smart battery)

WEB MANAGEMENT INTERFACE REFERENCE

GPS STATUS

MENU ITEM MENU ITEM DESCRIPTION

Node Name and IP address of each node

Result

Fix Type How node is connected (3D, 2D, or none)

Latitude Latitude of current node

Longitude Longitude of current node

Altitude Altitude above sea level of current node

Speed Speed of node (m/s) in the horizontal plane

Track Path of travel with respect to the Earth expressed in degrees - 000 degrees is

Climb Speed of node (m/s) in the vertical plane

Fix Time When node obtained a satellite ﬁx

Number of satellites

ID/PRN ID/PRN of each satellite node is connected to

Signal Strength of the connection between node and each satellite

NTP Server Status of the NTP server (available or unavailable)

North (angle increases clockwise through 360 degrees)

Number of satellites node is connected to

WEB MANAGEMENT INTERFACE REFERENCE

NETWORK TRAFFIC LOAD

MENU ITEM MENU ITEM DESCRIP-

Node Name and IP address of

Result

Mbps Total Total Mbps used on this

Mbps Wave

®

Relay

Mbps Wave Relay® Sent

Mbps Wave Relay® Received

Mbps Control Total Mbps used for

Mbps Control Ack Mbps used to control

Mbps Control RTS/CTS

Mbps Other Mbps used for other

Mbps Sent Total Mbps used for all

Mbps Sent Unicast Mbps used for Unicast

Mbps Sent Broadcast/Multicast

Mbps Received Total Mbps used to

Mbps Received Unicast

Mbps Received Broadcast/ Multicast

TION

each node

interface

Total Mbps used by Wave Relay

Mbps used by Wave Relay® to send

Mbps used by Wave Relay® to receive

control functions

ACK

Mbps used to control RTS/CTS

functions

transmissions

Mbps used for Broadcast/Multicast transmissions

receive all transmissions

Mbps used to receive Unicast transmissions

Mbps used to receive Broadcast/Multicast transmissions

®

NETWORK VISUALIZATION

This feature displays situational awareness GPS mapping for all network nodes in Google™ Earth. The drop down menu selects how often Google™ Earth will refresh its data from the visualization server. To access Network Visualization:

1. Click the “Network Visualization” button. The browser will attempt to open a ﬁle called “nodemonitor.kml.” This ﬁle contains geographic data to be displayed in Google™ Earth.

2. Either open the ﬁle directly from the pop-up dialogue box or save the ﬁle to the computer and open it separately.

The management computer must have Google™ Earth installed for this feature to work.

WEB MANAGEMENT INTERFACE REFERENCE

NETWORK DEFAULT CHECK

The Network Default Check page checks and displays which settings on each node are NOT set to the Network Default values. If a setting shows up in this list, it means that that particular setting on that node is NOT managed by Network Defaults and will NOT be changed if the Network Default is changed.

NETWORK CHANNEL PLAN

The Channel Plan page displays the channel center frequency and channel width for every radio of every node in the node list. Additionally, if “Network Default” is displayed before the channel information, it means that that setting is managed by Network Defaults.

MENU ITEM

Node Name and IP address of

Result

Radio X Radio(s) in use on each

Channel Y/Z

MENU ITEM DESCRIPTION

each node

node

Channel center frequency/ channel width for each radio

WEB MANAGEMENT INTERFACE REFERENCE

STATION LIST

The Station List page displays the list of 802.11 client stations connected to radios with 802.11 access point enabled for each node.

MENU ITEM MENU ITEM DESCRIPTION

Node Name and IP address of each node

Result

Radio X Radio on the node

macaddr MAC address of each client device

rssi Signal strength to client device

last_rx Time (in seconds) since a packet was

IP FLOW LIST

The IP Flow List page displays the list of IP data ﬂows passing through node sorted by measured throughput.

connected to the access point

last received

MENU ITEM MENU ITEM DESCRIPTION

Node Name and IP address of each node

Result

Mbit/s Speed of each IP data ﬂow in Mbps

Pkt/s Number of packets transferred each second for each IP data ﬂow

Total bytes Number of bytes transferred for each IP data ﬂow

Destination IP IP address of destination node

Source IP IP address of source node

Direction/ Interfaces

Direction of and interfaces used by each IP data ﬂow (MANET, Ethernet X, or this node)

WEB MANAGEMENT INTERFACE REFERENCE

IP MULTICAST STATUS

IP Multicast Status displays IGMP Snooping and IP Multicast Pruning status. This feature shows a table with a row for each multicast group, displaying an “F” if that group is forwarded over the MANET, or a “-” if it is not.

There are known issues with IGMP in Windows X P.

ATTENTION: PRIOR TO FW VERSION 18.4.0, NETWORK WILL NOT FUNCTION PROPERLY IF PRUNING STATUS IS NOT CONSISTENT THROUGHOUT THE NETWORK.

MENU ITEM MENU ITEM DESCRIPTION

Node Name and IP address of each

Result

Group Multicast address of nodes con-

Registered to receive packets for group

node

nected to managed node

Interface used to receive data for each multicast address (Ethernet X or MANET)

WRoIP STATUS

WRoIP Status displays the Wave Relay® over IP gateway status for each node.

MENU ITEM MENU ITEM DESCRIPTION

Node Name and IP address of each node

Result

Gateway Which gateway the node is connected to as well as the priority of that gate-

Elected Whether the gateway is elected or not

Election Priority Election priority of the gateway over other gateways/number of other WRoIP

way

gateways on the IP network.

WEB MANAGEMENT INTERFACE REFERENCE

NETWORK CONFIGURATION

The “Network Conﬁguration” tab contains options to manage the network node list, conﬁgure the network defaults, upgrade and reboot the network, and change the network password.

WEB MANAGEMENT INTERFACE REFERENCE

NETWORK NODE LIST

The Node List is a list of IP Addresses of nodes managed by the Web Management Interface.

1. To manage the Node List, click “Network Conﬁguration” > “Network Node List.”

2. Enter the IP Address of a node in the “Manually Add IP(s)” ﬁeld and click the “Add” button to add the node associated with that IP Address to the Node List. Alternatively, nodes may be added from the “Other Nodes on Network” window if they are detected by the network. These nodes may be added individually with the “Selected IPs” button or all at once with the “All” button. The “Clear Nodes” button will clear the “Other Nodes on Network” window.

3. Repeat this process for every node to be managed. The IP Addresses will appear in the “Management Node List” window on the left side of the screen (see screenshot). The Node List may be rearranged and edited from the “Management Node List” window.

4. When the list is populated with all IP Addresses/Nodes, click the “Push Management List to Network” button to send the Managed IP List to all nodes in the network. Node names auto populate across the network.

WEB MANAGEMENT INTERFACE REFERENCE WEB MANAGEMENT INTERFACE REFERENCE

NETWORK DEFAULTS

Network Defaults facilitate the management of a large number of nodes. Network Defaults enable administrators to manage settings on all network nodes speciﬁed in the Node List rather than to manage individual settings on single nodes. Any changes to Network Defaults will affect only nodes that are in the Node List. To ensure proper Network Default conﬁguration, conﬁrm that the Node List is current and conﬁgured properly before making changes to Network Defaults. Note that individual nodes will adopt Network Default settings only if those individual nodes are conﬁgured to use Network Defaults.

SHOW/HIDE ADVANCED FIELDS

For convenience, this button allows you to show (or hide) many of the less frequently used node conﬁguration ﬁelds. The default is to hide the advanced ﬁelds (and thus display a briefer page). If you choose to show the advanced ﬁelds, your choice will remain in effect when you revisit the page. Advanced ﬁelds are indicated as such in the descriptions below.

MANAGEMENT SETTINGS

MENU ITEM MENU ITEM DESCRIPTION

Netmask Deﬁnes default netmask for the Web Management Interface

Gateway Deﬁnes default gateway for the Web Management Interface

WEB MANAGEMENT INTERFACE REFERENCE

RADIO CHANNEL SETTINGS

Each radio must be a assigned a center frequency and bandwidth. These settings determine the “channel” on which the node operates. Up to 16 Network Default channel settings may be conﬁgured to facilitate management of groups of radios of different nodes.

MENU ITEM MENU ITEM DESCRIPTION

Channel Name Each channel can be assigned a name which to be used in status func-

Frequency Each radio should be a assigned a frequency. Two radios must be set

Bandwidth Each radio should be assigned a bandwidth. Two radios must be set to

Max Link Distance

Channel Density The channel density setting controls how aggressively the radios

Radio Preference Radio Preference instructs the routing protocol to prefer links on a radio

tions.

to the same frequency in order to communicate. A warning will be displayed if the frequency setting does not match the radio hardware. A node with a radio channel set to “Network Default X” in node conﬁguration will automatically change center frequency and bandwidth if the settings for “Network Default X” are changed in Network Default conﬁguration.

the same bandwidth in order to communicate. Bandwidth should be increased for shorter distances and decreased for increased distances.

Max Link Distance should be set to the upper bound of how long any individual link in the network may need to be. All nodes on the network MUST be set to the same Max Link Distance. A node with a radio channel set to “Network Default X” in node conﬁguration will automatically change Max Link Distance if the settings for “Network Default X” are changed in Network Default conﬁguration.

compete for access to the shared medium. A number of nodes will be displayed in parentheses after each menu item. Choose the menu item that corresponds to the number of nodes in your network. A node with a radio channel set to “Network Default X” in node conﬁguration will automatically change Channel Density if the settings for “Network Default X” are changed in Network Default conﬁguration.

(consider them lower cost than normal). This can be used to help shift trafﬁc towards radios running on certain channels.

None: None is the default factory setting. All links are considered equally. Medium: Routing protocol is more likely to use this radio to forward trafﬁc. High: Routing protocol is signiﬁcantly more likely to use this radio to forward

trafﬁc. A node with a radio channel set to “Network Default X” in node conﬁguration will automatically change Radio Preference if the settings for “Network Default X” are changed in Network Default conﬁguration.

WEB MANAGEMENT INTERFACE REFERENCE

MANET

MENU ITEM MENU ITEM DESCRIPTION

IP Multicast Routing AUTO: Node will prune multicast packets that are not requested

Root Gateway Priority (advanced)

DHCP Server Filter (advanced)

SNAP OUI (advanced)

DHCP SERVER (ADVANCED)

If enabled, the DHCP server will serve IP addresses to devices connected to the node via the wired Ethernet or wireless 802.11 Access Point interfaces.

(default, most efﬁcient setting for network). PULL ALL MULTICAST: Node will accept all multicast packets it hears on the network. Note: Windows CE/XP computers do not respond to IGMP Multicast Group Queries sent by Wave Relay nodes. “Pull All Multicast” should be used in networks with Windows CE/XP computers to work around this issue.

HIGH: Any node in your network directly connected to wired infrastructure should have priority set to “HIGH.”

MEDIUM: All other non-mobile routers should be set to “MEDIUM.” LOW: Mobile routers should be set to “LOW.”

ALLOW: Device will pass DHCP messages FROM a DHCP server

which is bridged directly by one of its interfaces. Only the devices which are directly wired to the switch where the DHCP server resides need to be set to “ALLOW.” BLOCK: Device will not bridge any DHCP reply packets that it picks up off of any of its bridged interfaces. By setting all of the nodes in the network (except the nodes physically connected to the real DHCP server) to “BLOCK,” you will ensure that users of your system will always use the correct DHCP server.

Controls the Subnetwork Access Protocol Organizationally Unique Identiﬁer - The factory OUI, 0018A6, is registered to Persistent Systems, LLC with the IEEE. SNAP OUI is used to identify Wave Relay Changing this ﬁeld allows the user to obscure which protocol is being used by the system. All nodes must be set to the same value or they will not communicate.

®

packets.

MENU ITEM MENU ITEM DESCRIPTION

DHCP Server Scope

Selects which DHCP clients the DHCP server serves IP addresses to. “Local Ethernet/AP Only” serves IP addresses to nodes connected via Ethernet or a wireless 802.11 Access Point. “Entire Network” serves IP addresses to all nodes in the network. “Local Ethernet/AP Only” is the recommended setting.

WEB MANAGEMENT INTERFACE REFERENCE

Address Range Start

Address Range End

Netmask Netmask assigned to DHCP clients

Default Gateway Gateway assigned to DHCP clients

DNS Server 1 Primary DNS server assigned to DHCP clients

DNS Server 2 Secondary DNS server assigned to DHCP clients

WINS Server WINS server assigned to DHCP clients

Lease Time DHCP lease time (defaults to 1 hour)

Start of range of IP addresses assigned to DHCP clients

End of range of IP addresses assigned to DHCP clients

ACCESS POINT (AP) SETTINGS (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

802.11 Access Point (advanced)

The following ﬁelds are only visible when the 802.11 Access Point is “Enabled.”

ESSID (advanced) Sets the name of the network that the access point advertises

ESSID Visibility (advanced) The ESSID can be conﬁgured to be “Visible” or “Hidden.”

AP Security (advanced) Enables or disables 802.11 security on the Access Point - Only

Each radio can be conﬁgured to function as an 802.11 access point. Standard clients such as laptops with built in 802.11 cards may access this system. If the AP is disabled, the ESSID and Beacon Interval conﬁguration options have no effect. For maximum performance, always disable the 802.11 AP unless it is required. To use a radio as a 802.11 Access Point, the radio MUST be set to a valid 802.11 frequency (Numbered channels in the frequency selection menu i.e. “2412 / 5-20 MHz - Channel 1”) and the channel width MUST be set to 20 MHz.

to clients.

Generally, the ESSID is conﬁgured to be “Visible” to make it easy for clients to connect to the access point. For additional security/privacy the ESSID can be conﬁgured as “Hidden.”

WPA2-PSK (Wi-Fi Protected Access v2 with pre-shared keys) is supported.

WEB MANAGEMENT INTERFACE REFERENCE

WPA2 Passphrase (advanced)

AP Broadcast Rate (advanced)

AP Beacon Interval (advanced)

Sets a shared passphrase when AP Security is set to WPA2

- The passphrase should be an ASCII string of length 8-63 characters, excluding these characters: ‘,”\&/<>

Controls the rate at which broadcasts are transmitted from an 802.11 Access Point - Increasing this rate can signiﬁcantly increase network capacity but will reduce the range of client connectivity. If the rate is set too high, client devices will have trouble receiving broadcast packets from the 802.11 access point.

The 802.11 access point can send beacons at an interval between twice and ten times per second.

ETHERNET SETTINGS (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

Routing Metric (advanced) Deﬁnes link capacity for the routing protocol - A value lower

than the 100 Mbps default should be used when nodes are connected via non-switched Ethernet (e.g. a third-party point-to-point wireless link). The metric allows the routing protocol to make an intelligent decision on if it is better to route over this Ethernet port or use an alternate route which is faster.

VLAN SETTINGS (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

VLAN ID (advanced) Each VLAN-aware bridge port is assigned a VLAN ID. Un-

VLAN Priority (advanced)

VLAN Trunking (advanced)

tagged frames received by the port are tagged with the speciﬁed VLAN ID. Frames that are sent by the port which have a VLAN tag matching the speciﬁed VLAN ID will have their tags removed (i.e. they are sent by the port untagged).

Speciﬁes the 802.11 priority of the VLAN tag added to

untagged frames received by this port

Controls the ﬁltering of VLAN tagged frames that do NOT match

this port’s VLAN ID. When trunking is enabled (trunk port), ALL non-matching VLAN tagged frames are passed (no ﬁltering). When trunking is disabled (access port), all non-matching VLAN tagged frames are blocked (ﬁltered)

WEB MANAGEMENT INTERFACE REFERENCE

BANDWIDTH MANAGEMENT SETTINGS (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

IP Mcast/ Bcast Limit (advanced)

WAVE RELAY SETTINGS (ADVANCED)

WRoIP allows the Wave Relay® network to extend over and seamlessly interact with a large routed IP network. In order to use this capability, one or more Wave Relay® nodes must be setup as WRoIP gateways. A WRoIP gateway must be directly connected to an appropriately conﬁgured IP router.

MENU ITEM MENU ITEM DESCRIPTION

WRoIP (advanced) WRoIP gateway nodes must have the WRoIP protocol

Multicast Routing Mode (advanced)

Netmask (advanced) Deﬁnes the netmask of the IP subnet speciﬁc to the directly

Gateway (advanced) Deﬁnes the IP address of the IP router in the IP subnet spe-

Deﬁnes the maximum bandwidth allowed for IP multicast or broadcast network trafﬁc received on the given interface and retransmitted onto the Wave Relay megabits/sec (Mbps). To disable the limit, set to zero

®

OVER IP (WROIP)

®

network. Trafﬁc in excess of this limit will be dropped. Units are

enabled on the interface directly connected to the IP router. All other nodes should have the WRoIP protocol disabled. When the WRoIP protocol is enabled on an interface, the interface will no longer function as a normal Wave Relay Ethernet port for connecting Ethernet devices: it will only work for connecting the IP router.

Selects pruning options for multicast trafﬁc:

IP Router Controlled (default): All multicast packets travel to the cloud network Wave Relay Controlled: Only subscribed multicast feeds are passed to the cloud network to reduce network trafﬁc congestion.

connected IP router interface

ciﬁc to the directly connected IP router interface - WRoIP protocol packets will be forwarded to this IP address in order to be sent over the IP network.

®

WEB MANAGEMENT INTERFACE REFERENCE

MTU (advanced) Deﬁnes the maximum transmissible unit size for the IP net-

Multicast Address (advanced) Deﬁnes the multicast IP address used by the WRoIP protocol

UDP Port (advanced) Deﬁnes the UDP port used by WRoIP protocol packets

work - WRoIP protocol packets sent over the IP network will be limited to this MTU. All nodes that communicate over the IP network should be set to the same value.

- The next higher IP multicast address will also be used by the WRoIP protocol. For example, if 239.255.90.67 is set as the multicast address, both 239.255.90.67 and 239.255.90.68 will be used.

POSITION SETTINGS (ADVANCED)

MENU ITEM MENU ITEM DESCRIPTION

Update Interval Controls how often nodes report information back to visualiziation server

ESD UDP Port Deﬁnes the port number to receive position updates via an external ESD

External Update UDP Port

CoT UDP Port Deﬁnes the port number to receive position updates via external CoT feed

CDF UDP Port Deﬁnes the port number to receive position updates via an external CDF

with visualization enabled - A smaller value will result in smoother movement of mobile nodes in Google™ Earth. A shorter update interval uses more bandwidth.

feed

Deﬁnes the port number to receive position updates via the external Wave

®

‘wr-update-gps’ command

Relay

feed

WAVE RELAY® SA (GOOGLE™ EARTH NETWORK VISUALIZATION) SETTINGS

MENU ITEM MENU ITEM DESCRIPTION

Report to Visualization Server

Enable or disables network visualization for all nodes set to use the Network Default (typically the whole network) - Visualization is also used by the Tracking Antenna system and should be enabled on nodes that you wish to be able to track.

WEB MANAGEMENT INTERFACE REFERENCE

Visualization Server (advanced)

Deﬁnes the IP address to which nodes will send their visualization updates

(may be either a multicast address [224.0.0.0,239.255.255.255] or the unicast address of a device running the visualization server.) - The factory default is a multicast address. When using multicast, each node sends visualization updates to the entire connected network. All nodes run a visualization server and receive updates from all other connected nodes. When using unicast, each node sends visualization updates to the selected address only. If the unicast address is the management IP address of a node, that node will run a visualization server to receive the updates. Visualization updates are sent from the management IP address, so the selected address must be reachable by all nodes with visualization enabled; it should be either in the same subnet or reachable through the default gateway. Multicast operation allows the most robust visualization for mobile networks because it provides true distributed operation with partitions and merges. Unicast operation requires all visualization users to be able to contact the selected server, but offers reduced network overhead for larger static networks.

CURSOR ON TARGET (COT) SETTINGS (ADVANCED)

This feature enables transmission of local positioning information to a CoT server on the network. This feature is not available on all ﬁrmware versions.

MENU ITEM MENU ITEM DESCRIPTION

Send Position Enables or disables transmission of CoT packets to server

Server IP Deﬁnes the IP address of the CoT server - This IP address can be a unicast or

Server Port Deﬁnes the UDP port of the CoT server

Type Deﬁnes the contents of the CoT “type” attribute

multicast address

SIMPLE SA PACKET GENERATOR (SSPG) (ADVANCED)

These settings exist for backwards compatability with an outdated protocol. See earlier versions of the manual for more information.

WEB MANAGEMENT INTERFACE REFERENCE

PTT SETTINGS

MENU ITEM MENU ITEM DESCRIPTION

Enable Push-toTalk

Volume Deﬁnes the default earpiece volume for headsets - Valid values are 0

Microphone Level Deﬁnes the default microphone level for headsets - Valid values are 0

Transmit Mode (advanced)

Transmit on keypress

Transmit continuously

Tones on Transmit (advanced)

Tones on Receive (advanced)

Advanced Features (advanced)

Silynx PTT Headset

Microphone Voltage

Enables or disables the PTT subsystem to allow push-to-talk communication among voice-equipped devices

through 100. Optimal values vary with headset manufacturer.

Audio is transmitted only when the PTT button is pressed on the headset.

Audio is continuously transmitted. Other nodes may monitor the channel only. Selected Channel audio transmissions will interrupt monitored continuously transmitted audio.

Enables or disables an audible checktone (either Beeps or Verbal) at

the beginning of each transmitted message

Enables or disables an audible checktone (either Beeps or Verbal) at the beginning of each received message

Enables the serial port on the node (Silynx PTT Headsets require this setting be enabled)

Enables +5V power supply voltage on the center pin of the 6-pin headset connector (required for some headsets)

CHANNEL DEFINITIONS (ADVANCED)

The Wave Relay

®

Network has 16 channels numbered 0 through 15. Channel 0 is the Flash Override Channel and has priority over channels 1-15. Channels 1-15 are normal audio channels. Each channel is deﬁned by a Multicast Address and a Multicast Port. After Channel Deﬁnition settings have been conﬁgured, click the “Set All” button.

WEB MANAGEMENT INTERFACE REFERENCE

MENU ITEM

Channel Displays the channel number to

Name Deﬁnes the text name of the

Multicast Address

Multicast Port

MENU ITEM DESCRIPTION

be conﬁgured

channel

Deﬁnes the Multicast Address for the channel Valid values are within the range of 224.0.0.0 through

239.255.255.255. Note that each talk group must have a unique multicast address and port.

Deﬁnes the Multicast UDP port for audio trafﬁc - Valid values are within the range of 1 through 65534. Note that each talk group must have a unique multicast address and port.

FLASH OVERRIDE

Flash Override is a new feature which allows audio to be sent to all nodes even if those nodes have selected a different audio channel.

• A ﬂash override transmission is triggered by a “tap-tap-hold” of the PTT

button(button is pressed and released twice quickly in succession immediately preceding the normal hold for the duration of the transmission.)

• The user will hear a unique “triple” tone on TX and RX to indicate a ﬂash over-

ride.

AUDIBLE NOTIFICATIONS

MENU ITEM MENU ITEM DESCRIPTION

Low Battery Enables or disables audible notiﬁcation when the battery is depleted to

In-Net/Out-Net Enables or disables an audible notiﬁcation when a chosen node enters or

Node to Monitor

5% (notiﬁcation will occur every 5 minutes)

leaves the network

Selects a node to monitor for In-Net/Out-Net audible notiﬁcations from the node list

WEB MANAGEMENT INTERFACE REFERENCE

RS-232 SETTINGS (ADVANCED)

The RS-232 serial-over-Ethernet feature can be used for remote control of a distant serial device via the Wave Relay® network. A typical application is for a PC to control a remotely located pan/tilt camera via a serial link. Two operational modes are supported: “serial-to-serial” mode and “virtual-to-serial” mode. For further description, see RS-232 Conﬁguration Help.

MENU ITEM MENU ITEM DESCRIPTION

Mode

Disabled The serial-over-Ethernet feature is turned off.

Server Use this mode when the device to be controlled (e.g. pan/tilt unit)

Client Use this mode when a controller (e.g. PC) is connected to a Wave

Echo Mode Instructs the serial port to retransmit any received serial data

Serial Port (advanced) Selects the primary or secondary RS-232 port on the Wave Relay

Serial-over-Ethernet TCP Port (advanced)

Server IP Address (advanced)

Serial-over-Ethernet Protocol (advanced)

Raw Serial messages are encapsulated into packets and are

Telnet - RFC2217 Serial messages are encapsulated into packets as per RFC2217,

Baud (advanced) Valid settings are 300, 1200, 2400, 4800, 9600, 19200, 38400,

Data Bits (advanced) Valid settings are 7 or 8 bits.

Parity (advanced) Valid settings are None, Even, or Odd.

Stop Bits (advanced) Valid settings are 1 or 2 bits.

Flow Control (advanced)

is connected to a Wave Relay

Relay® device serial port.

out on its transmit pin (useful for debugging serial connections in cases where Rx/Tx pins might be accidentally reversed in the cable)

Deﬁnes the TCP port for serial-over-Ethernet trafﬁc

Deﬁnes the default IP address of the serial-over-Ethernet server

transmitted unaltered over the network. This setting requires that the RS-232 parameters (baud, parity, etc.) be set correctly at both ends. This setting is typically used in serial-to-serial mode, e.g. when a hardware serial controller is used to control a remote serial device.

and baud settings are automatically controlled by the protocol. This setting is typically used in serial-to-virtual mode, e.g. when a PC with virtual COM ports is used to control a remote serial device.

57600, or 115200.

Valid choices are XON/XOFF (a.k.a. software ﬂow control) or None. Note that RTS/CTS (a.k.a. hardware ﬂow control) is not supported.

®

device serial port.

®

.

WEB MANAGEMENT INTERFACE REFERENCE

DATE/TIME SETTINGS

MENU ITEM MENU ITEM DESCRIPTION

Set local timezone Sets the local time zone as ±12 hours from UTC (settings also

NTP Server Address Deﬁnes the address, if available, of the NTP (Network Time Proto-

Automatic powerdown/powerup