QandA_bidders_Utility_Meters.pdf

"Solutions to Any Problems"

Request for Information (RFI):

To: Samuel Hevrin/Barry Jundt

Project: FA4460-15-B-0006 RPR (SUS) Install Utility Meters Multi Facilities

(NKAK 15-1033)

1. Will the 40 meters in the base bid be repaired/replaced by a mod to the contract if they are found to be inoperable after the new JACE is installed and operational?

2. SOW 2.05.D.: At the end of this statement it mentions a new meter/vault. What is the purpose of the vault?

3. SOW 2.07.C.: States that the existing meters communicate via non-proprietary

ModBus to the Primary Server and via radio from primary server to the secondary server. Is this statement reversed?

4. Is there any data available that will give an idea of the areas that have been able to communicate via the existing radio transceivers?

5. Will Entergy be available for shutting down facility power for the contractor to install necessary metering equipment?

6. Will there be any cost, to the contractor, associated with Entergy shutting down the facilities?

7. Can the ct’s be installed inside of the Entergy owned transformers?

8. Can the ct’s be installed inside of existing switchgear (disconnects, panels, panelboards, switchboards, etc.)

9. Will all new ct’s be required where new meters are to be installed, replacing an old meter, or can the existing ct’s be utilized?

10. Is the intent to install new electrical service equipment, other than the AMRS, with main disconnects and ct cabinets where they are not currently installed?

11. If an existing electric service is worked on to install ct’s and meters will it be required to be brought up to current NEC standards?

12. Can the meters be installed on a rack adjacent to the transformer on the Entergy owned transformer pads?

13. There are some facilities, in the mechanical, that call to connect to the AMRS system. If these facilities do not currently have or do not call to receive a new AMR electric meter, how do you propose to connect them to the AMRS?

14. Where a repeater is required, can a wood pole be installed to support the height required for the antenna?

15. How many zones does the existing JACE have?

29 PINE TREE LOOP, NORTH LITTLE ROCK,

AR, 72116 CONTACT (501) 773-1362

1117158078C Sticky Note If one or more of the meters in the base bid are found to be inoperable, they may or may not be replaced. If LRAFB decides to replace, a modification to the contract would be necessary.

1117158078C Sticky Note The vault is assumed to be necessary to intercept the underground lines.

1117158078C Sticky Note The primary server to secondary server communicates via RF. The meters communicate with the primary server via wireless protocol.

1117158078C Sticky Note Existing repeaters have been successful in reaching most of the facility. However, remote areas require additional repeaters.

1117158078C Sticky Note Yes, Entergy will be available with proper Design/Build Contractor coordination.

1117158078C Sticky Note There may or may not be costs to the Contractor. Design/Build Contractor shall coordinate with Entergy.

1117158078C Sticky Note Yes, CT's may be installed inside the secondary side of Entergy's transformers. However, coordination with Entergy is required.

1117158078C Sticky Note The CT's may be installed in existing switchgear. However, the Design-Build Contractor is responsible for ensuring the system works where installed. Installation in switchgear may cause wireless connectivity issues. The D/B Contractor takes responsibility.

1117158078C Sticky Note New CT's/PT's are required where installing a NEXUS meter where no NEXUS meter currently exists. If a NEXUS meter currently is installed, use of the existing CT's/PT's is acceptable.

1117158078C Sticky Note No other service entrance equipment is intended to be installed.

1117158078C Sticky Note If NEC shortfalls are encountered, D/B contractor shall issue RFI for guidance. Unforeseen site conditions will be handled via contract modification.

1117158078C Sticky Note Nexus meters maybe installed on D/B installed racks mounted to Entergy owned transformer pads (not on transformers).

1117158078C Sticky Note Facilities that presently do not have AMR electric meters would require one be installed in order to connect gas or water meters. The table should reflect this.

1117158078C Sticky Note Design/Build Contractor to use metal poles.

1117158078C Sticky Note The existing JACE (Java Application Control Engine, NOT Java Apple Computer Emulator) takes four antenna into one JACE.

Technical Support:

Online support: http://www.digi.com/support/eservice/login.jsp

Phone: (801) 765-9885

90001003_A

2008.08.20

X-CTU

Configuration & Test Utility Software

User’s Guide

Contents

Introduction 2

PC Settings Tab 3

COM port setup: 3

Host Setup: 4

User COM ports: 4

Range Test Tab 4

Packet Data and Size 4

RSSI: 6

API Function: 6

The Terminal Tab 7

The main terminal window 7

Assemble Packet 8

Modem Configuration tab 9

Reading the Radios firmware 9

Making changes to the radios firmware 9

Writing firmware to the radio 10

Downloading updated firmware files 11

Modem Profiles 12 http://www.digi.com/support/eservice/login.jsp

© 2008 Digi International Page 2 of 16

Introduction

This User’s Guide is intended to discuss the functions of Digi’s X-CTU software utility. Each function will be discussed in detail allowing a better understanding of the program and how it can be used.

X-CTU is a Windows-based application provided by Digi. This program was designed to interact with the firmware files found on Digi’s RF products and to provide a simple-to-use graphical user interface to them.

X-CTU is designed to function with all Windows-based computers running Microsoft

Windows 98 SE and above. X-CTU can either be downloaded from Digi’s Web site or an installation CD. When properly installed it can be launched by clicking on the icon on the PC desktop (see Figure 1) or selecting from the Start menu (see Figure 2).

Figure 1 Figure 2

When launched, you will see four tabs across the top of the program (see Figure 3). Each of these tabs has a different function. The four tabs are:

PC Settings: Allows a customer to select the desired COM port and configure that port to fit the radios settings.

Range Test: Allows a customer to perform a range test between two radios.

Terminal: Allows access to the computers COM port with a terminal emulation program. This tab also allows the ability to access the radios’ firmware using AT commands (for a complete listing of the radios’ AT commands, please see the product manuals available online).

