LUM0107AA Z9 P2 PE2 User Reference Manual v1122 Jul 2019
LUM0107AA Z9 P2 PE2 User Reference Manual v1122 Jul 2019
Firmware v1.1.2.2
User-Reference Manual
Safety Information
The products described in this manual can fail in a variety of modes due to misuse, age, or malfunction and is not
designed or intended for used in systems requiring fail-safe performance, including life safety systems. Systems
with the products must be designed to prevent personal injury and property damage during product operation
and in the event of product failure.
Warning! Do not remove or insert any of the cables while the unit is powered on unless the area is
known to be free of ignition concentrations of flammable gasses or vapors.
Warranty Information
FreeWave Technologies, Inc. warrants the FreeWave® ZumLink Z9-P2 or Z9-PE2 (Product) that you have
purchased against defects in materials and manufacturing for a period of two years from the date of shipment,
depending on model number. In the event of a Product failure due to materials or workmanship, FreeWave will,
at its discretion, repair or replace the Product. For evaluation of Warranty coverage, return the Product to
FreeWave upon receiving a Return Material Authorization (RMA). The replacement product will remain under
warranty for 90 days or the remainder of the original product warranty period, whichever is longer.
IN NO EVENT WILL FREEWAVE TECHNOLOGIES, INC., ITS SUPPLIERS, OR ITS LICENSORS BE LIABLE FOR ANY DAMAGES ARISING
FROM THE USE OF OR INABILITY TO USE THIS PRODUCT. THIS INCLUDES BUSINESS INTERRUPTION, LOSS OF BUSINESS
INFORMATION, INABILITY TO ACCESS OR SEND COMMUNICATION OR DATA, PERSONAL INJURY OR DAMAGE, OR OTHER LOSS
WHICH MAY ARISE FROM THE USE OF THIS PRODUCT. THE WARRANTY IS EXCLUSIVE AND ALL OTHER WARRANTIES EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE
ARE EXPRESSLY DISCLAIMED.
FreeWave’s Warranty does not apply in the following circumstances:
1. If Product repair, adjustments, or parts replacements are required due to accident, neglect, or undue
physical, electrical, or electromagnetic stress.
2. If Product is used outside of FreeWave specifications as stated in the Product's data sheet.
3. If Product has been modified, repaired, or altered by Customer unless FreeWave specifically authorized
such alterations in each instance in writing. Where applicable, this includes the addition of conformal
coating.
Warning! The Z9-P2 is sold as a multi-board solution, assembled at the FreeWave factory. Any
alteration, including the separation of the individual boards, voids the FreeWave warranty.
Warning! The Z9-PE2 is sold as a fully enclosed device, assembled at the FreeWave factory.
Opening the device voids the FreeWave warranty.
Table of Contents
Preface 14
1. Overview 16
1.1. Communication Method 17
1.2. ZumBoost Technology 17
1.2.1. Adaptive Spectrum Learning 17
1.2.2. Forward Error Correction 17
1.3. Packet Aggregation 17
1.3.1. Packet Compression 18
1.4. IQ Application Environment 18
2. Included & User-supplied Equipment 19
2.1. Included Equipment 19
2.2. User-supplied Equipment 19
3. Port Connections and Pinout Assignments 20
3.1. Z9-P2 Port Connections 21
3.2. Z9-PE2 Port Connections 21
3.3. Serial and Ethernet Port Details 22
3.4. Serial Pinout Assignments 23
4. Installation 24
5. Configuration 27
5.1. Drag and Drop Configuration 28
5.2. CLI Configuration 34
5.2.1. Connect the Z9-P2 or Z9-PE2 to the Computer 34
5.2.2. Access the CLI and Change the IP Address and nodeId 35
5.3. Web Interface Configuration 39
5.3.1. Setup the Computer IP Address Configuration 40
5.3.2. Web Interface Configuration - Z9-P2 or Z9-PE2 44
6. Creating a Basic ZumLink Gateway and Endpoint Network 46
7. IQ Application Environment 48
7.1. Download the IQ Application Environment 49
7.2. Drag and Drop - Installation of the IQ Application Environment 52
7.3. Web Interface - Installation of IQ Application Environment 56
7.4. CLI Activation of the IQ Application Environment 60
7.4.1. Get the License File from FreeWave 60
7.4.2. Drag and Drop the License File onto the Z9-P2 or Z9-PE2 61
7.4.3. Activate the IQ Application Environment 64
7.4.4. Verify Successful Licensing and Activation 67
7.5. Web Interface Activation of the IQ Application Environment 69
Preface
Additional Information
Note: Use the http://support.freewave.com/ website to download the latest documentation for the
Z9-P2 or Z9-PE2.
Registration is required to use this website.
Document Styles
This document uses these styles:
l Parameter setting text appears as: [Page=radioSettings]
l File names appear as: configuration.cfg.
l File paths appear as: C:\Program Files (x86)\FreeWave Technologies.
l User-entered text appears as: xxxxxxxxx.
Caution: Indicates a situation that MAY cause damage to personnel, the radio, data, or
network.
Warning! Indicates a situation that WILL cause damage to personnel, the radio, data, or
network.
1. Overview
Note: The frequency hopping capability is available at all bandwidths and the single channel (DM)
operation is available for bandwidths of at least 500 kHz.
l Adds redundant information to a data stream to detect packet errors and corrects them to
Note: **See Approved Antennas (on page 196) for detailed information.
Approved antennas can be purchased directly from FreeWave.
Port Connections
l Z9-P2 Port Connections (on page 21)
l Z9-PE2 Port Connections (on page 21)
l Serial and Ethernet Port Details (on page 22)
Pinout Assignments
l Serial Pinout Assignments (on page 23)
Note: ***See the COM Parameters (on page 198) for detailed information.
4. Installation
l The Z9-P2 or Z9-PE2 is approved to operate with an input voltage range of +6 to +30 VDC
that can supply at least 0.9 Amps at 6 VDC.
l See the Technical Specifications (on page 453) for additional information.
FREEWAVE Recommends: All input power supply wires should be at least 20 AWG (0.52 mm2)
wires.
A dedicated and stable power supply line is preferred.
The power supply used MUST provide more current than the amount of current drain listed in the
specifications for the product and voltage (at least 0.49 Amps at 12V).
Warning! Use electrostatic discharge (ESD) protectors to protect the Z9-P2 or Z9-PE2 from
electric shock and provide filtered conditioned power with over-voltage protection.
Note: The images in this procedure are for Windows® 7 and/or Windows® 10 and Firefox®.
Procedure
1. Install an FCC-approved antenna.
2. Connect the antenna feed line to the Z9-P2 or Z9-PE2.
Warning! Only FCC approved antennas may be used. See Approved Antennas (on
page 196).
The antenna must be professionally installed on a fixed, mounted, and permanent
outdoor structure to satisfy RF exposure requirements.
Any antenna placed outdoors must be properly grounded.
Use extreme caution when installing antennas and follow all instructions included with
the antenna.
Important!: Torque to lock the conductors: 0.5-0.6 N-m. Torque for the mating jack: 0.3 N-m.
Important!: The USB does NOT power the Z9-P2 or Z9-PE2. It only provides a configuration
interface.
5. Configuration
Important!: Windows® 7 or later is required to use the USB Drag and Drop.
Note: The images in this procedure are for Windows® 7 and/or Windows® 10 and Firefox®.
Procedure
1. Connect the USB cable to the computer and the Micro USB end to the Z9-P2 or Z9-PE2.
The FreeWave Drivers and ZumLink windows may open. (Figure 7 and Figure 8)
6. Paste (press <Ctrl+V>) the copied config.txt file into the designated folder.
Important!: The txt file must be copied to a separate location on the computer to edit.
The file CANNOT be changed directly in the ZumLink folder.
8. Click the Notepad® File menu and click Save As. Figure 11
Note: The file name used in this example is for illustration purposes only.
Any name can be used. NO SPACES are allowed in the file name.
12. Click the Save as type list box arrow and select All Files.
Figure 12: Save As dialog box with All Files (*.*) selected.
l systemInfo.deviceName
l systemInfo.deviceId
Note: See the systemInfo Parameters (on page 336) for detailed information about the
parameters.
l [Page=radioSettings]
l radioSettings.txPower
l radioSettings.rfDataRate***
l radioSettings.radioMode
l radioSettings.networkId***
l radioSettings.nodeId**
l radioSettings.radioFrequency***
l radioSettings.radioHoppingMode***
l radioSettings.beaconInterval
Note: See radioSettings Parameters (on page 285) for detailed information about these
settings.
**Each radio with the same networkId must have a UNIQUE nodeId.
A unique nodeId is required so that only one node will unicast an acknowledgment.
Otherwise, two or more nodes will unicast an acknowledgment that may collide.
***These are the Golden Settings and they MUST match between all radios with the
same networkId.
15. For illustration, the radioSettings.radioMode was changed from Endpoint to Gateway.
Figure 13
16. After changes are completed, press <Ctrl+S> or, on the File menu, click Save to save the
updated file.
21. Drag and drop the .cfg or .cfg.txt file to the ZumLink window. Figure 15
Figure 15: Drag and Drop the .cfg File to the ZumLink Window
22. Wait for the .cfg or .cfg.txt file to integrate with the ZumLink config.txt file.
Note: The more changes made in the .cfg or .cfg.txt file, the longer the Z9-P2 or Z9-PE2
takes to process the file and update the config.txt file.
If very few changes are made, the .cfg or .cfg.txt file does not appear in the window.
When the config.txt is updated, the changed .cfg or .cfg.txt file is removed from the list of
files in the ZumLink window.
23. Double-click the result.txt file to verify there are No errors Detected with the identified
changes in the file. Figure 16
Note: If an error is detected, the result.txt file will indicate that errors are present.
24. As appropriate, repeat the Drag and Drop procedure to correct any errors.
25. Optional: Double-click the config.txt file to view and verify the new Z9-P2 or Z9-PE2
configuration.
26. Optional: Change the Passwords (on page 163).
Note: The images in this procedure are for Windows® 7 and/or Windows® 10 and Firefox®.
2. Continue with Access the CLI and Change the IP Address and nodeId (on page 35).
5.2.2. Access the CLI and Change the IP Address and nodeId
Note: This procedure provides a Tera Term terminal connection to the FreeWave CLI. Other
terminal emulators (e.g., HyperTerminal, PuTTY) may be used.
The images in this procedure are for Windows® 7 and/or Windows® 10 and Firefox®.
1. On the computer connected to the Z9-P2 or Z9-PE2, open a terminal program (e.g., Tera
Term http://ttssh2.osdn.jp/).
2. In Tera Term, click the File menu and select New Connection. Figure 19
The Tera Term: Serial Port Setup dialog box opens. Figure 22
Figure 22: Tera Term: Serial Port Setup dialog box with Default Settings
6. Using Figure 22 as the example, verify the COM port settings are:
Speed (Baud Rate): 115200
Data (Databits): 8 bit
Parity: none
Stop bits: 1 bit
7. Click OK to save the changes and close the dialog box.
8. In the Tera Term window, press <Enter>.
The FreeWave CLI Login returns.
9. Enter admin for the Username and press <Enter>.
13. Optional: Change the gateway (on page 263) and the netmask (on page 267) addresses, if
required.
14. At the > prompt, type nodeId=nnn and press <Enter>.
Note: Go to http://support.freewave.com/ to login and download the latest firmware for the
Z9-P2 or Z9-PE2.
Registration is required to use this website.
1. Connect the CAT5e / CAT6 Ethernet cable to the Z9-P2 or Z9-PE2 Ethernet port and the
Ethernet port on the computer.
2. On the computer, open the Windows® Control Panel.
3. View the Control Panel window by Category and click Network and Sharing Center.
Figure 25
The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box opens. Figure 30
9. IMPORTANT: Make a note of the current settings (to reverse this procedure later).
12. Click OK to save the changes and close the dialog box.
13. Click Close twice to close the Local Area Connection Properties and Local Area
Connection Status dialog boxes.
14. Continue with Web Interface Configuration - Z9-P2 or Z9-PE2 (on page 44).
1. Verify the Setup the Computer IP Address Configuration (on page 40) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
7. In the IP Address text box, enter the new IP Address for the Z9-P2 or Z9-PE2.
8. Optional: Change the gateway (on page 263) and the netmask (on page 267) addresses, if
required.
9. Click the Update button to save the changed information.
Warning! At this point, for Ethernet connections, the connection to the Z9-P2 or Z9-PE2
is disabled.
10. Re-connect to the Z9-P2 or Z9-PE2 using the new IP Address entered in Step 7.
11. In the Configuration window, click the Radio Settings tab.
The Radio Settings parameters are shown in Figure 34:
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
12. In the Node ID text box, enter the same unique 3-digit number used in the last octet of
the IP Address entered in Step 7.
13. Click the Update button to save the changed information.
14. Continue with: Change the Passwords (on page 163).
Note: The basic network described in this procedure is created by using either the Drag and Drop
Configuration (on page 28), the CLI Configuration (on page 34), or the Web Interface Configuration
(on page 39) procedure.
Procedure
Note: This example procedure is specific for CLI configuration.
Note: See radioSettings Parameters (on page 285) for detailed information.
5. For the other radio in the network, at the > prompt, type
radioSettings.radioMode=Endpoint and press <Enter>.
6. Verify the radioSettings.networkId= setting is the same on ALL radios in the
network.
7. IQ Application Environment
The Z9-P2 or Z9-PE2 employs the IQ Application Environment to provide application deployment.
Procedure
1. On the http://support.freewave.com/ web page, open the Firmware window for the Z9-P2
or Z9-PE2.
Important!: If continuing from the v1122-Download the Update File procedure for the
Firmware_v1_1_2_2.zip file, return to the Firmware window. Figure 36
4. Click OK.
The Enter name of file to save to dialog box opens. Figure 39
5. Search for and select a location to save the .zip file to and click Save.
The Enter name of file to save to dialog box closes.
6. Open a Windows® Explorer window and find the location where the .zip file was saved.
7. Double-click the .zip file.
8. Extract the files from the .zip file into the parent location.
Note: The file includes the .pkg file used for the IQ Application Environment installation.
9. Continue with:
l Drag and Drop - Installation of the IQ Application Environment (on page 52)
1. Verify the Download the IQ Application Environment (on page 49) procedure is completed.
2. IMPORTANT: Install the 1_Device_Firmware_v1_1_2_2.pkg file first.
See v1122-Firmware Update - Drag and Drop.
3. Locate and select the downloaded 3_Optional_IQ_Developer_Edition_v1_1_2_2.pkg
upgrade file. Figure 40
4. Drag and drop the .pkg file on to the ZumLink window. Figure 41
The .pkg file will disappear after a few minutes.
Important!: If the .pkg file is NOT accepted, a Windows® error message appears
immediately. Figure 42
a. If the .pkg file was rejected, change the extension of the .pkg file to .pkg.txt and select
that file.
b. Drag and drop the .pkg.txt file to the ZumLink window.
The .pkg.txt file will disappear after a few minutes.
The Copying message appears. Figure 43
Caution: DO NOT click the Cancel button to stop the drag-n-drop process.
If the drag-n-drop process is canceled during the file copy process, the Z9-P2 or Z9-PE2
cannot be accessed in Windows® File Explorer.
If this happens, reboot the Z9-P2 or Z9-PE2 and re-start the drag-n-drop process.
When the file is copied, the Z9-P2 or Z9-PE2 window is similar to Figure 44:
Note: If, after 6-10 minutes, the .pkg file has NOT disappeared, refresh the ZumLink
window.
Warning! DO NOT remove power from the Z9-P2 or Z9-PE2 during or immediately after
the firmware update process!
Wait until the Home window (on page 378) Web Interface is accessible before removing
power from the Z9-P2 or Z9-PE2 device.
If power is removed prematurely during the update process, the Web Interface pages
may not be accessible.
To recover from a failed Web Interface update, use the v1122-Firmware Update - Drag
and Drop procedure to reinstall the .pkg file and WAIT for the file update process to
complete.
5. Optional: View the updated rteTemplateVersion (on page 315) in the sys.info.txt file to
verify the update information. Figure 45
Important!: For the v1.1.2.2 update, these settings should have this information:
systemInfo.deviceFirmwareVersion=FWT1122TB.66
Web Interface - Device Firmware Version is FWT1122TB.66
systemInfo.rteTemplateVersion=FWT1122TP.16
Web Interface - Rte Template Version is FWT1122TP.16
If neither of these are listed in their respective settings, repeat the upgrade procedure.
6. Contact FreeWave Technical Support (on page 14) for the license key file.
7. Continue with:
l CLI Activation of the IQ Application Environment (on page 60)
1. Verify the Download the IQ Application Environment (on page 49) procedure is completed.
2. IMPORTANT: Install the 1_Device_Firmware_v1_1_2_2.pkg file first.
See v1122-Firmware Update - Drag and Drop.
Important!: If continuing from the v1122-Firmware Update - Web Interface-ZL procedure for
the Firmware_v1_1_1_2.zip file, go to Step 6.
3. Using a CAT5e / CAT6 Ethernet cable, connect the Z9-P2 or Z9-PE2 Ethernet port to the
computer's Ethernet port.
4. Open a web browser.
5. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
Note: If the User Name or Password were changed, enter the applicable information.
Note: When using the Web Interface on a computer with Windows® 8 or Windows® 10,
clicking Cancel does not halt the upload process.
The File Upload window refreshes and shows the uploaded file.
Warning! DO NOT remove power from the Z9-P2 or Z9-PE2 during or immediately after
the firmware update process!
Wait until the Home window (on page 378) Web Interface is accessible before removing
power from the Z9-P2 or Z9-PE2 device.
If power is removed prematurely during the update process, the Web Interface pages
may not be accessible.
To recover from a failed Web Interface update, use the v1122-Firmware Update - Drag
and Drop procedure to reinstall the .pkg file and WAIT for the file update process to
complete.
The System Info window opens showing the updated firmware on the Z9-P2 or Z9-PE2.
Figure 51
Important!: For the v1.1.2.2 update, these settings should have this information:
systemInfo.deviceFirmwareVersion=FWT1122TB.66
Web Interface - Device Firmware Version is FWT1122TB.66
systemInfo.rteTemplateVersion=FWT1122TP.16
Web Interface - Rte Template Version is FWT1122TP.16
If neither of these are listed in their respective settings, repeat the upgrade procedure.
14. Contact FreeWave Technical Support (on page 14) for the license key file.
15. Continue with:
l CLI Activation of the IQ Application Environment (on page 60)
Note: See the Web Interface Activation of the IQ Application Environment (on page 69) to use the
Web Interface to activate the IQ Application Environment
Warning! The process of activating IQ Application Environment activates a fresh copy of the
IQ environment.
If IQ has already been activated, this procedure will erase any user-generated content and
settings in the existing Linux development environment.
These are the basic steps to license and activate the IQ Application Environment:
A. Get the License File from FreeWave (on page 60)
B. Drag and Drop the License File onto the Z9-P2 or Z9-PE2 (on page 61)
C. Activate the IQ Application Environment (on page 64)
D. Verify Successful Licensing and Activation (on page 67)
Note: Where nnnnnnnnnn is the 10-digit Serial number of the Z9-P2 or Z9-PE2.
5. Search for and select a location to save the .LIC file to.
6. Continue with Drag and Drop the License File onto the Z9-P2 or Z9-PE2 (on page 61).
7.4.2. Drag and Drop the License File onto the Z9-P2 or Z9-PE2
Note: The images in this procedure are for Windows® 7 and/or Windows® 10 and Firefox®.
1. Connect the USB cable to the computer and the Micro USB end to the Z9-P2 or Z9-PE2.
The FreeWave Drivers and Z9-P2 or Z9-PE2 windows open. Figure 52 and Figure 53
4. Drag and drop the License_nnnnnnnnnn.LIC file on to the ZumLink window. Figure 56
Figure 56: Drag and Drop the License_nnnnnnnnnn.LIC file to the ZumLink
window
5.
Figure 57: Failed .LIC Message dialog box
a. If the .LIC file was rejected, change the extension of the .LIC file to .LIC.txt and select
that file.
b. Drag and drop the .LIC.txt file to the ZumLink window.
4. Click OK.
The Tera Term New Connection dialog box closes.
The Tera Term window opens.
5. In the Tera Term window, press <Enter>.
The FreeWave CLI Login returns.
6. Enter admin for the Username and press <Enter>.
7. Enter admin for the Password and press <Enter>.
Note: If the User Name or Password were changed, enter the applicable information.
The password does not appear when typing - it looks blank.
Verification Settings
Parameter Value
radioFirmwareVersion (on page 341) FWT1071TR.42
deviceFirmwareVersion (on page 337) FWT1122TB.66
rteVersion (on page 344) FWT1122TP.16
rteTemplateVersion (on page 344) FWT1122TP.16
licenses (on page 340) Custom Apps
Note: See the CLI Activation of the IQ Application Environment (on page 60) to use the CLI to
activate the IQ Application Environment.
Warning! The process of activating IQ Application Environment activates a fresh copy of the
IQ environment.
If IQ has already been activated, this procedure will erase any user-generated content and
settings in the existing Linux development environment.
These are the basic steps to license and activate the IQ Application Environment:
A. Get the License File from FreeWave (on page 69)
B. Setup the Computer IP Address Configuration (on page 70)
C. Download the License File (on page 74)
D. Activate the IQ Application Environment (on page 77)
E. Verify Successful Licensing and Activation (on page 81)
Note: Where nnnnnnnnnn is the 10-digit Serial number of the Z9-P2 or Z9-PE2.
5. Search for and select a location to save the .LIC file to.
6. Continue with Setup the Computer IP Address Configuration (on page 70).
1. Connect the CAT5e / CAT6 Ethernet cable to the Z9-P2 or Z9-PE2 Ethernet port and the
Ethernet port on the computer.
2. On the computer, open the Windows® Control Panel.
3. View the Control Panel window by Category and click Network and Sharing Center.
Figure 65
The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box opens. Figure 70
9. IMPORTANT: Make a note of the current settings (to reverse this procedure later).
12. Click OK to save the changes and close the dialog box.
13. Click Close twice to close the Local Area Connection Properties and Local Area
Connection Status dialog boxes.
14. Continue with Download the License File (on page 74).
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
5. Enter admin in both the User Name and Password text boxes and click OK.
The Login dialog box closes.
Note: If the User Name or Password were changed, enter the applicable information.
8. Click Open.
The dialog box closes and the File Upload window returns showing the selected
file. Figure 76
9. Click Send.
The File Upload window refreshes and shows the uploaded file.
10. Continue with Activate the IQ Application Environment (on page 77).
2. Click Continue.
The Tera Term: New Connection window opens. Figure 78
3. Click OK.
The Tera Term New Connection dialog box closes.
The SSH Authentication window opens. Figure 79
4.
Figure 79: SSH Authentication window
Note: If the User Name or Password were changed, enter the applicable information.
The password does not appear when typing - it looks blank.
14. Continue with Verify Successful Licensing and Activation (on page 81).
Verification Settings
Parameter Value
radioFirmwareVersion (on page 341) FWT1071TR.42
deviceFirmwareVersion (on page 337) FWT1122TB.66
rteVersion (on page 344) FWT1122TP.16
rteTemplateVersion (on page 344) FWT1122TP.16
licenses (on page 340) Custom Apps
There are different Editions of IQ available that incorporate developer tools and/or 3rd-party
software. All IQ Editions allow access to the Linux environment through the devuser login.
Once a developer is ready to integrate an application into IQ or build an application within IQ, they
should first visit FreeWave’s GitHub wiki environment that provides guidance on a wide range of
topics. (https://github.com/FreeWaveTechnologies/ZumIQ)
Procedure
1. Verify Successful Licensing and Activation (on page 81) is completed.
2. Log in to the FreeWave CLI as devuser.
The default password is devuser.
A Linux Bash prompt appears. Figure 86
Figure 86: Linux Bash Prompt for the Z9-P2 or Z9-PE2 DEVUSER
Note: The IQ GitHub site contains many valuable tools including demonstrations, sample
applications, troubleshooting guides and other information that can be very useful.
5. Scroll to the bottom of the Main page and click the Wiki link for IQ app development
information. Figure 88
Figure 88: Wiki link on the FreeWave GitHub ZumIQ Main Page
6. In the Wiki, go to Contents sidebar > Reference to locate the Installed Packages for the
version on the Z9-P2 or Z9-PE2.
This section provides procedure information about administration of the Z9-P2 or Z9-PE2
parameters.
l Change the COM Parameters (on page 91)
l Change the Data Path Parameters (on page 94)
l Change the Encryption Parameters (on page 96)
l Change the Io Ex Com Parameters (on page 98)
l Change the Local Diagnostics - Monitored Node (on page 99)
l Change the Modbus Parameters (on page 101)
l Change the Network Parameters (on page 103)
l Change the NTP Parameters (on page 105)
l Change the Radio Settings Parameters - Endpoint (on page 107)
l Change the Radio Settings Parameters - Endpoint-Repeater (on page 109)
l Change the Radio Settings Parameters - Gateway (on page 111)
l Change the Radio Settings Parameters - Gateway-Repeater (on page 114)
l Change the Security Parameters (on page 117)
l Change the Services Parameters (on page 119)
l Change the SNMP Parameters (on page 121)
l Change the System Info Parameters (on page 123)
l Change the Terminal Server Relay Parameters (on page 125)
1. Connect the CAT5e / CAT6 Ethernet cable to the Z9-P2 or Z9-PE2 Ethernet port and the
Ethernet port on the computer.
2. On the computer, open the Windows® Control Panel.
3. View the Control Panel window by Category and click Network and Sharing Center.
Figure 89
The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box opens. Figure 94
9. IMPORTANT: Make a note of the current settings (to reverse this procedure later).
12. Click OK to save the changes and close the dialog box.
13. Click Close twice to close the Local Area Connection Properties and Local Area
Connection Status dialog boxes.
14. Optional: Continue with these Web Interface administration procedures:
l Change the COM Parameters (on page 91)
15. Optional: Continue with the Web Interface - Network Diagnostics (on page 127).
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click either the COM1 or COM2 tab to access their respective COM parameters. Figure 97
or Figure 98
Note: See the COM Parameters (on page 198) for detailed information about the parameters.
The parameters for COM1 and COM2 are the same except for the TerminalServerPort (on
page 209) parameter setting.
Important!: The RTS and CTS signals are ONLY available for COM2.
The RTS and CTS signals are NOT supported for COM1.
i. In the Delay Before Send MS text box, enter the milliseconds of time delay.
j. In the Break Before Send Us text box, enter the number of milliseconds the COM port
will send a break signal.
k. In the Terminal Server Port text box, enter the designated TCP port number.
l. In the Terminal Server Time Out text box, enter the number of seconds the Terminal
Server remains open without transmitting or receiving data from the network.
Note: TxBytes (on page 211), RxBytes (on page 208), and connectionDrops (on page 200)
are Read-only parameters.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Data Path tab to access the Data Path parameters. Figure 100
Note: See the dataPath Parameters (on page 216) for detailed information about the
parameters.
b. In the OTA Max Fragment Size text box, enter the maximum fragment size, in bytes,
sent over the air.
c. Click the FEC Rate list box arrow and select the Forward Error Correction (FEC) rate.
d. Click the Aggregate Enabled list box arrow and select True to enable this parameter
and increase throughput of small packets.
e. In the Route Min Signal Margin Thresh text box, enter the minimum threshold signal
margin in dB.
f. In the MAC Table Entry Age Timeout text box, enter the number of seconds before
an inactive entry in the MAC Table ages out and expires.
8. Click the Update button to save the changed information.
FREEWAVE Recommends: When viewing local diagnostics, if the RadioBadCRC (on page 241)
count is more than 15-20% of the total transmitted packets (the RadioLLTx (on page 244) count),
enabling the fecRate (on page 219) setting is beneficial.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Encryption tab to access the Encryption parameters. Figure 102
Note: See the encryption Parameters (on page 230) for detailed information about the
parameters.
7. Click the Encryption Mode list box arrow and select the designated encryption mode.
8. In the KeyX text box, enter either the 128- or 256-bit key in 16 or 32 hexadecimal format
respectively.
9. Click the Active Key list box arrow and select the designated active key.
Note: See the activeKey (on page 231) parameter for additional information.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Local Diagnostics tab to access the Local Diagnostics parameters.
Note: See the localDiagnostics Parameters (on page 235) for detailed information about the
parameters.
8. In the Monitored Node text box, enter the nodeId (on page 296) to monitor.
9. Click the Update button to save the changed information.
FREEWAVE Recommends: When viewing local diagnostics, if the RadioBadCRC (on page 241)
count is more than 15-20% of the total transmitted packets (the RadioLLTx (on page 244) count),
enabling the fecRate (on page 219) setting is beneficial.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Modbus tab to access the Modbus parameters. Figure 106
Note: See the modbus Parameters (on page 252) for detailed information about the
parameters.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Network tab to access the Network parameters. Figure 108
Note: See the network Parameters (on page 262) for detailed information about the
parameters.
e. In the Txqueuelen text box, enter the maximum number of packets to hold in the
transmit queue.
f. In the MTU text box, enter the maximum transmission unit.
g. Click the Netmask Filter Enabled list box arrow and select True to enable the bridge
firewall and restrict network communication to current IPv4 subnet.
h.In the Nameserver Address 1 text box, enter a user-defined DNS IP address.
i.
In the Nameserver Address 2 text box, enter a user-defined DNS IP address..
j.
Click the Arp Filter Enabled list box arrow and select True to enable the parameter.
k.In the Vlan MGMT text box, enter the Management VLAN ID.
l.
In the Vlan Tag Port 1 and/or Vlan Tag Port 2 text boxes, enter the VLAN ID for the
designated port.
8. Click the Update button to save the changed information.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the NTP tab to access the NTP parameters. Figure 110
Note: See the NTP Parameters (on page 280) for detailed information about the parameters.
a. Click the NTP Reference list box arrow and select either NETWORK_TIME_
SERVER or REFCLK_LOCALCLOCK.
b. In the NTP Restart text box, enter Now to restart the the NTP system.
c. In the NTP Date text box, enter Now to synchronize the local clock with the time from
the NTP servers specified in the ntp_address (on page 281) settings.
d. In the NTP Address 2 to 5 text boxes, enter the IP address of the servers used for
synchronizing time.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings tab to access the Radio Settings parameters.
7. Click the Radio Mode list box arrow and select the device type to designate the Z9-P2 or
Z9-PE2 as an Endpoint. Figure 112
Note: See the radioSettings Parameters (on page 285) for detailed information about the
parameters.
f. Optional: In the LNA Bypass text box, enter 1 to bypass the Low Noise Amplifier
(LNA) and reduce the radio module receive signal by 10dB.
g. In the Max Link Distance in Miles text box, enter the maximum one-way distance (in
miles) used to set the maximum expected propagation delay between any Endpoints in
the network.
h. In the Frequency Masks text box, enter the exact specified format of the frequency
range to mask.
Caution: The exact syntax is required in the Frequency Masks text box.
See frequencyMasks (on page 290) for detailed information.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings tab to access the Radio Settings parameters.
7. Click the Radio Mode list box arrow and select the device type to designate the Z9-P2 or
Z9-PE2 as an Endpoint_Repeater. Figure 114
Note: See the radioSettings Parameters (on page 285) for detailed information about the
parameters.
g. Optional: In the LNA Bypass text box, enter 1 to bypass the Low Noise Amplifier
(LNA) and reduce the radio module receive signal by 10dB.
h. In the Max Link Distance in Miles text box, enter the maximum one-way distance (in
miles) used to set the maximum expected propagation delay between any Endpoints in
the network.
i. In the Frequency Masks text box, enter the exact specified format of the frequency
range to mask.
Caution: The exact syntax is required in the Frequency Masks text box.
See frequencyMasks (on page 290) for detailed information.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings tab to access the Radio Settings parameters.
7. Accept the Radio Mode default of Gateway. Figure 116
Note: See the radioSettings Parameters (on page 285) for detailed information about the
parameters.
g. Click the Beacon Interval list box arrow and select how often a Gateway radio sends
out a beacon packet and changes to the next radio frequency in the hopping pattern.
h. In the Beacon Burst Count text box, enter the number of consecutive beacons to
send per beaconInterval time.
i. Optional: In the LNA Bypass text box, enter 1 to bypass the Low Noise Amplifier
(LNA) and reduce the radio module receive signal by 10dB.
j. In the Max Link Distance in Miles text box, enter the maximum one-way distance (in
miles) used to set the maximum expected propagation delay between any Endpoints in
the network.
k. In the Frequency Masks text box, enter the exact specified format of the frequency
range to mask.
Caution: The exact syntax is required in the Frequency Masks text box.
See frequencyMasks (on page 290) for detailed information.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings tab to access the Radio Settings parameters.
7. Click the Radio Mode list box arrow and select the device type to designate the Z9-P2 or
Z9-PE2 as a Gateway_Repeater. Figure 118
Note: See the radioSettings Parameters (on page 285) for detailed information about the
parameters.
g. Click the Beacon Interval list box arrow and select how often a Gateway radio sends
out a beacon packet and changes to the next radio frequency in the hopping pattern.
h. In the Beacon Burst Count text box, enter the number of consecutive beacons to
send per beaconInterval time.
i. Optional: In the LNA Bypass text box, enter 1 to bypass the Low Noise Amplifier
(LNA) and reduce the radio module receive signal by 10dB.
j. In the Max Link Distance in Miles text box, enter the maximum one-way distance (in
miles) used to set the maximum expected propagation delay between any Endpoints in
the network.
k. In the Frequency Masks text box, enter the exact specified format of the frequency
range to mask.
Caution: The exact syntax is required in the Frequency Masks text box.
See frequencyMasks (on page 290) for detailed information.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Security tab to access the Security parameters. Figure 120
Note: See the security Parameters (on page 317) for detailed information about the
parameters.
b. Optional: Click the Enable Ethernet Login list box arrow and select False to disable
SSH logins.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Services tab to access the Services parameters. Figure 122
Note: See the services Parameters (on page 320) for detailed information about the
parameters.
7. In the Time Out CLI text box, enter the number of seconds of idle time before the CLI
connection is closed.
8. Click the Update button to save the changed information.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
Note: See the SNMP Parameters (on page 322) for detailed information about the
parameters.
b. Click the V2C Enabled list box arrow and select True to enable SNMP V2C.
c. Click the V3 Enabled list box arrow and select True to enable SNMP V3.
d. In the RO Community Name text box, enter the user-designated name for SNMP
V1/V2C Read-only access.
e. In the RW Community Name text box, enter the user-designated name for SNMP
V1/V2C Read-Write access.
Note: The SNMP User text box is Read-only in the Web Interface.
Use the CLI to change this parameter.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the System Info tab to access the System Info parameters. Figure 126
Note: See the systemInfo Parameters (on page 336) for detailed information about the
parameters.
Note: All other parameters in the System Info window are Read-only.
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Terminal Server Relay tab to access the Terminal Server Relay
parameters. Figure 128
Note: See the TerminalServerRelay Parameters (on page 347) for detailed information about
the parameters.
This section provides procedure information about adding, saving, and viewing the Z9-P2 or Z9-
PE2 Network Diagnostic diagrams.
l Add a Gateway Device IP Address (on page 128)
l Download a Support Bundle (on page 131)
l Save Network Diagnostics (on page 134)
l Save a Network Diagram Image (on page 137)
l Show Table in the Network Diagnostics Window (on page 141)
l View the Network Diagnostics - Breadthfirst (on page 143)
l View the Network Diagnostics - Cose-bilkent (on page 145)
l View the Network Diagnostics - Grid (on page 147)
l View the Network Diagnostics - Margin (on page 149)
l View the Network Diagnostics - Margin with Neighbors (on page 151)
l View the Network Diagnostics - RSSI (on page 154)
l View the Network Diagnostics - RSSI with Neighbors (on page 156)
l View the Network Diagnostics - Rx Rate (on page 159)
l View the Network Diagnostics - Tx Rate (on page 161)
Note: The images in this procedure are for Windows® 10 and/or Firefox®.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 130
The diagram takes a few moments to render.
The Options list box default selection is Margin.
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
6. Click the Options list box arrow and select the Gateway IP option. Figure 131
The Add Device IP dialog box opens showing the currently designated Gateway IP
address. Figure 132
7. In the IP text box, enter the IP address of the designated a Gateway device and click
Submit.
Important!: Network settings are NOT changed when the Gateway IP address is specified.
Note: The images in this procedure are for Windows® 10 and/or Firefox®.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 134
The diagram takes a few moments to render.
The Options list box default selection is Margin.
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
6. Click the Options list box arrow and select the Download Support Bundle option. Figure
135
Figure 135: Options list box - Download Support Bundle option Selected
7. Click OK.
The Enter name of file to save to dialog box opens.
8. Search for and select a location to save the .zip file to and click Save.
The Enter name of file to save to dialog box closes.
9. Contact FreeWave Technical Support (on page 14) for information on where to send the
saved .zip file.
Note: The images in this procedure are for Windows® 10 and/or Firefox®.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 138
The diagram takes a few moments to render.
The Options list box default selection is Margin.
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
6. Click the Options list box arrow and select the Save Network Diagnostics option. Figure
139
Figure 139: Options list box - Save Network Diagnostics option Selected
7. Click OK.
The Enter name of file to save to dialog box opens.
8. Search for and select a location to save the .json file to and click Save.
The Enter name of file to save to dialog box closes.
9. Open a Windows® File Explorer window and find the location where the .json file was
saved.
10. Open the .json file to review the current network performance reading and monitor network
performance over time.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 143
The diagram takes a few moments to render.
The Options list box default selection is Margin.
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
6. Click the Options list box arrow and select the Save Image option. Figure 144
8. Click OK.
The Enter name of file to save to dialog box opens. Figure 147
9. Search for and select a location to save the .PNG file to and click Save.
10. Open a Windows® Explorer window and find the location where the .PNG file was saved.
11. Open the .PNG file to review the changes in the network using the Network Diagram.
Figure 148
Note: The images in this procedure are for Windows® 10 and/or Firefox®.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 150
The diagram takes a few moments to render.
The Options list box default selection is Margin.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 153
The diagram takes a few moments to render.
The Options list box default selection is Margin.
6. Click the Options list box arrow and select the Breadthfirst option to show the
Breadthfirst connections in the Network Diagram. Figure 154
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 156
The diagram takes a few moments to render.
The Options list box default selection is Margin.
6. Click the Options list box arrow and select the Cose-bilkent option to show the Cose-
bilkent connections in the Network Diagram. Figure 157
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 159
The diagram takes a few moments to render.
The Options list box default selection is Margin.
6. Click the Options list box arrow and select the Grid option to show the Grid connections in
the Network Diagram. Figure 160
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 162
The diagram takes a few moments to render.
The Options list box default selection is Margin.
The Link Margin connections appear in the Network Diagram Figure 163
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 165
The diagram takes a few moments to render.
The Options list box default selection is Margin.
6. Click the Options list box arrow and select the Margin with Neighbors option to show the
Margin with Neighbors connections in the Network Diagram. Figure 166
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
7. Optional: Use the cursor to hover over the Gateway-Endpoint link to view the dBm
rate. Figure 167
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 169
The diagram takes a few moments to render.
The Options list box default selection is Margin.
6. Click the Options list box arrow and select the RSSI option to show the RSSI connections
in the Network Diagram. Figure 170
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 172
The diagram takes a few moments to render.
The Options list box default selection is Margin.
6. Click the Options list box arrow and select the RSSI with Neighbors option to show the
RSSI with Neighbors connections in the Network Diagram. Figure 173
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
7. Optional: Use the cursor to hover over the Gateway-Endpoint link to view the dBm
rate. Figure 174
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 176
The diagram takes a few moments to render.
The Options list box default selection is Margin.
6. Click the Options list box arrow and select the Rx Rate option to show the Rx Rate
connections in the Network Diagram. Figure 177
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
Procedure
1. Verify the Setup the Computer IP Address Configuration (on page 86) procedure is
completed.
2. Open a web browser.
3. In the URL address bar, enter the IP address of the connected Z9-P2 or Z9-PE2 and press
<Enter>.
The Home window (on page 378) opens.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 179
The diagram takes a few moments to render.
The Options list box default selection is Margin.
6. Click the Options list box arrow and select the Tx Rate option to show the Tx Rate
connections in the Network Diagram. Figure 180
To update the Network Diagnostics window (on page 387), refresh the browser to clear
the browser cache.
Important!: The Z9-P2 or Z9-PE2 password is ONLY changed through the CLI.
See CLI Configuration (on page 34) to connect via CLI.
FREEWAVE Recommends: From a security standpoint, it is best practice to change both the
admin password and the devuser passwords.
Example: system.password=admin,12345,12345.
Note: An error message appears when there is an error in typing the new password
command.
1. Login to the FreeWave CLI using admin and the current password.
The FreeWave Shell returns. Figure 181
Note: Where devuser is the current password and nnnnn is the new devuser password.
The CLI shows the new password was accepted. Figure 183
11. IP Filtering
IP Filtering is used to allow only traffic in a designated IP subnet to traverse the radio network.
l Within the radio subnet, the IPv4, TCP, ICMP (ping), ARP, and UDP traffic is permitted to
traverse the radio network, while all other Ethernet traffic is blocked.
l The IP Filtering setting does NOT need to match on all the radios in the network.
Only enable IP Filtering on individual radios with incoming LAN Ethernet traffic to filter from
the network.
IP Filtering can prevent non-radio Ethernet traffic from adversely affecting the performance and
capacity of the radio network.
Procedure
Note: This procedure provides a Tera Term terminal connection to the FreeWave CLI. Other
terminal emulators (e.g., HyperTerminal, PuTTY) may be used.
The images in this procedure are for Windows® 7 and/or Windows® 10 and Firefox®.
1. On the computer connected to the Z9-P2 or Z9-PE2, open a terminal program (e.g., Tera
Term http://ttssh2.osdn.jp/).
2. In Tera Term, click the File menu and select New Connection. Figure 184
The Tera Term: Serial Port Setup dialog box opens. Figure 187
Figure 187: Tera Term: Serial Port Setup dialog box with Default Settings
6. Using Figure 187 as the example, verify the COM port settings are:
Speed (Baud Rate): 115200
Data (Databits): 8 bit
Parity: none
Stop bits: 1 bit
7. Click OK to save the changes and close the dialog box.
8. In the Tera Term window, press <Enter>.
The FreeWave CLI Login returns.
9. Enter admin for the Username and press <Enter>.
10. Enter admin for the Password and press <Enter>.
The IP Filtering setting does NOT need to match on all the radios in the network.
Only enable IP Filtering on individual radios with incoming LAN Ethernet traffic to filter
from the network.
Note: See Example: Network Topology with Traffic at the Gateway (on page 170).
Figure 190 is a common network topology where IP filtering on the Gateway radio reduces
unwanted traffic on the radio network.
In this example:
l Only traffic on the 192.168.111.255 netmask passes over the radio network.
l The red laptop and the camera traffic are on the 222.nnn subnet; their traffic is blocked at
the Gateway radio.
l Only IPv4. TCP, UDP, ICMP (ping), and ARP traffic destined to and from the desired
subnet is transmitted over the radio network.
l VLAN tagged packets are filtered out because the radio is not considered on the VLAN and
therefore VLAN packets cannot be on the same subnet.
12. Repeaters
ZumLink Repeater allows the extension of the ZumLink network, forwarding packets between
ZumLink devices that could otherwise not communicate directly with each other. The advantage
of using Repeaters is to reach very long distances and "hop" over or around obstacles like
buildings or hills.
The ZumLink Repeater can be configured as either a Gateway-Repeater or Endpoint-Repeater.
l The Gateway-Repeater is a Gateway that also repeats packets.
l The Endpoint-Repeater is an Endpoint able to repeat packets and master beacons.
Note: An Endpoint-Repeater strongly favors its wired device over Endpoints it’s repeating for.
ZumLink Repeaters support all 5 data rates; 115.2kbps, 250kbps, 500kbps, 1Mbps, and 4Mbps.
l At 115.2kbps and 250kbps data rates, hopping capability must be enabled for the ZumLink
Repeaters.
l At 500kbps, 1Mbps, and 4Mbps data rates, hopping capability is optional.
When hopping capability is employed, one radio must be configured as the Gateway (or Gateway-
Repeater).
l The beacon from the Gateway radio must be heard by the Repeater.
l The Repeater must also re-send the beacon so that the Endpoints, and downstream
Repeaters, it communicates with can stay synchronized with the frequency hopping
pattern.
l To keep the Gateway and Endpoint-Repeater beacons from colliding, the Endpoint-
Repeaters must have their own time slot (radio Repeater slot).
l The Endpoint-Repeater has a radio Repeater slot range from 1-3.
l A maximum number of 3 Endpoint-Repeaters are supported in an overlapping
FREEWAVE Recommends: Set the beaconBurstCount (on page 286) to 2 or more for optimal
throughput when Repeaters are used and the RF environment is noisy.
This increases the number of beacons sent in a beacon interval.
Caution: The repeating operation occurs on the same frequencies normally used for transmit
and receive.
This causes the throughput of the communication path utilizing the Repeater to be reduced by
approximately 50 percent with each Repeater hop.
Only communication paths via Repeaters are impacted, communication paths that do not
utilize the Repeater remain at full throughput.
Note: For detailed procedures, see Basic Gateway and Endpoint-Repeater Setup (on page 176).
Note: *See the dataPath Parameters (on page 216), network Parameters (on page 262), or radioSettings Parameters (on page 285) for
additional information.
1. Set the radioMaxRepeaters to match the number of overlapping Repeaters with a maximum of 3.
l Setting this value too high adds unnecessary latency to the network.
l In this example, set this to 1.
2. Set the radioRepeaterSlot to designate which Repeater slot to use, up to the radioMaxRepeaters setting.
l In this example, set this to 1.
3. Set the beaconBurstCount (on page 286) to 2 or more for optimal throughput when Repeaters are used and the RF environment
is noisy.
This increases the number of beacons sent in a beacon interval.
Note: ****See the dataPath Parameters (on page 216), network Parameters (on page 262), or radioSettings Parameters (on page 285) for
additional information.
1. On the computer connected to the Z9-P2 or Z9-PE2, open a terminal program (e.g., Tera
Term http://ttssh2.osdn.jp/).
2. In Tera Term, click the File menu and select New Connection. Figure 191
The Tera Term: Serial Port Setup dialog box opens. Figure 194
Figure 194: Tera Term: Serial Port Setup dialog box with Default Settings
6. Using Figure 194 as the example, verify the COM port settings are:
Speed (Baud Rate): 115200
Data (Databits): 8 bit
Parity: none
Stop bits: 1 bit
7. Click OK to save the changes and close the dialog box.
8. In the Tera Term window, press <Enter>.
The FreeWave CLI Login returns.
9. Enter admin for the Username and press <Enter>.
Note: See rfDataRate (on page 307) for the correct command format of the RF
Data Rate.
Note: See rfDataRate (on page 307) for the correct command format of the RF
Data Rate.
Note: See rfDataRate (on page 307) for the correct command format of the RF
Data Rate.
If Hopping is ON (radiosettings.radioHoppingMode=Hopping_On) go to
Hopping On: Gateway and Endpoint-Repeater Setup (on page 180).
Note: See rfDataRate (on page 307) for the correct command format of the RF
Data Rate.
Note: See rfDataRate (on page 307) for the correct command format of the RF
Data Rate.
Note: See rfDataRate (on page 307) for the correct command format of the RF
Data Rate.
12.3.1. Gateway-Repeater
Figure 197 shows:
l Endpoints that cannot peer directly can communicate through a Gateway-Repeater,
extending the length of a point-to-multipoint network.
l Repeater is operating in Gateway-Repeater mode.
l No performance loss for Gateway-Repeater to Endpoint 1-Endpoint 2-Endpoint 3
communication.
l The throughput for Endpoint 2 to Endpoint 3 communication via Gateway-Repeater is
reduced by approximately 50 percent.
12.3.2. Endpoint-Repeater
Figure 198 shows:
l Endpoints that cannot peer directly can communicate through an Endpoint-Repeater,
extending the length of a point-to-point network.
l Repeater is operating in Endpoint-Repeater mode.
l No performance loss for Gateway to Endpoint 3, Gateway to Endpoint-Repeater, or
Endpoint-Repeater to Endpoint 1-Endpoint 2 communication.
l The throughput for Endpoint 1-Endpoint 2 to Gateway communication via Endpoint-
Repeater is reduced by approximately 50 percent.
Note: An Endpoint-Repeater strongly favors its wired device over Endpoints it’s repeating for.
Important!: Supporting three Repeaters in the same overlapping RF coverage does NOT limit the
total number of Repeaters that can be chained together. However, make careful considerations
regarding the throughput impact of chained Repeaters.
Note: An Endpoint-Repeater strongly favors its wired device over Endpoints it’s repeating for.
l Z9-PE2
l FreeWave Part Number: AOH4003SP
Mounting Procedures
l Z9-P2 Mounting (on page 192)
l Z9-PE2 Mounting (on page 194)
Note: See Remove the Z9-P2 or Z9-PE2 from the DIN Rail (on page 195) for additional information.
User-supplied Equipment
l Medium Phillips-head screwdriver
l Medium Flat-head screwdriver
Procedure
1. Use the Pan-head machine screws to attach the DIN Rail Bracket to the Z9-P2.
2. Orient the DIN Rail Bracket / DIN Rail Spring Clip assembly so:
a. The spring-loaded end of the DIN Rail Spring Clip is on the bottom lip of the rail.
b. The fixed (not spring-loaded) end of the DIN Rail Spring Clip is on the top.
Caution: Per the manufacturer's instructions, the DIN Rail Spring Clip is oriented with
the spring-loaded end on the bottom lip of the rail.
a. Use the Flat-head machine screws to attach the DIN Rail Spring Clip to the DIN Rail
Bracket.
b. Mount the Z9-P2 to the 35mm DIN rail using the rail slide on the enclosure. Figure 202
Figure 202: Z9-P2 Attached to a DIN Rail with the Power Connection on Top
User-supplied Equipment
l Medium Phillips-head screwdriver
l Medium Flat-head screwdriver
Procedure
Note: The Z9-P2 or Z9-PE2 can be installed using the four corner screws on the bottom of the radio.
On the bottom of the Z9-P2 or Z9-PE2, there is a set screw installed in the left-rear mounting hole.
This set screw must be removed if the Z9-P2 or Z9-PE2 is mounted using the four corner screws.
1. Use the Pan-head machine screws to attach the DIN Rail Bracket to the Z9-PE2.
2. Orient the DIN Rail Bracket / DIN Rail Spring Clip assembly so:
a. The spring-loaded end of the DIN Rail Spring Clip is on the bottom lip of the rail.
b. The fixed (not spring-loaded) end of the DIN Rail Spring Clip is on the top.
Caution: Per the manufacturer's instructions, the DIN Rail Spring Clip is oriented with
the spring-loaded end on the bottom lip of the rail.
a. Use the Flat-head machine screws to attach the DIN Rail Spring Clip to the DIN Rail
Bracket.
b. Mount the Z9-PE2 to the 35mm DIN rail using the rail slide on the enclosure. Figure 203
Figure 203: Z9-PE2 Attached to a DIN Rail with the Power Connection on
Top
Note: These antennas, including antenna gains, are approved for use with the ZumLink device.
Warning! A proper combination with the ZumLink is required to ensure the system meets
FCC requirements.
Note: See the COM window (on page 364) for parameter location.
The parameters for COM1 and COM2 are the same except for the TerminalServerPort (on page 209)
parameter setting.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
15.1. baudrate
baudrate
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.baudrate=nnnn
l Com2.baudrate=nnnn
Note: See the COM window (on page 364) for parameter location.
15.2. breakBeforeSendUs
breakBeforeSendUs
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.breakBeforeSendUs=nnnn
l Com2.breakBeforeSendUs=nnnn
breakBeforeSendUs
Setting Description
Web Interface Break Before Send Us
window 1. In the Break Before Send Us text box, enter the number of milliseconds
the COM port will send a break signal.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
15.3. connectionDrops
connectionDrops
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.connectionDrops
l Com2.connectionDrops
Web Interface Connection Drops
window
Note: This parameter is read-only in the Web Interface.
See the COM window (on page 364) for parameter location.
connectionDrops
Setting Description
Description The Com1.connectionDrops or Com2.connectionDrops command reports the
number of terminal server connections dropped due to inactivity on the network
socket.
l The number of drops only increments if a connection is left open and no data is
sent.
l Connections that are closed by either side before the time out are not
considered a dropped connection.
15.4. databits
databits
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.databits=7
l Com2.databits=7
l Com1.databits=8
l Com2.databits=8
Web Interface Databits
window 1. Click the Databits list box arrow and select the number of data bits in the
frame for COM1 or COM2.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
Default Setting 8
Options l 7
l 8
Description The Com1.databits or Com2.databits parameter designates the number of data
bits in the frame for COM1 or COM2.
15.5. delayBeforeSendMs
delayBeforeSendMs
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.delayBeforeSendMs=nnnn
l Com2.delayBeforeSendMs=nnnn
Note: See the COM window (on page 364) for parameter location.
15.6. duplex
duplex
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
duplex
Setting Description
CLI Command l Com1.duplex=Half
l Com2.duplex=Half
l Com1.duplex=Full
l Com2.duplex=Full
Web Interface Duplex
window 1. Click the Duplex list box arrow and select the duplex designation.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
Note: See Ports and Pinouts for input and output information.
15.7. flowControl
flowControl
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command For Com2, the command is:
l Off: Com2.flowControl=Off
l On: Com2.flowControl=Hardware
Web Interface Flow Control
window 1. If applicable for COM2, click the Flow Control list box arrow and select
Hardware to activate flowControl.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
flowControl
Setting Description
Options l Off
l Hardware
Description The Com2.flowControl parameter designates the hardware flow control as either
On (Hardware) or Off.
15.8. handler
handler
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
handler
Setting Description
CLI Command CLI
When CLI is designated, a configuration CLI is on the COM port.
The command is:
l Com1.handler=cli
l Com2.handler=cli
ModbusPassthru
When ModbusPassthru is designated, modbus requests are sent out to
modbus sensors that are received via Modbus TCP or Modbus RTU.
The command is:
l Com1.handler=ModbusPassthru
l Com2.handler=ModbusPassthru
ModbusRTU
When ModbusRTU is designated, receive Modbus RTU requests from a serial
modbus RTU device.
The command is:
l Com1.handler=ModbusRTU
l Com2.handler=ModbusRTU
Off
When Off is designated, this allows for application use with no setup. A port is
never opened.
The command is:
l Com1.handler=Off
l Com2.handler=Off
Setup
When Setup is designated, the COM port then frees up the port for application
use.
The command is:
l Com1.handler=Setup
l Com2.handler=Setup
Terminal Server
When Terminal Server is designated, the COM port acts as a terminal server.
l The TCP port number is set by the COM1 TerminalServerPort (on page 209).
l The default port number for COM1 is 5041.
The command is:
l Com1.handler=TerminalServer
handler
Setting Description
l Com2.handler=TerminalServer
Trace
When Trace is designated, a configuration CLI with trace is on the COM port.
l Com1.handler=trace
l Com2.handler=trace
Web Interface Handler
window 1. Click the Handler list box arrow and select the designated protocol handler.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
15.9. mode
mode
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
mode
Setting Description
CLI Command l Com1.mode=RS232
l Com2.mode=RS232
l Com1.mode=RS485
l Com2.mode=RS485
Web Interface Mode
window 1. Click the Mode list box arrow and select the COM port mode.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
15.10. parity
parity
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.parity=None
l Com2.parity=None
l Com1.parity=Even
l Com2.parity=Even
l Com1.parity=Odd
l Com2.parity=Odd
parity
Setting Description
Web Interface Parity
window 1. Click the Parity list box arrow and select the COM port parity bits for the
system.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
15.11. RxBytes
RxBytes
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.RxBytes
l Com2.RxBytes
Web Interface RX Bytes
window
Note: This parameter is read-only in the Web Interface.
See the COM window (on page 364) for parameter location.
15.12. stopbits
stopbits
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.stopbits=1
l Com2.stopbits=1
l Com1.stopbits=2
l Com2.stopbits=2
Web Interface Stopbits
window 1. Click the Stopbits list box arrow and select the COM port number of stop
bits.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
Default Setting 1
Options l 1
l 2
Description The Com1.stopbits or Com2.stopbits parameter designates the COM port
number of stop bits.
15.13. TerminalServerPort
Note: See Terminal Server Relay Examples (on page 352) for additional information.
TerminalServerPort
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.TerminalServerPort=nnnn
l Com2.TerminalServerPort=nnnn
TerminalServerPort
Setting Description
Web Interface Terminal Server Port
window 1. In the Terminal Server Port text box, enter the designated TCP port
number.
2. Click the Update button to save the change.
Note: See the COM window (on page 364) for parameter location.
15.14. TerminalServerTimeOut
Note: See Terminal Server Relay Examples (on page 352) for additional information.
TerminalServerTimeOut
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.TerminalServerTimeOut=nnnn
l Com2.TerminalServerTimeOut=nnnn
Note: Where nnnn is the amount of time, in seconds, the Terminal Server
remains open.
TerminalServerTimeOut
Setting Description
Web Interface Terminal Server Time Out
window 1. In the Terminal Server Time Out text box, enter the number of seconds
the Terminal Server remains open without transmitting or receiving data
from the network.
2. Click the Update button to save the change.
3. Reboot the Z9-P2 or Z9-PE2 for changes to take effect.
Note: See the COM window (on page 364) for parameter location.
Note: This can prevent an idle socket from remaining open indefinitely and
preventing new connections.
15.15. TxBytes
TxBytes
Setting Description
CLI / Web Page l [Page=Com1]
l [Page=Com2]
CLI Command l Com1.TxBytes
l Com2.TxBytes
Web Interface TX Bytes
window
Note: This parameter is read-only in the Web Interface.
See the COM window (on page 364) for parameter location.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
16.1. factoryDefaults
factoryDefaults
Setting Description
CLI / Web Page [Page=config]
CLI Command l config.factoryDefaults=set
l factoryDefaults=set
Web Interface Factory Defaults
window
Note: See the Config window (on page 366) for parameter location.
16.2. licenseState
licenseState
Setting Description
CLI / Web Page [Page=config]
CLI Command l config.licenseState
l licenseState
Web Interface License State
window
Note: See the Config window (on page 366) for parameter location.
licenseState
Setting Description
Description The config.licenseState command reports the extra feature licenses in the Z9-
P2 or Z9-PE2.
16.3. reset
reset
Setting Description
CLI / Web Page [Page=config]
CLI Command l Reboot the entire Z9-P2 or Z9-PE2 device:
l config.reset=now
l config.reset=reboot
l Reset to restart the main application:
l config.reset=reset
Web Interface Reset
window
Note: See the Config window (on page 366) for parameter location.
16.4. restore
restore
Setting Description
CLI / Web Page [Page=config]
CLI Command l config.restore=now
l config.restore
l restore
restore
Setting Description
Web Interface Restore
window
Note: See the Config window (on page 366) for parameter location.
16.5. save
save
Setting Description
CLI / Web Page [Page=config]
CLI Command l config.save=now
l config.save
l save
Web Interface Save
window
Note: See the Config window (on page 366) for parameter location.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
17.1. aggregateEnabled
aggregateEnabled
Setting Description
CLI / Web Page [Page=dataPath]
CLI Command l Enable:
l dataPath.aggregateEnabled=true
l aggregateEnabled=true
l Disable:
l dataPath.aggregateEnabled=false
l aggregateEnabled=false
Web Interface Aggregate Enabled
window 1. Click the Aggregate Enabled list box arrow and select True to enable this
parameter and increase throughput of small packets.
2. Click the Update button to save the change.
aggregateEnabled
Setting Description
Description The aggregateEnabled (on page 217) setting increases throughput of small
packets by combining multiple packets into a single packet minimizing the number
of packets required for transmission.
Notes
l Increases latency by 20msec and reduces poll rates.
l When enabled, this setting adds 20 msec of latency.
l However, net throughput may increase due to sending fewer, larger
packets.
l If another packet is not received within 20 msec, the aggregated packet is
transmitted.
l This setting does NOT need to match on all radios.
l Does NOT affect medium and large packets.
l Packets below 900 bytes are aggregated up to an aggregated packet size of
970 bytes.
17.2. compressionEnabled
compressionEnabled
Setting Description
CLI / Web Page [Page=dataPath]
CLI Command l Enable:
l dataPath.compressionEnabled=true
l compressionEnabled=true
l Disable:
l dataPath.compressionEnabled=false
l compressionEnabled=false
compressionEnabled
Setting Description
Web Interface Compression Enabled
window 1. Click the Compression Enabled list box arrow and select False to disable
compression of outgoing packets.
2. Click the Update button to save the change.
Notes
l When enabled, the Packet Compression setting increases latency by a
maximum of 10msec.
l When enabled, the Packet Compression setting ensures that the packet
transmitted is no larger than the current packet size.
l Net throughput may increase due to sending more data in each packet.
l All radios have the ability to de-compress received packets regardless of their
compression setting.
l This setting does NOT need to match on all radios.
17.3. fecRate
fecRate
Setting Description
CLI / Web Page [Page=dataPath]
fecRate
Setting Description
CLI Command l Enable:
l dataPath.fecRate=RATE_7_8
l fecRate=RATE_7_8
l Disable:
l dataPath.fecRate=RATE_1_1
l fecRate=RATE_1_1
Web Interface FEC Rate
window 1. Click the FEC Rate list box arrow and select the Forward Error Correction
(FEC) rate.
2. Click the Update button to save the change.
Note: See the Data Path window (on page 368) for parameter location.
fecRate
Setting Description
Description The dataPath.fecRate setting enables the Forward Error Correction (FEC) rate.
Note: The fecRate (on page 219) increases the reliability of the data
transferred over the air at the cost of some transmission throughput.
Notes
l The FEC setting MUST match on ALL radios in the network, to maintain over-
the-air compatibility.
l When enabled, this setting indicates that for every 7 bytes in, the radio sends 8
bytes out, with the 8th byte used for parity / error correction.
l Reduces throughput by 13%.
l Improves sensitivity by 3dB to maximize link range in noisy environments.
l Adds redundant information to a data stream to detect packet errors and
corrects them to avoid retransmission of the packet.
l Adds resilience in noisy environments.
l FEC reduces the maximum achievable throughput.
l However, in noisy environments, net throughput may increase due to
reduced errors and retries.
Caution: When enabling FEC, start with the farthest Endpoints, then
any Repeaters, then lastly the Gateway.
As FEC is enabled on each radio, that radio is temporarily dropped off
the network, until any downstream Repeaters and the Gateway also
have FEC enabled, at which time all communication will resume.
17.4. MacTableEntryAgeTimeout
MacTableEntryAgeTimeout
Setting Description
CLI / Web Page [Page=dataPath]
MacTableEntryAgeTimeout
Setting Description
CLI Command l dataPath.MacTableEntryAgeTimeout=nnnn
l MacTableEntryAgeTimeout=nnnn
Note: See the Data Path window (on page 368) for parameter location.
FREEWAVE Recommends: Set this timeout longer than the polling rate
on the network.
Entries do not use the new timeout value until they are updated when a
packet transfers.
Note: See MacTableShow (on page 239) to view the MAC to nodeId
mapping table.
17.5. otaMaxFragmentSize
otaMaxFragmentSize
Setting Description
CLI / Web Page [Page=dataPath]
CLI Command l dataPath.otaMaxFragmentSize=nnnn
l otaMaxFragmentSize=nnnn
Note: See the Data Path window (on page 368) for parameter location.
17.6. routeMinSignalMarginThresh
routeMinSignalMarginThresh
Setting Description
CLI / Web Page [Page=dataPath]
CLI Command l dataPath.routeMinSignalMarginThresh=nnnn
l routeMinSignalMarginThresh=nnnn
routeMinSignalMarginThresh
Setting Description
Web Interface Route Min Signal Margin Thresh
window 1. In the Route Min Signal Margin Thresh text box, enter the minimum
threshold signal margin in dB.
2. Click the Update button to save the change.
Note: See the Data Path window (on page 368) for parameter location.
Default Setting l 10
Options l The minimum value is -5.
l The maximum value is 60.
Description The dataPath.routeMinSignalMarginThresh parameter designates the minimum
(threshold) signal margin, in dB, the next hop must be considered part of the
packet route.
Notes
l When Repeaters are enabled, the packets take the path through the radio
network with the minimum number of hops.
l By increasing the threshold value, the possible routes can be reduced to allow
a particular routing path to be preferred.
Example: If the best-reported link margin for the next hop is 20 dB, this
number should be set to 16 or less. This prevents the traffic from choosing
an alternative route with lower margin.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
18.1. dcAppStartTime
Important!: Time zones do not apply to the Z9-P2 or Z9-PE2.
dcAppStartTime
Setting Description
CLI / Web Page [Page=date]
CLI Command l date.dcAppStartTime
l dcAppStartTime
Web Interface DC App Start Time
window
Note: This parameter is read-only in the Web Interface.
See the Date window (on page 370) for parameter location.
18.2. dcAppUptime
Important!: Time zones do not apply to the Z9-P2 or Z9-PE2.
dcAppUptime
Setting Description
CLI / Web Page [Page=date]
CLI Command l date.dcAppUptime
l dcAppUptime
Web Interface DC App Uptime
window
Note: This parameter is read-only in the Web Interface.
See the Date window (on page 370) for parameter location.
dcAppUptime
Setting Description
Description The date.dcAppUptime parameter reports the number of Days, Hours, Minutes,
and Seconds since the main app started.
18.3. time
Important!: Time zones do not apply to the Z9-P2 or Z9-PE2.
time
Setting Description
CLI / Web Page [Page=date]
CLI Command l date.time
l time
Web Interface Time
window
Note: This parameter is read-only in the Web Interface.
See the Date window (on page 370) for parameter location.
18.4. timeString
Important!: Time zones do not apply to the Z9-P2 or Z9-PE2.
timeString
Setting Description
CLI / Web Page [Page=date]
CLI Command date.timeString=MM/DD/YYYY HH.MM.SS
timeString
Setting Description
Web Interface Time String
window
Note: This parameter is read-only in the Web Interface.
See the Date window (on page 370) for parameter location.
18.5. upTime
Important!: Time zones do not apply to the Z9-P2 or Z9-PE2.
upTime
Setting Description
CLI / Web Page [Page=date]
CLI Command l date.upTime
l upTime
Web Interface Up Time
window
Note: This parameter is read-only in the Web Interface.
See the Date window (on page 370) for parameter location.
18.6. upTimeString
Important!: Time zones do not apply to the Z9-P2 or Z9-PE2.
upTimeString
Setting Description
CLI / Web Page [Page=date]
CLI Command l date.upTimeString
l upTimeString
Example: A return of Uptime 5 Days 01:36:41 means the unit has been
up for 5 days, 1 hour, 36 minutes, and 41 seconds.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
19.1. activeKey
Caution: Encryption settings MUST match on ALL radios in the network to maintain over-the-
air compatibility.
When enabling Encryption, start with the farthest Endpoints, then any Repeaters, then lastly
the Gateway.
As Encryption is enabled on each radio, that radio temporarily drops off the network, until any
downstream Repeaters and the Gateway also have Encryption enabled, at which time all
communication will resume.
activeKey
Setting Description
CLI / Web Page [Page=encryption]
CLI Command l encryption.activeKey=Off
l activeKey=Off
l encryption.activeKey=Key1 to Key16
l activeKey=Key1 to Key16
Example: encryption.activeKey=Key10.
Note: See the Encryption window (on page 372) for parameter location.
Important!: Assigning the activeKey to a key that is NOT set will NOT
allow communication across the link.
Keys MUST BE set before they can become active keys.
19.2. encryptionMode
Caution: Encryption settings MUST match on ALL radios in the network to maintain over-the-
air compatibility.
When enabling Encryption, start with the farthest Endpoints, then any Repeaters, then lastly
the Gateway.
As Encryption is enabled on each radio, that radio temporarily drops off the network, until any
downstream Repeaters and the Gateway also have Encryption enabled, at which time all
communication will resume.
encryptionMode
Setting Description
CLI / Web Page [Page=encryption]
CLI Command l AES Counter Mode:
l encryption.encryptionMode=AES_CTR
l encryptionMode=AES_CTR
l AES Counter Mode with MIC (Message Integrity Check):
l encryption.encryptionMode=AES_CCM
l encryptionMode=AES_CCM
Web Interface Encryption Mode
window 1. Click the Encryption Mode list box arrow and select the designated
encryption mode.
2. Click the Update button to save the change.
Note: See the Encryption window (on page 372) for parameter location.
Key1 to Key16
Setting Description
CLI / Web [Page=encryption]
Page
CLI l encryption.Key1=Key1 to Key16
Command l Key1=Key1 to Key16
Example: encryption.getKey=key8.
21.1. signalLevel
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
signalLevel
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.signalLevel
l signalLevel
Web Interface Signal Level
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
Note: This setting shows -128.00 if no packet has been received since the
stats were cleared.
21.2. signalMargin
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
signalMargin
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.signalMargin
l signalMargin
Web Interface Signal Margin
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
signalMargin
Setting Description
Default Setting N/A
Options N/A
Description The localDiagnostics.signalMargin command reports the amount of signal
margin, in dB, the last received packet experienced.
Note: The signal margin is the difference between the signal level and
either the receive sensitivity or the noise level, whichever is higher, for the
configured RF data rate.
21.3. cntBadBCC
Important!: FreeWave internal use only.
21.4. cntBadSync
Important!: FreeWave internal use only.
21.5. cntETX
Important!: FreeWave internal use only.
21.6. cntSTX
Important!: FreeWave internal use only.
21.7. getStats
getStats
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.getStats
l getStats
getStats
Setting Description
Web Interface Get Stats
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.8. interfaceBytesRx
Important!: FreeWave internal use only.
21.9. interfaceBytesTx
Important!: FreeWave internal use only.
21.10. interfaceDataRx
Important!: FreeWave internal use only.
21.11. interfaceDataTx
Important!: FreeWave internal use only.
21.12. MacTableClear
MacTableClear
Setting Description
CLI / Web Page [Page=localDiagnostics]
MacTableClear
Setting Description
CLI Command l localDiagnostics.MacTableClear=Now
l localDiagnostics.MacTableClear=
l MacTableClear=Now
l MacTableClear=
Web Interface Mac Table Clear
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.13. MacTableShow
MacTableShow
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.MacTableShow
l MacTableShow
Web Interface Mac Table Show
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.14. monitoredNode
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
monitoredNode
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.monitoredNode=<Node ID here>
l monitoredNode=<Node ID here>
Web Interface Monitored Node
window 1. In the Monitored Node text box, enter the nodeId (on page 296) to monitor.
2. Click the Update button to save the change.
Note: See the Local Diagnostics window (on page 381) for parameter
location.
Use the showNodeDiags (on page 248) to view the received signal
level (RSSI) of this node.
21.15. noiseLevel
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
noiseLevel
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.noiseLevel
l noiseLevel
Web Interface Noise Level
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.16. RadioAckTx
Important!: FreeWave internal use only.
21.17. RadioBadAckRx
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RadioBadAckRx
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RadioBadAckRx
l RadioBadAckRx
Web Interface Radio Bad Ack RX
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.18. RadioBadCRC
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RadioBadCRC
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RadioBadCRC
l RadioBadCRC
RadioBadCRC
Setting Description
Web Interface Radio Bad CRC
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.19. RadioBadSync
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RadioBadSync
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RadioBadSync
l RadioBadSync
Web Interface Radio Bad Sync
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.20. RadioContentionDrop
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RadioContentionDrop
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RadioContentionDrop
l RadioContentionDrop
Web Interface Radio Contention Drop
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.21. RadioLLRx
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RadioLLRx
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RadioLLRx
l RadioLLRx
Web Interface Radio LL RX
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.22. RadioLLTx
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RadioLLTx
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RadioLLTx
l RadioLLTx
Web Interface Radio LL TX
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.23. RadioNoAckTx
Important!: FreeWave internal use only.
21.24. RadioReliableRx
Important!: FreeWave internal use only.
21.25. RadioReliableTx
Important!: FreeWave internal use only.
21.26. RadioRexmit
Important!: FreeWave internal use only.
21.27. RadioRx
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RadioRx
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RadioRx
l RadioRx
Web Interface Radio RX
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.28. RadioSendingDrop
Important!: FreeWave internal use only.
21.29. RadioTimedOut
Important!: FreeWave internal use only.
21.30. RadioTooLong
Important!: FreeWave internal use only.
21.31. RadioTooShort
Important!: FreeWave internal use only.
21.32. RadioTx
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RadioTx
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RadioTx
l RadioTx
Web Interface Radio TX
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.33. resetsDetected
Important!: FreeWave internal use only.
21.34. resetsSent
Important!: FreeWave internal use only.
21.35. resetStats
resetStats
Setting Description
CLI / Web Page [Page=localDiagnostics]
resetStats
Setting Description
CLI Command l localDiagnostics.resetStats=Now
l localDiagnostics.resetStats=
l resetStats=Now
l resetStats=
Web Interface Reset Stats
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.36. RxSuccess
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
RxSuccess
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.RxSuccess
l RxSuccess
Web Interface Rx Success
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.37. showChannelDiags
showChannelDiags
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.showChannelDiags
l showChannelDiags
Web Interface Show Channel Diags
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.38. showNodeDiags
showNodeDiags
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.showNodeDiags
l showNodeDiags
Web Interface Show Node Diags
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.39. SupplyVoltage
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
SupplyVoltage
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.SupplyVoltage
l SupplyVoltage
Web Interface Supply Voltage
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.40. timestamp
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
timestamp
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.timestamp
l timestamp
Web Interface Timestamp
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.41. TxAvailability
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
TxAvailability
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.TxAvailability
l TxAvailability
Web Interface Tx Availability
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.42. TxSuccess
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
TxSuccess
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.TxSuccess
l TxSuccess
Web Interface Tx Success
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
21.43. VSWR
Important!: Most of the localDiagnostics parameters are read-only.
The information reported is dependent upon the connected Z9-P2 or Z9-PE2.
VSWR
Setting Description
CLI / Web Page [Page=localDiagnostics]
CLI Command l localDiagnostics.VSWR
l VSWR
Web Interface Signal Level
window
Note: This parameter is read-only in the Web Interface.
See the Local Diagnostics window (on page 381) for parameter location.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
22.1. modbusDeviceId
modbusDeviceId
Setting Description
CLI / Web Page [Page=modbus]
CLI Command l modbus.modbusDeviceId=nnn
l modbusDeviceId=nnn
Note: See the Modbus window (on page 383) for parameter location.
Default Setting 1
Options 1 to 247
Description The modbus.modbusDeviceId parameter designates the Modbus device ID the
local device responds to during a modbusTcp (on page 255) request over the
network or a modbusRtuOverTcp (on page 254) request coming in via COM1 or
COM2.
22.2. modbusLayout
modbusLayout
Setting Description
CLI / Web Page [Page=modbus]
CLI Command l modbus.modbusLayout
l modbusLayout
Web Interface Modbus Layout
window
Note: This parameter is read-only in the Web Interface.
See the Modbus window (on page 383) for parameter location.
modbusLayout
Setting Description
Description The modbus.modbusLayout parameter reports the Modbus map for the local
device.
Example
>modbusLayout
radioSettings.radioMode type:uint32_t Protocol
address:31001 Number registers:2 Modbus FC:4 Address:1000
radioSettings.rfDataRate type:uint32_t Protocol
address:31003 Number registers:2 Modbus FC:4 Address:1002
radioSettings.radioMaxRepeaters type:uint32_t Protocol
address:31005 Number registers:2 Modbus FC:4 Address:1004
….
rfStats.DownRateAvg2 type:double Protocol address:32121
Number registers:4 Modbus FC:4 Address:2120
RESULT:0:OK
>
22.3. modbusRtuOverTcp
modbusRtuOverTcp
Setting Description
CLI / Web Page [Page=modbus]
CLI Command l modbus.modbusRtuOverTcp=nnnn
l modbusRtuOverTcp=nnnn
Note: Where nnnn designates the TCP port used for the Modbus RTU
over TCP requests.
Note: See the Modbus window (on page 383) for parameter location.
modbusRtuOverTcp
Setting Description
Description The modbus.modbusRtuOverTcp parameter designates the TCP port used for
the Modbus RTU over TCP requests.
22.4. modbusTcp
modbusTcp
Setting Description
CLI / Web Page [Page=modbus]
CLI Command l modbus.modbusTcp=nnnn
l modbusTcp=nnnn
Note: Where nnnn designates the TCP port used for the Modbus TCP
requests.
Note: See the Modbus window (on page 383) for parameter location.
22.5. read
read
Setting Description
CLI / Web Page [Page=modbus]
read
Setting Description
CLI Command l modbus.read
l read
Default Setting N/A
Options Bool LongABCD
Byte LongBADC
FloatABCD LongCDAB
FloatBADC LongDCBA
FloatCDAB Raw
FloatDCBA Unsigned
IntABCD IntDCBA
IntBADC Signed
IntCDAB
Description The modbus.read parameter creates a Modbus request from the CLI.
Example
>read --srcId=1 --srcAddress=1000 --srcFc=FC4 --
type=longABCD --numElements=4
Id:1 Fc:4 Address: 1000 Type: LongABCD Value: 0
Id:1 Fc:4 Address: 1002 Type: LongABCD Value: 4000000
Id:1 Fc:4 Address: 1004 Type: LongABCD Value: 0
Id:1 Fc:4 Address: 1006 Type: LongABCD Value: 1
RESULT:0:OK
>
22.6. readCoils
readCoils
Setting Description
CLI / Web Page [Page=modbus]
CLI Command l modbus.readCoils
l readCoils
Default Setting N/A
Options N/A
readCoils
Setting Description
Description The modbus.readCoils parameter creates a Modbus request to read coils from
the CLI.
Example
>readCoils --srcId=1 --srcAddress=100 --srcFc=FC1 --
numElements=4
Id:1 Fc:1 Address: 100 Value: 1
Id:1 Fc:1 Address: 101 Value: 1
Id:1 Fc:1 Address: 102 Value: 1
Id:1 Fc:1 Address: 103 Value: 1
RESULT:0:OK
22.7. write
write
Setting Description
CLI / Web Page [Page=modbus]
CLI Command l modbus.write
l write
Default Setting N/A
Options Bool LongABCD
Byte LongBADC
FloatABCD LongCDAB
FloatBADC LongDCBA
FloatCDAB Raw
FloatDCBA Unsigned
IntABCD IntDCBA
IntBADC Signed
IntCDAB
Description The modbus.write parameter creates a Modbus write request from the CLI to
write to a holding register.
Example
>write --srcId=1 --srcAddress=100 --type=intabcd --
value=1024
RESULT:0:OK
22.8. writeCoils
writeCoils
Setting Description
CLI / Web Page [Page=modbus]
CLI Command l modbus.writeCoils
l writeCoils
Default Setting N/A
Options N/A
Description The modbus.writeCoils parameter creates a Modbus write request from the CLI
to write to the coils.
Example
>writeCoils --srcId=1 --srcAddress=100 --value=0x55 --
numElements=4
RESULT:0:OK
Modbus TCP
1. On the Z9-P2 or Z9-PE2, connect to port 502.
2. Use the Modbus TCP protocol.
3. In the CLI, enter modbus.modbusTcp=nnnn to change the port.
Note: Where nnnn designates the TCP port used for the Modbus TCP requests.
Set to 0 (zero) to disable Modbus TCP.
See modbusTcp (on page 255) for additional information.
Note: Where nnnn designates the TCP port used for the Modbus RTU over TCP requests.
Set to 0 (zero) to disable Modbus RTU over TCP requests.
See modbusRtuOverTcp (on page 254) for additional information.
22.10.2. Reading from the External Modbus RTU Serial Device using
COM2
1. Connect the device to the COM2 serial port.
2. Configure the COM port baudrate (on page 199) and other settings to match the serial
Modbus device.
3. Change the COM2 handler (on page 204) to Com2.handler=ModbusPassthru.
Notes
l Incoming requests that are not for the local Z9-P2 or Z9-PE2 device or for IOEX are sent
out COM2.
l Responses are returned out the port that the request came in on.
l The protocol is converted from Modbus TCP to Modbus RTU and back where necessary.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
23.1. arpFilterEnabled
arpFilterEnabled
Setting Description
CLI / Web Page [Page=network]
CLI Command l Enable the parameter: network.arpFilterEnabled=True
l Disable the parameter: network.arpFilterEnabled=False
Web Interface Arp Filter Enabled
window 1. Click the Arp Filter Enabled list box arrow and select True to enable the
parameter.
2. Click the Update button to save the change.
Note: See the Network window (on page 385) for parameter location.
23.2. gateway
gateway
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.gateway=nnn.nnn.nnn.nnn
l gateway=nnn.nnn.nnn.nnn
Note: See the Network window (on page 385) for parameter location.
gateway
Setting Description
Description The network.gateway parameter designates the Gateway IP address for the
network.
23.3. ip_address
ip_address
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.ip_address=nnn.nnn.nnn.nnn
l ip_address=nnn.nnn.nnn.nnn
Note: See the Network window (on page 385) for parameter location.
23.4. mac_address
mac_address
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.mac_address
l mac_address
mac_address
Setting Description
Web Interface MAC Address
window
Note: This parameter is read-only in the Web Interface.
See the Network window (on page 385) for parameter location.
23.5. MTU
mtu
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.mtu=nnnn
l mtu=nnnn
Note: See the Network window (on page 385) for parameter location.
mtu
Setting Description
Description The network.mtu parameter designates the maximum transmission unit (MTU)
frame size for the Z9-P2 or Z9-PE2.
Notes
l The MTU size only effects communications that originate or terminate on this
device, such as the web services or the Terminal Servers.
l All other traffic passing through the radio network is affected by this setting.
23.6. nameserver_address1
nameserver_address1
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.nameserver_address1=nnn.nnn.nnn.nnn
l nameserver_address1=nnn.nnn.nnn.nnn
Note: See the Network window (on page 385) for parameter location.
23.7. nameserver_address2
nameserver_address2
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.nameserver_address2=nnn.nnn.nnn.nnn.
l nameserver_address2=nnn.nnn.nnn.nnn
Note: See the Network window (on page 385) for parameter location.
23.8. netmask
netmask
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.netmask=nnn.nnn.nnn.nnn
l netmask=nnn.nnn.nnn.nnn
Note: See the Network window (on page 385) for parameter location.
netmask
Setting Description
Default Setting 255.255.255.0
Options N/A
Description The network.netmask parameter designates the Netmask of the Z9-P2 or Z9-
PE2.
23.9. netmaskFilterEnabled
netmaskFilterEnabled
Setting Description
CLI / Web Page [Page=network]
CLI Command l Enable:
l network.netmaskFilterEnabled=true
l netmaskFilterEnabled=true
l Disable:
l network.netmaskFilterEnabled=false
l netmaskFilterEnabled=false
Web Interface Netmask Filter Enabled
window 1. Click the Netmask Filter Enabled list box arrow and select True to enable
the bridge firewall and restrict network communication to current IPv4
subnet.
2. Click the Update button to save the change.
netmaskFilterEnabled
Setting Description
Description The network.netmaskFilterEnabled enables a bridge firewall to restrict network
communication to the current IPv4 subnet.
Notes
l Allows ONLY IPv4, TCP, UDP, ICMP (ping), and ARP communication that is
in the network.netmask parameter subnet to enter into the radio network.
l VLAN tagged packets are filtered out because the radio is not considered on
the VLAN and therefore VLAN packets cannot be on the same subnet.
l Enabling Netmask Filter can prevent non-radio Ethernet traffic from adversely
affecting the performance and capacity of the radio network.
23.10. stpEnabled
stpEnabled
Setting Description
CLI / Web Page [Page=network]
CLI Command l Enable:
l network.stpEnabled=true
l stpEnabled=true
l Disable:
l network.stpEnabled=false
l stpEnabled=false
Web Interface STP Enabled
window 1. Click the STP Enabled list box arrow and select True to enable the
Spanning Tree Protocol.
2. Click the Update button to save the change.
23.11. txqueuelen
txqueuelen
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.txqueuelen=nnnn
l txqueuelen=nnnn
Note: See the Network window (on page 385) for parameter location.
Default Setting 25
Options l The minimum value is 1.
l The maximum value is 1000.
Description The network.txqueuelen parameter designates the maximum number of packets
that can be buffered before they are rejected by the radio.
Notes
l The radio is still trying to send packets as soon as it receives them.
l If the queue size is too small in an Ethernet network with a high rate of small
packets, then packets could be lost.
l Increasing TX Queue Length may increase throughput if there is a lot of
network chatter that causes packets to be lost at the network layer.
l Increasing TX Queue Length can increase latency if the packets are arriving
at the Ethernet interface at an average rate that is above the capacity of the
radio link.
23.12. vlanMgmt
vlanMgmt
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.vlanMgmt=nnnn
l vlanMgmt=nnnn
Note: Where nnnn designates the Management VLAN ID for the Z9-P2 or
Z9-PE2.
Note: See the Network window (on page 385) for parameter location.
23.13. vlanTagPort1
vlanTagPort1
Setting Description
CLI / Web Page [Page=network]
vlanTagPort1
Setting Description
CLI Command l network.vlanTagPort1=nnnn
l vlanTagPort1=nnnn
Note: See the Network window (on page 385) for parameter location.
Note: Set to 0 (zero) to disable VLAN tagging for the designated Ethernet
port and allow VLAN tags to pass unchanged through the Z9-P2 or Z9-
PE2.
l The VLAN Tag ID is set on the Z9-P2 or Z9-PE2 designated Ethernet port.
l Egress Traffic
l Egress traffic tagged with the VLAN ID has the tag stripped and sent out the
designated Ethernet port.
l Egress traffic with 802.11ad double tags will have one tag stripped and sent
out the designated Ethernet port.
l Ingress Traffic
l Ingress traffic to the designated Ethernet port has the VLAN tag with that ID
added.
l Ingress traffic that is already tagged can have an additional tag added
(802.11ad double tag).
l vlanTagPort1 and vlanTagPort2 can have the same VLAN Tag ID.
23.14. vlanTagPort2
vlanTagPort2
Setting Description
CLI / Web Page [Page=network]
CLI Command l network.vlanTagPort2=nnnn
l vlanTagPort2=nnnn
Note: See the Network window (on page 385) for parameter location.
Note: Set to 0 (zero) to disable VLAN tagging for the designated Ethernet
port and allow VLAN tags to pass unchanged through the Z9-P2 or Z9-
PE2.
l The VLAN Tag ID is set on the Z9-P2 or Z9-PE2 designated Ethernet port.
l Egress Traffic
l Egress traffic tagged with the VLAN ID has the tag stripped and sent out the
designated Ethernet port.
l Egress traffic with 802.11ad double tags will have one tag stripped and sent
out the designated Ethernet port.
l Ingress Traffic
l Ingress traffic to the designated Ethernet port has the VLAN tag with that ID
added.
l Ingress traffic that is already tagged can have an additional tag added
(802.11ad double tag).
l vlanTagPort1 and vlanTagPort2 can have the same VLAN Tag ID.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
24.1. rx_bytes
rx_bytes
Setting Description
CLI / Web Page [Page=networkStats]
CLI Command l networkStats.rx_bytes
l rx_bytes
Web Interface RX Bytes
window
Note: This parameter is read-only in the Web Interface.
See the Network Stats window (on page 392) for parameter location.
24.2. rx_dropped
rx_dropped
Setting Description
CLI / Web Page [Page=networkStats]
CLI Command l networkStats.rx_dropped
l rx_dropped
Web Interface RX Dropped
window
Note: This parameter is read-only in the Web Interface.
See the Network Stats window (on page 392) for parameter location.
24.3. rx_errors
rx_errors
Setting Description
CLI / Web Page [Page=networkStats]
CLI Command l networkStats.rx_errors
l rx_errors
Web Interface RX Errors
window
Note: This parameter is read-only in the Web Interface.
See the Network Stats window (on page 392) for parameter location.
24.4. rx_packets
rx_packets
Setting Description
CLI / Web Page [Page=networkStats]
CLI Command l networkStats.rx_packets
l rx_packets
Web Interface RX Packets
window
Note: This parameter is read-only in the Web Interface.
See the Network Stats window (on page 392) for parameter location.
24.5. tx_bytes
tx_bytes
Setting Description
CLI / Web Page [Page=networkStats]
CLI Command l networkStats.tx_bytes
l tx_bytes
Web Interface TX Bytes
window
Note: This parameter is read-only in the Web Interface.
See the Network Stats window (on page 392) for parameter location.
24.6. tx_dropped
tx_dropped
Setting Description
CLI / Web Page [Page=networkStats]
CLI Command l networkStats.tx_dropped
l tx_dropped
Web Interface TX Dropped
window
Note: This parameter is read-only in the Web Interface.
See the Network Stats window (on page 392) for parameter location.
tx_dropped
Setting Description
Description The networkStats.tx_dropped command reports the number of Ethernet packets
received from the Ethernet port but dropped because the transmit queue is full.
24.7. tx_errors
tx_errors
Setting Description
CLI / Web Page [Page=networkStats]
CLI Command l networkStats.tx_errors
l tx_errors
Web Interface TX Errors
window
Note: This parameter is read-only in the Web Interface.
See the Network Stats window (on page 392) for parameter location.
24.8. tx_packets
tx_packets
Setting Description
CLI / Web Page [Page=networkStats]
CLI Command l networkStats.tx_packets
l tx_packets
tx_packets
Setting Description
Web Interface TX Packets
window
Note: This parameter is read-only in the Web Interface.
See the Network Stats window (on page 392) for parameter location.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
25.1. ntp_address
ntp_address
Setting Description
CLI / Web Page [Page=ntp]
CLI Command l ntp.ntp_address1=nnn.nnn.nnn.nnn
l ntp.ntp_address2=nnn.nnn.nnn.nnn
l ntp.ntp_address3=nnn.nnn.nnn.nnn
l ntp.ntp_address4=nnn.nnn.nnn.nnn
l ntp.ntp_address5=nnn.nnn.nnn.nnn
ntp_address
Setting Description
Description The ntp.ntp_address1-5 parameter designates the IP address of the server used
for synchronizing time.
Notes
l This can be a server such as time.nist.gov, time1.google.com or it can be
the IP address of another radio in the network.
l A maximum of five NTP servers are allowed.
l The fields in the NTP Parameters (on page 280) parameters are not validated
by the system.
l Use 0.0.0.0 to skip a specific server.
A common use is to have all of the Endpoints and Repeaters use the
IP address of the Gateway radio then the entire network will stay
synchronized to the Gateway time.
25.2. ntpDate
ntpDate
Setting Description
CLI / Web Page [Page=ntp]
CLI Command l ntp.ntpDate=now
l ntpDate=now
Web Interface NTP Date
window 1. In the NTP Date text box, enter Now to synchronize the local clock with the
time from the NTP servers specified in the ntp_address (on page 281)
settings.
2. Click the Update button to save the change.
Note: See the NTP window (on page 394) for parameter location.
ntpDate
Setting Description
Description The ntp.ntpDate parameter sets the local time from other NTP servers on the
network.
l The server with the best clock, as defined by the NTP protocol, is used.
l The fields in the NTP Parameters (on page 280) parameters are not validated
by the system.
25.3. ntpReference
ntpReference
Setting Description
CLI / Web Page [Page=ntp]
CLI Command l ntp.ntpReference=NETWORK_TIME_SERVER
l The reference is from other systems on the network.
l ntp.ntpReference=REFCLK_LOCALCLOCK
l The reference is generated by the local clock.
Web Interface NTP Reference
window 1. Click the NTP Reference list box arrow and select either NETWORK_
TIME_SERVER or REFCLK_LOCALCLOCK.
2. Click the Update button to save the change.
Note: See the NTP window (on page 394) for parameter location.
25.4. ntpRestart
ntpRestart
Setting Description
CLI / Web Page [Page=ntp]
CLI Command l ntp.ntpRestart=now
l ntpRestart=now
Web Interface NTP Restart
window
Note: This parameter is read-only in the Web Interface.
See the NTP window (on page 394) for parameter location.
Note: See the Radio Settings window - Endpoint (on page 396).
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
26.1. beaconBurstCount
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
beaconBurstCount
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.beaconBurstCount=n
l beaconBurstCount=n
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
Default Setting 3
Options Any number between 1 and 7.
Description The radioSettings.beaconBurstCount setting designates the number of
consecutive beacons to send per beaconInterval time.
Notes
l The radioSettings.beaconBurstCount is set only on the Gateway device.
l The Endpoint radios obtain this value from a Gateway with the same
networkId via the beacon frame.
l This setting is only used when
radiosettings.radioHoppingMode=Hopping_On.
l Increasing the number of beacons may improve RF link reliability in noisy
environments.
l Decreasing the number of beacons may improve throughput in environments
where interference is minimal.
26.2. beaconInterval
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
beaconInterval
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.beaconInterval=TWENTY_FIVE_MS
l beaconInterval=TWENTY_FIVE_MS
l radioSettings.beaconInterval=FIFTY_MS
l beaconInterval=FIFTY_MS
l radioSettings.beaconInterval=ONE_HUNDRED_MS
l beaconInterval=ONE_HUNDRED_MS
l radioSettings.beaconInterval=TWO_HUNDRED_MS
l beaconInterval=TWO_HUNDRED_MS
l radioSettings.beaconInterval=FOUR_HUNDRED_MS
l beaconInterval=FOUR_HUNDRED_MS
Web Interface Beacon Interval
window 1. Click the Beacon Interval list box arrow and select how often a Gateway
radio sends out a beacon packet and changes to the next radio frequency in
the hopping pattern.
2. Click the Update button to save the change.
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
beaconInterval
Setting Description
Description The radioSettings.beaconInterval controls how often a Gateway radio sends out
a beacon packet and changes to the next radio frequency in the hopping pattern.
Notes
l The radioSettings.beaconInterval is set only on the Gateway device.
l The Endpoint radios obtain this value from a Gateway with the same
networkId via the beacon frame.
l This setting is only used when
radiosettings.radioHoppingMode=Hopping_On.
l A shorter Beacon Interval may improve the RF link reliability in noisy
environments.
26.3. frequencyKey
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
frequencyKey
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.frequencyKey=Key0
l frequencyKey=Key0
l radioSettings.frequencyKey=Key1 to Key16
l frequencyKey=Key1 to Key16
Web Interface Frequency Key
window 1. Click the Frequency Key list box arrow and select the Key number used as
an index to select a hopping table.
2. Click the Update button to save the change.
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
frequencyKey
Setting Description
Options l Key0 (zero)
l Key1 to Key16
Valid frequencyKey Values
frequencyKey
Setting Description
Description The radioSettings.frequencyKey setting designates the Key number used as an
index to select a hopping table.
Notes
l Use a unique Frequency Key setting to use different hop patterns for each
ZumLink network.
l This setting is only used when
radiosettings.radioHoppingMode=Hopping_On.
l The number of available frequency keys is based on the number of hopping
sequences in the hop table.
l An invalid frequency key setting is determined by being outside of the
specified range.
l If an invalid frequency key setting is found, the
radioSettings.frequencyKey is NOT changed.
l A frequency key setting is also invalid if the frequency key setting is larger
than the number of hopping tables configured for a specific rfDataRate.
l In this instance, the radioSettings.frequencyKey is set to Key0 (zero).
Important!: The Endpoint radios obtain this value from a Gateway with the
same networkId (on page 296) via the beacon frame.
After communications are established, any change of this value are picked
up by the Endpoints.
26.4. frequencyMasks
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
frequencyMasks
Setting Description
CLI / Web Page [Page=radioSettings]
frequencyMasks
Setting Description
CLI Command l radioSettings.frequencyMasks=nnnn
l frequencyMasks=nnnn
Note: Where nnnn is the specified format of the frequency range to mask
shown in:
A. Single Channel Format,
B. Range of Channels Format, or
C. Combination of Channels Format.
Important!: Hop table frequency masking masks the channels that fall
within the range plus or minus one-half (½) the channel bandwidth.
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
frequencyMasks
Setting Description
Options
Caution: ONLY A comma MUST separate the values - NOT a
comma with a space.
l frequencyMasks=xxx.yyyy-xxx.yyyy,xxx.yyyy-xxx.yyyy
C. Combination of Channels Format
l frequencyMasks=xxx.yyyy-xxx.yyyy,xxx.yyyy
frequencyMasks
Setting Description
Description The radioSettings.frequencyMasks setting designates specific frequencies or a
set of frequencies in the hopping pattern to remove from usage.
Notes
l This setting is only used when
radiosettings.radioHoppingMode=Hopping_On.
l All radios in the network MUST use the same value for this parameter.
l When Frequency Masks is enabled, interference fixed at certain frequencies
within the spectrum can be avoided by the transmitter.
l Least significant zeros are NOT required.
l .9, .09, .009 are valid entries as well as .9000, .0900, .0090.
l The radioSettings.frequencyMasks parameter needs to be re-entered when
moving between rfDataRate (on page 307).
Important!: Special rules must be applied for the 115.2 and 250 kbps data
rates to enforce regulatory rules.
Notes for 115.2 and 250 kbps Rates for Regulatory Compliance
For 115.2 kbps:
l If the number of hopping channels contained in the hop table is > 50, txPower
(on page 309) can be set to values up to and including 30 dBm.
l radioSettings.txPower is NOT automatically changed.
l If the number of hopping channels contained in the hop table is < 50, all
masking is removed and all of the channels contained in the hop table are re-
enabled.
l radioSettings.txPower is NOT automatically changed.
frequencyMasks
Setting Description
l If the number of hopping channels contained in the hop table is < 25, all
masking is removed and all of the channels contained in the hop table are re-
enabled.
l radioSettings.txPower is NOT automatically changed.
26.5. lnaBypass
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
lnaBypass
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l Enable LNA:
l radioSettings.lnaBypass=0
l lnaBypass=0
l Bypass LNA:
l radioSettings.lnaBypass=1
l lnaBypass=1
Web Interface LNA Bypass
window 1. In the LNA Bypass text box, enter 1 to bypass the Low Noise Amplifier
(LNA) and reduce the radio module receive signal by 10dB.
2. Click the Update button to save the change.
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
26.6. maxLinkDistanceinMiles
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
maxLinkDistanceinMiles
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.maxLinkDistanceinMiles=nnn
l maxLinkDistanceinMiles=nnn
Note: Where nnn is the maximum one-way distance (in miles) between
any nodes in the network.
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
26.7. networkId
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
networkId
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.networkId=nnnn
l networkId=nnnn
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
Important!: If radios are on the same frequency, they still receive data
from radios of a different networkId, but the data is dropped.
26.8. nodeId
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
nodeId
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.nodeId=nnnn
l nodeId=nnnn
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
Default Setting Predetermined by the Z9-P2 or Z9-PE2, this is an auto-generated, unique number
from 2 through 65533.
Options N/A
Description The radioSettings.nodeId parameter designates the unique ID of the device.
Notes
l Each radio with the same networkId must have a UNIQUE nodeId.
l Otherwise, two or more nodes will unicast an acknowledgment that may
collide.
l The Gateway or Gateway-Repeater device ALWAYS has a nodeId of value
1. It cannot be changed.
26.9. radioFrequency
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
radioFrequency
Setting Description
CLI / Web Page [Page=radioSettings]
radioFrequency
Setting Description
CLI Command l radioSettings.radioFrequency=nnn.nnnn
l radioFrequency=nnn.nnnn
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
Default Setting 915.0000 for the Standard Hop Set - 900 MHz Channels (on page 431)
Options Valid Ranges
Data Rate MHz Range
4 Mbps 904.5504 - 925.7472
1.5 Mbps (Beta) 903.2562 - 925.8354
1 Mbps 903.0528 - 927.0144
500 kbps 902.7072 - 927.3600
250 kbps 902.5344 - 927.4176
115.2 kbps 902.4768 - 927.5904
radioFrequency
Setting Description
Description The radioSettings.radioFrequency parameter designates the operating center
frequency in MHz.
Notes
l All radios in the network MUST use the same value for this parameter.
l This setting is only used when
radiosettings.radioHoppingMode=Hopping_Off.
l The range of this parameter is dependent on the rfDataRate (on page 307)
setting.
l The frequency interval is 100 Hz.
l The minimum value increases and the maximum value decreases as the
radioSettings.rfDataRate increases.
l The increase in channel bandwidth affects these ranges.
l If the radioSettings.radioFrequency parameter is set too close to the band
edge for the current radioSettings.rfDataRate, the radio module rejects the
setting.
l A minimum of 3 hopping channels are supported when
radioSettings.rfDataRate =RATE_4M, RATE_1M, and RATE_500K.
Important!: A few seconds are needed to apply the change; allow some
time prior to reading back this value.
26.10. radioHoppingMode
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
radioHoppingMode
Setting Description
CLI / Web Page [Page=radioSettings]
radioHoppingMode
Setting Description
CLI Command l Enable:
l radiosettings.radioHoppingMode=Hopping_On
l radioHoppingMode=Hopping_On
l Disable:
l radiosettings.radioHoppingMode=Hopping_Off
l radioHoppingMode=Hopping_Off
Web Interface Radio Hopping Mode
window 1. Click the Radio Hopping Mode list box arrow and select Off to disable
frequency hopping.
2. Click the Update button to save the change.
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
radioHoppingMode
Setting Description
Description The radioSettings.radioHoppingMode parameter enables frequency hopping.
Notes
l All radios in the network MUST use the same value for this parameter.
l For rfDataRate values of 115.2 and 250 kbps, the
radioSettings.radioHoppingMode is forced On and CANNOT be set to
radiosettings.radioHoppingMode=Hopping_Off.
l For rfDataRate values of 500 kbps, 1 Mbps, and 4 Mbps, the choice of the
selected hopping mode is based on network frequency planning and channel
conditions.
l A Gateway is required when the
radiosettings.radioHoppingMode=Hopping_On.
l A Gateway is NOT required when the
radiosettings.radioHoppingMode=Hopping_Off.
Important!: Special rules must be applied for the 115.2 and 250 kbps data
rates to enforce regulatory rules.
Notes for 115.2 and 250 kbps Rates for Regulatory Compliance
For 115.2 kbps:
l If the number of hopping channels contained in the hop table is > 50, txPower
(on page 309) can be set to values up to and including 30 dBm.
l radioSettings.txPower is NOT automatically changed.
l If the number of hopping channels contained in the hop table is < 50, all
masking is removed and all of the channels contained in the hop table are re-
enabled.
l radioSettings.txPower is NOT automatically changed.
26.11. radioMaxRepeaters
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
radioMaxRepeaters
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.radioMaxRepeaters=n
l radioMaxRepeaters=n
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
radioMaxRepeaters
Setting Description
Description The radioSettings.radioMaxRepeaters parameter designates the maximum
Repeater slots in the network when the
radiosettings.radioHoppingMode=Hopping_On.
Note: The Endpoint radios obtain this value from a Gateway with the same
networkId via the beacon frame.
Note: Setting this value too high adds unnecessary latency to the
network.
Communication Method
The Z9-P2 or Z9-PE2 use Listen Before Talk (LBT) and Carrier Sense Multiple
Access (CSMA). There are no assigned slots. The radios transmit when the
channel is clear.
l The Gateway broadcasts packets to all Endpoints and Endpoint-Repeaters
within range.
l The Endpoints unicast packets back to the Gateway or downstream Endpoint-
Repeaters.
l The Gateway acknowledges the Endpoint or Endpoint-Repeater packets.
FreeWave’s traditional protocol has a Gateway Time Slot and an Endpoint Time
Slot within a frame.
l The Gateway transmits in its slot and listens in the Endpoint slot.
l The Endpoint transmits its slot and listens in the Gateway slot.
26.12. radioMode
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
radioMode
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.radioMode=Gateway
l radioMode=Gateway
l radioSettings.radioMode=Endpoint
l radioMode=Endpoint
l radioSettings.radioMode=Gateway_Repeater
l radioMode=Gateway_Repeater
l radioSettings.radioMode=Endpoint_Repeater
l radioMode=Endpoint_Repeater
Web Interface Radio Mode
window 1. Click the Radio Mode list box arrow and select the device type to
designate the Z9-P2 or Z9-PE2 as.
2. Click the Update button to save the change.
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
radioMode
Setting Description
Description The radioSettings.radioMode parameter designates the device type.
Notes
l Each network can have only ONE Gateway or Gateway-Repeater device.
l See Repeaters (on page 171) for additional information.
l The remaining devices MUST BE configured as Endpoints or Endpoint-
Repeaters.
l The Gateway or Gateway-Repeater device ALWAYS has a nodeId of value
1. It cannot be changed.
l The Endpoint or Endpoint-Repeater nodeId values are 2 through 65535.
l A Gateway is required when the
radiosettings.radioHoppingMode=Hopping_On.
l A Gateway is NOT required when the
radiosettings.radioHoppingMode=Hopping_Off.
l The Gateway-Repeater repeats packets.
l The Endpoint-Repeater has a unique nodeId and repeats packets and master
beacons.
l See Repeaters (on page 171) for additional information.
26.13. radioRepeaterSlot
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
radioRepeaterSlot
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.radioRepeaterSlot=n
l radioRepeaterSlot=n
radioRepeaterSlot
Setting Description
Web Interface Radio Repeater Slot
window 1. In the Radio Repeater Slot text box, enter which repeater slot the
Endpoint-Repeater uses.
2. Click the Update button to save the change.
Note: The Radio Repeater Slot parameter is only visible when the Z9-P2
or Z9-PE2 is designated as an Endpoint-Repeater.
See the Radio Settings window - Endpoint (on page 396) for parameter
location.
Default Setting 1
Options l 1
l 2
l 3
Description The radioSettings.radioRepeaterSlot parameter designates which repeater slot,
up to the radioMaxRepeaters setting, the Endpoint-Repeater uses.
Notes
l The radioSettings.radioRepeaterSlot is set on the Endpoint-Repeater
device when radiosettings.radioHoppingMode=Hopping_On.
l This setting does NOT apply when
radiosettings.radioHoppingMode=Hopping_Off.
l Repeater slots must be unique for Repeaters that are in communication range
so the beacons do not collide.
l Endpoint-Repeaters can share a slot number when they do not overlap and
form longer repeater chains.
l The number of entered Repeater slots cannot be larger than the numbered
entered in the radioMaxRepeaters (on page 302) setting.
26.14. rfDataRate
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
rfDataRate
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.rfDataRate=RATE_4M
l rfDataRate=RATE_4M
l radioSettings.rfDataRate=RATE_1M
l rfDataRate=RATE_1M
l radioSettings.rfDataRate=RATE_1.5M_BETA_FEATURE
l radioSettings.rfDataRate=RATE_500K
l rfDataRate=RATE_1.5M_BETA_FEATURE
l radioSettings.rfDataRate=RATE_250K
l rfDataRate=RATE_250K
l radioSettings.rfDataRate=RATE_115.2K
l rfDataRate=RATE_115.2K
Web Interface RF Data Rate
window 1. Click the RF Data Rate list box arrow and select the RF link data rate in bits
per second.
2. Click the Update button to save the change.
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
rfDataRate
Setting Description
Description The radioSettings.rfDataRate parameter designates the RF link data rate in bits
per second.
Notes
l All radios in the network MUST use the same value for this parameter.
l A higher RF link data rate provides more throughput but at the expense of link
distance or fade margin.
l When changing from lower data rates to higher ones
(e.g.,rfDataRate=RATE_115.2K to rfDataRate=RATE_1M), the
radioFrequency (on page 297) may be set back to the default if the frequency
would have been out of band.
l When selecting data rates of either rfDataRate=RATE_115.2K or
rfDataRate=RATE_250K, radioSettings.radioHoppingMode is
automatically forced to radiosettings.radioHoppingMode=Hopping_
On and cannot be turned off.
l For all other data rates, the radioSettings.radioHoppingMode remains at its
current setting.
Important!: Special rules must be applied for the 115.2 and 250 kbps data
rates to enforce regulatory rules.
Notes for 115.2 and 250 kbps Rates for Regulatory Compliance
For 115.2 kbps:
l If the number of hopping channels contained in the hop table is > 50, txPower
(on page 309) can be set to values up to and including 30 dBm.
l radioSettings.txPower is NOT automatically changed.
l If the number of hopping channels contained in the hop table is < 50, all
masking is removed and all of the channels contained in the hop table are re-
enabled.
l radioSettings.txPower is NOT automatically changed.
rfDataRate
Setting Description
l radioSettings.txPower is NOT automatically changed.
26.15. txPower
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
txPower
Setting Description
CLI / Web Page [Page=radioSettings]
CLI Command l radioSettings.txPower=nn
l txPower=nn
Note: See the Radio Settings window - Endpoint (on page 396) for
parameter location.
Default Setting l 30
Options l The minimum value is 10.
l The maximum value is 30.
txPower
Setting Description
Description The radioSettings.txPower setting designates the dB RF output transmit power
for the Z9-P2 or Z9-PE2.
Notes
l Output power is limited to maximum of 30dBm or 1 Watt.
l Use a higher power to increase link margin.
l Use a lower transmit power to reduce interference when multiple radio links
are in close proximity.
l The maximum radioSettings.txPower can be limited if the
radiosettings.radioHoppingMode=Hopping_On.
l See frequencyMasks (on page 290) for additional details.
Note: See the Radio Settings Helpers window (on page 404).
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
27.1. frequencyMasksErrors
frequencyMasksErrors
Setting Description
CLI / Web Page [Page=radioSettingsHelpers]
CLI Command l radioSettingsHelpers.frequencyMasksErrors
l frequencyMasksErrors
Web Interface Frequency Masks Errors
window
Note: This parameter is read-only in the Web Interface.
See the Radio Settings Helpers window (on page 404) for parameter
location.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
28.1. rteInstalledByAppsVersion
rteInstalledByAppsVersion
Setting Description
CLI / Web Page [Page=runtimeEnvironment]
CLI Command l runtimeEnvironment.rteInstalledByAppsVersion
l rteInstalledByAppsVersion
Web Interface Rte Installed by Apps Version
window
Note: This parameter is read-only in the Web Interface.
See the Runtime Environment window (on page 406) for parameter
location.
28.2. rteReset
rteReset
Setting Description
CLI / Web Page [Page=runtimeEnvironment]
CLI Command l runtimeEnvironment.rteReset=Cancel
l rteReset=Cancel
l runtimeEnvironment.rteReset=Hard
l rteReset=Hard
l runtimeEnvironment.rteReset=Now
l rteReset=Now
Web Interface Rte Reset
window
Note: This parameter is read-only in the Web Interface.
See the Runtime Environment window (on page 406) for parameter
location.
rteReset
Setting Description
Default Setting N/A
Options l Cancel
l Hard
l Now
Description The runtimeEnvironment.rteReset parameter designates the update or reset of
the runtime application environment.
l runtimeEnvironment.rteReset=Cancel is used to REMOVE the
rteReset=Hard command BEFORE the next boot of the Z9-P2 or Z9-PE2.
l runtimeEnvironment.rteReset=Hard completely resets the file system
of the runtime application environment to match the latest installed developer
user package.
l This will stage the development runtimeEnvironment to be applied on the
next reboot.
l The runtime application environment reset takes place at the time of next
boot.
l runtimeEnvironment.rteReset=Now
l This reboots the Z9-P2 or Z9-PE2 and copies the Linux application
environment into the runtime location.
This will take several minutes to complete.
The larger the IQ Application Environment, the longer the time needed.
28.3. rteTemplateVersion
rteTemplateVersion
Setting Description
CLI / Web Page [Page=runtimeEnvironment]
CLI Command l runtimeEnvironment.rteTemplateVersion
l rteTemplateVersion
Web Interface Rte Template Version
window
Note: This parameter is read-only in the Web Interface.
See the Runtime Environment window (on page 406) for parameter
location.
rteTemplateVersion
Setting Description
Options N/A
Description The runtimeEnvironment.rteTemplateVersion parameter reports the version
number for the IQ environment template.
This is the IQ environment applied when executing the rteReset=hard
command.
28.4. rteVersion
rteVersion
Setting Description
CLI / Web Page [Page=runtimeEnvironment]
CLI Command l runtimeEnvironment.rteVersion
l rteVersion
Web Interface Rte Version
window
Note: This parameter is read-only in the Web Interface.
See the Runtime Environment window (on page 406) for parameter
location.
Note: If this setting is blank, the application environment has not been
initialized.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
29.1. enableEthernetLogin
enableEthernetLogin
Setting Description
CLI / Web Page [Page=security]
CLI Command l Enable:
l security.enableEthernetLogin=true
l enableEthernetLogin=true
l Disable:
l security.enableEthernetLogin=false
l enableEthernetLogin=false
Web Interface Enable Ethernet Login
window 1. Click the Enable Ethernet Login list box arrow and select False to disable
SSH logins.
2. Click the Update button to save the change.
29.2. enablePtpInterface
enablePtpInterface
Setting Description
CLI / Web Page [Page=security]
enablePtpInterface
Setting Description
CLI Command l Enable:
l security.enablePtpInterface=true
l enablePtpInterface=true
l Disable:
l security.enablePtpInterface=false
l enablePtpInterface=false
Web Interface Ethernet PTP Interface
window 1. Click the Ethernet PTP Interface list box arrow and select False to disable
the PTP (drag-and-drop) interface.
2. Click the Update button to save the change.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
30.1. timeOutCli
timeOutCli
Setting Description
CLI / Web Page [Page=services]
CLI Command l services.timeOutCli=nnnn
l timeOutCli=nnnn
Note: See the Services window (on page 410) for parameter location.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
31.1. roCommunityName
roCommunityName
Setting Description
CLI / Web Page [Page=SNMP]
CLI Command l snmp.roCommunityName=enter_unique_name_here
l roCommunityName=enter_unique_name_here
Note: See the SNMP window (on page 412) for parameter location.
Important!: Special characters are allowed EXCEPT # but they may not
be compatible with 3rd-party SNMP managers.
31.2. rwCommunityName
rwCommunityName
Setting Description
CLI / Web Page [Page=SNMP]
CLI Command l snmp.rwCommunityName=enter_unique_name_here
l rwCommunityName=enter_unique_name_here
rwCommunityName
Setting Description
Web Interface RW Community Name
window 1. In the RW Community Name text box, enter the user-designated name for
SNMP V1/V2C Read-Write access.
2. Click the Update button to save the change.
Note: See the SNMP window (on page 412) for parameter location.
Important!: Special characters are allowed EXCEPT # but they may not
be compatible with 3rd-party SNMP managers.
31.3. snmpUser
snmpUser
Setting Description
CLI / Web Page [Page=SNMP]
CLI Command l Add User**:
l snmpUser=add <username>
l Modify User**:
l snmpUser=modify <username>
l Remove User:
l snmpUser remove <username>
l View All Users:
l snmpUser=show
snmpUser
Setting Description
Web Interface SNMP User
window
Note: This parameter is read-only in the Web Interface.
See the SNMP window (on page 412) for parameter location.
31.4. v1Enabled
v1Enabled
Setting Description
CLI / Web Page [Page=SNMP]
v1Enabled
Setting Description
CLI Command l Enable SNMP V1:
l snmp.v1Enabled=true
l v1Enabled=true
l Disable SNMP V1:
l snmp.v1Enabled=false
l v1Enabled=false
Web Interface V1 Enabled
window 1. Click the V1 Enabled list box arrow and select True to enable SNMP
V1.
2. Click the Update button to save the change.
Note: See the SNMP window (on page 412) for parameter location.
31.5. v2cEnabled
v2cEnabled
Setting Description
CLI / Web Page [Page=SNMP]
CLI Command l Enable SNMP V2C:
l snmp.v2cEnabled=true
l v2cEnabled=true
l Disable SNMP V2C:
l snmp.v2cEnabled=false
l v2cEnabled=false
Web Interface V2C Enabled
window 1. Click the V2C Enabled list box arrow and select True to enable SNMP
V2C.
2. Click the Update button to save the change.
v2cEnabled
Setting Description
Default Setting False
Options l True
l False
Description The snmp.v2cEnabled parameter enables SNMP V2C.
31.6. v3Enabled
v3Enabled
Setting Description
CLI / Web Page [Page=SNMP]
CLI Command l Enable SNMP V3:
l snmp.v3Enabled=true
l v3Enabled=true
l Disable SNMP V3:
l snmp.v3Enabled=false
l v3Enabled=false
Web Interface V3 Enabled
window 1. Click the V3 Enabled list box arrow and select True to enable SNMP
V3.
2. Click the Update button to save the change.
Important!: The [Page=system] parameters are only available in the CLI window.
See the Access the CLI and Change the IP Address and nodeId (on page 35) procedure for CLI
access.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
32.1. dump
dump
Setting Description
CLI / Web Page [Page=system]
CLI Command l system.dump
l dump
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
32.2. dumpFormat
dumpFormat
Setting Description
CLI / Web Page [Page=system]
CLI Command l system.dumpFormat=Full
l dumpFormat=Full
l system.dumpFormat=Json
l dumpFormat=Json
l system.dumpFormat=Result
l dumpFormat=Result
l system.dumpFormat=Short
l dumpFormat=Short
l system.dumpFormat=Verbose
l dumpFormat=Verbose
dumpFormat
Setting Description
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
32.3. dumpPage
dumpPage
Setting Description
CLI / Web Page [Page=system]
CLI Command l system.dumpPage=enter_page_name_here
l dumpPage=enter_page_name_here
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
dumpPage
Setting Description
Options N/A
Description The system.dumpPage command reports all device configuration and status
values for the specified page, using the format specified in dumpFormat (on page
329).
32.4. dumpTag
Important!: FreeWave internal use only.
32.5. filter
Important!: FreeWave internal use only.
32.6. help
help
Setting Description
CLI / Web Page [Page=system]
CLI Command l system.help
l help
l help <parameter>
l to see help for a specific parameter
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
help
Setting Description
Description The system.help command lists the help.txt file.
32.7. login
password
Setting Description
CLI / Web Page [Page=system]
CLI Command system.login=[username],[password]
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
32.8. logout
logout
Setting Description
CLI / Web Page [Page=system]
CLI Command l system.logout
l logout
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
logout
Setting Description
Options N/A
Description The logout command logs out of the CLI session.
32.9. pages
pages
Setting Description
CLI / Web Page [Page=system]
CLI Command l system.pages
l pages
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
32.10. password
password
Setting Description
CLI / Web Page [Page=system]
CLI Command system.password=[oldpassword],[newpassword],[newpassword]
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
password
Setting Description
Description The system.password parameter designates the password.
Example: system.password=admin,12345,12345.
Note: An error message appears when there is an error in typing the new
password command.
32.11. passwordRestoreDefaults
passwordRestoreDefaults
Setting Description
CLI / Web Page [Page=system]
CLI Command l system.passwordRestoreDefaults
l passwordRestoreDefaults
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
32.12. showLayout
Important!: FreeWave internal use only.
32.13. tags
Important!: FreeWave internal use only.
32.14. whoami
whoami
Setting Description
CLI / Web Page [Page=system]
CLI Command l system.whoami
l whoami
Web Interface
Important!: The [Page=system] parameters are only available in the CLI
window
window.
See the Access the CLI and Change the IP Address and nodeId (on page
35) procedure for CLI access.
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
33.1. deviceConfiguration
deviceConfiguration
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.deviceConfiguration
l deviceConfiguration
Web Interface Device Configuration
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.2. deviceFirmwareVersion
deviceFirmwareVersion
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.deviceFirmwareVersion
l deviceFirmwareVersion
Web Interface Device Firmware Version
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.3. deviceId
deviceId
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.deviceId=nnnn
l deviceId
Default Setting 1
Options N/A
Description l The systemInfo.deviceId parameter designates the Device Identifier
selected for the Z9-P2 or Z9-PE2.
l The systemInfo.deviceId=nnnn parameter designates the device ID.
l Where nnnn is a user-designated device ID.
33.4. deviceModel
deviceModel
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.deviceModel
l deviceModel
Web Interface window Device Model
33.5. deviceName
deviceName
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.deviceName=nnnn
l deviceName
Note: Where nnnn is the user-defined name for the Z9-P2 or Z9-PE2.
Note: See the System Info window (on page 414) for parameter location.
33.6. hopTableVersion
hopTableVersion
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.hopTableVersion
l hopTableVersion
Web Interface Hop Table Version
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.7. layoutHash
layoutHash
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.layoutHash
l layoutHash
Web Interface Layout Hash
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.8. licenses
licenses
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.licenses
l licenses
Web Interface Licenses
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.9. modelCode
modelCode
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.modelCode
l modelCode
Web Interface Model Code
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.10. radioFirmwareVersion
radioFirmwareVersion
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.radioFirmwareVersion
l radioFirmwareVersion
Web Interface Radio Firmware Version
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.11. radioModel
radioModel
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.radioModel
l radioModel
Web Interface Radio Model
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.12. radioModelCode
radioModelCode
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.radioModelCode
l radioModelCode
Web Interface Radio Model Code
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.13. radioSerialNumber
radioSerialNumber
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.radioSerialNumber
l radioSerialNumber
Web Interface Radio Serial Number
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.14. resetInfo
resetInfo
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.resetInfo
l resetInfo
Web Interface Reset Info
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.15. rteTemplateVersion
rteTemplateVersion
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systeminfo.rteTemplateVersion
l rteTemplateVersion
Web Interface N/A
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.16. rteVersion
rteVersion
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systeminfo.rteVersion
l rteVersion
Web Interface N/A
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
rteVersion
Setting Description
Description The systeminfo.rteVersion command reports the version number for the active
IQ environment.
Note: If this setting is blank, the application environment has not been
initialized. For the IQ Application Environment, see Verify Activation.
33.17. serialNumber
serialNumber
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.serialNumber
l serialNumber
Web Interface Serial Number
window
Note: This parameter is read-only in the Web Interface.
See the System Info window (on page 414) for parameter location.
33.18. themeVersion
themeVersion
Setting Description
CLI / Web Page [Page=systemInfo]
CLI Command l systemInfo.themeVersion
l themeVersion
themeVersion
Setting Description
Web Interface window Theme Version
Note: See the Terminal Server Relay window (on page 416).
Note: In the CLI, if the "=" sign is appended to the parameter, it is an implied change to that
parameter.
If a value is NOT included after the "=", the value becomes a null, space, or 0 (zero) depending on
the parameter.
34.1. remote_termserv_ip_address
remote_termserv_ip_address
Setting Description
CLI / Web Page [Page=TerminalServerRelay]
CLI Command l TerminalServerRelay.remote_termserv_ip_
address=nnn.nnn.nnn.nnn
l remote_termserv_ip_address=nnn.nnn.nnn.nnn
Note: See the Terminal Server Relay window (on page 416) for parameter
location.
34.2. termserv_relay_mapping
termserv_relay_mapping
Setting Description
CLI / Web Page [Page=TerminalServerRelay]
termserv_relay_mapping
Setting Description
CLI Command l TerminalServerRelay.termserv_relay_mapping=TERMSERV_
RELAY_DISABLED
l termserv_relay_mapping=TERMSERV_RELAY_DISABLED
l TerminalServerRelay.termserv_relay_mapping=LOCAL_BOTH_
COM_TO_REMOTE_BOTH_COM
l termserv_relay_mapping=LOCAL_BOTH_COM_TO_REMOTE_BOTH_
COM
l TerminalServerRelay.termserv_relay_mapping=LOCAL_COM1_
TO_REMOTE_COM1
l termserv_relay_mapping=LOCAL_COM1_TO_REMOTE_COM1
l TerminalServerRelay.termserv_relay_mapping=LOCAL_COM2_
TO_REMOTE_COM2
l termserv_relay_mapping=LOCAL_COM2_TO_REMOTE_COM2
l TerminalServerRelay.termserv_relay_mapping=LOCAL_BOTH_
COM_TO_REMOTE_COM1
l termserv_relay_mapping=LOCAL_BOTH_COM_TO_REMOTE_COM1
l TerminalServerRelay.termserv_relay_mapping=LOCAL_BOTH_
COM_TO_REMOTE_COM2
l termserv_relay_mapping=LOCAL_BOTH_COM_TO_REMOTE_COM2
l TerminalServerRelay.termserv_relay_mapping=LOCAL_COM1_
TO_REMOTE_BOTH_COM
l termserv_relay_mapping=LOCAL_COM1_TO_REMOTE_BOTH_COM
l TerminalServerRelay.termserv_relay_mapping=LOCAL_COM2_
TO_REMOTE_BOTH_COM
l termserv_relay_mapping=LOCAL_COM2_TO_REMOTE_BOTH_COM
Web Interface Termserv Relay Mapping
window 1. Click the Termserv Relay Mapping list box arrow and select a setting used
for the transfer of a bi-directional byte stream between two serial device
servers.
2. Click the Update button to save the change.
3. Restart the Z9-P2 or Z9-PE2 for the changes to be implemented.
Note: See the Terminal Server Relay window (on page 416) for parameter
location.
termserv_relay_mapping
Setting Description
Options l TERMSERV_RELAY_DISABLED
l Data forwarding between local and remote COM ports is disabled.
l LOCAL_BOTH_COM_TO_REMOTE_BOTH_COM (on page 355).
l Data is forwarded between the local COM1 and remote COM1 ports.
l Data is forwarded between the local COM2 and remote COM2 ports.
l LOCAL_COM1_TO_REMOTE_COM1 (on page 356).
l Data is forwarded between the local COM1 and remote COM1 ports.
l LOCAL_COM2_TO_REMOTE_COM2 (on page 357).
l Data is forwarded between the local COM2 and remote COM2 ports.
l LOCAL_BOTH_COM_TO_REMOTE_COM1 (on page 358).
l Data is forwarded between the local COM1 and remote COM1 ports.
l Data is forwarded between the local COM2 and remote COM1 ports.
l LOCAL_BOTH_COM_TO_REMOTE_COM2 (on page 359).
l Data is forwarded between the local COM1 and remote COM2 ports.
l Data is forwarded between the local COM2 and remote COM2 ports.
l LOCAL_COM1_TO_REMOTE_BOTH_COM (on page 360).
l Data is forwarded between the local COM1 and remote COM1 ports.
l Data is forwarded between the local COM1 and remote COM2 ports.
l LOCAL_COM2_TO_REMOTE_BOTH_COM (on page 361).
l Data is forwarded between the local COM2 and remote COM1 ports.
l Data is forwarded between the local COM2 and remote COM2 ports.
termserv_relay_mapping
Setting Description
Description The TerminalServerRelay.termserv_relay_mapping parameter is used to
transfer a bi-directional byte stream between two serial device servers.
Notes
l The data relay is only supported between the terminal server on this Z9-P2 or
Z9-PE2 radio and the terminal server on a separate Z9-P2 or Z9-PE2 radio in
the same IP network.
See Terminal Server Relay Examples (on page 352).
l For the relay function to operate, COM1 must be assigned to port 5041 and and
COM2 must be assigned to port 5042 on both the local and remote terminal
servers.
l The TerminalServerRelay.termserv_relay_mapping should only be enabled
on one side of the connection.
l When the termserv_relay_mapping (on page 348) parameter is designated and
the flowControl (on page 203) parameter is set to Hardware, the COM port's
flow control does not function.
l Connected Terminal Servers and Terminal Server Relay (on page 353)
l LOCAL_BOTH_COM_TO_REMOTE_BOTH_COM (on page 355)
l LOCAL_COM1_TO_REMOTE_COM1 (on page 356)
l LOCAL_COM2_TO_REMOTE_COM2 (on page 357)
l LOCAL_BOTH_COM_TO_REMOTE_COM1 (on page 358)
l LOCAL_BOTH_COM_TO_REMOTE_COM2 (on page 359)
l LOCAL_COM1_TO_REMOTE_BOTH_COM (on page 360)
l LOCAL_COM2_TO_REMOTE_BOTH_COM (on page 361)
l Example: Multicast (on page 362)
Note: Figure 205 shows the ZumLink Z9-PE connections. They are the same for the Z9-P2 or Z9-
PE2.
l The Bridge connects the Ethernet interface with the radio interface.
l The Terminal Servers are connected to the COM ports.
l From any network interface you can get to the Terminal Servers.
The Terminal Server Relay is designed to connect the local Terminal Servers (hence the COM
ports) to any remote Terminal Server.
l This connection could be over the Ethernet or radio interface.
l It does not matter since it is a TCP connection.
l Each terminal server can have 20 concurrent TCP connections.
l Expects COM1 to be on port 5041 for both local and remote units.
l Expects COM2 to be on port 5042 for both local and remote units.
Figure 205: Terminal Servers and Terminal Server Relay (Client) Connected
Together through the Bridge
35.2. LOCAL_BOTH_COM_TO_REMOTE_BOTH_COM
Figure 206 illustrates the Terminal Server Relay command:
LOCAL_BOTH_COM_TO_REMOTE_BOTH_COM.
l Data is forwarded between the local COM1 and remote COM1 ports.
l Data is forwarded between the local COM2 and remote COM2 ports.
35.3. LOCAL_COM1_TO_REMOTE_COM1
Figure 207 illustrates the Terminal Server Relay command:
LOCAL_COM1_TO_REMOTE_COM1.
l Data is forwarded between the local COM1 and remote COM1 ports.
35.4. LOCAL_COM2_TO_REMOTE_COM2
Figure 208 illustrates the Terminal Server Relay command:
LOCAL_COM2_TO_REMOTE_COM2.
l Data is forwarded between the local COM2 and remote COM2 ports.
35.5. LOCAL_BOTH_COM_TO_REMOTE_COM1
Figure 209 illustrates the Terminal Server Relay command:
LOCAL_BOTH_COM_TO_REMOTE_COM1.
l Data is forwarded between the local COM1 and remote COM1 ports.
l Data is forwarded between the local COM2 and remote COM1 ports.
35.6. LOCAL_BOTH_COM_TO_REMOTE_COM2
Figure 210 illustrates the Terminal Server Relay command:
LOCAL_BOTH_COM_TO_REMOTE_COM2.
l Data is forwarded between the local COM1 and remote COM2 ports.
l Data is forwarded between the local COM2 and remote COM2 ports.
35.7. LOCAL_COM1_TO_REMOTE_BOTH_COM
Figure 211 illustrates the Terminal Server Relay command:
LOCAL_COM1_TO_REMOTE_BOTH_COM.
l Data is forwarded between the local COM1 and remote COM1 ports.
l Data is forwarded between the local COM1 and remote COM2 ports.
35.8. LOCAL_COM2_TO_REMOTE_BOTH_COM
Figure 212 illustrates the Terminal Server Relay command:
LOCAL_COM2_TO_REMOTE_BOTH_COM.
l Data is forwarded between the local COM2 and remote COM1 ports.
l Data is forwarded between the local COM2 and remote COM2 ports.
Note: See the COM Parameters (on page 198) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
5. Click either the COM1 or COM2 tab to access their respective COM parameters. Figure
215 or Figure 216
Note: The parameters for COM1 and COM2 are the same except for the TerminalServerPort
(on page 209) parameter setting.
See the COM Parameters (on page 198) for detailed information about the parameters.
6. Optional: On the Menu list, click the Configuration link to Change the COM Parameters
(on page 91).
Note: See the config Parameters (on page 212) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
4. On the Menu list, click the System Info link. Figure 217
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Config tab to access the Config parameters. Figure 218
Note: See the dataPath Parameters (on page 216) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Data Path tab to access the Data Path parameters. Figure 220
7. Optional: On the Menu list, click the Configuration link to Change the Data Path
Parameters (on page 94).
Note: See the date Parameters (on page 225) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Date tab to access the Date parameters. Figure 222
Note: See the encryption Parameters (on page 230) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Encryption tab to access the Encryption parameters. Figure 224
Note: See the encryption Parameters (on page 230) for detailed information about the
parameters.
7. Optional: On the Menu list, click the Configuration link to Change the Encryption
Parameters (on page 96).
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
4. On the Menu list, click the File Upload link. Figure 225
Note: If the User Name or Password were changed, enter the applicable information.
Send button Click to start the update process on the Z9-P2 or Z9-PE2.
Cancel button Click to cancel the file transfer if already started or refresh the window and
clear the selected file.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Login dialog box closes and the Help window opens. Figure 228
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: See the ioexcom Parameters (on page 234) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Io Ex Com tab to access the Io Ex Com parameters. Figure 231
Note: See the ioexcom Parameters (on page 234) for detailed information about the
parameters.
Note: See the localDiagnostics Parameters (on page 235) for detailed information about the
parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Local Diagnostics tab to access the Local Diagnostics parameters. Figure 233
Note: See the localDiagnostics Parameters (on page 235) for detailed information about the
parameters.
7. Optional: On the Menu list, click the Configuration link to Change the Local Diagnostics -
Monitored Node (on page 99).
Note: See the modbus Parameters (on page 252) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Modbus tab to access the Modbus parameters. Figure 235
Note: See the modbus Parameters (on page 252) for detailed information about the
parameters.
7. Optional: On the Menu list, click the Configuration link to Change the Modbus Parameters
(on page 101).
Note: See the network Parameters (on page 262) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Network tab to access the Network parameters. Figure 237
Note: See the network Parameters (on page 262) for detailed information about the
parameters.
7. Optional: On the Menu list, click the Configuration link to Change the Network
Parameters (on page 103).
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
The Network Diagnostics window opens, scanning the network. Figure 239
The diagram takes a few moments to render.
The Options list box default selection is Margin.
Options list box Save Image Select the Save Image option to open the Save Image dialog
box.
Options list box Gateway IP Select the Gateway IP option to open the Add Device IP
dialog box and add a Gateway IP address.
Options list box Save Select the Save Network Diagnostics option to open the
Network Opening network_diag.json dialog box.
Diagnostics
Note: See Save Network Diagnostics (on page 134) to
save the current network performance reading for later
review and to monitor network performance over time.
Options list box Download Select the Download Support Bundle option to open the
Support Opening support_bundle_nnn.zip dialog box.
Bundle
Note: Where nnn is the selected device in the Network
Diagram.
Options list box Refresh Select the Refresh Network Diagnostics option to updated
Network the current network performance reading.
Diagnostics
Options list box Clear All Select the Clear All Stats option to reset the localDiagnostics
Stats Parameters (on page 235), networkStats Parameters (on page
274), and Network Diagnostics.
Options list box Clear Stats Select the Clear Stats option to clear only the local
diagnostics.
Options list box RSSI Click the Options list box arrow and select the RSSI option to
show the RSSI connections in the Network Diagram.
Options list box Tx Rate Click the Options list box arrow and select the Tx Rate option
to show the Tx Rate connections in the Network Diagram.
Options list box Rx Rate Click the Options list box arrow and select the Rx Rate option
to show the Rx Rate connections in the Network Diagram.
Options list box Margin with Click the Options list box arrow and select the Margin with
Neighbors Neighbors option to show the Margin with Neighbors
connections in the Network Diagram.
Options list box RSSI with Click the Options list box arrow and select the RSSI with
Neighbors Neighbors option to show the RSSI with Neighbors
connections in the Network Diagram.
Options list box Cose- Click the Options list box arrow and select the Cose-bilkent
bilkent option to show the Cose-bilkent connections in the Network
Diagram.
Options list box Grid Click the Options list box arrow and select the Grid option to
show the Grid connections in the Network Diagram.
Options list box Dagre When Dagre is select, the network diagram shows possible
loops in a complicated network.
Options list box Paused When Paused is selected, no updates or layout changes are
made in the network diagram.
Options list box Updating When Updating Layout is select, the node layouts are
Layout automatically set by the computer.
Note: See the networkStats Parameters (on page 274) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Network Stats tab to access the Network Stats parameters. Figure 241
Note: See the NTP Parameters (on page 280) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the NTP tab to access the NTP parameters. Figure 243
7. Optional: On the Menu list, click the Configuration link to Change the NTP Parameters
(on page 105).
Note: See the radioSettings Parameters (on page 285) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings tab to access the Radio Settings parameters. Figure 245
Note: By default, the radioMode (on page 304) parameter is set to Endpoint.
See the radioSettings Parameters (on page 285) for detailed information about the
parameters.
7. Optional: On the Menu list, click the Configuration link to Change the Radio Settings
Parameters - Endpoint (on page 107).
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
Note: See the radioSettings Parameters (on page 285) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings tab to access the Radio Settings parameters.
Note: By default, the radioMode (on page 304) parameter is set to Endpoint.
See the radioSettings Parameters (on page 285) for detailed information about the
parameters.
7. Click the Radio Mode list box arrow and select Endpoint_Repeater. Figure 247
8. Optional: On the Menu list, click the Configuration link to Change the Radio Settings
Parameters - Endpoint-Repeater (on page 109).
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
Note: See the radioSettings Parameters (on page 285) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings tab to access the Radio Settings parameters.
Note: By default, the radioMode (on page 304) parameter is set to Endpoint.
See the radioSettings Parameters (on page 285) for detailed information about the
parameters.
7. Click the Radio Mode list box arrow and select Gateway. Radio Settings window -
Gateway (on page 401)
8. Optional: On the Menu list, click the Configuration link to Change the Radio Settings
Parameters - Gateway (on page 111).
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
Note: See the radioSettings Parameters (on page 285) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings tab to access the Radio Settings parameters.
Note: By default, the radioMode (on page 304) parameter is set to Endpoint.
See the radioSettings Parameters (on page 285) for detailed information about the
parameters.
7. Click the Radio Mode list box arrow and select Gateway_Repeater. Figure 251
8. Optional: On the Menu list, click the Configuration link to Change the Radio Settings
Parameters - Gateway-Repeater (on page 114).
Important!: Only radioSettings that apply to the current radioMode, rfDataRate, and
radioHoppingMode, and are visible in the CLI and the Web Interface and can be changed.
Note: This window is only available if the radioHoppingMode (on page 299) parameter is set to
Hopping_On.
See the radioSettingsHelpers Parameters (on page 311) for detailed information about the
parameters.
See frequencyMasks (on page 290) for usage.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Radio Settings Helpers tab to access the Radio Settings Helpers
parameter. Figure 253
Note: See the runtimeEnvironment Parameters (on page 313) for detailed information about the
parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Runtime Environment tab to access The Runtime Environment parameters.
Figure 255
Note: See the security Parameters (on page 317) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
5. Click the Security tab to access the Security parameters. Figure 257
Note: See the security Parameters (on page 317) for detailed information about the
parameters.
6. Optional: On the Menu list, click the Configuration link to Change the Security Parameters
(on page 117).
Note: See the services Parameters (on page 320) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Services tab to access the Services parameters. Figure 259
Note: See the services Parameters (on page 320) for detailed information about the
parameters.
7. Optional: On the Menu list, click the Configuration link to Change the Services
Parameters (on page 119).
Note: See the SNMP Parameters (on page 322) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
Note: See the SNMP Parameters (on page 322) for detailed information about the
parameters.
7. Optional: On the Menu list, click the Configuration link to Change the SNMP Parameters
(on page 121).
Note: See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the System Info tab to access the System Info parameters. Figure 263
7. Optional: On the Menu list, click the Configuration link to Change the System Info
Parameters (on page 123).
Note: See the TerminalServerRelay Parameters (on page 347) for detailed information about the
parameters.
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
Note: If the User Name or Password were changed, enter the applicable information.
6. Click the Terminal Server Relay tab to access the Terminal Server Relay
parameters. Figure 265
Note: See the TerminalServerRelay Parameters (on page 347) for detailed information about
the parameters.
7. Optional: On the Menu list, click the Configuration link to Change the Terminal Server
Relay Parameters (on page 125).
Note: If this is the first time the Z9-P2 or Z9-PE2 is accessed, enter its default IP address of
192.168.111.100.
If the IP address was changed, enter that IP Address.
See the systemInfo Parameters (on page 336) for detailed information about the parameters.
4. On the Menu list, click the User Data - Drag and DropUser Data link.
Note: If the User Name or Password were changed, enter the applicable information.
The Login dialog box closes and the User Data window opens. Figure 267
Note: See the Z9-P2 or Z9-PE2 Files and Descriptions (on page 465) for additional information.
These sections describe the additions, changes, and known limitations in each software version
for the ZumLink Z9-P2 or Z9-PE2. The most recent version is listed first.
The latest firmware and software versions and the most recent list of known limitations and
workarounds are available on www.freewave.com.
Note: See the SupplyVoltage (on page 248) parameter for more information.
l VLAN Management
l Users can only access the device from the VLAN ID.
l If the VLAN tag is set on a specific Ethernet port, that port cannot be used to access
Note: See the vlanMgmt (on page 271) parameter for additional information.
l Windows® File Explorer now shows 4.4 GB of space instead of the 1.8 GB in previous
software versions.
l This is a result of the ptp directory moving to a new partition.
l To view space available for applications, login as devuser and run the command df-h.
l The /persist directory is where applications reside.
l Cannot change the date.timeString once the time is set using NTP.
l The UCD-SNMP-MIB-WP201.txt file is missing definition for dskIndex.
l The Ethernet ports can become unresponsive after changing networks and the
vlanTagPort1 (on page 271) and/or vlanTagPort2 (on page 273) IDs.
l Workaround: Reboot the Z9-P2 or Z9-PE2 for changes to take effect.
l Setting the vlanTagPort1 (on page 271) or vlanTagPort2 (on page 273) may affect the
connectivity of the other port.
l Unable to get input voltage via Modbus.
l When using the Web Interface on a computer with Windows® 8 or Windows® 10, clicking
Cancel does not halt the upload process.
l Files uploaded using the Web Interface drag-n-drop procedure are now write-protected
and cannot be deleted.
l When changing and saving the radioSettings Parameters (on page 285), the CLI interface
may momentarily lock.
l If there is enough space to transfer the update firmware but not enough to facilitate the
update, the update fails and the Upgrade Failed LEDs do not function.
l Workaround: Users should verify the available free space before uploading an update
firmware file.
At least 2x free space is needed on the Z9-P2 or Z9-PE2 for the firmware update file.
l Users should wait at least 30 seconds after a factory default command is issued before
making configuration changes.
l The fields in the NTP Parameters (on page 280) parameters are not validated by the
system.
l Workaround: Verify the NTP parameter settings are correct.
l Unable to set the time when the ntpReference (on page 283) parameter =NETWORK_
TIME_SERVER.
l The highest baud rate supported for RS422 and RS485 is 421 kbps.
l In Firmware v1.1.2.2, when the flowControl (on page 203) parameter is set to hardware,
the COM port's flow control does not function.
l Exiting from the CLI may take up to 30 seconds.
l Entering the shortcut text of ModbusTcp and ModbusRtuOverTcp results in a
DUPLICATE_PARAMETER Error.
l Workaround: The fully-qualified parameter of modbus.modbusTcp and
l VSWR reading may be inconsistent between the Network Diagram on the Network
Diagnostics window (on page 387) and the information reported in the Local Diagnostics
window (on page 381).
l The File Upload window (on page 374) shows a 100% upload when the upload file has not
completed on Windows® 8 and Windows® 10 computers.
l Workaround: Wait the appropriate amount of time or watch the LEDs to indicate
completion of file transfer or use the v1112-Firmware Update - Drag and Drop
procedure.
l When setting the parameter arpFilterEnabled=true, ARP requests and responses are
NOT blocked on VLAN interfaces.
l Rebooting a pair of radios simultaneously when one of the Z9-P2 or Z9-PE2 has the
parameter termserv_relay_mapping=Enabled, the terminal server relay takes up to 6
minutes to become active.
l To update the Network Diagnostics window (on page 387), refresh the browser to clear the
browser cache.
l When the termserv_relay_mapping (on page 348) parameter is designated and the
flowControl (on page 203) parameter is set to Hardware, the COM port's flow control does
not function.
l Significant data is lost between radios when operating in close proximity (3-6 feet) when
radioSettings.rfDataRate=RATE_4M (See rfDataRate (on page 307)).
l Workarounds:
l When using the USB, the CLI may lock up on units with termserv_relay_mapping (on page
348) enabled.
l Workarounds:
l The signalLevel (on page 236) parameter reports a maximum of -42 dBm when the
rfDataRate=RATE_1M.
Note: When the Radio Hopping Mode is Disabled, the frequency can be set manually.
These are the supported item groups in the Z9-P2 or Z9-PE2 MIB file:
l CPU Usage (on page 435)
l Disk Usage (on page 435)
l Memory Usage (on page 437)
l FreeWave Technologies - MIB (on page 438)
l SNMP Write Access (on page 451)
>snmp
[Page=snmp]
v1Enabled=false
v2cEnabled=true
v3Enabled=false
roCommunityName=public
rwCommunityName=private
snmpUser
RESULT:0:OK
Best practice for snmp.v2cEnabled is to change the snmp.rwCommunityName for a production network.
Note: Specifications are subject to change without notice. For the most up-to-date specifications
information, see the product's data sheet available at www.freewave.com.
Computing Resources
Note: Access to the Computing Resources for the Z9-P2 or Z9-PE2 requires licensing.
For information, contact FreeWave Sales at www.freewave.com/how-to-buy.
Computing Resources
Specification Description
CPU ARM Cortex-A8 1 GHz
RAM 1 GB
Storage 1 GB
OS Debian-based Linux
Data Transmission
Data Transmission
Specification Description
Type Frequency Hopping Spread Spectrum
Modulation l 2 level GFSK
l 4- and 8-ary FSK
Link Throughput l Maximum of 1.6 Mbps
l 4 Mbps with Compression
Error Detection l ARQ
l CRC
l Retransmit on error
l Forward Error Correction (FEC)
Hopping Rates 400, 200, 100, 50, 25 ms
Hopping Channels l Maximum of 110 channels
l rfDataRate (on page 307) dependent
Hopping Patterns l Maximum of 16 patterns
l rfDataRate (on page 307) dependent
Protocol Adaptive Spectrum Learning (ASL)
User Interface Rate l Ethernet Rate: 10/100 Mbps
l Serial Rate: up to 250 kbps
Data Encryption 128-and 256-bit AES CCM
Advanced Features l Packet Aggregation
l Packet Compression
General Information
General Information
Specification Description
Operating Temperature l Z9-P2
l -40°C to +85°C
l -40°F to +185°F
l Z9-PE2
l -40°C to +75°C
l -40°F to +167°F
Z9-PE2:
Interfaces
Interfaces
Specification Description
Data Connectors l Four RJ-45s
l 2 Ethernet
l 2 Serial
USB Connector l Micro USB
l Type A USB (Future Expansion)
RF Connector TNC
Power Connectors Phoenix Contact (# 1776692)
Management
Management
Specification Description
Management l Enterprise MIB
l HTTP
l MIB-II
l Modbus
l SNMPv1/v2c/v3
l SSH
Networking
Networking
Specification Description
Serial l Modbus RTU
l Modbus/TCP
l TCP client
l TCP server
Traffic Filtering l ARP filter
l Netmask filter
VLAN 802.1Q
Power Requirements
Maximum Recommended
Operating Voltage
Current Draw Supplied Current
+6 VDC 870 mA 900 mA
+12 VDC 490 mA 520 mA
+24 VDC 270 mA 300 mA
+30 VDC 220 mA 250 mA
Receiver
Receiver
Specification Description
IF Selectivity > 40 dB
System Gain 135 dB
Sensitivity RF Data Rate Without FEC With FEC
115.2 kbps -105 dBm -108 dBm
250 kbps -102 dBm -105 dBm
500 kbps -99 dBm -102 dBm
1 Mbps -95 dBm -98 dBm
1.5 Mbps (Beta) -90 dBm -93 dBm
4 Mbps -83 dBm -86 dBm
Transmitter
Transmitter
Specification Description
Frequency Range l 902 to 928MHz
l Thailand:
Z9-P2-THA & Z9-PE2-THA: 920 to 925 MHz
Frequency Stability 15ppm
Output Power l 10mW to 1W
l User selectable
Output Impedance 50 ohms
Range 97 km (60 miles), clear line of sight
Channel Spacing l 230.4 kHz l 1382.4 kHz
l 345.6 kHz l 1612.8 (Beta) kHz
l 691.2 kHz l 3225.6 kHz
Figure 268: Exposed Copper Heat Sink Surface of the Z9-P2 Radio PCB
Appendix D: LEDs
Note: See Z9-P2 Port Connections (on page 21) or Z9-PE2 Port Connections (on page 21) for additional information.
Normal Operation
LEDs - Normal Operation
CD TX RX Condition Notes
Solid Red (Bright) Not Linked While operating with Frequency Hopping enabled,
this LED indicates the radio has NOT received the
beacon within the last 60 seconds.
Solid Green Radio linked The radio is linked with a margin of 20dB or greater
above sensitivity or noise level, whichever is
highest.
Solid Green Solid Green Receiving Data The radio is actively receiving data over the wireless
or RF link.
Alternate Solid
Green / Solid Red
(Bright)
COM LEDs
Note: During boot, the COM LEDs will cycle indicating startup.
LEDs - COM
LED LED Color Description
COM1 Left Blinking Green Transmitting data on COM1.
COM1 Right Blinking Green Receiving data on COM1.
COM2 Left Blinking Green Transmitting data on COM2.
COM2 Right Blinking Green Receiving data on COM2.
Ethernet LEDs
LEDs - Ethernet
LED LED Color Description
Ethernet Left Solid Green l Shows Power.
l LED is lit while power is applied to the Ethernet module.
Ethernet Right Solid Green Shows Ethernet link but no activity.
Ethernet Right Blinking Green l Shows Activity.
l LED will blink / flicker while sending and receiving data on the Ethernet port.
When the Windows® File Explorer window of the Z9-P2 or Z9-PE2 is opened, there are default
files that appear.
This is a list of those files and descriptions of their purpose.
Note: If the Z9-P2 or Z9-PE2 has been updated or rebooted, other files may appear.
Note: This file appears after the ZumLink has been updated to a newer
version of firmware.
help.txt The help.txt file contains online user assistance information using the CLI
commands.
layout.txt The layout.txt file is used for management applications to provide the CLI and
config.cfg with a format description of the commands.
modbuslayout.txt
Note: The modbuslayout.txt file is not used.
result.txt The result.txt is used to verify the acceptance or rejection of each parameter
change applied to the config.txt file.
Note: This file appears after the config.txt file of the ZumLink has been
changed.
sys_info.txt The sys_info.txt file provides information about the radio including serial
number, model number, firmware versions, and device name.
This table provides a register map for the Modbus Input / Output devices.
Note: The Register Names that can be polled using Modbus correspond to the pages of the CLI.
Export Notification
FreeWave Technologies, Inc. products may be subject to control by the Export Administration Regulations (EAR)
and/or the International Traffic in Arms Regulations (ITAR). Export, re-export, or transfer of these products without
required authorization from the U.S. Department of Commerce, Bureau of Industry and Security, or the U.S.
Department of State, Directorate of Defense Trade Controls, as applicable, is prohibited. Any party exporting, re-
exporting, or transferring FreeWave products is responsible for obtaining all necessary U.S. government
authorizations required to ensure compliance with these and other applicable U.S. laws. Consult with your legal
counsel for further guidance.
Restricted Rights
Any product names mentioned in this manual may be trademarks or registered trademarks of their respective
companies and are hereby acknowledged.
This manual is only for use by purchasers and other authorized users of FreeWave products.
No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical,
or for any purpose without the express written permission of FreeWave Technologies, Inc. FreeWave reserves
the right to make changes to this manual without notice. FreeWave assumes no responsibility or liability for the
use of this manual or the infringement of any copyright or other proprietary right.
FreeWave products are designed and manufactured in the United States of America.
Warning! DO NOT OPEN THE ZumLink Z9-P2 or Z9-PE2 WHEN AN EXPLOSIVE ATMOSPHERE IS
PRESENT.
FCC Notifications
FCC Supplier's Declaration of Conformity
FreeWave Technologies, Inc.
5395 Pearl Parkway, Boulder, CO 80301
Phone Number: 303.381.9200
Website: www.freewave.com
declare under our sole responsibility that the product Models: Z9-P2 or Z9-PE2 complies with Part 15 of FCC
Rules.
Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2)
this device must accept any interference received, including interference that may cause undesired operation.
The content of this guide covers FreeWave Technologies, Inc. models sold under FCC ID: KNYPMT0101AB.
All models sold under the listed FCC ID(s) must be installed professionally and are only approved for use when
installed in devices produced by FreeWave Technologies or third party OEMs with the express written approval
of FreeWave Technologies, Inc. Changes or modifications should not be made to the device.
Changes or modifications not expressly approved by the party responsible for compliance could void the user's
authority to operate the equipment.
FCC Part 15 Class A
Note: This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with
the User-Reference Manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference in which case the user will be
required to correct the interference at their own expense.
(This radio communication equipment has the electromagnetic field strength in compliance with the Safety
Standard for the Use of Radio communication Equipment on Human Health announced by the National
Telecommunications Commission.)
UL Power Source
Input power shall be derived from a certified, Class 2:
l single power source or
l a limited power source (LPS) in accordance with:
l UL 60950-1
l IEC/EN 60950-1
l CAN/CSA C22.2 No. 60950-1-07.
l Input voltage for the Z9-P2 or Z9-PE2 is +6 to +30 VDC.
UL and Safety Notification
Z9-P2 is a Recognized component under UL File Numbers: e484141 and e327789.
E484141
Power Source
l Z9-P2 or Z9-PE2 IS intended to be operated from a Limited Power Source (LPS) or Class 2 power source
in accordance with IEC/EN/UL 60950-1 and CAN/CSA C22.2 No. 60950-1-07.
l The Z9-P2 or Z9-PE2 IS approved to operate with an input voltage range of +6 to +30 VDC.
l When used with external power supply by Kuantech KSAS012xxxyyyyzz where 'xxx' 060 to 240, 'yyyy' =
0020 minimum, zz = VU or HU or D5, the power supply shall be located within a max 50C ambient; used
with external by SHENZHEN MINGXIN POWER TECHNOLOGIES CO LTD MX15 Series, the power supply
shall be located within a max 40C ambient.
l Lorsqu'il est utilisé avec une alimentation externe par Kuantech KSAS012xxxyyyyzz où 'xxx' 060 à 240,
'aaaa' = 0020 minimum, zz = VU ou HU ou D5, l'alimentation doit être située dans une température
ambiante maximale de 50°C, utilisé avec externe par la série SHENZHEN MINGXIN POWER
TECHNOLOGIES CO LTD MX15, l'alimentation doit être située dans une plage de température ambiante
maximale de 40°C.
Standards and Editions
l HazLoc Standards
l ANSI / ISA-12.12.01-2015
l CAN / CSA C22.2 No. 213-15
l Nonincendive Electrical Equipment for Use in Class I and II, Division 2 and Class III, Division 1 and 2
Hazardous (Classified) Locations
l Ordinary Location Standards
l UL 60950, 2nd Edition
l CAN / CSA-C22.2 No. 60950, 2nd Edition
l IEC 60950, 2nd Edition
l EN 60950, 2nd Edition
l Essential Health and Safety Requirements related to the design and construction of products intended for
use in potentially explosive atmospheres given in Annex II to Directive 2014/34/EU of the European
Parliament and the Council. Compliance with:
l EN 60079-0:2012 + A11:2013
l EN 60079-15:2010
l DEMKO 16 ATEX 1705X Rev 1
l II 3 G Ex nA IIC T5/T6 Gc
Schedule of Limitations
l Antenna connection is internal wiring only.
l The Ex Components shall only be used in an area of not more than pollution degree 2, as defined in
IEC/EN60664-1.
l The Ex Components shall be installed in an enclosure with tool removable door or cover that provides a
degree of protection not less than IP 54 in accordance with IEC/EN60679-15.
l Transient protection shall be provided that is set at a level not exceeding 140% of the peak rated voltage
value at the supply terminals to the equipment.
l The T6 Tcode is allowed when used in a maximum rated ambient temperature of 60°C. (Z9-PE2 only)
l The T5 Tcode is allowed when used in a maximum rated ambient temperature of 75°C. (Z9-PE2 only)
Z9-P2 Only
l The maximum recorded temperature on the Z9-P2 was 99°C on U8 (interface board).
l All temperatures normalized to 85°C.
l Suitability of temperatures shall be determined in the end-use investigation, with consideration given to
conducting the heating test within the end-use application.
l Temperature code determination must be performed in the end-product evaluation.
l Connector J12 may not be provided with mating connectors. As such, the securement of these
connectors must be evaluated during end-product investigation.
Installation Instructions
l This equipment is suitable for use in Class I, Division 2, Groups A, B, C and D OR non-hazardous
locations only.
Warning! EXPLOSION HAZARD – Do not disconnect equipment unless power has been
removed or the area is known to be non-hazardous.
AVERTISSEMENT – RISQUE D’EXPLOSION. NE PAS DEBRANCHER A MOINS QUE
L’ALIMENTATION N’AIT ETE COUPEE OU QUE L’ENDROIT SOIT CONNE POUR ETRE
NON DANGEREUX.
l This equipment is intended to be mounted within a suitable enclosure that is only accessible with the use
of a tool.