Modem Configuration: Allows the ability to program the radios’ firmware settings via a graphical user interface. This tab also allows customers the ability to change firmware versions.

© 2008 Digi International Page 3 of 16

Figure 3

PC Settings Tab

When the program is launched, the default tab selected is the “PC Settings” tab. The PC Settings tab is broken down into three basic areas: The COM port setup, the Host Setup, and the User

Com ports.

COM port setup:

The PC settings tab allows the user to select a COM port and configure the selected COM port settings when accessing the port. Some of these settings include:

Baud Rate: Both standard and non-standard

Flow Control: Hardware, Software (Xon/Xoff), None

Data bits: 4, 5, 6, 7, and 8 data bits

Parity: None, Odd, Even, Mark and Space

Stop bit: 1, 1.5, and 2

To change any of the above settings, select the pull down menu on the left of the value and select the desired setting. To enter a non-standard baud rate, type the baud rate into the baud rate box to the left.

The Test / Query button is used to test the selected COM port and PC settings. If the settings and COM port are correct, you will receive a response similar to the one depicted in Figure 4 below.

© 2008 Digi International Page 4 of 16

Figure 4

Host Setup:

The Host Setup tab allows the user to configure how the X-CTU program is to interface with a radio’s firmware. This includes determining whether API or AT command mode will be used to access the module’s firmware as well as the proper command mode character and sequence.

By default, the Host Settings are as follows:

API mode: not enabled (Not checked)

Command mode Character: + (ACSII) 2B (Hex).

Before Guard Time: 1000 (1 Sec)

After Guard Time: 1000 (1 Sec)

This is the default value of our radios. If this is not the value of the AT, BT, or GT commands of the connected radio, enter the respective value here.

User COM ports:

The user COM port option allows the user to “Add” or “Delete” a user-created COM port.

This is only for temporary use. Once the program has closed, the user-created COM port will disappear and is no longer accessible to the program.

Range Test Tab

The range test tab is designed to verify the range of the radio link by sending a user-specified data packet and verifying the response packet is the same, within the time specified. For performing a standard range test, please follow the steps found in most

Quick Start or Getting Started Guides that ship with the product.

Packet Data and Size

By default, the size of the data packet sent is 32 bytes. This data packet specified can be adjusted in either size or the text sent.

© 2008 Digi International Page 5 of 16

Figure 5

To modify the size of the packet sent, change the value next to the “Create Data” box and click on the “Create Data” button (see Figure 5). If you want to change the data sent, delete the text in the transmit window and place in your desired text.

By modifying the text, data packet size, packet delay and the data receive timeout; the user is able to simulate a wide range of scenarios.

© 2008 Digi International Page 6 of 16

RSSI:

The RSSI option of the X-CTU allows the user to see the RSSI (Received Signal Strength

Indicator) of a received packet when performing a range test.

API Function:

The X-CTU also allows the user to test the API function of a radio during a range test.

To perform a range test with the API function of the radio, follow the steps outlined below:

1: Configure the Base with API enabled and a unique 16 bit or 64 bit source address.

2: Configure the remote radio with a unique source address and set the

Destination address to equal the Base radio’s source address.

3: Enable the API option of the X-CTU on the PC Settings tab and connect the base radio to the PC (See Figure 3).

4: Connect the red loopback adapter to the remote radio and place them a distance apart.

5: Enter either the 16 bit or 64 bit destination address of the remote radio into the Destination Address box on the Range Test tab (See figure 6).

6: Create a data packet of your choosing by typing in the data in the Transmit box

7: To start a Range test, click on Start.

You will notice the TX failures, Purge, CCA, and ACK messages will increment accordingly while the range test is performed.

To stop a range test, click on the Stop button.

© 2008 Digi International Page 7 of 16

Figure 6

The Terminal Tab

The Terminal tab has three basic functions:

Terminal emulator

Ability to send and receive predefined data pacts (Assemble packet)

Ability to send and receive data in Hex and ASCII formats (Show/Hide hex)

The main terminal window

The main white portion of this tab is where most of the communications information will occur while using X-CTU as a terminal emulator. The text in blue is what has been typed in and directed out to the radio’s serial port while the red text is the incoming data from the radio’s serial port (see Figure 7).

© 2008 Digi International Page 8 of 16

Figure 7

Assemble Packet

The Assemble Packet option on the Terminal tab is designed to allow the user to assemble a data packet in either ASCII or Hex characters. This is accomplished by selecting the Assemble packet window and choosing either ASCII (default) or Hex. Once selected, the data packet is assembled by typing in the desired characters as depicted in

Figure 8.

Figure 8

The Line Status indicators depicted in Figure 5 shows the status of the RS-232 hardware flow control lines. Green indicates the line is asserted while black indicates de-asserted.

© 2008 Digi International Page 9 of 16

The Break option is for engaging the serial line break. This can be accomplished by checking or asserting the Break option. Asserting the Break will place the DI line high and prevent data from being sent to the radio.

Modem Configuration tab

The Modem configuration tab has four basic functions:

1: Provide a Graphical User Interface with a radio’s firmware

2: Read and Write firmware to the radio’s microcontroller

3: Download updated firmware files from either the web or from a compressed file

4: Saving or loading a modem profile

Reading a radio’s firmware

To read a radio’s firmware, follow the steps outlined below:

1: Connect the radio module to the interface board and connect this assembly or a packaged radio (PKG) to the PC’s corresponding port (IE: USB, RS232, Ethernet etc.).

2: Set the PC Settings tab (see Figure 3) to the radio’s default settings.

3: On the Modem Configuration tab, select “Read” from the Modem Parameters and Firmware section (see Figure 9).

Making changes to a radio’s firmware

Once the radio’s firmware has been read, the configuration settings are displayed in three colors (see Figure 10):

Black – not settable or read-only

Green – Default value

Blue – User-specified

To modify any of the user-settable parameters, click on the associated command and type in the new value for that parameter. For ease of understanding a specific command, once the command is selected, a quick description along with its limits is provided at the bottom of the screen. Once all of the new values have been entered, the new values are ready to be saved to the radio’s non-volatile memory.

© 2008 Digi International Page 10 of 16

Figure 9

Writing firmware to the Radio

To write the parameter changes to the radio’s non-volatile memory, click on the Write button located in the Modem Parameters and Firmware section (see Figure 10)

© 2008 Digi International Page 11 of 16

Figure 10

Downloading Updated Firmware Files

Another function of the Modem Configuration tab is allowing the user to download updated firmware files from either the web or install them from a disk or CD. This is accomplished by following the steps below:

1: Click on the Download New Versions… option under the Version section

2a: Click on Web for downloading new firmware files from the web

2b: Click on the File when installing compressed firmware files from a CD or saved file (see Figures 11 and 12)

2bi: Browse to the location the file is saved at and click on Open (see

Figure 13)

3: Click on OK and Done when prompted

© 2008 Digi International Page 12 of 16

Figure 11 Figure 12

Figure 13

Modem Profiles

The X-CTU has the ability to save and write saved modem profiles or configuration to the radio. This function is useful in a production environment when the same parameters need to be set on multiple radios.

How to save a profile:

1: Set the desired settings within the radio’s firmware as described in the

Making changes to the radios firmware section

2: Click Save in the Profile section

3: Type in the desired name of this profile in the File Name box (see Figure 14)

4: Browse to the location where you wish to save your profile

5: Click Save

© 2008 Digi International Page 13 of 16

Figure 14

How to load a saved profile:

1: Click on Load from the profile section

2: Browse to the location of the file and click on the desired file (see Figure 15)

3: Click Open

Figure 15

To save the loaded profile to the radio once you have loaded the file, follow the steps outlined in the Writing firmware to the radio section above.

To find out how to load the saved profiles in a production environment from a DOS prompt, please follow the steps outlined in Digi’s online Knowledgebase at http://www.maxstream.net/support/knowledgebase/article.php?kb=126 http://www.maxstream.net/support/knowledgebase/article.php?kb=126

© 2008 Digi International Page 14 of 16

Remote Modem Management

XBee 802.15.4 modules with firmware version 1xCx and above, XBee ZNet 2.5 modules, and

XBee ZB modules offer the ability to be configured with over the air commands. With the addition of this new feature, the user is able to configure remote radio parameters with X-CTU or API packets. To use the remote configuration tool, the following is required:

- The radio connected to the PC must be in API mode

- The remote radio must be associated or within range of the base radio

To access remote radios through X-CTU’s Modem Configuration tab, perform the steps below:

- Enable API on the PC Settings tab

- Verify the COM port selection and settings

- On the Modem Configuration tab, select the Remote Configuration option on the top left corner of the program

- Select Open Com port

- Select Discover

© 2008 Digi International Page 15 of 16

- Select the desired modem from the discovered node list

- On the Modem configuration tab, select Read

The remote radio’s configuration is now displayed on the Modem Configuration tab. At this point, the same options exist with respect to Read and Write parameter changes. Please note that the ability to change firmware versions is still limited to the radio’s UART.

To clear the discovered node list, click on Node List and Clear.

The Node List option provides several additional options, including:

- Ability to print the discovered list

- Ability to remove a specific node from a list

- Ability to add additional nodes that have not been discovered

- Save the Node List

- Load a saved Node List

- Select/filter All, Routers, or End nodes

For specific questions related to the X-CTU configuration and test utility software, please contact our

Support department, Mon – Fri, 8am – 5pm U.S. Mountain Time:

© 2008 Digi International Page 16 of 16

US and Canada Toll free:

(866)765-9885

Local or International calls:

(801) 765-9885

Online support: http://www.digi.com/support/eservice/login.jsp http://www.digi.com/support/eservice/login.jsp

XLR PRO

Long Range Radio Solution User Guide

XLR PRO User Guide (Part number 90002202 C)

Disclaimers Information in this document is subject to change without notice and does not represent a commitment on the part of Digi International Inc.. Digi provides this document “as is,” without warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of fitness or merchantability for a particular purpose. Digi may make improvements and/or changes in this manual or in the product(s) and/ or the program(s) described in this manual at any time.

Trademarks and copyright Digi, Digi Device Cloud, the Digi logo, and Punch2 are trademarks or registered trademarks in the United States and other countries worldwide. All other trademarks mentioned in this document are the property of their respective owners.

© 2015 Digi International Inc. All rights reserved.

Customer support Telephone (8:00 am — 5:00 pm CST):

US & Canada: 866.765.9885

Worldwide: 801.765.9885

Online: www.digi.com/support/eservice

Mail:

Digi International Inc.

11001 Bren Road East

Minnetonka, MN 55343

USA

Warranty View product warranties online: http://www.digi.com/howtobuy/terms

Revision Date Description

A September 2014 Initial release.

B March 2015 Removed the Data sample rx indicator frame type. Made minor editorial corrections. Updated information about the DN, ND and FN commands.

Added a note about the ATWR command. Removed the “0x92 - Data sample rx indicator” frame.

C May 2015 Revised to incorporate the following changes:

• Revisions to web configuration and Device Cloud configuration options available with XLR PRO firmware version 1006.

• Revisions to Device Cloud brand name, as well as Device Cloud default login URLs.

This edition obsoletes all prevision editions.

http://www.digi.com/support/eservice/ http://www.digi.com/howtobuy/terms

Contents

About XLR PRO Technical specifications 8 Data rates and sensitivity 10 Power supply 10 Operational modes 10

Serial 10 Ethernet (IP socket) 11 Ethernet RF Bridging 11

Hardware interfaces 11 Serial (RJ45) port 11 USB (mini USB) 11 Ethernet 11 LEDs 12 Reset button 12 Antenna port 13

XLR PRO documentation 13

XLR PRO hardware XLR PRO kit contents 14

Front panel 15 RJ45 serial port pinout 16

Hardware setup 17 Connect the hardware 17 Mount the XLR PRO 18

Mounting guidelines 19 Antenna placement 19

XLR PRO operation XLR PRO operational design 20

Ethernet RF bridging 21 Serial mode selection 21 Serial mode 22

RS-232 22

RS-485/422 23

IP socket mode 23 XLR PRO User Guide 3

Controlling parameters 23 Operational description 24

Serial communications 24 XLR PRO serial buffers 24 XLR PRO serial interface protocols 25

AT Command Mode 26 Firmware updates 28

XLR PRO networking methods Ethernet RF bridging 30

Related parameters: ID, PL, RR, MT 30 Ethernet RF bridging 31

64-bit addresses 31 Unicast 32 Broadcast 32

XLR PRO serial addressing basics 32 Related parameters: SH, SL, DH, DL, TO 32

64-bit addresses 32 Unicast 32 Broadcast 32 Delivery method 32

Point-to-point/multipoint (P2MP) 33 Repeater/directed broadcast 33

Related parameters: CE, NH, NN, BH 33 Transmission timeouts 34

Transmitting a broadcast 34

XLR PRO AT command reference tables Special commands 35 MAC/PHY level commands 35 Diagnostics commands (MAC statistics and timeouts) 36 RF network commands 38 RF addressing commands 38 Addressing discovery/configuration commands 41 RF security commands 44 Serial interfacing commands 44 Hardware diagnostics commands 46 Ethernet and IP socket mode commands 46 Device Cloud commands 48 Web configuration commands 49 Ethernet RF bridging commands 49 AT command options 50 Firmware commands 50

XLR PRO API operation API frame format 51

API operation (AP parameter = 1) 51 API operation with escape characters (AP parameter = 2) 52

Data bytes that need to be escaped: 52 XLR PRO API serial exchanges 53

AT commands 53 XLR PRO User Guide 4

Transmitting and receiving RF data 54 Remote AT commands 54

Supporting the API 55 XLR PRO frame descriptions 55

AT command 55 AT command—queue parameter value 55 TX request 56 Explicit TX Request 57 Remote AT command request 59 AT command response 59 Modem status 60 Transmit status 60 RX indicator 61 Explicit rx indicator 62 Remote command response 63

XLR PRO advanced application features Remote configuration commands 65

Sending a remote command 65 Applying changes on remote devices 65 Remote command responses 65

Network commissioning and diagnostics 66 Device configuration 66 Device placement 66

Loopback testing 66 Device discovery 66

Network discovery 66 Neighbor polling 67

General purpose flash memory 67 Accessing general purpose flash memory 67

Working with flash memory 73 Over-the-air firmware upgrades 74

Distributing the new application 74 Verifying the new application 75 Installing the application 75 Keep in mind 75

Configuring the XLR PRO using XCTU Download and install XCTU 76 Connect XLR PRO to your PC 76 Launch XCTU and add the XLR PRO 77 Configure parameters using XCTU 78 Determine or assign an IP address 78

Determine the DHCP address 78 Assign a static address 79 Update firmware with XCTU 79

Configuring XLR PRO using the web configuration interface Access the XLR PRO web configuration interface 80 Set general options 81 Set Ethernet network options 81 XLR PRO User Guide 5

Set Ethernet RF bridging options 82 Set Device Cloud connectivity options 83 Set XLR radio options 83 Set XLR radio serial options 84 Set XLR radio IP socket (Ethernet) options 85 Update firmware 86 Set web configuration options 87 Reboot an XLR PRO 88 Restore factory default settings 88

Configuring XLR PRO using Device Cloud Create a Device Cloud account 89 Get the MAC address for the XLR PRO 89 Add a Digi XLR PRO to Device Cloud 90 Update firmware with Device Cloud 91 Configure XLR PRO with Device Cloud 92

Configure Device Cloud connectivity options 93 Configure Ethernet network options 94 Configure Ethernet RF bridging options 95 Configure IP Socket Mode options 96 Configure serial mode options 97 Configure system options 98 Configure web configuration options 99 Configure XLR radio configuration options 100

Schedule configuration changes 101

Troubleshooting Serial interface issues 102

No data on serial port 102 RS-485/422 does not work 102

Ethernet issues 102 LAN stopped working when XLR PRO was plugged in 102

General issues 102 All of the LEDs are lit on the XLR PRO 102

Safety notices and certifications RF exposure statement 103 Class I, Division 2 (CID2) certification—USA and Canada 103 FCC (United States) certification 104

FCC Part 15 Class B 104 Radio Frequency Interface (RFI) (FCC 15.105) 104 Labeling requirements (FCC 15.19) 105 Modifications (FCC 15.21) 105

Industry Canada (IC) certifications 105 RF Exposure 105

XLR PRO approved antennas Omni-directional antennas 106 Yagi antennas 108 XLR PRO User Guide 6

About XLR PRO

XLR PRO® is a high performance, industrial grade long-range radio solution that offers serial, Ethernet socket, and Ethernet bridging connectivity to ensure reliable wireless data communications over long distances.

Packaged in a sturdy, ruggedized enclosure and using patent-pending Punch2™ Technology to maximize range and significantly increase immunity to interference, the XLR PRO 900 MHz radio can connect a variety of devices across many industrial applications.

Punch2 Technology leverages chirp spread spectrum (CSS) modulation to provide better receiver sensitivity, multipath performance, and interference rejection than is available through commonly used frequency hopping spread spectrum (FHSS) or direct sequence spread spectrum (DSSS) systems. The advantages of Punch2 Technology arise from the characteristics of the chirp signal as well as several digital-signal-processing techniques that enhance performance and reliability. With Punch2 Technology, data is spread to a higher bandwidth by multiplying each transmit modulation symbol with a chirp signal. Operating at an expanded bandwidth provides several benefits:

• Greater receiver sensitivity

• Interference immunity

• Improved multipath performance

• Adjustable data rates

XLR PRO flexible configuration and management options allow you to quickly set up and deploy one or more XLR PROs, as well as apply firmware updates, get device status information, and more.

XLR PRO User Guide 7

Technical specifications

The following table summarizes XLR PRO technical specifications.

XLR PRO Specifications

General

Dimensions 18 x 13 x 3.8 cm (7.1 x 5 x 1.5 inches)

Weight 0.68kg (1.5 lbs)

Ethernet protocols UDP/TCP, DHCP client

Ethernet physical layer 10/100BASET-T/TX

RoHS Compliant

Performance

Frequency range ISM 902 to 928 MHz

RF data rate 9.4 kb/s to 3.2 Mb/s

Maximum transmit power (software selectable)

+30 dBm (1 watt)

Rural range line of sight 1.2 Mb/s up to 100+ miles1

Urban range line of sight 9.4 kb/s up to 25 miles1

141 kb/s up to 8 miles2

591 kb/s up to 3.6 miles

3.2 Mb/s up to 1 mile2

Receiver sensitivity 9.4 kb/s -120 dBm

141 kb/s -112 dBm

3.2 Mb/s -98 dBm

Receiver selectivity 141 kb/s 70 dB (below 908 MHz, above 922 MHz)

40 dB (908 MHz to 922 MHz)

Interface data rate (software selectable)

460.8 kb/s (TCP/UDP socket)

921.6 kb/s (serial RS-485)

460.8 kb/s (serial RS-232)

Networking and security

Modulation Punch2 Technology (patent pending)

Supported network topologies Point-to-point/point-to-multipoint

Encryption 128-bit AES XLR PRO User Guide 8

Power requirements

Supply voltage 9VDC to 26VDC

Receive current @ 9 VDC 300 mA

@ 12 VDC 230 mA

@ 26 VDC 120 mA

Transmit current @ 9 VDC 950 mA

@ 12 VDC 840 mA

@ 26 VDC 400 mA

Environmental

Operating temperature -40° C to 70° C

Regulatory approvals

Emissions/immunity FCC Part 15B

Hazardous locations Class I, Division 2, Groups A, B, C, and D

Connectors

Antenna RPTNC

Power supply Phoenix

Ethernet (2) RJ45

Serial (1) RJ45

Configuration port Mini USB (currently not implemented)

1. Based on 100-mile range results. Other data rates scale based on sensitivity levels. Results will vary based on noise levels and line of sight quality.

2. Estimated based on 3.6-mile range results.

XLR PRO Specifications XLR PRO User Guide 9

Data rates and sensitivity Data rates and sensitivity The following table lists XLR PRO available data rates along with the corresponding receiver sensitivity.

Power supply The XLR PRO must be powered by a UL-listed power supply rated between 9 and 26V DC. Refer to the following table for the required input current settings.

Operational modes XLR PRO offers three operational modes:

• Serial (RS-232/RS-485)

• Ethernet (IP socket)

• Ethernet RF Bridging

Serial When operating in serial mode, the front panel serial port provides connectivity to the XLR PRO via RS-232 or RS-485/422.

RF data rate setting (ATBR) Data rate

Receiver sensitivity (dBm, 25°C)

0 9.4 kb/s -120

1 28 kb/s -118

2 66 kb/s -116

3 141 kb/s -112

4 291 kb/s -109

5 591 kb/s -106

6 1.2 Mb/s -103

7 2.4 Mb/s -100

8 3.2 Mb/s -98

Input voltage DC Minimum current rating

9 to 15 3 Amps

15 to 20 2 Amps

21 to 26 1.5 Amps XLR PRO User Guide 10

Hardware interfaces Ethernet (IP socket) In IP socket mode, the XLR PRO is able to transmit and receive serial data via a TCP or UDP connection from either of the front panel Ethernet ports to the XLR PRO.

Ethernet RF Bridging In Ethernet RF bridging mode, the XLR PRO functions as an Ethernet cable replacement, supporting point-to-multi-point transmission for a maximum of 16 XLR PROs. By default, bridging mode is disabled. Serial data from serial or IP socket mode operates concurrently with Ethernet RF Bridging. If serial and Ethernet traffic are sent at the same time, latency will be encountered.

Hardware interfaces The XLR PRO offers the following hardware interfaces.

Serial (RJ45) port The XLR PRO serial port (RJ45) supports RS-232 or RS-485/422 protocols.

USB (mini USB) At present, the mini USB port is for internal manufacturing use only.

Ethernet The Ethernet interface is 10/100 Base-T with a two-port managed Ethernet switch. The XLR PRO does not support Power over Ethernet (PoE) and must be externally powered through the DC power jack.

XLR PRO User Guide 11

Hardware interfaces LEDs The following table describes XLR PRO LED behavior. (For a diagram of the XLR PRO LEDS, see Front panel on page 15.)

Reset button You can use the Reset button to reset the XLR PRO and to restore factory default settings.

To reset the XLR PRO:

1 Hold down the Reset button for up to five seconds. The serial data in and serial data out LEDs flash three times to indicate that five seconds have passed.

2 Release the Reset button. The XLR PRO resets.

To restore factory default settings:

1 Hold down the Reset button for about eight seconds. While you are holding down the reset button, the serial data in and serial data out LEDs flash three times to indicate that five seconds have passed. Continue to hold down the Reset button until the serial data in and serial data out LEDs flash six times.

2 Release the Reset button. The XLR PRO is restored to factory default settings.

Action LED Status Description

Startup Power Solid Power LED glows solid red.

Link margin indicators

(RSSI)

Solid All of the link margin indicator LEDs show green for one second.

Serial Data In (green)

Solid On initial power on, if the green serial data in LED shows solid for three seconds, the XLR PRO is in serial mode.

Serial Data Out (yellow)

Solid On initial power on, if the yellow serial data out LED shows solid for three seconds, the XLR PRO is in IP socket mode.

Data transmissions

Power Solid While power is on, the power LED shows solid red.

Link margin indicators

(RSSI)

Solid The link margin indicator LEDs illuminate for four seconds to show the signal strength of the last valid RF packet received.

3 LEDs = Very strong signal (> 30 dB fade margin) 2 LEDs = Strong signal (>20 dB fade margin) 1 LED = Moderate signal (>10 dB fade margin) 0 LED = Weak signal (<10 dB fade margin)

Serial Data In (green)

Flashing Serial data in LED shows flashing when serial data is being transmitted.

Serial Data Out (yellow)

Flashing Serial data out LED shows flashing when serial data is being received.

XLR PRO User Guide 12

XLR PRO documentation Antenna port The antenna port is a 50 ohm RF signal connector for connecting to an external antenna. The connector type is Reverse Polarity TNC (RPTNC) female. The connector has threads on the outside of a barrel and a male center conductor.

XLR PRO documentation XLR PRO documentation includes the following publications:

Title Part Number Description

XLR PRO Quick Start Guide 90002204 Provides a brief summary of the XLR PRO kit.

XLR PRO Getting Started Guide 90002203 Provides step-by-step instructions for setting up a pair of XLR PROs to test over-the-air communications between the radios.

XLR PRO User Guide 90002202 Provides complete information on all XLR PRO features; describes how to configure XLR PROs using XCTU, the Web configuration interface, and Device Cloud; provides reference information on all supported AT commands.

XLR PRO User Guide 13

XLR PRO hardware

XLR PRO kit contents The following figure shows the XLR PRO accessories kit.

Item Description

1 XLR PRO

2 Power supply

3 Ethernet cable

4 USB to RS-232 serial converter

XLR PRO User Guide 14

Front panel The following figure shows XLR PRO front panel connectors and LEDs.

WARNING! Use the serial port for serial connections only. Do not connect the serial RJ45 port to any Power over Ethernet (PoE) device. Doing so can permanently damage the XLR PRO or PoE device and void the XLR PRO warranty.

5 RJ45/DB9F adapter

6 Antenna

Item Description

21 3

Item Description

1 Ethernet port 1

2 Ethernet port 2

3 Mini USB

4 Serial data out LED

5 Serial data in LED

6 Power LED

7 Serial port

8 Link margin indicator LEDs (RSSI)

9 Reset button

10 DC power jack XLR PRO User Guide 15

RJ45 serial port pinout

WARNING! Use the serial port for serial connections only. Do not connect the serial RJ45 port to any Power over Ethernet (PoE) device. Doing so could permanently damage the XLR PRO or PoE device and void the XLR PRO warranty.

Pin RS-232 RS-485 (4-wire) RS-485 (2-wire)

1 RXD TX+ TX/RX+

2 CTS TX- TX/RX-

3 TXD RX+ Unused

4 GND GND GND

5 GND GND GND

6 RTS RX- Unused

7 DSR/DCD Unused Unused

8 DTR Unused Unused XLR PRO User Guide 16

Hardware setup

Connect the hardware The following figure shows how to connect the XLR PRO cables and antenna.

XLR PRO User Guide 17

Mount the XLR PRO

CAUTION! You must install the XLR PRO in a Restricted Access Location. In addition, you must restrict access to personnel who have been instructed on potential hazards, as well as physically restrict access using a tool, or lock and key, or other means controlled by a responsible authority.

The XLR PRO provides mounting holes in the bottom of the unit by which you can mount the unit directly on a wall or attach mounting brackets.

There are two mounting brackets for the XLR PRO, one for a flush mount and another for a right angle mount. The following illustrations show the dimensions of each option.

DIN rail bracket, right-angle (not to scale)

Flush-mount bracket (not to scale) XLR PRO User Guide 18

Mounting guidelines Follow these general guidelines when mounting the XLR PRO:

• Use the pre-drilled mounting holes located on the bottom of the XLR PRO unit to attach the XLR PRO to the wall of an enclosure or DIN Rail bracket. Do not alter or move the mounting holes.

• To attach brackets to the XLR PRO, use four (4) 6-32x3/8” screws. Do not use screws that are longer than 3/8”.

Antenna placement

• Mount the XLR PRO antenna vertically—that is, pointed directly up or down.

• If the XLR PRO is mounted within a metal enclosure, use an antenna external to the enclosure connected to the XLR PRO using a a 50 ohm coaxial cable, suitable for 900MHz UHF radio transmission.

XLR PRO User Guide 19

XLR PRO operation

XLR PRO operational design The XLR PRO uses a multi-layered firmware base for data flow. The flow of data depends on the hardware and software configuration you choose. The configuration block diagram below shows the host serial interface as the physical starting point and the antenna as the physical endpoint for transferred data. As long as an interface block is able to touch another block above or below, the two interfaces can interact. For example, if the XLR PRO is using API mode, Transparent Mode is not available.

API Mode Con gura on

Command Handler

Antenna

MAC/PHY

Packet Handler

NWK (Repeater/Directed Broadcast)

Ethernet

RF

Bridging

Ethernet Interfaces

Serial Port

Device CloudWeb UIIP Socket

Mode

Serial Connec on Manager

Transparent Mode

AT Command Mode XLR PRO User Guide 20

Ethernet RF bridging In Ethernet RF bridging mode, the XLR PRO functions as an Ethernet cable replacement, supporting point-to-multipoint transmissions for up to 16 XLR PROs. It is configured by these parameters:

• BE - Bridge Enable. This parameter must be set to 1 to enable bridging, but it is disabled by default.

• BA – Destination RF MAC address for Ethernet bridging. Default value is 0xFFFF which is the broadcast address. If pairing XLR PRO devices is desired, then this should be set to the RF MAC address of the opposing XLR PRO. This can be identified by querying the SH and SL parameters on the opposite XLR PRO (example: BA=0x0013A20012345678).

With bridging enabled, the XLR PRO radios on the RF network should be treated as if they were a single Ethernet cable. A qualified network administrator should evaluate the radio deployment if multiple XLR PRO radios will be used on the same LAN or if bridging multiple large networks together.

Serial mode selection The XLR PRO provides three serial modes:

• RS-232

• RS-485/422

• IP socket

At any given time, only one serial mode can be selected based on the detection of cable connections and configuration options. The following factors determine serial mode selection:

• DTR: XLR PRO detects DTR on the serial port.

• 4E (Enable RS-485 mode): RS-485 configuration option is enabled or disabled.

• ES (Enable IP socket mode): IP Socket configuration option is enabled or disabled.

The following flow chart indicates how the three factors (DTR, 4E, and ES) affect which mode of operation is active:

XLR PRO User Guide 21

By default, Enable RS-485 mode (4E) is 0 (disabled) and Enable IP socket mode (ES) is 1 (enabled). In this default case, RS-232 mode is selected if DTR is present. Otherwise, IP socket mode is selected.

The 4E and ES configuration options allow you to select other modes, independent of DTR, which may not be present on a serial port connection.

You must have an active DTR signal to automatically detect a serial connection. If the serial cable or end device does not include an active DTR signal, disable socket mode (ES = 0) using XCTU, the web configuration, or Device Cloud.

Serial mode When serial mode is the primary interface, the Serial Data In (green) LED will light for about three seconds. Serial mode can be either RS-232 or RS-485/422, depending on serial mode selection. The following parameters must be configured to match the host device, regardless of whether RS-232 or RS-485 is selected:

• BD - Baud rate (See the AT command table for limits)

• NB - Parity (None, Even, or Odd)

• SB - Stop bits (1 or 2)

RS-232

RS-232 connections support hardware flow control using CTS and RTS and requires matching parameters on the XLR PRO and the host device. This includes the following:

Reset

DTR?

RS‐232

Yes 4E?

No

ES?

RS‐485IP Socket

No

No

Yes

Yes XLR PRO User Guide 22

• D6 - RTS flow control. If enabled, then XLR PRO will not output data unless RTS is asserted. The host device should not de-assert RTS for long periods of time to avoid filling the serial transmit buffer. If an RF data packet is received, and the serial transmit buffer does not have enough space for all of the data bytes, the entire RF data packet will be discarded.

• D7 - CTS flow control. If enabled, then XLR PRO will not assert CTS low unless it can handle more data from the host.

• FT - Flow control threshold. If CTS flow control is enabled (with D7 parameter), the XLR PRO deasserts CTS when the serial receive buffer reaches the threshold defined by the FT parameter.

Once CTS is de-asserted, it will not be asserted again until the receive buffer has 17 bytes less than the threshold defined by FT. By default, FT is 65 bytes less than the maximum space available for receive data.

RS-485/422

An RS-485 connection requires that 4E=1 and it also requires matching parameters on the XLR PRO and the host device. This includes the following:

• 4E - Enable RS-485/422. If 4E is set to 0, then the XLR PRO will use RS-232. This parameter needs to be set to 1 in order to use RS-485/422 on the serial port.

• 4D - Full duplex (4-wire) or half duplex (2-wire) operation. A default value of 0 selects half duplex operation and 1 selects full duplex.

• 4T - RS-485/422 termination. Enable or disable line termination on the RS-485/422 interface. The default value of 0 indicates that there is no line termination on the XLR PRO. If 4T is set to 1, then a 120 termination resistor will be present on the RS-485/422 connection. This parameter will have no effect on the XLR PRO if it is configured for RS-232.

IP socket mode IP socket mode provides serial communication for a single TCP or UDP port on the XLR PRO (multiple simultaneous connections are not supported). This would normally happen over the Ethernet connection, but it may also occur over the bridge if Ethernet RF bridging is enabled and another XLR PRO (which also has Ethernet RF bridging enabled) provides the Ethernet connection to an IP host.

With the factory default settings, the XLR PRO listens on port 9750 for incoming TCP traffic. A telnet session can be initiated to the XLR PRO’s IP address as a simple IP socket connection.

The same operations that can occur in serial mode can also occur in IP socket mode. Those operations are based on the payload of the IP frames. In other words, serial data coming to and from the XLR PRO is equivalent to the payload of the IP socket mode data.

Controlling parameters

IP socket mode is configured by these parameters:

• IB - IP socket mode baud rate. This is set to the maximum rate of 460800 b/s by default, but it may be set to a lower rate for throttling, if desired.

• IP - IP protocol. Default value of 1 selects TCP and 0 selects UDP. This parameter must match the protocol used by the IP host.

• C0 - TCP or UDP port on which the XLR PRO will listen. The IP host must send data to this port in order for the XLR PRO to accept the incoming data. If configuring the XLR PRO using XCTU, the port number is displayed in hexadecimal.

• DY - Destination IP port. (See DX above.)

XLR PRO User Guide 23

• DX - Destination IP address. This tells the XLR PRO where to send data if it initiates the conversation. If operating in TCP mode and a TCP connection does not currently exist, then the XLR PRO will attempt to make a connection to this IP address (and the IP port given by DY) to send the data to the selected IP host and port. However, if a TCP connection already exists, then the data will be sent to that connection, ignoring the DX and DY parameters. If operating in UDP mode, this rule changes slightly because it is a connectionless protocol. If the first IP socket mode data comes from the XLR PRO, then DX/DY will be used. If not, then all UDP data will be sent to the IP address and port from which the original data arrived.

• TM - TCP client connection timeout. A client connection is one which was initiated by the XLR PRO.

This parameter tells how many seconds a TCP client connection will remain connected when no data is being sent or received on the connection.

• TS - TCP server connection timeout. A server connection is one which was initiated by an external IP host. This parameter tells how many seconds a TCP server connection will remain connected when no data is being sent or received on the connection.

In addition to the above IP socket mode parameters, the MY parameter is also used in IP socket mode:

• MY - IP address of the XLR PRO. By default, this address is learned from a DHCP server, but it may be set to any value if static mode is used (MA=1).

Operational description

IP socket mode may start up in the following cases:

1. It may start at reset, based on the mode selection rules previously described.

2. It may start when parameters that affect the mode are changed and applied.

3. It may start when the RS-232 cable is unplugged.

When IP socket mode is the primary interface, the Serial Data Out (yellow) LED will light for about three seconds.

Upon starting or restarting the XLR PRO, either a TCP or a UDP listener is set up depending on the IP parameter. If UDP data is received or if a TCP connection gets established before the XLR PRO attempts to send data, then the DX and DY parameters are unused. In this case, the XLR PRO takes the role of a TCP or UDP server. But if the XLR PRO has data to send before an IP host sends data to the XLR PRO, then DX and DY determine the destination of that data until the TCP connection times out or until IP socket mode is restarted, whichever comes first.

Serial communications Whether the XLR PRO is configured for RS-232, RS-485/422, or IP socket mode, the XLR PRO will handle the traffic as serial data. The XLR PRO handles all serial traffic identically regardless of which interface is being used.

XLR PRO serial buffers

Serial receive buffer

When serial data enters the XLR PRO, the data is stored in the serial receive buffer until it can be processed. Under certain conditions, the XLR PRO may not be able to process data in the serial receive buffer immediately. If large amounts of serial data are sent to the XLR PRO such that the serial receive buffer would overflow, then the new data will be discarded. If using RS-232, this can be XLR PRO User Guide 24 avoided by using hardware flow control. Software flow control can be used regardless of which serial interface is being used.

Serial transmit buffer

When serial RF data is received, the data is moved into the serial transmit buffer and sent out of the active serial interface of the XLR PRO. If the serial transmit buffer becomes full and system buffers are also full, then the entire RF data packet is dropped. Whenever data is received faster than it can be processed and transmitted out the serial port, there is a potential of dropping data.

XLR PRO serial interface protocols

The XLR PRO supports both transparent and Application Programming Interface (API) serial interfaces.

Transparent operation

When operating in transparent mode, the XLR PRO acts as a serial line replacement. All serial data received through the serial interface is queued up for RF transmission. When RF data is received, the data is sent out through the active serial interface. The XLR PRO configuration parameters are configured using the AT command mode interface.

Data is buffered in the serial receive buffer until one of the following causes the data to be packetized and transmitted:

• No serial characters are received for the amount of time determined by the RO (Packetization Timeout) parameter. If RO = 0, no packetization will occur and characters will be transmitted immediately.

• The Command Mode Sequence (GT + CC + GT) is received. Any character buffered in the serial receive buffer before the sequence is transmitted.

• The maximum number of characters that will fit in an RF packet is received. See the NP parameter.

API operation

API operation is an alternative to transparent operation. The frame-based API extends the level to which a host application can interact with the networking capabilities of the XLR PRO. When in API mode, all data entering and leaving the module is contained in frames that define operations or events within the XLR PRO.

Transmit data frames (received through the serial port) include:

• RF Transmit data frame

• Command Frame (equivalent to AT commands)

Receive Data Frames (sent out the serial port) include:

• RF-received data frame

• Command response

• Event notifications such as reset and so on

The API provides alternative means of configuring modules and routing data at the host application layer. A host application can send data frames to the XLR PRO that contain address and payload information instead of using command mode to modify addresses. The XLR PRO will send data frames to the application containing status packets; as well as source, and payload information from received data packets.

The API operation option facilitates many operations such as:

XLR PRO User Guide 25

• Transmitting data to multiple destinations without entering Command Mode

• Receiving the success or failure status of each transmitted RF packet

• Identifying the source address of each received packet

Comparing transparent and API operation

The following table compares the advantages of transparent and API modes of operation:

As a general rule of thumb, API mode is recommended when a device:

• Sends RF data to multiple destinations

• Sends remote configuration commands to manage devices in the network

• Receives RF data packets from multiple devices, and the application needs to know which device sent which packet

If the above conditions do not apply, then you may prefer transparent operation due to the simplicity of operation. You can use a mixture of devices running API Mode and Transparent Mode in a network.

AT Command Mode To modify or read radio parameters, the XLR PRO must first enter Command Mode - a state in which incoming serial characters are interpreted as commands. When the XLR PRO is configured for API mode, AT Commands can be issued locally or remotely using the appropriate API frames. For more

Transparent operation features

Simple interface All received serial data is transmitted unless the XLR PRO is in command mode. The XLR PRO will act as a serial cable replacement.

Easy to support It is easier for an application to support transparent operation and command mode. Integrates easily with existing serial equipment and will work “out of the box” in many applications.

API operation features

Easy to manage data transmissions to multiple destinations

Transmitting RF data to multiple remotes only requires changing the address in the API frame. This process is much faster than in transparent operation where the application must enter AT command mode, change the address, exit command mode, and then transmit data.

Each API transmission can return a transmit status frame indicating the success or reason for failure.

Received data frames indicate the sender's address

All received…