FX SERIES

RFID FIXED
READER

Integration Guide

MN000026A12EN Rev. A
FX SERIES RFID READER
INTEGRATION GUIDE
MN000026A12EN
Revision A
April 2020
Copyright
ZEBRA and the stylized Zebra head are trademarks of Zebra Technologies Corporation, registered in many
jurisdictions worldwide. All other trademarks are the property of their respective owners. ©2019-2020 Zebra
Technologies Corporation and/or its affiliates. All rights reserved.

COPYRIGHTS & TRADEMARKS: For complete copyright and trademark information, go to

www.zebra.com/copyright.

WARRANTY: For complete warranty information, go to www.zebra.com/warranty.

END USER LICENSE AGREEMENT: For complete EULA information, go to www.zebra.com/eula.

For Australia Only

For Australia Only. This warranty is given by Zebra Technologies Asia Pacific Pte. Ltd., 71 Robinson Road, #05-
02/03, Singapore 068895, Singapore. Our goods come with guarantees that cannot be excluded under the
Australia Consumer Law. You are entitled to a replacement or refund for a major failure and compensation for any
other reasonably foreseeable loss or damage. You are also entitled to have the goods repaired or replaced if the
goods fail to be of acceptable quality and the failure does not amount to a major failure.

Zebra Technologies Corporation Australia’s limited warranty above is in addition to any rights and remedies you
may have under the Australian Consumer Law. If you have any queries, please call Zebra Technologies
Corporation at +65 6858 0722. You may also visit our website: www.zebra.com for the most updated warranty
terms.

Terms of Use
• Proprietary Statement
This manual contains proprietary information of Zebra Technologies Corporation and its subsidiaries
(“Zebra Technologies”). It is intended solely for the information and use of parties operating and
maintaining the equipment described herein. Such proprietary information may not be used, reproduced,
or disclosed to any other parties for any other purpose without the express, written permission of Zebra
Technologies.
• Product Improvements
Continuous improvement of products is a policy of Zebra Technologies. All specifications and designs are
subject to change without notice.
• Liability Disclaimer
Zebra Technologies takes steps to ensure that its published Engineering specifications and manuals are
correct; however, errors do occur. Zebra Technologies reserves the right to correct any such errors and
disclaims liability resulting therefrom.
• Limitation of Liability

In no event shall Zebra Technologies or anyone else involved in the creation, production, or delivery of the
accompanying product (including hardware and software) be liable for any damages whatsoever
(including, without limitation, consequential damages including loss of business profits, business
interruption, or loss of business information) arising out of the use of, the results of use of, or inability to
use such product, even if Zebra Technologies has been advised of the possibility of such damages. Some
jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above
limitation or exclusion may not apply to you.

3
Revision History
Changes to the original manual are listed below:

Change Date Description

-01 Rev A 1/2014 Initial release

-02 Rev A 2/2015 Zebra Re-Branding

-03 Rev A 4/2016 Updates for SNAP; updated screen shots.

-04 Rev A 7/2016 Updates:

- Changed the installing antenna separation distance to 13.4 in (34 cm).
- Changed max antenna gain exceed to + 6.6dBiL.
- Changed Max Conducted RF Power at Antenna Input for US.
- Changed Max Antenna Gain Allowed for US.
- Added Canada and Taiwan to Antenna Gain and Radiated Power table.

-05 Rev A 7/2016 Updates to EU column of Antenna Gain and Radiated Power table.
- Changed Max Conducted RF Power at Antenna Input.
- Changed Max Antenna Gain Allowed.

-06 Rev A 11/2017 Update guide to include FX9600; Guide title updated to FX Series RFID Fixed
Reader Integration Guide.

-07 Rev A 12/2017 Correction to antenna port technical specification for FX9600.

-08 Rev A 7/2018 Updates:

- FX9600 Bluetooth dongle support information.
- Air Protocol ISO/IEC 18000-63.

-09 Rev A 9/2018 Added:

- "Requirements" section to "Quick Start".
- "Install" below Applications.
- FX9600 Serial Port Data Configuration.

Updated:
- "Quick Start" steps 1 & 2.
- Warning statement below "Connecting FX7500 and FX9600 RFID Reader
Antennas".
- Statement below "Microsoft RNDIS Driver for Windows 7."
- Several items on page 34.
- Global update -> ’click’ to ’select’ (techpubs style change).
- Replaced the following screen shots and corresponding screen selections:
Figures 7, 35, 39, 51, 52. 55
- Tables 7 and 8.
- System Log field definitions.

Deleted:
- All instances of Java JRE.
- ’Read Tags’ notes (security and clearing java cache).
- JVM references in Reader Profiles.

4
 Change Date Description

-10 Rev A 8/2019 Added:

- FX Connect information.
- New troubleshooting information.
- New Important statement in the Connecting FX7500 and FX9600 RFID Reader
Antennas section.

Updated:
- 123RFID to 123RFID Desktop.
- Administrator Console introduction.
- Commit/Discard section.
- Screen shots.
- Related documents, software and reference guide.
- Auto Discovery section.
- Cable loss and cable length default value.
- Data Prefix/Data Suffix in Table 9 and 11.
- Server URL in Manage License section.
- Capability response valid period.
- FX Connect Licensing Mechanism

-11EN Rev A 4/2020 Updated:

- FX series operating system
- Network Services Settings section
- FX Series Licensing Management section
- Reader Profile section
- Reader Configuration via USB Thumb Drive section.

Added:
- Example JSON format of Tag Data section
- Example Key-Value Pair format of Tag Data section
- Licensing errors troubleshooting
- 2-step firmware update
- Ethernet/IP section
- Cellular Connectivity with Sierra Modem section
- SOTI MOBI Client section
- Moving vs Stationary section
- REST RCI Support section.

-12EN Rev A 4/2020 - Updated the Procuring Licenses section.

- Added notes that mentioned the FX7500 Reader does not support Network
Connect (EtherNet/IP).
- Updated Table 12.
- Updated Figure 12.

5
Table of Contents
Copyright ........................................................................................................................................... 3
For Australia Only ....................................................................................................................... 3
Terms of Use .................................................................................................................................... 3
Revision History ................................................................................................................................ 4

About This Guide

Introduction ..................................................................................................................................... 12
Chapter Descriptions ...................................................................................................................... 12
Notational Conventions ................................................................................................................... 13
Related Documents and Software .................................................................................................. 13
Service Information ......................................................................................................................... 14

Quick Start
Introduction ..................................................................................................................................... 15
Requirements .................................................................................................................................. 15
Quick Start Demonstration .............................................................................................................. 15
Step 1, Setup ............................................................................................................................ 16
Step 2, Connecting to the Reader ............................................................................................. 17
Step 3, First Time / Start-Up Login ............................................................................................ 17
Step 4, Set Region .................................................................................................................... 18
Step 5, Read Tags .................................................................................................................... 20

Getting Started
Introduction ..................................................................................................................................... 21
FX Series Features ......................................................................................................................... 21
FX7500 Parts ............................................................................................................................ 22
FX7500 Rear Panel ................................................................................................................... 23
FX7500 LEDs ............................................................................................................................ 24
FX9600 Parts ............................................................................................................................ 25
FX9600 Rear Panel ................................................................................................................... 26
FX9600 LEDs ............................................................................................................................ 26

Installation and Communication

Introduction ..................................................................................................................................... 28

6
 Table of Contents

Unpacking the Reader .................................................................................................................... 28

Mounting and Removing the FX Series Readers ............................................................................ 29
Mounting Tips ...................................................................................................................... 29
Mounting the FX7500 With a Mounting Plate ............................................................................ 29
FX7500 Direct Mounting ........................................................................................................... 30
Mounting the FX9600 Reader ......................................................................................................... 31
Concrete Wall Mounting ...................................................................................................... 31
Wood or Metal Wall Mounting ............................................................................................. 31
Drywall Mounting ................................................................................................................. 31
VESA Mounting ................................................................................................................... 31
Connecting FX7500 and FX9600 RFID Reader Antennas ............................................................. 32
Communications and Power Connections ...................................................................................... 33
Ethernet Connection ................................................................................................................. 33
Ethernet: Power through AC Outlet ..................................................................................... 33
Ethernet: Power through Standard PoE or PoE+ ................................................................ 34
USB Connection ........................................................................................................................ 34
Zebra USB RNDIS Driver .................................................................................................... 34
Microsoft RNDIS Driver for Windows 7 ............................................................................... 35
Sample Implementation ...................................................................................................... 36
GPIO Interface Connection ....................................................................................................... 37
LED Sequences .............................................................................................................................. 38
System Start-up/Boot LED Sequence ....................................................................................... 38
PWR LED Sequence to Indicate IPv4 Status after Booting ...................................................... 38
Reset to Factory Defaults LED Sequence ................................................................................ 38
LED Sequence for Software Update Status .............................................................................. 38
Reading Tags .................................................................................................................................. 39

123RFID Desktop
Introduction ..................................................................................................................................... 40
Features .......................................................................................................................................... 41
Communication with 123RFID Desktop .......................................................................................... 41
123RFID Desktop Requirements .................................................................................................... 41

Administrator Console
Introduction ..................................................................................................................................... 42
Reader Administrator Console Selections ...................................................................................... 42
Profiles ...................................................................................................................................... 43
Resetting the Reader ................................................................................................................ 43
Auto Discovery .......................................................................................................................... 44
Connecting to the Reader ............................................................................................................... 45
Obtaining the IP Address via Command Prompt ...................................................................... 45
Connecting via Host Name ....................................................................................................... 46
Connecting via IP Address ........................................................................................................ 46
Using Zero-Configuration Networking when DHCP Server is Not Available ............................. 46
Administrator Console Login ........................................................................................................... 47
First Time / Start-Up Login ........................................................................................................ 47
Logging In with Default User ID and Password ................................................................... 47
Setting the Region ..................................................................................................................... 48
Reader Administrator Console ........................................................................................................ 49

7
 Table of Contents

Administrator Console Option Selections .................................................................................. 49

Status .............................................................................................................................................. 51
Reader Statistics ............................................................................................................................. 52
Reader Gen2 Optional Operation Statistics .............................................................................. 53
NXP Custom Command Operation Statistics ............................................................................ 54
Event Statistics .......................................................................................................................... 55
Other Custom Command Operation Statistics .......................................................................... 56
Configure Reader ............................................................................................................................ 57
Reader Parameters ................................................................................................................... 57
Read Points ............................................................................................................................... 58
Antenna Status .................................................................................................................... 58
Antenna Configuration ........................................................................................................ 59
Read Points - Advanced ........................................................................................................... 59
Configure Region ...................................................................................................................... 60
Certificates ................................................................................................................................ 61
Certificate Configuration ...................................................................................................... 62
Creating a Custom Certificate ............................................................................................. 63
Script Usage ........................................................................................................................ 70
Read Tags ...................................................................................................................................... 71
Communication Settings ................................................................................................................. 72
Configure Network Settings - Ethernet Tab .............................................................................. 72
IPV4 .................................................................................................................................... 72
IPV6 .................................................................................................................................... 73
Configure Network Settings - Wi-Fi Tab .................................................................................... 73
IPV4 .................................................................................................................................... 73
IPV6 .................................................................................................................................... 74
Configure Network Settings - Bluetooth Tab ............................................................................. 74
Configure LLRP Settings ........................................................................................................... 75
SNMP Settings .......................................................................................................................... 76
Wireless Settings ...................................................................................................................... 77
Network Services Settings ........................................................................................................ 78
FX9600 Serial Port Configuration ............................................................................................. 78
Serial Port Configuration - Debug Port ................................................................................ 79
Serial Port Configuration - Push Data Port .......................................................................... 79
Serial Port Configuration - Free Port ................................................................................... 82
FX Connect ............................................................................................................................... 82
Using FX Connect ............................................................................................................... 82
Running Inventory on FX Connect ...................................................................................... 90
Example JSON format of Tag Data ..................................................................................... 90
Example Key-Value Pair Format of Tag Data ..................................................................... 91
Configuring the HTTP Post Server ...................................................................................... 92
Configuring the HTTP Proxy Server .................................................................................... 93
Configuring USB HID .......................................................................................................... 93
Configuring the TCP/IP Socket ........................................................................................... 94
Configuring the USB Flash Drive ........................................................................................ 97
FX Series Licensing Management .................................................................................................. 97
FX Series Licensing Model ....................................................................................................... 97
Procuring Licenses .................................................................................................................... 97
Types of Licenses ..................................................................................................................... 98
Evaluation License .............................................................................................................. 98
Perpetual License ............................................................................................................... 98

8
 Table of Contents

Enabling a License .................................................................................................................... 98

Time Tampering ........................................................................................................................ 98
FX Series Licensing Mechanism ..................................................................................................... 99
License Acquisition Modes ........................................................................................................ 99
Acquiring License from Production Server (ON-Line Mode) ............................................... 99
Acquiring License from UAT Server (ON-Line) ................................................................. 101
Acquiring License from Local License Server (ON-Line) .................................................. 102
Acquiring License by Downloading Bin File (OFF-Line) .................................................... 102
Device ID ........................................................................................................................... 103
Activation ID ...................................................................................................................... 103
How to Return License ............................................................................................................ 104
How to Setup and Manage the Local License Server ............................................................. 105
How to Download Capability Response from The Cloud Server ............................................. 106
System Time Management ........................................................................................................... 112
IPV6 IP Sec ................................................................................................................................... 113
Change Password ......................................................................................................................... 114
FX Series User Accounts ........................................................................................................ 114
Managing User Login and Logout ........................................................................................... 115
GPIO ............................................................................................................................................. 115
Applications ................................................................................................................................... 116
Reader Profiles ............................................................................................................................. 117
FIPS Support ........................................................................................................................... 119
Firmware Version/Update ............................................................................................................. 120
Firmware Update ..................................................................................................................... 121
Commit/Discard Functionality Changes ........................................................................................ 121
Region Configuration Commit ................................................................................................. 121
New Property Change Work Flow ........................................................................................... 123
System Log ................................................................................................................................... 125
Configure System Log ............................................................................................................. 126
Reader Diagnostics ....................................................................................................................... 127
Shutdown ...................................................................................................................................... 128

Configure and Connect via Wi-Fi and Bluetooth

Wireless Network Advanced Configuration ................................................................................... 129
Sample Configuration Files ..................................................................................................... 130
Preferred Configurations for Access Points .................................................................................. 131
Access Point Configuration for Android Device ...................................................................... 132
Open Network ................................................................................................................... 132
WPA2 PSK ........................................................................................................................ 132
WPA PSK .......................................................................................................................... 133
Internet Connection Configuration for iPhone ......................................................................... 133
Connecting to a Wireless Network Using a Wi-Fi Dongle ............................................................. 134
Connecting to a Peer Device over Bluetooth Using a Bluetooth Dongle ...................................... 138
Copying Files to the Reader ......................................................................................................... 140

Application Development
Introduction ................................................................................................................................... 141

9
 Table of Contents

Firmware Upgrade
Introduction ................................................................................................................................... 142
Prerequisites ................................................................................................................................. 142
Failsafe Update ............................................................................................................................. 143
Two-step firmware update ............................................................................................................ 143
Update Phases ............................................................................................................................. 144
Updating FX Series Reader Software ........................................................................................... 145
Verifying Firmware Version ..................................................................................................... 145
Updating Methods ................................................................................................................... 146
Update Using a USB Drive (Recommended) .................................................................... 146
File-Based Update ............................................................................................................ 147
FTP-Based Update ........................................................................................................... 150
Verifying Firmware Version ..................................................................................................... 151

EtherNet/IP
Introduction ................................................................................................................................... 153
EtherNet/IP ................................................................................................................................... 153
Using EtherNet/IP ................................................................................................................... 153
Supported RFID Operations Through EtherNet/IP: ................................................................. 154

Cellular Connectivity with Sierra Modem

Introduction ................................................................................................................................... 156
Cellular Connectivity with Sierra Modem ...................................................................................... 156
Steps to Configure RV50X ...................................................................................................... 157
Steps to send reader data to cloud using Sierra Modem. ................................................. 161

SOTI MOBI Client

Introduction ................................................................................................................................... 162
SOTI MOBI Client ......................................................................................................................... 162

Gen2 V2 Enhancement
Introduction ................................................................................................................................... 165
Gen2 V2 Enhancement ................................................................................................................. 165

Reader Configuration via USB Thumb Drive

Introduction ................................................................................................................................... 166
Reader Configuration via USB Thumb Drive ................................................................................ 166

GPS and Triggers for Trucking and Delivery

Introduction ................................................................................................................................... 168
GPS and New Triggers For Trucking and Delivery Use Cases .................................................... 168
Specific examples of trigger configuration ........................................................................ 170

10
 Table of Contents

Moving and Stationary Tags

Introduction ................................................................................................................................... 175
Moving vs Stationary ..................................................................................................................... 175

REST RCI Support

Introduction ................................................................................................................................... 181
REST RCI Support ........................................................................................................................ 181
Communication ....................................................................................................................... 182

Troubleshooting
Troubleshooting ............................................................................................................................ 183
Troubleshooting for Licensing Errors ............................................................................................ 188

Technical Specifications
Technical Specifications ............................................................................................................... 190
Cable Pinouts ................................................................................................................................ 192
10/100bT Ethernet / PoE Connector ....................................................................................... 192
USB Client Connector ............................................................................................................. 193
USB Host Connector ............................................................................................................... 193
FX7500 GPIO Port Connections ............................................................................................. 194
FX9600 GPIO Connections ..................................................................................................... 194

Static IP Configuration
Introduction ................................................................................................................................... 197
Reader IP Address or Host Name is Known ................................................................................. 197
Reader IP is Not Known (DHCP Network Not Available) .............................................................. 199

RF Air Link Configuration

Introduction ................................................................................................................................... 201
Radio Modes ................................................................................................................................. 201

Copying Files To and From the Reader

Introduction ................................................................................................................................... 206
SCP ............................................................................................................................................... 206
FTP ............................................................................................................................................... 206
FTPS ............................................................................................................................................. 206

Data Protection
Introduction ................................................................................................................................... 207

Index

11
ABOUT THIS GUIDE

Introduction
This Integration Guide provides information about installing, configuring, and using the FX7500 and FX9600 RFID
readers and is intended for use by professional installers and system integrators. The FX7500 and FX9600 readers
provide real time, seamless tag processing for EPC Class1 Gen2 compliant tags.

NOTE Screens and windows pictured in this guide are samples and may differ from actual screens.

Chapter Descriptions
Topics covered in this guide are as follows:
• Quick Start provides a Quick Start tag reading demonstration.
• Getting Started provides the FX7500 and FX9600 RFID fixed readers features, parts, and LED indications.
• Installation and Communication provides information on installing and setting up the FX7500 and FX9600
readers.
• 123RFID Desktop describes 123RFID Desktop for fixed RFID readers.
• Administrator Console describes how to connect to the reader, how to use the web-based Administrator
Console to configure and manage FX7500 and FX9600 readers and detailed information about FX
Connect.
• Configure and Connect via Wi-Fi and Bluetooth details wireless network advanced configuration, preferred
configurations for access points, and how to connect to a peer device over Bluetooth using a USB
Bluetooth dongle.
• Application Development provides information on developing applications for the FX7500 and FX9600.
• Firmware Upgrade provides reader firmware upgrade information on using the web-based Administrator
Console and an FTP or FTPS server running a host computer.
• EtherNet/IP provides the overview of EtherNet/IP for FX Series RFID reader.
• Cellular Connectivity with Sierra Modem includes the information on how to configure the Sierra Modem
RV50X to provide cellular connectivity for the FX9600 RFID Reader.
• SOTI MOBI Client provides information on SOTI Mobicontrol and includes references to the appropriate
guides.
• Gen2 V2 Enhancement describes the Gen2V2 commands supported by the FX Series RFID Reader and
includes the reference to the appropriate guide.
• Reader Configuration via USB Thumb Drive includes the steps to transfer a reader configuration to
another reader via a USB thumb drive.

12
 About This Guide

• GPS and Triggers for Trucking and Delivery provides information on the GPS feature and three new
triggers for trucking and delivery.
• Moving and Stationary Tags recommends the LLRP and RFID3 APIs configurations to read the moving
and stationary tags.
• REST RCI Support provides information on the Reader Communication Interface (RCI) commands and
includes the references to the appropriate guides.
• Troubleshooting describes FX7500 and FX9600 readers troubleshooting procedures.
• Technical Specifications includes the technical specifications for the readers.
• Static IP Configuration describes three methods of setting the static IP address on an FX7500 and FX9600
RFID Reader.
• RF Air Link Configuration describes how to select air link configuration from a set of available air link
profiles.
• Copying Files To and From the Reader describes the SCP, FTP, and FTPS protocols for copying files.
• Data Protection describes how the FX7500 and FX9600 protects RFID data in transition.

Notational Conventions
The following conventions are used in this document:
• “RFID reader”, “reader”, or “FX Series” refers to the Zebra FX7500 and/or FX9600 RFID readers.
• Bullets (•) indicate:
• Action items
• Lists of alternatives
• Lists of required steps that are not necessarily sequential.
• Sequential lists (e.g., those that describe step-by-step procedures) appear as numbered lists.

Related Documents and Software

The following documents provide more information about the reader.
• FX7500 RFID Reader Quick Start Guide, p/n MN000070Axx.
• FX9600 RFID Reader Quick Start Guide, p/n MN-003087-xx.
• FX Series Reader Software Interface Control Guide, p/n 72E-131718-xx. Describes Low Level Reader
Protocol (LLRP) and Reader Management (RM) extensions for the reader.
• RFID Demo Applications User Guide, p/n 72E-160038-xx. Provides instructions for using sample
applications which demonstrate how to use Zebra RFID readers.
• Zebra FX Series Embedded C/CPP SDK User Guide Linux. Provides instructions for using the FX Series
Embedded native C/C++ SDK for Linux.
• Zebra FX Series Embedded Java SDK User Guide Linux. Explains how to use the FX Series Embedded
Java SDK for Linux.
• Zebra FX Series Embedded Java SDK User Guide Windows. Describes instruction for using the FX Series
Embedded Java SDK for Windows.
• Programmer's Guide provided with the Zebra RFID SDK. This introductory guide describes how to perform
various functions using the RFID3 API set.
• RFID3 API
• EPCglobal Low Level Reader Protocol (LLRP) Standard
For the latest version of these guides and software, visit: www.zebra.com/support.

13
 About This Guide

Service Information
If you have a problem using the equipment, contact your facility's technical or systems support. If there is a
problem with the equipment, they will contact the Zebra Global Customer Support Center at:
www.zebra.com/support.
When contacting Zebra support, please have the following information available:

• Serial number of the unit

• Model number or product name
• Software type and version number.
Zebra responds to calls by e-mail, telephone or fax within the time limits set forth in support agreements.
If your problem cannot be solved by Zebra support, you may need to return your equipment for servicing and will
be given specific directions. Zebra is not responsible for any damages incurred during shipment if the approved
shipping container is not used. Shipping the units improperly can possibly void the warranty.
If you purchased your business product from a Zebra business partner, contact that business partner for support.

14
Quick Start

Introduction
This chapter provides system requirements and a Quick Start setup demonstration.

Requirements
• Fixed reader.
• Ethernet cable.
• Personal computer running Windows with Internet Explorer 11.
• Antenna cable.
• Antenna.
• Power supply (AC power supply or PoE/PoE+ injector).
• RFID tags (EPC Global Gen2 compliant).

Quick Start Demonstration

The Quick Start demonstration offers a simple, temporary way to quickly set up the reader and read tags. The
demonstration includes:
• Step 1, Setup on page 16
• Step 2, Connecting to the Reader on page 17
• Step 3, First Time / Start-Up Login on page 17
• Step 4, Set Region on page 18
• Step 5, Read Tags on page 20

15
 Quick Start

Step 1, Setup
For information on complete component kits available from Zebra, see Technical Specifications.

1. Unpack the reader. See Unpacking the Reader on page 28.

2. Place the reader on a desktop.
3. Connect the antenna to antenna Port 1. See Figure 1 and Figure 2.
4. Connect the Ethernet cable to the Ethernet port. See Figure 1 and Figure 2.

NOTE: Connecting the reader to a subnet that supports DHCP is recommended. This Quick Start procedure is
not guaranteed to work if DHCP is disabled in the reader and if the reader is connected directly to a PC.

5. To connect to power:
• When using an AC power supply, connect the AC power supply to a power outlet and connect to the power
port.
• When using PoE or PoE+, plug the Ethernet cable into the PoE/PoE+ injector.
6. Wait for the green power LED to stay lit. See System Start-up/Boot LED Sequence on page 38 for boot-up
details.

Figure 1 FX7500 RFID Fixed Reader Rear Panel Connections

Port 1 Port 2 Port 3 Port 4 GPIO 24 VDC

Antenna Ports (Four Ports, Reverse TNC) Reset GPIO USB USB 10/100BaseT Power
Client Host Ethernet (with PoE)

Figure 2 FX9600 RFID Fixed Reader Rear Panel Connections

10/100BaseT Ethernet USB USB

(with PoE/PoE+) Host Client

Debug Serial
Antenna Ports (Eight Ports, Reverse TNC) GPIO Port Reset Power

16
 Quick Start

Step 2, Connecting to the Reader

To connect via host name:

1. Open a web browser to connect to the reader.

2. Enter the host name printed on the reader label in the browser address bar. If the label is missing or damaged,
it is possible to create the host name by using the reader model name as a prefix followed by the last six hex
numbers from the MAC address. For example, for an FX9600 with the MAC address 0023683BA63A, the host
name is FX96003BA63A. The string to enter in the browser address bar is http://FX96003BA63A.

NOTE: Connect the reader to a network that supports host name registration and lookup to ensure the network
can access the reader using the host name. For instance, some networks can register host names
through DHCP. When first connecting to the reader, it is recommended to keep DHCP enabled in both
the PC and in the reader, although it is not guaranteed that host name will work all the time. Use the host
name printed on the reader label, or construct it using the reader MAC address on the bottom of the
reader.

Step 3, First Time / Start-Up Login

When starting the reader for the first time:

1. In the User Login window, enter admin in the User Name: field and enter change in the Password: field.

Figure 3 User Login Window

NOTE: If you forget the user ID and/or password, see Reset to Factory Defaults LED Sequence on page 38 to
reset the reader to factory defaults, and then select admin for the user name and enter change in the
password field to regain access.

2. Select Login. The Region Configuration window appears.

NOTE: The Region Configuration window does not appear for US reader configurations. For these models, the
Administrator Console main window appears. See Figure 21 on page 43.

17
 Quick Start

Step 4, Set Region

Set the region of operation. Setting the unit to a different region is illegal.

NOTE: Region configuration is not available for readers configured to operate in the United States region (under
FCC rules). In this case, skip this step.

1. In the Configure Region Settings window, select the region from the drop-down menu.

Figure 4 Selecting the Region

2. Select the Communication Standard, if applicable.

3. Select Frequency Hopping, if applicable.
4. Select the appropriate channel(s), if applicable.
5. Select the I understand check box.
6. Select Set Properties to complete the region selection. The Operation Successful window displays a Saving.
Please wait... message with a progress symbol until the commit completes.
7. When the commit completes, a gray floppy disk icon displays indicating that the commit completed
successfully. See Commit/Discard Functionality Changes on page 121 for more information.

18
 Quick Start

Figure 5 Region Configuration, Operation Successful Window

19
 Quick Start

Step 5, Read Tags

Select Read Tags to view the Reader Operation window.

Figure 6 Read Tags Window

• Select Start to initiate an on-demand scan on the connected antennas that are enabled.
• Select Stop to stop the inventory operation.
• Select Clear to clear the current tag list.

The list of tags appears in a table with the following attributes for each tag:

• EPC Id: Unique tag EPC ID.

• Tag Seen Count: Number of times the tag is identified on the specific antenna.
• RSSI: Received Signal Strength Indication.
• Antenna Id: Antenna ID on which the tag is seen.
• Seen Time: UTC time (in microseconds) showing when the tag was first seen.

20
Getting Started

Introduction
This chapter provides the FX7500 and FX9600 RFID fixed readers features, parts, and LED indications.

FX Series Features
The Zebra FX Series RFID readers are based on Zebra's FX Series fixed reader platform and are easy to use,
deploy, and manage. The RFID read performance provides real-time, seamless EPC-compliant tags processing
for inventory management and asset tracking applications in large scale deployments.
The Zebra FX Series RFID readers provide a wide range of features that enable implementation of complete,
high-performance, intelligent RFID solutions.

Table 1 FX Series RFID Reader Features

Feature Zebra FX7500 Zebra FX9600
Air Protocol ISO 18000-63 ISO 18000-63
(EPC Class 1 Gen2 V2) (EPC Class 1 Gen2 V2)
Housing Construction Die-Cast Aluminum Plastic Die-Cast Aluminum
Sheet Metal
Operating System1 Linux v4.9 Linux v4.9
Java OpenJDK Run time v1.8 Run time v1.8
JVM OpenJDK Zero build JVM OpenJDK Zero build 25.102-b14
25.102-b14
Operating Temperature -20° to +55° C -20° to +55° C
Antenna Ports 2 Port, 4 Port 4 Port, 8 Port
Power Supply +24V DC, POE, POE+ +24V DC, POE, POE+
API RFID3 RFID3
Monostatic/Bistatic Monostatic Monostatic
GPIO 2 Input, 3 Output 4 Input, 4 Output
Maximum RF Output Power +31.5 dBm +33 dBm
1
The Linux kernel and tool chain for embedded application development have been updated starting with
version 3.0.35. Applications created with older tool chain need to be recompiled with new embedded SDK. If
recompiling is not an option, please see note on reverting back to older firmware version in Firmware Update
section.

21
 Getting Started

Table 1 FX Series RFID Reader Features (Continued)

Feature Zebra FX7500 Zebra FX9600
RX Sensitivity -82 dBm -86 dBm
IP Sealing IP40 IP53
Power-Over-Ethernet Yes Yes
Embedded Applications Yes Yes
SDKs
Embedded1 Applications: C, Java C, Java
Host Based Applications: C, Java, .Net C, Java, .Net
Wi-Fi/Bluetooth Dongle Support Yes Yes
1The Linux kernel and tool chain for embedded application development have been updated starting with
version 3.0.35. Applications created with older tool chain need to be recompiled with new embedded SDK. If
recompiling is not an option, please see note on reverting back to older firmware version in Firmware Update
section.

WARNING: For Mounting in Environmental Air Handling Space (EAHS): Do not install the Mounting Bracket,
Antenna, Cables, PSU, and PoE (Power Injector) in the EAHS unless they are suitable for use in EAHS
per UL 2043.

FX7500 Parts
Figure 7 FX7500 RFID Reader Rear Panel Connections

Port 1 Port 2 Port 3 Port 4 GPIO 24 VDC

Antenna Ports (Four Ports, Reverse TNC) Reset GPIO USB USB 10/100BaseT Power
Client Host Ethernet (with PoE)

22
 Getting Started

Figure 8 FX7500 RFID Reader

PWR A C TV STAT APP
LEDs

Rear Panel
Antenna Ports (Reverse TNC)
r

CAUTION:Use only parts provided with the FX7500 RFID readers, or Zebra approved/recommended parts.
Substituting other cables or parts can degrade system performance, damage the reader, and/or void the
warranty.

FX7500 Rear Panel

Table 2 Rear Panel Descriptions

Port Description

Antenna Ports Two port version: Connect up to two antennas.

(Reverse TNC) Four port version: Connect up to four antennas.
See Table 18 on page 190 for the maximum antenna gains and RF output powers for both
US/Canada and EU. See Connecting FX7500 and FX9600 RFID Reader Antennas on page
32 for connection information.

Reset To reset the reader insert a paper clip into the reset hole, press and hold the reset button for
not more than 2 seconds. This resets the reader, but retains the user ID and password.

GPIO See GPIO Interface Connection on page 37 for more information.

USB Client The USB client port supports (by default) a network mode of operation. This enables a
secondary network interface as a virtual adapter over USB.
Advanced users can create a custom communication protocol on the USB port. See USB
Connection on page 34 for connection information.

USB Host Use the USB host port to connect USB devices such as Wi-Fi / Bluetooth over USB dongles
and flash memory drives.

23
 Getting Started

Table 2 Rear Panel Descriptions

Port Description

10/100BaseT Insert a standard RJ45 Ethernet cable to connect to an Ethernet network with or without PoE
Ethernet capability, or to a local computer. See Ethernet Connection on page 33 for connection
information.

Power DC connector connects to a Zebra approved power supply AC adapter (varies depending on the
country). Maximum power 24 VDC, 3.25 A.

FX7500 LEDs
The reader LEDs indicate reader status as described in Table 3. For the LED boot up sequence see System
Start-up/Boot LED Sequence on page 38.

Figure 9 FX7500 RFID Readers LEDs

PWR A C TV STAT APP

Table 3 FX7500 LED Indications

LED Function Color/Status Description

PWR Power Off Reader is powered off

Amber Solid Booting
Red Flashing Firmware upgrade
Amber Solid Application initialization after booting
Green Solid Reader is powered on and operational

ACTV Activity Off No RF operations

Amber Flashing On for 500 mSec indicates another tag operation
Green Flashing On for 500 mSec indicates a tag is inventoried or read

STAT Status Off No errors or GPIO events

Red Solid Firmware update failure
Red Flashing On for 500 mSec indicates an error in RF operation
Green Flashing On for 500 mSec indicates a GPI event

APP Application Green/Red/Amber Controlled through RM

24
 Getting Started

FX9600 Parts
Figure 10 FX9600 RFID Reader Rear Panel Connections
10/100BaseT Ethernet USB-A USB-B
(with PoE/PoE+) Host Client

Debug Serial
Antenna Ports (Eight Ports, Reverse TNC) GPIO Port Reset Power

Figure 11 FX9600 RFID Reader

LEDs

Rear Panel
Antenna Ports (Reverse TNC)

CAUTION:Use only parts provided with the FX9600 RFID readers, or Zebra approved/recommended parts.
Substituting other cables or parts can degrade system performance, damage the reader, and/or void
the warranty.

25
 Getting Started

FX9600 Rear Panel

Table 4 Rear Panel Descriptions

Port Description

Antenna Ports Four port version: Connect up to four antennas.

(Reverse TNC) Eight port version: Connect up to eight antennas.
See Table 18 on page 190 for the maximum antenna gains and RF output powers for both
US/Canada and EU.
See Connecting FX7500 and FX9600 RFID Reader Antennas on page 32 for connection
information.

Reset To reset the reader, insert a paper clip into the reset hole, press and hold the reset button for
not more than 2 seconds. This resets the reader but retains the user ID and password.

GPIO See GPIO Interface Connection on page 37 for more information.

USB Client The USB client port supports (by default) a network mode of operation. This enables a
secondary network interface as a virtual adapter over USB.
Advanced users can create a custom communication protocol on the USB port. See USB
Connection on page 34 for connection information.

USB Host Use the USB host port to connect USB devices such as Wi-Fi / Bluetooth over USB dongles
and flash memory drives.

RS-232 Use the RS-232 interface for debug serial port.

10/100BaseT Insert a standard RJ45 Ethernet cable to connect to an Ethernet network with or without
Ethernet PoE/PoE+ capability, or to a local computer. See Ethernet Connection on page 33 for
connection information.

Power DC connector connects to a Zebra approved power supply AC adapter (varies depending on the
country). Maximum power 24 VDC, 3.25 A.

FX9600 LEDs
The reader LEDs indicate reader status as described in Table 3. For the LED boot up sequence see System
Start-up/Boot LED Sequence on page 38.

26
 Getting Started

Figure 12 FX9600 RFID Readers LEDs

PWR ACTV STAT APP

Table 5 FX9600 LED Indications

LED Function Color/Status Description

PWR Power Off Reader is powered off

Amber Solid Booting
Red Flashing Firmware upgrade
Amber Solid Application initialization after booting
Green Solid Reader is powered on and operational

ACTV Activity Off No RF operations

Amber Flashing On for 500 mSec indicates another tag operation
Green Flashing On for 500 mSec indicates a tag is inventoried or read

STAT Status Off No errors or GPIO events

Red Solid Firmware update failure
Red Flashing On for 500 mSec indicates an error in RF operation
Green Flashing On for 500 mSec indicates a GPI event

APP Application Green/Red/Amber Controlled through RM

27
Installation and
Communication

Introduction
This chapter includes the following FX7500 and FX9600 RFID reader installation and communication procedures:

• Unpacking the Reader on page 28

• Mounting and Removing the FX Series Readers on page 29
• Mounting Tips on page 29
• Mounting the FX7500 With a Mounting Plate on page 29
• FX7500 Direct Mounting on page 30
• Connecting FX7500 and FX9600 RFID Reader Antennas on page 32
• Communications and Power Connections on page 33
• Ethernet Connection on page 33
• USB Connection on page 34
• GPIO Interface Connection on page 37
• System Start-up/Boot LED Sequence on page 38

CAUTION:FX Series RFID readers must be professionally installed.

WARNING: For Mounting in Environmental Air Handling Space (EAHS): Any cables used to interconnect to other
equipment must be suitable for use in EAHS as per UL2043.

Unpacking the Reader

Remove the reader from the shipping container and inspect it for damage. Keep the shipping container, it is the
approved shipping container and should be used if the reader needs to be returned for servicing.

28
 Installation and Communication

Mounting and Removing the FX Series Readers

Mounting Tips
Mount the reader in any orientation. Consider the following before selecting a location for the FX7500 and FX9600
readers:

• Mount the reader indoors, in operating range and out of direct sunlight, high moisture, and/or extreme
temperatures.
• Mount the reader in an area free from electromagnetic interference. Sources of interference include
generators, pumps, converters, non-interruptible power supplies, AC switching relays, light dimmers, and
computer CRT terminals.
• Ensure that any cable losses between the reader and antenna are taken into account to ensure the
desired level of system performance.
• Ensure that power can reach the reader.
• The recommended minimum horizontal mounting surface width is 7 1/2 inches for the FX7500 only.
However, the unit can mount on surfaces as narrow as 6 inches (in locations where unit overhang is not an
issue). For vertical mounting the unit can mount on a surface as small as 6 inches by 6 inches.
• Mount the reader onto a permanent fixture, such as a wall or a shelf, where it is not disturbed, bumped, or
damaged. The recommended minimum clearance on all sides of the reader is five inches.
• Use a level for precise vertical or horizontal mounting.

Mounting the FX7500 With a Mounting Plate

WARNING: For Mounting in Environmental Air Handling Space (EAHS): Do not install the Bracket, Cables in the
EAHS unless they are suitable for use in EAHS per UL 2043.

NOTE: The Mounting Plate section applies to the FX7500 RFID Fixed Reader only.

1. Position the mounting plate on a flat surface (wall or shelf). Position the release tab on the top. See Figure 13.
2. Mark the hole locations using the mounting plate as a guide. See Figure 13. Remove the mounting plate and
drill holes (appropriate for the surface material) at the marked locations.

NOTE: For wood surfaces, drill two 1/8" diameter by 7/8" deep holes. For drywall/masonry surfaces, drill two
3/16" diameter by 7/8" deep (min) holes and install using the provided anchors.

29
 Installation and Communication

Figure 13 Mounting Plate, Front

Mounting Holes Release Tab

Screw Head Stops

(4 typical)

3. Reposition the mounting plate over the mounting holes and secure using the supplied fasteners (as
appropriate for the surface material).

NOTE: Mount the reader with the cable connections up or down, depending on the installation requirements.

CAUTION:Use a hand screw driver to install the mounting plate (do not use a power driver). Do not use
excessive torque, and tighten the screws so that they are just snug on the screw head stops
(see Figure 13). If the reader does not engage the mounting plate, loosen the screw(s) 1/8 to 1/4 turn
and try again.

4. Position the reader by aligning the markers on the metal base plate and the wall bracket, with the key-slot
holes over the mounting screws. Gently slide the reader down to lock into place.
5. To remove the reader, press the release tab and slide the reader up while gently pulling out.

FX7500 Direct Mounting

CAUTION:Not using the mounting plate for the FX7500 reader can affect read performance at elevated
temperatures. Also, if not using the mounting plate, secure the reader to prevent it from coming off of
the mounting screws.

To mount the unit without using the mounting plate:

1. Use the mounting bracket as a template to locate the holes, or locate and mark the holes on 4 3/16” centers,
+/- 1/32”.
2. For wood surfaces, drill two 1/8" diameter by 7/8" deep holes on 4.192" centers. For drywall/masonry surfaces,
drill two 3/16" diameter by 7/8" deep (min) holes on 4.192" centers and install using the provided anchors.
3. Position the reader with the key-slot holes over the mounting screws and gently slide the reader down to lock
into place.
4. Adjust the screw head height to assure a snug fit. Or if the screws are accessible from the back, use machine
screws with a lock washer/nut and tighten the nut (from the back) to secure the reader.

30
 Installation and Communication

Mounting the FX9600 Reader

The FX9600 is equipped with two mounting flanges and slotted keyholes that accept three #8 (M4) mounting
screws. Pre-drill mounting surface according to the following dimensions. The mounting surface must be able to
support up to 10 pounds (2.3 kg).

Figure 14 FX9600 Mechanical Dimensions

256 mm
(10.10”)
Mounting
Tab (4)

110.7 mm
(4.4”)

Concrete Wall Mounting

To mount the RFID Reader to a hollow concrete block wall, Zebra recommends metal sleeve type concrete
anchors that accept #8 screws and flat washers.

Wood or Metal Wall Mounting

To mount the RFID Reader to a wood or sheet metal wall, Zebra recommends either #8 x 1 inch wood screws or #8
x 1 inch sheet metal screws and washers.

Drywall Mounting
To mount the RFID Reader to drywall, Zebra recommends either #8 toggle bolts or #8 drywall anchors.

VESA Mounting
The FX9600 may be mounted via four VESA hole on 100 mm x 100 mm pattern using 10-32 screw.

31
 Installation and Communication

Connecting FX7500 and FX9600 RFID Reader Antennas

IMPORTANT: The Zebra antennas that are approved and provide optimal performance for various uses cases
are AN510, AN440, AN480, AN610, AN620, AN710, and AN720. To meet optimum RF
specifications, an antenna with maximum VSWR = 1.4 must be used.

WARNING: Follow antenna installation and power connection instructions in its entirety before operating the FX
readers to avoid personal injury or equipment damage that may result from improper use. To
safeguard personnel, be sure to position all antenna(s) according to the specified requirements for
your regulatory region.

CAUTION:Power off the reader before connecting antennas. Never disconnect the antennas while the reader is
powered on or reading tags. This can damage the reader.

Do not turn on the antenna ports from a host when the antennas are not connected.

Maximum antenna gain (including any cable loss) cannot exceed 6 dBiL. See Table 6 for
corresponding maximum conducted RF power at antenna input.

When mounting the antennas outside the building, connect the screen of the coaxial cable to earth
(ground) at the entrance to the building. Perform this in accordance with applicable national electrical
installation codes. In the U.S., this is required by Section 820.93 of the National Electrical Code,
ANSI/NFPA 70.

WARNING: For Mounting in Environmental Air Handling Space (EAHS): Do not install Antennas and Antenna
Cables in the EAHS unless they are suitable for use in EAHS as per UL 2043.

Table 6 Maximum Antenna Power

FX7500/FX9600 US and Canada EU Other Countries

Max Radiated Power Allowed 4W EIRP 2W ERP Per local regulatory requirements

Max Conducted RF Power at 30dBm N/A Per local regulatory requirements

Antenna Input1
1Antenna Input refers to the end of the cable that plugs into the antenna (not the antenna port on the
reader).

To connect the antennas to the reader (see Figure 15):

1. For each antenna, attach the antenna reverse TNC connector to an antenna port.
2. Secure the cable using wire ties. Do not bend the cable.

Figure 15 FX7500 RFID Reader Antenna Connection

Rear Panel

Antenna Ports (Reverse TNC)

32
 Installation and Communication

Figure 16 FX9600 RFID Reader Antenna Connection

Rear Panel
Antenna Ports (Reverse TNC)

Communications and Power Connections

Use a standard Ethernet connection, PoE to connect the FX7500 and PoE or PoE + Ethernet for the FX9600
RFID reader, to a host or network.

Ethernet Connection
The reader communicates with the host using an Ethernet connection (10/100Base-T Ethernet cable). This
connection allows access to the Administrator Console, used to change reader settings and control the reader.
With a wired Ethernet connection (10/100Base-T cable), power the FX7500 or FX9600 RFID readers using either
the reader Zebra AC power supply, or by Power-Over-Ethernet through the Ethernet cable.

Ethernet: Power through AC Outlet

The FX7500 and FX9600 RFID readers communicates to the host through a 10/100Base-T Ethernet cable and
receives power through a Zebra AC power supply.

1. Route the Ethernet cable.

2. Route the power cable.
3. Terminate the Ethernet cable.
4. Connect the Ethernet cable to the LAN port on the FX7500 reader (see Figure 7 on page 22) or FX9600 reader
(see Figure 10 on page 25).
5. Connect the other end of the Ethernet cable to the host system LAN port.
6. Connect the Zebra AC power supply to a wall outlet.
7. Insert the power supply barrel connector into the FX7500/FX9600 reader power port and rotate clockwise a
1/4 turn for full locking engagement.
8. Verify that the unit booted properly and is operational. See System Start-up/Boot LED Sequence on page 38.
9. On a networked computer, open an Internet browser and connect to the reader.
See Connecting to the Reader on page 45.
10. Log in to the Administrator Console. See Administrator Console Login on page 47.

33
 Installation and Communication

Ethernet: Power through Standard PoE or PoE+

The PoE installation option allows the FX7500 and FX9600 RFID readers to communicate and receive power on
the same 10/100Base-T Ethernet cable.

1. Insert the PoE Ethernet connector on the RJ45 Ethernet cable into the reader 10/100BaseT Ethernet port. See
Figure 7 on page 22 or Figure 10 on page 25.
2. Connect the other end of the cable to an Ethernet network with PoE or PoE+ capability.
3. Verify that the reader booted properly and is operational.
See System Start-up/Boot LED Sequence on page 38.
4. On a networked computer, open an Internet browser and connect to the reader.
See Connecting to the Reader on page 45.
5. Log in to the Administrator Console. See Administrator Console Login on page 47.

CAUTION:Do not connect to PoE networks outside the building.

USB Connection
The USB client port supports (by default) a Network mode of operation. This enables a secondary network
interface as a virtual network adapter over USB. The Ethernet network interfaces co-exists with the USB virtual
network adapter. However, only one application connection (RFID connection or web console connection) is
allowed at any time. See Sample Implementation on page 36 for an example of how the standard network adapter
can be used in conjunction with the USB virtual network adapter. To use the USB virtual network adapter, install
the USB RNDIS Driver on the PC or follow the instructions to install the Microsoft RNDIS driver for Windows 7
below.

To connect the FX7500 or FX9600 to the host PC, insert a USB cable into the USB client port on the reader. For
the FX7500, see Figure 7 on page 22 or for the FX9600, see Figure 10 on page 25. Connect the other end of the
cable to a USB port on the host PC.

Zebra USB RNDIS Driver

To use the USB virtual network adapter, install the Zebra USB Remote Network Device (RNDIS) driver and enable
the driver on the FX7500 or FX9600. The Zebra RNDIS driver supports 32-bit version operating systems Windows
Vista, Windows 7, and Windows Server 2008. For Windows 7 32-bit and 64-bit systems, it is recommend to use
Microsoft RNDIS driver (see Microsoft RNDIS Driver for Windows 7 on page 35).

To install the RNDIS driver on the host.

1. Download the installer file Zebra RNDIS.msi from www.zebra.com/support to the host PC.
2. Select this file on the host PC to install the host side drivers for using the USB Remote Network Device
Interface on the FX7500 or FX9600.
3. Connect a USB cable between the host and the reader. The Welcome to the Found New Hardware Wizard
screen appears.
4. Select the No, not this time radio button and select Next.
5. Select the default option Install Software Automatically (Recommended).
6. In the Hardware Installation pop-up window, select Continue Anyway.
7. Select Finish to complete the installation. This assigns the host an auto-configured IP address. The network is
now ready to use and the reader’s IP address is fixed to 169.254.10.1.

34
 Installation and Communication

Microsoft RNDIS Driver for Windows 7

The following steps are the recommended procedure for Windows 7:

1. After connecting a USB cable between the PC and reader, the RNDIS driver automatically installs. If it does
not, right-click on Computer and select Manage. From System Tools, select Device Manager. Under Other
Devices, look for an entry for RNDIS with an exclamation icon indicating that the driver was not installed.

Figure 17 Computer Management Window

2. Right-click the icon and select Update Driver Software. Search for the device driver software by selecting
Browse my computer for driver software.
3. Select Let me pick from a list of device drivers on my computer.
4. Select Network adapters.

35
 Installation and Communication

Figure 18 Selecting Device Type

5. Select Microsoft Corporation from the manufacturer list.

6. Under Network Adapter, select Remote NDIS Compatible Device, and select Next.

After installation, the PC recognizes the reader as an RNDIS device. The PC obtains the IP address
169.254.10.102, and the reader is reachable at the IP address 169.254.10.1.

Sample Implementation
This implementation assumes that only one FX7500 or FX9600 reader is connected to a host PC via USB. This
feature does not function with multiple readers connected to the host. Zebra recommends disabling any other
network interface on the PC.

Use an application that uses RFID3 APIs such as Power Session, or use an LLRP application to connect to the
reader to read tags.

1. The primary RFID server connects to the FX7500 or FX9600 via the Ethernet interface.
2. The host PC connects to the FX7500 or FX9600 via the USB port. An application on the host PC monitors
communication between the primary RFID server and reader.
3. When the application on the host PC detects a communication failure between the primary RFID server and
the reader, it connects to and controls the reader using the USB virtual interface.
4. The FX7500 and FX9600 listens on the USB virtual interface on a fixed port (49152) as well as on the standard
LLRP port (5084). To enable this, select the Allow LLRP Connection Override check box in Configure LLRP
Settings console window.

36
 Installation and Communication

Figure 19 Communication / Configure LLRP Settings Window

Only one LLRP session can be active on the reader, either through the primary Ethernet interface or through the
virtual network over USB interface.

If a connection is active on one interface, a subsequent connection attempt on a second interface disconnects the
first. The second connection attempt always prevails and creates a new session.

GPIO Interface Connection

This pluggable terminal block allows connecting individual wires independently. A single connector accommodates
both inputs and outputs and a +24 VDC supply pin for external sensors and signaling devices.
See Table 21 on page 194 for pinout information. The GPIO interface is electrically isolated from the reader's
chassis ground, but its ground is common to the power return of the 24 VDC external supply when this is present.

GPIO signals allow some flexibility. Inputs are pulled up within the reader to +5 VDC and can be shorted to ground
to pull them low. They are broadly compatible with industrial sensors with NPN outputs and may also be connected
directly to relays or switch contacts. Alternatively, they can be driven by 5V logic. In the logic low state, the current
sourced from the reader is approximately 3 mA, so standard gates in most logic families can drive them directly.
Current flow in the logic high state is close to zero. Although the GPIO interface is fully operational in all power
modes, the +24 VDC supply is only available when an external supply is present.

NOTE: Do not connect the +24 VDC output directly to any of the general-purpose inputs. Although these can
withstand voltages above 5V, they are designed to operate optimally in the range of 0 to +5 VDC.

The general-purpose outputs are open-drain (NPN type) drivers, pulled up to 5V. Each output can withstand
voltages up to +30 VDC but should not be driven negative. Drive 24V relays, indicator lamps, etc., by wiring them
between the +24 VDC supply pin and the general-purpose output pins. Although each output can sink up to 1A, the
maximum current that can be drawn from the internal 24V supply is 1A, so use an external power supply if the
current requirements exceeds this. Note that the state of the general-purpose outputs is inverted, i.e., driving a
control pin high at the processor pulls the corresponding output low.

37
 Installation and Communication

LED Sequences
System Start-up/Boot LED Sequence
For LED locations, see Figure 9 on page 24 for the FX7500 and Figure 12 on page 27 for the FX9600. During
system start-up:

1. All LEDs turn on for a few seconds when power is applied to the reader.
2. All LEDs turn off and the PWR LED turns amber.
3. The PWR LED turns green to indicate successful RFID application initialization.
4. When the sequence completes, the green PWR LED remains on and all other LEDs are off.

PWR LED Sequence to Indicate IPv4 Status after Booting

After the RFID application initializes:

1. The PWR LED turns green for 5 seconds to indicate success (following the sequence from
System Start-up/Boot LED Sequence).
2. The reader checks the eth0 IPv4 address and indicates the IPv4 status using the LEDs:
• If the reader has a DHCP address, the PWR LED blinks green for 3 seconds.
• If the reader has static IP address, the PWR LED blinks amber 3 seconds.
• If the reader has an IP address from zero-configuration networking algorithm, the PWR LED blinks red for
3 seconds.
• If the reader doesn't have valid IP, the PWR LED blinks amber and green using a 90-second timeout to
indicate that it is waiting to acquire an IP address.
• If it obtains a valid IP within the timeout period, the reader indicates the status as described above.
• If the timeout expires before the reader obtains an IP, the PWR LED stops blinking.
3. The PWR LED again turns solid green.

Reset to Factory Defaults LED Sequence

Holding the reset button for 8 seconds resets the reader to the factory default configuration.

1. All LEDs turn on as usual when you press and hold the reset button.
2. The PWR LED blinks amber when the reset button is held.
3. The PWR LED blinks green fast 5 times to indicate that the reader detects a reset operation.
4. Release the reset button to reset the reader to factory defaults.

LED Sequence for Software Update Status

1. The PWR LED blinks red during the software update process.
2. After reset, the STAT LED blinks red if the radio module requires a firmware update.

38
 Installation and Communication

Reading Tags
After the reader powers up, test the reader. See System Start-up/Boot LED Sequence on page 38.
1. Enable tag reading using the web-based Administrator Console (see Read Tags on page 71) or control the
reader through a real-time application such as Power Session.
2. Present a tag so it is facing the antenna and slowly approach the antenna until the activity LED turns green,
indicating that the reader read the tag. See Figure 9 on page 24. The distance between the tag and the
antenna is the approximate read range.

NOTE: For optimal read results, do not hold the tag at an angle or wave the tag, as this can cause the read
distance to vary.

39
123RFID Desktop

Introduction
This chapter briefly describes 123RFID Desktop, the Zebra setup tool for fixed RFID readers.

For more information on 123RFID Desktop, go to www.zebra.com/123rfid.

Figure 20 123RFID Desktop Reader Screen

40
 123RFID

Features
123RFID Desktop is a software tool that simplifies reader setup.

Intuitive enough for first time users, 123RFID Desktop finds and connects to a reader with three simple clicks.

• Optimize the reader and its antenna settings using the easy-to-use configuration wizard. Settings are
saved in a configuration file or can be printed as a report.
• Analyze tag data using filters, such as EPC or RSSI, and check system performance by looking at charts.

Through 123RFID Desktop a user can accomplish the following.

• Find, connect reader, and start reading tags with three simple mouse clicks.
• Streamline the optimization process using the intuitive configuration wizard
• Save optimized settings to a file for later use.
• Load an already saved configuration file to the connected reader.
• Print a report of optimized settings.
• Analyze tag data using filtering tools
• Use the Asset Tag List file to filter by known tags.
• Filter by EPC or RSSI values.
• Check reader performance using charts
• Charts that represent tag read counts by antennas.
• Check RSSI signal on individual tags during an inventory.
• Program the GPIO accessory, for example to have a photo-eye sensor activate an inventory session.
• Built-in screen by screen help and How-To-Videos link to guide users through the tool.

For more information go to www.zebra.com/123rfid.

Communication with 123RFID Desktop

Connect a reader to a Windows PC over the local WiFi network or by USB cable.

123RFID Desktop Requirements

• Host computer running Windows 7 or Windows 10.
• A fixed reader.

41
Administrator Console

Introduction
This chapter describes the FX Series web-based Reader Administrator Console functions and procedures, and
detailed information about FX Connect. Access the Administrator Console using a web browser from a host
computer, and use this to manage and configure the readers. The Administrator Console main window and support
windows have four areas, each containing unique information about the reader.

NOTE: The screens and windows in this chapter may differ from actual screens and windows. The applications
described may not be available on (or applicable to) all devices. Procedures are not device-specific and
are intended to provide a functional overview.

By default, TCP Port # 8001 is used for communication between the web console and reader. Access to this port is
needed for the following web pages to function correctly.

• Advanced Antenna Configuration

• ReadTags
• Services
• Serial Port Communication
• FXConnect
• License Manager
• User Application
• Profiles
• File based firmware upload
• Syslog Export

Reader Administrator Console Selections

• Selection Menu - Selects the function for the primary information window.
• Primary Information Window - Provides the primary function information.
• USB Port Status - Provides details on the USB device connected to the USB host port. Hover the mouse
pointer over the blue link, available only when a device is detected.

42
 Administrator Console

• Help Information Window

• Provides detailed information to support the primary information window
• Includes a scroll bar to scroll through information
• Includes a toggle button to turn on/off the help information window

NOTE: It is recommended to clear the browser cache to ensure that the web pages pick up the latest frame
content and functionality.

Figure 21 Reader Administrator Console Main Menu

Selection
Menu Primary Information Window

Help
Information
Window
Toggle On/Off
Button

Help
Information
Window

Profiles
Use profiles for multiple reader deployments to save configuration time, as only a few APIs are needed to
completely configure a reader. See Reader Profiles on page 117.

Resetting the Reader

To reset the reader, press and hold the reset button for not more than 2 seconds. See Figure 8 on page 23 for the
reset button location. The reader reboots but retains the user ID and password.
See System Start-up/Boot LED Sequence on page 38.

NOTE: Hard rebooting the reader (disconnecting power) is not recommended as this discards all the tag events
and system log information.

43
 Administrator Console

Auto Discovery
The FX7500 and FX9600 readers supports WS-Discovery and Bonjour (zero-configuration networking methods) to
discovery readers in a subnet. The reader implements WS-Discovery conforming to RFID Reader Management
Profile (RDMP) specification in ISO 24791-3. RDMP is based on an extension for Device Profile for Web Services
(DPWS). The discovery mechanism is limited to subnets and does not work across subnets. The Power Session
application supports this feature, and it lists the discovered reader using reader host names. Because this feature
is based on WS-Discovery, the readers can also be discovered in Windows Vista and Windows 7 computers by
selecting the Network icon in a file browser.

Users of Linux, Windows and MAC OS PCs can discover FX Series readers in the subnet using Apple's Bonjour
protocol.

• Windows users must download Bonjour Print Services first from

https://support.apple.com/downloads/bonjour_for_windows.
• Linux users must install Avahi Service Discover from https://www.avahi.org.
• MAC OS has Bonjour support built in.

To discover FX Series readers, append .local to the reader host name (for example, FX75007F721E.local) on a
browser as shown in Figure 22.

Figure 22 Append .local to the reader host name on a web browser

In Windows and MAC OS, reader services can be discovered by using the command line as follows:

dns-sd -B _llrp._tcp
Browsing for _llrp._tcp
13:54:32.809 ...STARTING...
Timestamp A/R Flags if Domain Service Type Instance Name
13:54:33.055 Add 2 4 local. _llrp._tcp. FX75007F721E

The command for HTPP service discovery is dns-sd -B _http._tcp.

Linux users can use the following command to list the services:
avahi-browse -a -k -d local
+ eth0 IPv6 FX75007F721E _ssh._tcp local
+ eth0 IPv4 FX75007F721E _ssh._tcp local
+ eth0 IPv6 FX75007F721E _sftp-ssh._tcp local
+ eth0 IPv4 FX75007F721E _sftp-ssh._tcp local
+ eth0 IPv6 FX75007F721E _http._tcp local

44
 Administrator Console

Connecting to the Reader

NOTE: This section describes procedures in a Windows environment.

To use the Administrator Console to manage the reader, first power up the reader and connect it to an accessible
network. The green power LED indicates that the reader is ready. If the green power LED is not lit, reset the
reader. See Resetting the Reader on page 43.

Connect to the reader in one of two ways:

1. Connecting via Host Name on page 46.

2. Connecting via IP Address on page 46. (To obtain the IP address, see Obtaining the IP Address via Command
Prompt on page 45)

There are three ways to assign an IP address to the reader:

1. Using DHCP on the network.

2. Using Zero-Configuration Networking when DHCP Server is Not Available on page 46.
3. Statically assigning an IP. See Static IP Configuration on page 197.

Any method of assigning the IP supports connection using host name or IP address. Alternatively, connect the
reader directly to a local computer using zero-configuration networking. See Using Zero-Configuration Networking
when DHCP Server is Not Available on page 46.

NOTE: When using zero-configuration networking, the FX7500 and FX9600 readers cannot communicate
with computers on different subnets, or with computers that do not use automatic private IP addressing.

Obtaining the IP Address via Command Prompt

The Administrator Console provides the reader IP address. See Figure 21 on page 43. To obtain the reader IP
address without logging into the reader, open a command window and ping the reader host name.
See Connecting via Host Name on page 46.

Figure 23 IP Ping Window

45
 Administrator Console

Connecting via Host Name

To connect to the reader using the host name:

CAUTION:Reader host name is not guaranteed to work at all times. Its recommended use is only in networks where
the probability for IP collisions is low, such as a network in which a DNS server is configured to work
together with DHCP to register host names. Host name usage is not recommended in a network where
there is no strict control to prevent IP collisions, such as informal networks that use IP static configuration
without strict control.

1. Open a browser. Recommended browsers are IE11 (disabling Compatibility View is recommended),
Chrome v58, and FireFox v54.
2. Enter the host name provided on the reader label in the browser (for example: http://fx7500cd3b0d) and press
Enter. The Console Login window appears and the reader is ready.
3. Proceed to Administrator Console Login on page 47 to log in to the reader.

NOTE: Connect the reader to a network that supports host name registration and lookup to ensure the network can
access the reader using the host name. For instance, some networks can register host names through
DHCP. When first connecting to the reader, it is recommended to keep DHCP enabled in both the PC and
the reader, although it is not guaranteed that the host name will work all the time. Use the host name
printed on the reader label, or construct it using the reader MAC address on the reader back label. The host
name is a string with prefix FX7500 or FX9600, followed by the last three MAC address octets. For
example, for a MAC address of 00:15:70:CD:3B:0D, use the prefix FX7500, followed by the last three MAC
address octets (CD, 3B, and 0D), for the host name FX7500CD3B0D. Type http://FX7500CD3B0D in the
browser address bar to access the reader.

For a network that does not support host name registration and lookup, use the Power Session auto
discovery feature to obtain the IP address, and use the IP address connect method.

Connecting via IP Address

To use the IP address to connect to the reader:
1. Open a browser. The minimum browser recommends are IE11 (disabling Compatibility View is recommended),
Chrome v58, and FireFox v54.
2. Enter the IP address in the browser (e.g., http://157.235.88.99) and press Enter. The Console Login window
appears and the reader is ready.
3. Proceed to Administrator Console Login on page 47 to login to the reader.

Using Zero-Configuration Networking when DHCP Server is Not Available

If a DHCP server is not available, the FX7500 and FX9600 readers can use zero-configuration networking to
automatically provide a unique network IP address. The reader can then use TCP/IP to communicate with other
computers also using a zero-configuration networking-generated IP address.

NOTE: When using zero-configuration networking, the FX7500 and FX9600 reader cannot communicate with
computers on different subnets, or that do not use automatic private IP addressing. Automatic private IP
addressing is enabled by default.

The zero-configuration networking procedure is recommended when the reader is connected directly to a PC. It
reduces the overhead needed to configure the reader to a static IP address.
When zero-configuration networking executes after failing to detect a DHCP server, the reader automatically
assigns an IPv4 IP address to the Ethernet interface in the form 169.254.xxx.xxx. This IP address is predictable
because it uses the last 2 bytes of the MAC address, usually represented as HEX values, to complete the IPv4
address. These values are converted to decimal format (e.g., if the MAC address ends with 55:9A, the IPv4
address assigned by the zero-configuration algorithm is 169.254.85.148.
Windows-based computers support APIPA/zero-configuration networking by default when DHCP fails. To enable
APIPA for a Windows PC, visit http://support.microsoft.com/ and search for APIPA.

46
 Administrator Console

Administrator Console Login

NOTE: The recommended browsers are IE11 (disabling Compatibility View is recommended), Chrome v58,
and FireFox 54. These browsers were tested and validated to work properly. Other browsers may or
may not work properly.

First Time / Start-Up Login

When starting the reader for the first time, set the region of reader operation. Setting the reader to a different region
is illegal.

Logging In with Default User ID and Password

Upon connecting to the reader with a web browser, the User Login window appears.

Figure 24 User Login Window

1. Enter admin in the User Name: field and change in the Password: field and select Login.

For global reader configurations, the Region Configuration window appears. For US reader configurations, the
Administrator Console main window appears.

47
 Administrator Console

Setting the Region

For global reader configurations, set the region of operation.

IMPORTANT: Setting the unit to a different region is illegal.

NOTE: Region configuration is not available for readers configured to operate in the United States region (under
FCC rules). In this case, skip this step.

1. In the Configure Region Settings window, select the region from the drop-down menu.

Figure 25 Selecting the Region

2. Select the Communication Standard if applicable.

3. Select Frequency Hopping, if applicable.
4. Select the appropriate channel(s), if applicable.
5. Select the I understand check box.
6. Select Set Properties to complete the region selection. The Operation Successful window appears. Commit
step is no longer required to save configuration. See Commit/Discard Functionality Changes on page 121.

48
 Administrator Console

Reader Administrator Console

The Reader Administrator Console main window appears after successfully logging into the reader.

Figure 26 Reader Administrator Console Main Window

Administrator Console Option Selections

NOTE: When the reader firmware is updated, the outdated web page may be displayed due to cache. Refresh
the browser to update the browser web page.

Select an item from the selection menu on the left to select:

• Status - see Status on page 51

• Operation Statistics - see Reader Statistics on page 52
• Gen2 Optional - see Reader Gen2 Optional Operation Statistics on page 53
• NXP - see NXP Custom Command Operation Statistics on page 54
• Events - see Event Statistics on page 55
• Other Custom - see Other Custom Command Operation Statistics on page 56
• Configure Reader - see Configure Reader on page 57
• Read Points - see Read Points on page 58
• Advanced - see Read Points - Advanced on page 59
• Region - see Configure Region on page 60
• Certificates - see Certificates on page 61
• Read Tags - see Read Tags on page 71

49
 Administrator Console

• Communication - see Communication Settings on page 72

• LLRP - see Configure LLRP Settings on page 75
• SNMP - see SNMP Settings on page 76
• Wireless - see Wireless Settings on page 77
• Serial Port Configuration - see FX9600 Serial Port Configuration on page 78
• FX Connect - see FX Connect on page 82
• Services - see Network Services Settings on page 78
• Date/Time - see System Time Management on page 112
• IP Sec - see IPV6 IP Sec on page 113
• License Manager - see FX Series Licensing Management on page 97
• Change Password - see Change Password on page 114
• GPIO - see GPIO on page 115
• Applications - see Applications on page 116
• Profiles - see Reader Profiles on page 117
• Firmware - see Firmware Version/Update on page 120
• Update - see Firmware Update on page 121
• System Log - see System Log on page 125
• Configure - see Configure System Log on page 126
• Diagnostics - see Reader Diagnostics on page 127
• Shutdown - see Shutdown on page 128
• Logout - select Logout to immediately log out of the Administrator Console.

50
 Administrator Console

Status
Select Status on the selection menu to view the Reader Status window. This window displays information about the
reader and read points (antennas).

Figure 27 Reader Status Window

The Reader Status window provides consolidated reader status information:

• System Clock: The current system clock value, in the format of [Year] [Month] [Day] [Hour: Minute:
Second] [Time Difference with UTC]. Select the link to adjust the reader date and time settings.
• Up Time - Displays how long the reader has been running, in the format [Number of Days] [Number of
Hours] [Number of Minutes] [Number of Seconds].
• Temperature - Displays current temperature of the reader in Celsius and Fahrenheit.
• CPU Usage: Displays the CPU usage for the system and reader applications, including customer
applications.
• RAM Usage: Displays the total allocated RAM for the reader application and customer applications (if
any), the memory used, and the free memory.
• Flash Usage: Displays the flash memory usage by partition.
• Refresh Interval - Sets the refresh interval (in seconds) for the window. The status information refreshes
every N seconds (where N is the user configured value for the refresh interval). The minimum refresh
interval value is 10 seconds; the maximum allowed is 86,400 seconds.

51
 Administrator Console

Reader Statistics
Select Operation Statistics to view the Reader Operation Statistics window. This window provides options to view
the statistics of individual read points or combined statistics for all read points, including the success and failure
values of statistics for each read point. The statistic count is cumulative once the reader starts or the Reset
Statistics button is selected.

Figure 28 Reader Operation Statistics Window

• Choose ReadPoint - Select a specific read point or select All from the drop-down list to display the
statistics.
• IdentificationCount - Displays the number of successful (and failed) tag inventories.
• ReadCount - Displays the number of successful (and failed) tag reads.
• WriteCount - Displays the number of successful (and failed) tag writes.
• LockCount - Displays the number of successful (and failed) lock operations on tags.
• KillCount - Displays the number of successful (and failed) kill operations on tags.
• Reset Statistics - Resets all success and failure counts (including the optional Gen2 and Custom statistics)
for all read points.
• Refresh Interval - Sets the refresh interval (in seconds) for this window. The statistics information for the
chosen read point is refreshed every N seconds (where N is the set refresh interval). The minimum value is
10 seconds and the maximum value allowed is 86,400 seconds. Input a new value and select Change to
set a new interval.

52
 Administrator Console

Reader Gen2 Optional Operation Statistics

Select Gen2 Optional to view the Reader Gen2 Operation Statistics window. This window provides options to view
the statistics of read points for the optional Gen2 operations the reader supports.

Figure 29 Reader Gen2 Operation Statistics Window

• Choose ReadPoint - Select a specific read point from the drop-down list to display the statistics, or select
All to view the combined statistics for all read points.
• BlockErase - Displays the number of successful (and failed) block erase operations.
• BlockWrite - Displays the number of successful (and failed) block write operations.
• BlockPermalock - Displays the number of successful (and failed) block permalock operations.
• Reset Statistics - Resets all success and failure counts (including the standard Gen2 and custom statistics)
for all read points.
• Refresh Interval - Sets the refresh interval (in seconds) for this window. The statistics information for the
chosen read point is refreshed every N seconds (where N is the set refresh interval). The minimum value is
10 seconds and the maximum value allowed is 86,400 seconds. Input a new value and select Change to
set a new interval.

53
 Administrator Console

NXP Custom Command Operation Statistics

Select NXP to view the NXP Custom Command Operation Statistics window. This window provides options to view
the statistics of read points for the custom NXP operations the reader supports.

Figure 30 NXP Custom Command Operation Statistics Window

• Choose ReadPoint - Select a specific read point from the drop-down list to display the statistics, or select
All to view the combined statistics for all read points.
• ChangeEAS - Displays the number of successful (and failed) change EAS operations performed on NXP
tags.
• EASAlarm - Displays the number of successful (and failed) EAS alarms received from tags.
• SetQuiet - Displays the number of successful (and failed) set quiet operations performed on NXP tags.
• ResetQuiet - Displays the number of successful (and failed) reset quiet operations performed on NXP tags.
• ChangeConfig - Displays the number of successful (and failed) change configuration operations
performed on NXP tags.
• Reset Statistics - Resets all the success and failure counts (including the standard and optional Gen2
operation statistics) for all the read points.
• Refresh Interval - Sets the refresh interval (in seconds) for this window. The statistics information for the
chosen read point is refreshed every N seconds (where N is the set refresh interval). The minimum value is
10 seconds and the maximum value allowed is 86,400 seconds. Input a new value and select Change to
set a new interval.

54
 Administrator Console

Event Statistics
Select Events to view the Events Statistics window. This window provides options to view the statistics of events.

Figure 31 Event Statistics Window

• AmbientTemperatureHighAlarm - Displays the number of events raised for ambient temperature high
alarm.
• AmbientTemperatureCriticalAlarm - Displays the number of events raised for ambient temperature
critical alarm.
• PATemperatureHighAlarm - Displays the number of events raised for PA temperature high alarm.
• PATemperatureCriticalAlarm - Displays the number of events raised for PA temperature critical alarm.
• ForwardPowerHighAlarm - Displays the number of events raised for forward power high alarm.
• ForwardPowerLowAlarm - Displays the number of events raised for forward power low alarm.
• ReversePowerHighAlarm - Displays the number of events raised for reverse power high alarm.
• EchoThresholdAlarm - Displays the number of events raised for echo threshold alarm.
• DatabaseWarning - Displays the number of warning events raised whenever the radio tag list buffer is
almost full.
• DatabaseError - Displays the number of events raised when the radio tag list buffer is full.
• GPIInformation - Displays the number of events raised for radio GPI events.
• Reset Statistics - Resets all the success and failure counts for all the read points.
• Refresh Interval - Sets the refresh interval (in seconds) for this window. The statistics information for the
chosen read point is refreshed every N seconds (where N is the set refresh interval). The minimum value is
10 seconds and the maximum value allowed is 86,400 seconds. Input a new value and select Change to
set a new interval.

55
 Administrator Console

Other Custom Command Operation Statistics

Select Other Custom to view the Other Custom Command Operation Statistics window. This window provides
options to view the statistics of read points for the custom operations the reader supports.

Figure 32 NXP Custom Command Operation Statistics Window

• Choose ReadPoint - Select a specific read point from the drop-down list to display the statistics, or select
All to view the combined statistics for all read points.
• QTOperation - Displays the number of successful (and failed) QT operations performed on Monza4 QT
tags.
• Reset Statistics - Resets all the success and failure counts for all the read points.
• Refresh Interval - Sets the refresh interval (in seconds) for this window. The statistics information for the
chosen read point is refreshed every N seconds (where N is the set refresh interval). The minimum value is
10 seconds and the maximum value allowed is 86,400 seconds. Input a new value and select Change to
set a new interval.

56
 Administrator Console

Configure Reader
Use the Configure Reader menus to access the following functions.

Reader Parameters
Select Configure Reader in the selection menu to configure reader settings using this window.

Figure 33 Reader Parameters

• Name - Sets the user-configured reader name. Accepts up to 32 alphanumeric characters.

• Description - Sets a user-configured reader description. Accepts up to 32 alphanumeric characters.
• Location - Enter information on the reader location. Accepts up to 32 alphanumeric characters.
• Contact - Enter the name of the reader manager contact. Accepts up to 32 alphanumeric characters.
• GPI Debounce Time - Delays input events up to this time, and delivers these events only if the PIN states
remains on the same level.
• Operation Status - Displays the current operation status of the reader (Enabled, Disabled, or Unknown).
• Antenna Check - Controls the antenna sensing feature on the reader. Disabled indicates that the reader
does not attempt to check if an antenna is connected on the ports. When Enabled, the reader monitors the
presence of an antenna on the port and only transmits RF if an antenna is connected.
• Idle Mode Timeout (secs) - Set this turn off the radio and the antenna-check feature when the reader is
idle for the specified time interval. Set 0 to disable this feature. The default value is zero.

NOTE: Set a value (non zero) to enable this feature for the following purposes:
1. To save the battery capacity when the reader is charged by a power outlet in a vehicle.
2. To allow the overall reader temperature to be reduced. When the radio function is turned off, the
overall reader temperature can be reduced.

• Radio Power State - Displays the current state (On or Off) of the radio. The radio can be turned off if the
Idle Mode Timeout is set to a non-zero value and the radio is not performing RF operations for a time
period greater than the time specified by this timeout. The radio turns on automatically when RF operation
starts.

57
 Administrator Console

• Power Negotiation - When the Power Negotiation option is set as enabled, and committed, the FX7500
and FX9600 readers start power negotiation. Power negotiation occurs only if the reader is powered from
a switch that is capable of LLDP based power negotiation. If the reader is powered from a source that does
not support LLDP, power negotiation can still be enabled and disabled, but the reader does not carry out
any power negotiation.
The moment the power source is switched to an LLDP enabled switch, power negotiation occurs at startup
if it was enabled from the UI previously.
After power negotiation is enabled, and committed, it takes few seconds for the negotiation to complete
and power to reach the PoE+ level. This is the time taken for LLDP packet exchange between the reader
and the switch for power negotiation.
• Allow Guest User - This option controls if a guest user can access the reader using the web console. The
default setting is Enabled. When this option is enabled, a guest user can log in and view the reader
settings. Disabling this option prevents a guest user to access the reader's web console.
These settings only affect the display.

Read Points
Select Configure Reader > Read points in the selection menu to configure the read point settings and view the
current read points state.

Figure 34 Configure Read Points

Antenna Status
• Status buttons - indicate the status of the reader read points:
• Green: Connected - Read point is enabled and an antenna is connected to the port.
• Red: Not connected - Read point is enabled, but no antenna is connected to the port.
• Yellow: User disabled - The user disabled the read point.

Select a read point’s status button to view and/or change the selected antenna configuration.

• Refresh Interval - Sets the refresh interval (in seconds) to update the read point status. The minimum
value is 10 seconds and the maximum value allowed is 86,400 seconds. Input a new value and select
Change to set a new interval.

58
 Administrator Console

• Maintenance mode - Places the reader in maintenance mode which intermittently drives PWR, ACT, and
STAT LEDs to easily locate the reader. Also enables quick reporting of antenna status by setting the
refresh interval to 2 seconds. Note that you can not modify the refresh interval in this mode.

Antenna Configuration
• Choose Read Point - Select a read point to display the configuration.
• Description - Enter a read point description of up to 32 alphanumeric characters.
• User Configuration - Enable or disable the read point. Disabling a read point blocks RF operation using the
port/antenna.
• Air Protocol - Displays the air protocols the read point supports. The reader currently supports only EPC
Class1 GEN2 air protocol.
• Cable loss (dB/100 ft) - Specifies the cable loss in terms of dB per 100 feet length for the antenna cable
that is used to connect this read point port to the antenna. Refer to the specification of the antenna cable
for this information. The default value is 10. Setting this and the cable length to non-zero values allows the
compensating for the RF signal loss in the cable due to attenuation by specifying an appropriate increase
in the transmit power for this read point. The reader uses this and the cable length value to internally
calculate the cable loss. The calculated cable loss is internally added to the power level configured on the
read point.
• Cable length (ft) - Sets the cable length in feet of the physical cable that connects the read point port to
the antenna. The default cable length is 10 feet.
• Set Properties - Select Set Properties to apply the changes.

Read Points - Advanced

Select Configure Reader > Read points > Advanced in the selection menu to view the Advanced Antenna
Configuration window. Use this window to modify the transmission power and frequency configuration elements of
the antenna.

Figure 35 Advanced Antenna Configuration

NOTE: This page is not supported when LLRP is configured in secure mode.

59
 Administrator Console

Retrieve the current configuration of an antenna before applying the advanced configuration settings.

• Get Configuration - Select an antenna to get the current configuration for that antenna. After login, you
must get the antenna configuration for an antenna before settings can be applied. The antenna
configuration page retains the retrieved settings after login if you do not refresh the page using browser
refresh.
• Transmit Power - Displays the current transmit power setting after selecting Get Configuration, and
allows changing the transmit power for that antenna. This transmit power level does not include cable loss
compensation.
• Save Settings Permanently - Check this to save the settings permanently and persist them across
reboots.
• Apply - Select to apply the settings for the selected antennas. This applies the selected transmit power
and frequency/hop table configuration to all selected antennas. The settings are applied immediately and
have immediate effect on Inventory/Access operations. Also check Save Setting Permanently to persist
these settings across reboots unless modified by another client.

Configure Region
Different countries have different RF regulatory requirements. To assure regulatory compliance, select Region to
set the reader for specific regulatory requirements in the country of reader operation using the Configure Region
Settings window.

NOTE: Region configuration is not required for readers configured to operate in the United States region (under
FCC rules).

Because of the differing frequency requirements, there are several versions of the hardware. The list of choices on
this page is limited by the software to those selections compatible with the hardware in use. Note that if only one
option is compatible with the hardware, that option is selected automatically.

Figure 36 Configure Region Settings Window

• Region of Operation - Select the region for the country of operation from the drop-down list. This list
includes regions which have regulatory approval to use with the current board.
• Communication Standard - Select the communication standard from the list of standards that the chosen
region supports. If a region supports only one standard, it is automatically selected.

60
 Administrator Console

• Frequency Hopping - Check to select frequency hopping. This option appears only if the chosen region of
operation supports this.
• Selected Channels - Select a subset of channels on which to operate (from the list of supported channels).
This option appears only if the chosen region of operation supports this.
• Please confirm - Check the I understand check box to confirm your understanding that the choices are in
compliance with local regulatory requirements.
• Set Properties - Select to apply the changes.

Certificates
You can protect network services on the reader using SSL/TLS to secure the communication channel against
eavesdropping or tampering, and optionally authenticate peer networked nodes involved in the communication.
SSL/TLS protocol uses Public Key Infrastructure digital certificates. The following services on the reader support
SSL/TLS:

• Web Administrator Console service (HTTPS). See Network Services Settings on page 78.
• File Transfer Service (FTPS - explicit SSL/TLS over FTP). See Network Services Settings on page 78.
• Shell Service (SSH - by default always in secure mode).
• Secure LLRP Service (refer to the EPC Global LLRP Standard, Security in TCP Transport). See the
Enable Secure Mode option in Configure LLRP Settings on page 75.

NOTE: The supported version of SSL/TLS varies between services. Different services support SSL v3 and TLS
1.0 and above.

NOTE: The Validate Peer option in Secure LLRP Service configuration enables authentication of reader
and/or clients using digital certificates. You must import a custom certificate (instead of the default
self-signed certificate) to the reader to enable this option. See Configure LLRP Settings on page 75 for
details. Services other than Secure LLRP rely on password-based authentication.

NOTE: The SNMP service on the reader supports SNMP v2c and does not support security.

61
 Administrator Console

Certificate Configuration
The Certificate Configuration page is available under the Configure Reader menu when the Administrator
Console is in HTTPS mode only. To enable HTTPS mode, select Communication > Services, and on the
Reader Communication Parameters page select HTTPS from the Web Server drop-down menu.

Figure 37 Setting HTTPS Mode

NOTE: The user cannot change Web Server mode if Inventory is in progress.

Select Configure Reader > Certificates. The Certificate Configuration page provides the current certificate
details and an option to update to a custom certificate.

Figure 38 Certificate Configuration Page

62
 Administrator Console

The Current certificate details section displays the installed certificate's details such as issuer, serial number,
and validity information.

By default, the reader uses self-signed certificates (characterized by Subject name and Issuer in Current
certificate details) for all secure interfaces using SSL/TLS.

Self-signed certificates have restrictions, such as by default clients do not trust them because they are not issued
by a trusted Certification Authority (CA). Custom trusted certificates may be beneficial in certain use cases, for
example:

• LLRP by default does not authenticate the client or reader. Security extensions to the standard allow client
or reader authentication using digital certificates. The entities involved validate digital certificates by
confirming the certificates were issued from a trusted source. Therefore a custom certificate is required to
authenticate the client or reader. See the Validate Peer option in Configure LLRP Settings on page 75.
• By default web browsers display a warning or prevent connection to the Administrator Console when the
console service is in HTTPS mode. See Network Services Settings on page 78. This can be an
inconvenience for certain environments, particularly when browsers are configured to reject connection to
servers that do not publish a trusted certificate.

FX Series readers do not allow automatic certificate request and updating. The reader certificate must be issued
externally and imported to the reader.

The Update Certificate section allows importing a custom certificate to the reader. You must use one of the digital
certificate generation mechanisms to create the certificate (see Creating a Custom Certificate). The reader only
supports certificates in PKCS#12 format (typically with a .pfx extension). This format uses a signed certificate, with
a private key (optionally encrypted) bundled into a single file. The certificate must be hosted on a secure FTP
server (running in Explicit SSL/TLS over FTP mode). The following options are used to perform the update:

• FTPS URL: Full path to server, including ftps:// prefix, where the .pfx file is hosted.
• FTPS User ID: User login ID to secure FTP server.
• FTPS Password: Password for specified user.
• PFX Password: Password for encrypted key in the .pfx file, if the key is encrypted.

NOTE: The FX7500 and FX9600 support only a single digital certificate. If a custom certificate is installed, the
issuer of the certificate is trusted by the reader, so any client attempting to connect to the reader over
secure LLRP mode is trusted if the certificate issued to the client is from the same issuer.

NOTE: The FX7500 and FX9600 support only supports certificates using the RSA public key algorithm. When
obtaining a certificate issued from the reader or clients, ensure that RSA is the selected key algorithm.

NOTE: A manual reboot of the reader is required after updating the certificate for the services using SSL/TLS.

Creating a Custom Certificate

FX Series readers require that custom certificates are created externally and imported to the reader using a secure
FTP, as described previously. The certificate and key used by the reader must be in PKCS#12 format (a single .pfx
file), while the certificate and keys used by clients interfacing to the LLRP service on the reader must be in PEM
format. If you obtain a certificate in a different format it must be converted to the appropriate format using a tools
such as OpenSSL (www.openssl.org).

Digital certificates are typically requested and issued from a certification authority hosted internally in an enterprise
environment or by a trusted third party certification authority. The process of requesting and creating certificates
varies between platforms. For example, a Windows Server environment typically uses Microsoft Certification
Server to process certificate requests and issue certificates. Unix-based systems typically use OpenSSL. This

63
 Administrator Console

guide can not document all options. The following example illustrates one method of creating custom
certificates.

Custom Certificate Creation Example

The following example illustrates how to set up an OpenSSL-based certification authority to issue reader and
client certificates. These scripts can be executed in a Unix operating system or on Windows with a Unix shell
scripting environment such as Cygwin:

Create the following text files in a suitable folder on the host machine:

• caconfig.cnf - OpenSSL configuration file for Certification Authority certificate creation and signing
• samplereader.cnf - OpenSSL configuration file for reader certificate creation
• samplehost.cnf - OpenSSL configuration file for reader certificate creation
• InitRootCA.sh - Script for initializing a new Root Certification Authority
• CreateReaderCert.sh - Script for creating reader certificate
• CreateClientCert.sh - Script for creating client certificate

File contents are as follows. Refer to OpenSSL (www.openssl.org) documentation for details on configuration
options. Edit configuration options to accommodate the deployment environment.

caconfig.cnf

# Sample caconfig.cnf file for XYZ certification authority

# Default configuration to use when one is not provided on the command line.

[ ca ]

default_ca = local_ca

# Default location of directories and files needed to generate certificates.

[ local_ca ]

dir =.

certificate = $dir/cacert.pem

database = $dir/index.txt

new_certs_dir = $dir/signedcerts

private_key = $dir/private/cakey.pem

serial = $dir/serial

64
 Administrator Console

# Default expiration and encryption policies for certificates.

(continued on next page)

default_crl_days = 365

default_days = 1825

default_md = sha1

policy = local_ca_policy

# Default policy to use when generating server certificates. The following

# fields must be defined in the server certificate.

[ local_ca_policy ]

commonName = supplied

stateOrProvinceName = supplied

countryName = supplied

emailAddress = supplied

organizationName = supplied

organizationalUnitName = supplied

# The default root certificate generation policy.

[ req ]

default_bits = 2048

default_keyfile = ./private/cakey.pem

default_md = sha1

prompt = no

distinguished_name = root_ca_distinguished_name

65
 Administrator Console

x509_extensions = v3_ca

(continued on next page)

# Root Certificate Authority distinguished name. Change these fields to match

# your local environment!

[ root_ca_distinguished_name ]

commonName = XYZ Root Certification Authority

stateOrProvinceName = IL

countryName = US

emailAddress = [email protected]

organizationName = XYZ

organizationalUnitName = ABC Dept

[ root_ca_extensions ]

basicConstraints = CA:true

[ v3_req ]

basicConstraints = CA:FALSE

keyUsage = nonRepudiation, digitalSignature, keyEncipherment

[ v3_ca ]

basicConstraints = critical, CA:true, pathlen:0

nsCertType = sslCA

keyUsage = cRLSign, keyCertSign

extendedKeyUsage = serverAuth, clientAuth

nsComment = "CA Certificate"

[ ssl_client_server ]

basicConstraints = CA:FALSE

nsCertType = server, client

keyUsage = digitalSignature, keyEncipherment

66
 Administrator Console

extendedKeyUsage = serverAuth, clientAuth, nsSGC, msSGC

nsComment = "SSL/TLS Certificate"

samplereader.cnf

# samplehost.cnf - customized for a reader. Edit last 4 octets after FX7500 to suit hostname of reader to which
certificate is issued

[ req ]

prompt = no

distinguished_name = FX7500123456.ds

[ FX75000657E5.ds ]

commonName = FX7500123456

stateOrProvinceName = IL

countryName = US

emailAddress = root@FX7500123456

organizationName = Company Name

organizationalUnitName = Department Name

samplehost.cnf

# samplehost.cnf - customized for a client that will connect to the reader's LLRP port. Edit hostname to match
FQDN of client.

[ req ]

prompt = no

distinguished_name = clienthostname.mycompany.com

[clienthostname.mycompany.com ]

commonName = CLIENTHOSTNAME

stateOrProvinceName = IL

countryName = US

emailAddress = [email protected]

67
 Administrator Console

organizationName = Company Name

organizationalUnitName = Department Name

InitRootCA.sh

#Initialize from current directory

#Enable definition for environment variable OPENSSL_FIPS to execute in FIPS mode on system with FIPS
compliant OpenSSL build

#export OPENSSL_FIPS=1

export WORKSPACE_DIR=$( cd "$( dirname "$0" )" && pwd )

#Make sure CA key password is unique and secret

export CA_KEY_PASSWORD=CA-abcd12345

#Cleanup Certificate Store folder

rm -rf $WORKSPACE_DIR/CA-Certs

#Change directory to CA-Certs and create folders for certificate and key storage in myCA

mkdir -p $WORKSPACE_DIR/CA-Certs

cd $WORKSPACE_DIR/CA-Certs

mkdir -p myCA/signedcerts

mkdir -p myCA/private

cd myCA

#Initialize serial number

echo '01' > serial && touch index.txt

#Create CA private key and certificate

export OPENSSL_CONF=$WORKSPACE_DIR/caconfig.cnf

echo 'Creating CA key and certificate....'

openssl req -x509 -newkey rsa:2048 -out cacert.pem -outform PEM -days 1825 -passout
pass:$CA_KEY_PASSWORD

openssl x509 -in cacert.pem -out cacert.crt

echo 'Test Certificate Authority Initialized. CA certificate saved in cacert.crt. Install it to trusted CA certificate
store'

68
 Administrator Console

CreateReaderCert.sh

#Initialize from current directory

#Enable definition for environment variable OPENSSL_FIPS to execute in FIPS mode on system with FIPS
compliant OpenSSL build

#export OPENSSL_FIPS=1

export WORKSPACE_DIR=$( cd "$( dirname "$0" )" && pwd )

#Make sure passwords are unique and secret

export CA_KEY_PASSWORD=CA-abcd12345

export GENERATED_CERT_KEY_PASSWORD=abcd12345

cd $WORKSPACE_DIR/CA-Certs/myCA

#Create sample reader key and certificate

export OPENSSL_CONF=$WORKSPACE_DIR/samplereader.cnf

echo 'Creating reader key and certificate with its signing request ....'

openssl req -newkey rsa:1024 -keyout reader_key.pem -keyform PEM -out tempreq.pem -outform PEM
-passout pass:$GENERATED_CERT_KEY_PASSWORD

#CA now signs client certificate by processing its certificate signing request

echo 'CA Signing reader certificate....'

export OPENSSL_CONF=$WORKSPACE_DIR/caconfig.cnf

openssl ca -extensions ssl_client_server -in tempreq.pem -out reader_crt.pem -passin

pass:$CA_KEY_PASSWORD -batch

rm -f tempreq.pem

echo 'Exporting reader certificate and key to PKCS#12 format....'

openssl pkcs12 -export -out reader.pfx -inkey reader_key.pem -in reader_crt.pem -certfile cacert.crt -passin
pass:$GENERATED_CERT_KEY_PASSWORD -passout pass:$GENERATED_CERT_KEY_PASSWORD

echo 'Reader certificate, key and export to PKCS#12 format (.pfx) completed.'

echo 'Note: PFX protected with password: '$GENERATED_CERT_KEY_PASSWORD

69
 Administrator Console

CreateClientCert.sh

#Initialize from current directory

#Enable definition for environment variable OPENSSL_FIPS to execute in FIPS mode on system with FIPS
compliant OpenSSL build
#export OPENSSL_FIPS=1
export WORKSPACE_DIR=$( cd "$( dirname "$0" )" && pwd )
#Make sure passwords are unique and secret
export CA_KEY_PASSWORD=CA-abcd12345
export GENERATED_CERT_KEY_PASSWORD=abcd12345
cd $WORKSPACE_DIR/CA-Certs/myCA
echo 'Current dir:'$( cd "$( dirname "$0" )" && pwd )
#Create sample client key and certificate
export OPENSSL_CONF=$WORKSPACE_DIR/samplehost.cnf
echo 'Creating client key and certificate with its signing request ....'
openssl req -newkey rsa:1024 -keyout client_key.pem -keyform PEM -out tempreq.pem -outform PEM
-passout pass:$GENERATED_CERT_KEY_PASSWORD
#CA now signs client certificate by processing its certificate sigining request
echo 'CA Signing client certificate....'
export OPENSSL_CONF=$WORKSPACE_DIR/caconfig.cnf
openssl ca -in tempreq.pem -out client_crt.pem -extensions ssl_client_server -passin
pass:$CA_KEY_PASSWORD -batch
rm -f tempreq.pem
echo 'Client key, certificate creation and signing completed. Use files client_key.pem and client_crt.pem'

Script Usage
The following section illustrates how to use the previous scripts on the host machine.

Certification Authority Initialization

• Edit caconfig.cnf to change the configuration for CA if necessary.
• Execute CA initialization command sequence by invoking ./InitRootCA.sh.

Issue Reader certificate:

• Edit samplereader.cnf to update any configuration such as hostname if necessary.
• Execute CreateReaderCert.sh by invoking ./CreateReaderCert.sh.

Issue Client certificate:

• Certificate and key issued using this method can be directly used with the LLRP client.
• Edit samplehost.cnf to update any configuration such as hostname for the client, if necessary.
• Execute CreateClientCert.sh by invoking ./CreateClientCert.sh.

70
 Administrator Console

Read Tags
Select Read Tags to view the Reader Operation window. Use this window to perform inventory on the connected
antennas and view the list of inventoried tags.

NOTE: This page is not supported when LLRP is configured in secure mode.

Figure 39 Read Tags Window

• Start - Select to starts inventory operation on the connected antennas. If the there are no connected
antennas, no tags in the field of view, or all the antennas are user-disabled, the Read Tags window
indicates that inventory successfully started but no tags display.
• Stop - Stops the ongoing inventory operation.
• Clear - Clears the current tag list.

The list of tags appears in a table with the following attributes for each tag:

• EPC Id - Unique tag EPC ID.

• Tag Seen Count - Number of times the tag is identified on the specific antenna.
• RSSI - Received Signal Strength Indication.
• Antenna Id - Antenna ID on which the tag is seen.
• Seen Time: UTC time (in microseconds) showing when the tag was first seen.

71
 Administrator Console

Communication Settings
Select Communication to view the Configure Network Settings window. This window has tabs for Ethernet, Wi-Fi,
and Bluetooth. Each tab has options for IPV4 and IPV6.

Configure Network Settings - Ethernet Tab

Figure 40 Configure Network Settings - Ethernet Tab

IPV4
• Obtain IPV4 Address via DHCP - The reader supports both automatic TCP/IP configuration via DHCP
and manual configuration. The DHCP button turns DHCP on and off.

If DHCP is turned on, this window displays actual current values of the reader's IP address, subnet mask,
default gateway, and DNS server. Because these are obtained from the DHCP server, they cannot be
changed manually.

If DHCP is turned off, you can set the following values for these fields.
• Current IPV4 Address - IP address (in dotted notation) at which the reader is assigned.
• IPV4 Subnet Mask - Subnet mask (in dotted notation) appropriate for the network in which the reader
resides.
• IPV4 Default Gateway - Default gateway (in dotted notation) appropriate for the network in which the
reader resides.
• IPV4 DNS Server - DNS server (in dotted notation) appropriate for the network in which the reader
resides.
• MAC Address - The MAC address of the reader.

NOTE: You must select Set Properties to update the network configuration. If saving changes is not
successful, the system indicates the problem and allows correcting it by repeating the operation. DHCP
and IP address updates do apply until the reader is rebooted.

72
 Administrator Console

IPV6
• Obtain IPV6 Address via DHCP - The reader supports both automatic TCP/IPV6 configuration via DHCP
and manual configuration. The DHCP button turns DHCP on and off.

If DHCP is turned on, this window displays actual current values of the reader's IPV6 address, prefix
length, default gateway, and DNS server. Because these are obtained from the DHCP server, they cannot
be changed manually.

If DHCP is turned off, you can set the following values for these fields.
• Current IPV6 Address - IP address (in dotted notation) at which the reader is assigned.
• Prefix Length - Prefix length appropriate for the network in which the reader resides.
• IPV6 Default Gateway - Default gateway (in dotted notation) appropriate for the network in which the
reader resides.
• IPV6 DNS Server - DNS server (in dotted notation) appropriate for the network in which the reader
resides.
• MAC Address - The MAC address of the reader.

NOTE: You must select Set Properties to update the network configuration. If saving changes is not
successful, the system indicates the problem and allows correcting it by repeating the operation. DHCP
and IP address updates do apply until the reader is rebooted.

NOTE: Also enable automatic configuration for IPV6 through RA packets configuration. To enable or disable
RA packet configuration go to the Services window (see Services).

Configure Network Settings - Wi-Fi Tab

Figure 41 Configure Network Settings - Wi-Fi Tab

IPV4
The reader supports only DHCP-based configuration for Wi-Fi. This window displays the current values of the
reader's IP address, subnet mask, default gateway, and DNS server. Since these are obtained from the DHCP
server, they cannot be changed manually.

73
 Administrator Console

IPV6
The reader supports only DHCP based configuration for Wi-Fi. This window displays the current values of the
reader's IPV6 address, prefix length, default gateway, and DNS server. Since these are obtained from the DHCP
server, they cannot be changed manually.

Configure Network Settings - Bluetooth Tab

Figure 42 Configure Network Settings - Bluetooth Tab

The reader supports only automatic IP configuration of the Bluetooth interface.

If a Bluetooth client is connected to the reader, this window displays the current values of the reader's IPV4
address, Subnet mask, IPV6 address, and prefix length in the appropriate tabs. Because these are automatically
configured for a reader, they cannot be changed manually.

If a Bluetooth USB dongle is connected to the reader, you can set the following Bluetooth properties in this window:

• Discoverable - Select whether the reader is seen by other Bluetooth-enabled devices on discovery.
• Pairable - Select whether any Bluetooth-enabled device can pair with reader.
• Use Passkey - Enable this option to mandate the connecting device to supply a pre-determined passkey
to use for authentication while pairing.
• Passkey - The passkey to use for authentication.
• DHCP start address - The starting address of the DHCP IP range out of which an IP is assigned to the
connecting device.
• DHCP end address - The end address of the DHCP IP range out of which an IP is assigned to the
connecting device.

NOTE: The DHCP IP range specified using the DHCP start address and DHCP end address options also
determine the IP of the Bluetooth interface of the reader. The first two octets of the IP address of the
reader Bluetooth interface are taken from the IP range specified and the last two octets use the reader
BD address.

74
 Administrator Console

Configure LLRP Settings

Select LLRP to view and set the LLRP settings. By default, LLRP activates in server mode, where LLRP clients can
connect to the reader using the port number specified in the Client port field. You can also configure the reader in
LLRP client mode. In this case, configure the LLRP server address in this web page as well. LLRP cannot be
disabled since it is the primary native protocol for RFID for the reader.

Figure 43 Configure LLRP Settings Window

This window offers the following fields:

• LLRP Status - Displays the current state of the LLRP server on the reader. Indicates whether LLRP is
running.
• Operation Mode - Sets the LLPR mode in the reader to either Server or Client.

LLRP configuration options when the reader is in Server mode:

• Client IP - Displays the currently connected LLRP client's IP address. If there is no LLRP client
connection, this is 0.0.0.0.
• Client Port - Configures the LLRP listening port on the reader. The default is 5084.
• Connect Status - Indicates whether the client is connected. This button is grayed out if there is no client
connected. If an LLRP client is connected to the reader, this button is enabled; select this button to
disconnect the client.

LLRP configuration options when the reader is in Client mode:

• Server IP - Configures the IP address of the server to connect to.

• Client Port - Configures the LLRP host port to connect to. The default is 5084.
• Allow LLRP Connection Override (From USB IF) - This allows the reader to listen on an alternate port
(49152) on the virtual network (over USB) interface. When an LLRP client is connected over the primary
interface (Ethernet and primary LLRP port), a different client can override this connection on the alternate
interface (Virtual Network and alternate port 49152) if this option is enabled. This also permits overriding a
connection from a primary interface over an existing connection on an alternate interface. This option is off
by default. Changing this option restarts the LLRP service on the reader.

75
 Administrator Console

• Connect Status - Indicates whether the reader is connected to the LLRP host. This button toggles
between ConnectLLRP and DisconnectLLRP. Selecting ConnectLLRP initiates an LLRP connection to
the host server.

LLRP configuration options when the reader is in Secure mode:

• Security Mode - Specifies whether LLRP communicates in secure or unsecured mode. Checking Enable
Secure Mode switches the LLRP port to 5085 by default. You can override the port value. LLRP in secure
mode supports ciphers that are compliant with TLS1.2.
• Validate Peer - Specifies whether the validation of peer against the same certification authority issued
certificate is required. If you select the validate peer option, the secure LLRP service on the reader allows
connection for valid secure peer entities only if the certificate of the peer is issued from the same
certification authority that issued the certificate for the reader. By default the reader uses self-signed
certificates, and peer certificate based validation is disabled.

SNMP Settings
Select SNMP to view the Configure SNMP Settings window.

Figure 44 Configure SNMP Settings Window

Use this window to configure the SNMP host settings to allow sending network status events and receiving network
status event notifications:

• Send SNMP Trap To - Configures the host IP address to which the SNMP trap is sent. Leave this blank to
send no traps to any host.
• SNMP Community String - SNMP community string to use for SNMP set and get.
• SNMP Version - SNMP version to use in the reader. Supported versions are V1 and V2c.
• Send Server Heartbeat - Sends a heartbeat message periodically to the configured SNMP host.

NOTE: Send SNMP Trap To and Send Server Heartbeat take effect immediately after selecting Set
Properties. The modified SNMP Community String and SNMP Version are not affected until the
reader reboots.

76
 Administrator Console

Wireless Settings
Select Wireless to view the Reader Wireless Setting Parameters window.
Figure 45 Wireless Settings Window

Use the Wireless Setting window to set the wireless configuration on the reader. Zebra provides native support for
USB Wi-Fi adapters with the Realtek chipset RTL 8187 and RTL 8812AU. The following dongles were tested:
Table 7 Supported Wi-Fi Dongles

Zebra Zebra
Dongle Model FX7500 FX9600

TP-Link: AC 1200 Realtek RTL8812AU Yes Yes

ASUS: USB-AC56 Realtek RTL8812AU Yes Yes

Alfa Network Realtek RTL8812AU Yes Yes

Alfa AWUS036H Yes Yes

CCrane Versa Wifi USB Adapter II Yes Yes

The Wireless Settings window offers the following options:

• Get Details - Select to get details of the connected network, including the ESSID, signal strength, and
connection status.
• Disconnect - Select to disconnect from a connected network.
• Scan and Choose Network - Scan the available networks. Selecting this lists the ESSID in the drop-down
menu. If the ESSID is hidden (not broadcast), enter the ESSID in the text box provided.
• Passkey - Pre-shared key for the WPA/WPA2 network.
• Connect Automatically - Persist network setting across reboots and automatically retain association with
the configured AP.

NOTE: The scan function can take several seconds. All buttons on the page are disabled while the scan is in
progress, and re-enabled when the scan completes.

77
 Administrator Console

Network Services Settings

Select Services to view the Configure Network Service Settings window.

Figure 46 Configure Network Service Settings Window

NOTE: The user cannot change Web Server mode if Inventory is in progress.

The reader supports the following network services.

• Web Server - Configures the web server in either HTTP (unsecure) or HTTPS (secure) mode.
• Shell - Sets the shell to SSH (secure) mode or a disabled state.
• File Server - Sets the file server to either FTP (unsecure) or FTPS (secure) mode.
• Disable IPV6 Stack - Select this to disable the reader's IPV6 stack.
• Receive RA packets - This option is only valid when the IPV6 stack is enabled. Enable this to allow IPV6
IP configuration through RA packets; otherwise obtain the IP via DHCP in the Communication window or
assign statically.
• Node Server Port - Set the Node Server host connection port. The default value is 8001.
• Node Server Run Status - Displays the Node Server status:
• Green: Node Server is running.
• Red: Node Server is not running.

NOTE: You must select Set Properties to update the service configuration. If saving changes is not
successful, the system indicates the problem and allows correcting it by repeating the operation.

FX9600 Serial Port Configuration

The external FX9600 serial port can be configured to one of the following three modes:

• Debug port (default).

78
 Administrator Console

• Push data - Allows a connected client to receive tag data when inventory starts from the web console.
• Free port - Supports user app to use serial port.

NOTE: Changing the serial port mode requires restart of the reader to take effect.

Serial Port Configuration - Debug Port

In this mode, the FX9600 serial console is used as the debug kernel port. The kernel uses this port for debug
messages.
Figure 47 Serial Port Communication - Debug

Serial Port Configuration - Push Data Port

In this mode, the FX9600 serial port is used as a push data port. The inventory operation can be performed and a
TAG report is sent over the serial port with selected settings.
To configure Push Data:
1. Configure the serial port communication fields (see Figure 48).

79
 Administrator Console

Figure 48 Serial Port Communication - Push Data Configuration

Save
Connect

2. Select Save to save the current settings.

3. Reboot the reader to implement the changes.
4. Select Connect to connect to LLRP. If Auto Start is selected in Inventory Control options, the reader is set to
connect to LLRP upon boot up. Once connected, the inventory starts as per the Inventory Control configuration
and report tags over the serial port.
5. The tag data can be seen on the serial port as shown in Figure 50.

80
 Administrator Console

Figure 49 Serial Port Communication - Push Data Inventory Started

Figure 50 Tag Data

81
 Administrator Console

Serial Port Configuration - Free Port

When the FX9600 is the Free Port mode, the serial port in the FX9600 is able to perform operations such as open,
read, and write as per the user requirement.

Figure 51 Serial Port Communication - Free Port

FX Connect
FX Connect is a licensed feature which enables users to easily collect data from FX series RFID readers, namely
the FX7500 and FX9600. Data is pushed to the host PC in keystrokes via USB-HID or HTTP POST in a hassle free
manner. No knowledge of APIs or application development is required to receive RFID data from the reader. See
FX Series Licensing Management on page 97 for the detailed licensing information.

Using FX Connect
1. Open a web browser to connect to the FX reader using the host name or IP address. (See Quick Start on page
15 for startup instructions.)
2. Click Communication > FX Connect.

NOTE If no valid license is installed yet, the screen displays message to remind users to obtain a valid license.
See FX Series Licensing Management on how to enable FX Connect via a license.

If a valid license is installed, it is displayed in the FX Connect console.

82
 Administrator Console

Figure 52 FX Connect

3. Select the FX Connect drop-down arrow to select an option.

a. Disable - By default, FX Connect is disabled.
b. HTTP Post - This option enables the reader to push Inventory Tag data in JSON format to the web server
using the HTTP Post method. The web server could be running on local network or in the cloud.
See Table 8 for field information.
c. Keyboard Emulation - This option allows the user to push data over USB HID. It enables the reader to
send RFID data to an application running on a PC host connected to the reader via the USB client port.
Any application that can receive keyboard input is able to receive RFID data from the reader in this mode
because the reader uses Keyboard HID emulation to send data to the host PC. If this option is selected
and the user starts the Inventory, tag data is shown in a key-value pair in the selected text editor (Notepad,
MS Excel, etc.). See Table 9 for field information.
d. TCP/IP Socket - As in HTTP POST, this option also enables the reader to push Inventory Tag data in
JSON format to the defined TCP/IP socket port. Any client socket application connected to the reader with
defined port can receive Tag data. See Table 10 for field information.
e. USB Flash Drive - When this option is selected, the tag data is written to a specific file in attached USB
Flash drive in Key Value Pair format. This mode does not have any specific configurable parameters.
See Table 11 for field information.
4. Select Save to save the configuration settings for FX Connect.

83
 Administrator Console

Figure 53 HTTP Post Screen

Table 8 HTTP Post Configurable Options

Option Description

HTTP Post - This section displays the configurable parameters for the HTTP Post server.

Reader Name Reader name is the text string that appears in Post data to identify the
reader. See Configuring the HTTP Post Server on page 92 for details
on how to set up a web server to test this feature.

URL HTTP Post Server URL to receive post data.

Post Interval The period, in seconds, that FX Connect posts data to the web server.

Verify Peer Specifies whether or not peer validation is required. If the user selects
the option to validate peer, the HTTP Post service on the reader allows
connection for valid secure peer entities only if the certificate of peer is
issued from the same certification authority that issued the certificate for
the reader. By default, the reader issues self-signed certificates and the
option to enable peer certificate-based validation is disabled.

Verify Host Dictates whether to verify the certificate's name against the host.
Disabling this option allows self-signed certifications.

84
 Administrator Console

Table 8 HTTP Post Configurable Options (Continued)

Option Description

Authentication The type of authentication to use when connecting to the remote or

proxy server.

• NONE: No authentication at all.

• BASIC: Sends the user name and password in plain text over
the network.
• DIGEST: RFC 2617.
• DIGEST_IE: RFC 2617 but uses a special quirk that IE is
known to have used before version 7 and some servers
require.
• NTLM: Challenge-response and hash concept similar to Digest.
• ANY: FX Connect will automatically select the one it finds most
secure.
• ANYSAFE: FX Connect will automatically select any except
BASIC that it finds most secure.

User Name The user name required to connect to the Remote or Proxy Server for
certain Authentication types.

Password The password required to connect to the Remote or Proxy Server for
certain Authentication types.

HTTP Post Proxy: If reader is behind a proxy server then select the check box. This provides proxy server
related parameters. For more details on how to configure a proxy server see Configuring the HTTP Post Server
on page 92.

Proxy Server The Proxy Server Name or IP address with which to connect (when
specified).

Proxy Port The Proxy Server port to connect to.

Proxy Tunnel Dictates whether to tunnel through HTTP Proxy.

Authentication Same as HTTP Post Authentication but for the proxy server.

User Name Same as HTTP Post User Name but for the proxy server.

Password Same as HTTP Post Password but for the Proxy server.

Configure Antenna Power Enables the user to select the transmit power level for particular
antennas. By default, the maximum transmit power value supported by
the reader is selected for each antenna.

85
 Administrator Console

Table 8 HTTP Post Configurable Options (Continued)

Option Description

Inventory Control Parameters These are control options for some inventory parameters. This section
has options for inventory start/stop triggers, sessions on which to run
inventory, and periodic reporting time value. These parameters can be
configured to run inventory as per the requirement. If the user selects
the auto start option, inventory starts automatically upon boot up (based
on the start trigger chosen).

Tag Field Selection In this section the user can choose Tag Data Report fields to be sent
over HTTP Post to the server. The available fields to chosen are: EPC,
PC, Antenna ID, RSSI, Seen Count, etc. by selecting the corresponding
check-box. By default, EPC, PC, Antenna ID, and Seen Count are
selected.

The Tag Field Selection descriptions are as follow:

• EPC - The Tag EPC Data field.

• PC - PC BITS.
• Antenna ID - Antenna ID on which Tag is read.
• RSSI - The Peak RSSI value.
• Seen Count - The number of times the Tag is read (in-case of
periodic reporting).
• Timestamp - Timestamp when Tag is seen.
• Phase - Phase information reported by the reader when the tag is
seen.
• Channel Index - Index of the first channel when the tag is seen.
• Heart Beat - Heartbeat string to indicate that the reader is UP and
running.

Note: Heart Beat, when enabled, causes the reader to periodically send
a heartbeat string (********) to indicate that the reader is up and running.

The Period for heartbeat, in seconds, indicates the minimum delay

before sending out another heartbeat string.

86
 Administrator Console

Figure 54 Keyboard Emulation Screen

Table 9 Keyboard Emulation Configurable Options

Option Description

Output Format - This section displays the configurable parameters for the Keyboard Emulation.

Format Output format that is supported with USB HID is key-value pairs.

Delimiter The delimiter options are comma, space, and tab.

Line Ending The line ending options are None, CRLF, and LF.

Timestamp Format The timestamp format options are UTC and Unix.

Data Prefix/Data Suffix The user can add a prefix and suffix for each tag read record.
Note: Data Prefix and Data Suffix should be in a character sequence
only.

Configure Antenna Power See Table 8.

Inventory Control Parameters See Table 8.

Tag Field Selection See Table 8 (defaults vary).

87
 Administrator Console

Figure 55 TCP/IP Socket Screen

Table 10 TCP/IP Socket Configurable Options

Option Description

TCP/IP - This section displays the configurable parameters for the TCP/IP.

Port Number This is the TCP/IP port number for which FX Connect will open TCP/IP
socket and push data when inventory is running.

Configure Antenna Power See Table 8.

Inventory Control Parameters See Table 8.

Tag Field Selection See Table 8 (defaults vary).

88
 Administrator Console

Figure 56 USB Flash Drive

Table 11 USB Flash Drive Configurable Options

Option Description

Output Format - This section displays the configurable parameters for the USB Flash Drive.

Format Output format that is supported with USB HID is key-value pairs.

Delimiter The delimiter options are comma, space, and tab.

Line Ending The line ending options are None, CRLF, and LF.

Timestamp Format The timestamp format options are UTC and Unix.

Data Prefix/Data Suffix The user can add a prefix and suffix for each tag read record.
Note: Data Prefix and Data Suffix should be in a character sequence
only.

Configure Antenna Power See Table 8.

Inventory Control Parameters See Table 8.

Tag Field Selection See Table 8 (defaults vary).

89
 Administrator Console

Running Inventory on FX Connect

To start the inventory operation for the selected and configured Output mode:

1. From the FX Connect console select Connect.

NOTE Connect appears after the user selects Save.

Connect changes to Disconnect after a successful connection.

a. The inventory operation begins per the configured Start Trigger setting.
b. The inventory status light turns green when inventory beings running. It turns red when the inventory stops
per the configured Stop Trigger setting.
2. Select Disconnect.

NOTE Disconnect changes to Connect after a successful disconnection.

Example JSON format of Tag Data

For the HTTP POST and TCP/IP Socket mode, Tag Data is reported in JSON format. Below is the example of
JSON format (with selecting all Tag Field):

{"reader_name":"FX9600FB37EE FX9600 RFID Reader", "mac_address":"84:24:8D:EF:B2:F6",

"tag_reads":[{"epc":"8DF0000000000000007CCC62","pc":"3000","antennaPort":"1","peakRssi":"-58","seenC
ount":"4","timeStamp":"30/3/2020
17:7:23:67","phase":"0.00","channelIndex":"1","isHeartBeat":"false"},{"epc":"30304035A880C800001235CD"
,"pc":"3000","antennaPort":"1","peakRssi":"-48","seenCount":"2","timeStamp":"30/3/2020
17:7:23:847","phase":"0.00","channelIndex":"1","isHeartBeat":"false"}]}

Below is the example of Heartbeat JSON data, which is reported at a defined time interval as per the configuration.

{"reader_name":"FX9600FB37EE FX9600 RFID Reader", "mac_address":"84:24:8D:EF:B2:F6",

"tag_reads":[{"epc":"********","pc":"0","antennaPort":"0","peakRssi":"0","seenCount":"0","timeStamp":"3
0/2/2020 17:7:49:416565","phase":"0","channelIndex":"0","isHeartBeat":"true"}]}

90
 Administrator Console

Example Key-Value Pair Format of Tag Data

For the Keyboard Emulation and USB Flash Drive mode in FX Connect, Tag Data is reported in Key-Value Pair
format. Key-Value Pair format mostly depends on the delimiter and line-ending configuration. The Key-Value Pair
format varies as per the choice of these configuration option.

Apart from these, there is one special case; if EPC only is selected in Tag Field Selection, then Key-Value Pair
will have data output without any meta-data as shown in example 1 & 3 below.

1. With EPC only in Tag Field Selection and Line Ending as None.

ad72120544894bb660000059,e280689000000000182a55b1,303800000333f10000000039,303800000333f10
000000039,ad72120544894bb660000059,e280689000000000182a55b1,

2. With more selections in Tag Field Selection and Line Ending as None.

epc=303800000333f10000000039,pc=3000,antennaport=2,peakrssi=-60,seencount=1,timestamp=15112019
610110,phase=0.00,channelindex=6,epc=ad72120544894bb660000059,pc=3000,antennaport=2,peakrssi=-5
9,seencount=1,timestamp=15112019
610118,phase=0.00,channelindex=6,epc=e280689000000000182a55b1,pc=3000,antennaport=2,peakrssi=-60
,seencount=1,timestamp=15112019
610122,phase=0.00,channelindex=6,epc=303800000333f10000000039,pc=3000,antennaport=2,peakrssi=-58
,seencount=13,timestamp=15112019
61168,phase=0.00,channelindex=8,epc=ad72120544894bb660000059,pc=3000,antennaport=2,peakrssi=-54,
seencount=14,timestamp=15112019
61169,phase=0.00,channelindex=8,epc=e280689000000000182a55b1,pc=3000,antennaport=2,peakrssi=-59,
seencount=14,timestamp=15112019 61170,phase=0.00,channelindex=8,

3. With EPC only in Tag Field Selection and Line Ending as LF (Line Feed).

303800000333f10000000039,
ad72120544894bb660000059,
ad72120643c065b4867e00ab,
e280689000000000182a55b1,

91
 Administrator Console

4. With more selections in Tag Field Selection and Line Ending as LF (Line Feed).

epc=ad72120544894bb660000059,pc=3000,antennaport=2,peakrssi=-60,seencount=1,timestamp=15112019
6011418,phase=0.00,channelindex=6,
epc=303800000333f10000000039,pc=3000,antennaport=2,peakrssi=-58,seencount=1,timestamp=15112019
6011422,phase=0.00,channelindex=6,
epc=e280689000000000182a55b1,pc=3000,antennaport=2,peakrssi=-60,seencount=1,timestamp=15112019
6011433,phase=0.00,channelindex=6,
epc=ad72120544894bb660000059,pc=3000,antennaport=2,peakrssi=-55,seencount=44,timestamp=1511201
9 6016418,phase=0.00,channelindex=18,

NOTE In all the examples shown in from No. 1 to 4, Comma (,) is selected as the Delimiter.

Configuring the HTTP Post Server

NOTE You must have a valid license to run FX Connect. See FX Series Licensing Management for more
information.

To run the HTTP Server to receive tag data from FX Connect:

1. Open a web browser to connect to the FX reader using the host name or IP address. (See Quick Start for
startup instructions.)
2. Click Communication > FX Connect.

3. Install Python version 2.7 or above.

4. Go to: github.com/BurntSushi/nfldb/wiki/Python-&-pip-Windows-installation and follow the instructions to install
Python pip.
5. Open command shell.
6. Install Flask by typing the command: pip install Flask.
7. Save the text below as postServer.py.
from flask import Flask, request
app = Flask(__name__)

@app.route('/', methods = ['POST', 'GET'])

def message():
if request.method == 'POST':
app.logger.info('Request received.')
app.logger.info('Url: %s', request.url)
app.logger.info('Data: %s', (request.data).decode('utf-8'))
app.logger.info('Is JSON: %s', request.is_json)
else:
app.logger.info('GET request received.')

92
 Administrator Console

return 'OK\n'

if __name__ == '__main__':
app.run(host='0.0.0.0', port='5001', debug=1)

NOTE The script above runs HTTP server on port 5001; if needed, change the port number.

8. To see the HTTP Post output, run the command: python postServer.py. This start s the HTTP server which
receives tag data from FX Connect and displays the data in the command shell.

Configuring the HTTP Proxy Server

To setup the Squid proxy server on an Ubuntu machine:

1. Install, start, and enable Squid on the Ubuntu machine using the following commands.
$ sudo apt -y install squid
$ sudo systemctl start squid
$ sudo systemctl enable squid
2. The squid.conf file is created in: /etc/squid/squid.conf.
3. The default configuration file contains some configuration directives that affect the behavior of the Squid and
they need to be configured.

Open the squid.conf file and update the lines below, the Save.
a. Under rule allowing access from your local networks add the following statements:
acl all src 0.0.0.0/0.0.0.0
acl Safe_ports port 8081 # custom http
b. Under access permission configuration add the following statement:
http_access allow all
c. Under access permission configuration comment the statements:
#http_access allow localhost manager
#http_access deny manager
4. Restart the Squid with the following command:
sudo systemctl restart squid
5. The proxy server is now ready.
6. Check the logs in the proxy server with the following command:
sudo tail -f /var/log/squid/access.log

Configuring USB HID

NOTE It is recommended to use two host PCs - one to control the reader through the web console and another to
receive tag data.

NOTE Setting the reader to use USB HID disables RNDIS on the USB client port. The reader cannot be
accessed using the RNDIS IP Address (169.254.10.1) in this scenario.

93
 Administrator Console

To run FX Connect in Keyboard Emulation:

1. Open the reader web console to FX Connect (see Figure 52 on page 83).
2. Connect the reader to the host machine through the USB Client port (same as RNDIS).
See Figure 7 on page 22 and Figure 10 on page 25 for FX7500 and FX9600 USB Client ports. Windows
automatically detects the reader as an HID device when inventory starts on FX Connect and enables the
driver.

Figure 57 HID Device Detection

3. Open any text editor application or MS Excel to receive push data from the reader. Use your cursor to select
the spot where you want to print the tag data.
4. Start the inventory by selecting Connect on reader web console.

Tag data is printed in the application at the selected spot.

Configuring the TCP/IP Socket

To use TCP/IP socket for receiving Tag data

1. Run TCP/IP socket client application on host machine. TCP/IP client will read the Tag data sent by the reader.
Below is the simple TCP/IP client application which need to be compiled on host machine:
/*
* tcpclient.c - A simple TCP client
* usage: tcpclient <server IP> <port>
*/
#include <stdio.h>
#include <stdlib.h>
#include <string.h>

94
 Administrator Console

#include <unistd.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <netdb.h>
#include <sys/ioctl.h>

#define BUFSIZE 10240

/*
* error - wrapper for perror
*/
void error(char *msg) {
perror(msg);
exit(0);
}

int main(int argc, char **argv) {

int sockfd, portno, n;
struct sockaddr_in serveraddr;
struct hostent *server;
char *hostname;
char buf[BUFSIZE];
struct timeval t;
int iMode = 1;
int count = 0;

/* check command line arguments */

if (argc != 3) {
fprintf(stderr,"usage: %s <server IP> <port>\n", argv[0]);
exit(0);
}
hostname = argv[1];
portno = atoi(argv[2]);

/* socket: create the socket */

sockfd = socket(AF_INET, SOCK_STREAM, 0);
if (sockfd < 0)
error("ERROR opening socket");

/* gethostbyname: get the server's DNS entry */

server = gethostbyname(hostname);

95
 Administrator Console

if (server == NULL) {
fprintf(stderr,"ERROR, no such host as %s\n", hostname);
exit(0);
}
printf("Connecting to server : %s\n", server->h_name);

/* build the server's Internet address */

bzero((char *) &serveraddr, sizeof(serveraddr));
serveraddr.sin_family = AF_INET;
bcopy((char *)server->h_addr,
(char *)&serveraddr.sin_addr.s_addr, server->h_length);
serveraddr.sin_port = htons(portno);

/* connect: create a connection with the server */

if (connect(sockfd, (struct sockaddr *)&serveraddr, sizeof(serveraddr)) < 0){
printf("Connecting to socket failed.\n");
close(sockfd);
error("ERROR connecting");
return -1;
}
while(1){
/* print the server's reply */
bzero(buf, BUFSIZE);
n = read(sockfd, buf, BUFSIZE);
if (n < 0){
error("ERROR reading from socket");
} else if (n == 0){
printf("Server Socket closed \n");
break;
} else {
printf("\nMessage: %s", buf);
}
//if(count++ > 10)
// break;
}
close(sockfd);
return 0;
}

96
 Administrator Console

2. Once compiled, run this application with reader IP and PORT which is already configured on the reader.
3. After running the application, click on connect button on the reader web console to run inventory under FX
Connect.
4. Application will print the received tag data on screen.

Configuring the USB Flash Drive

To get the tag data in USB drive there no configuration is required. The user just need to attach the USB flash drive
in reader and click on Connect button at FX Connect web console.

The tag data will be pushed to USB flash drive in a file named as current timestamp.

FX Series Licensing Management

This section explains the licensing model and the licensing mechanism used in FX Series RFID Readers. FX
Connect and Network Connect are the licensed features on FX Series Readers. The following areas are covered:

NOTE FX7500 does not support Network Connect. FX9600 supports both FX Connect and Network Connect.

• License activation in the ON-Line and OFF-Line modes. See License Acquisition Modes on page 99.
• How to return licenses. See How to Return License on page 104.
• Setup and administration of the license server. See How to Setup and Manage the Local License Server
on page 105.
• How to download capability response from the cloud server. See How to Download Capability Response
from The Cloud Server on page 106.

See Troubleshooting for Licensing Errors on page 188 to troubleshoot errors related to licensing.

IMPORTANT: The date and time setting for the license acquiring process, see Time Tampering on page 98 for
more details.

FX Series Licensing Model

FX Connect & Network Connect features require a valid license to be installed in the reader. The FX
Connect/Network Connect license purchased from Zebra determines the number of FX7500/FX9600 readers that
can use FX Connect & Network Connect features. Only the readers that successfully acquire a license from the
license server can read tags and load the RFID tag data to the designated output. Users can request for a
evaluation/trial license but that is for a limited period only. The following sections explain the procedure to procure
the license. When the license is procured, the user receives an Activation ID which is used to activate/return the
license on the readers.

Procuring Licenses
Customers, partners, and distributors require a FX Series Product License (FX Connect/Network Connect), please
request an evaluation/trial license through your Account Manager.

Account Manager/Sales Engineers can request Trial/Eval License for FX Connect/Network Connect for customers,
partners, or distributors via SFDC Forms.

Zebra Engineering can request for an evaluation/trial license for FX Connect/Network Connect via Service NOW.

97
 Administrator Console

Types of Licenses
NOTE Network Connect (EtherNet/IP) is not supported in FX7500 Reader.

There are four type of licenses for FX Readers:

• FX Connect Evaluation License

• FX Connect Perpetual License
• Network Connect (EtherNet/IP) Evaluation License
• Network Connect (EtherNet/IP) Perpetual License

Evaluation License
The evaluation license is a time bound license. Based on the procurement type, it can be valid for 30, 60 or 90
days. When the trial period ends, the license is de-activated and the respective application is ceased from
operations. Upon expiration of the trial term, the user is required to purchase a renewal license or switch to a
permanent license.

Perpetual License
The perpetual license is a permanent license and is available for the life of the reader.

Enabling a License
To enable a license on FX Reader, procure the appropriate license (evaluation or perpetual), then log in to the
reader web interface to configure and activate the license.

Time Tampering
License operations such as acquiring and returning license are time dependent operations, so the FX Reader must
be configured with current date and time. Failing to do so will result in errors in the acquiring license and releasing
license processes.

The Reader time can be set automatically via the NTP server or configured manually in the Date Time windows
(see Figure 58).

NOTE Clock Wind Back is enabled in the Firmware. Any back tracing of date or time will result in license error.

98
 Administrator Console

Figure 58 System Time Management

FX Series Licensing Mechanism

License Acquisition Modes
Users can acquire a license for the FX Readers in an on-line or off-line modes.

The three available servers when the reader is the on-line mode are as follows:

NOTE The On-Line mode license acquisition methods (from the Production, UAT, and Local License servers)
require Internet connectivity.

• Production Server (ON-Line Mode).

• UAT Server (ON-Line Mode). See page 101.
• Local License Server (ON-Line Mode). See page 102.

User can also acquire license in the off-line mode, see Acquiring License by Downloading Bin File (OFF-Line) on
page 102 for more details.

Acquiring License from Production Server (ON-Line Mode)

This method is for the external customer. This is the default license acquisition mode and it has the minimal setup
and configuration. The FX Reader must have the Internet connection to acquire a license form the Production
server. The license server is hosted on the cloud and the FX reader contacts the cloud-based license server to
acquire licenses.

99
 Administrator Console

Figure 59 Manage License - Production Server

To acquire licenses from the Production server:

1. Select the appropriate option for the fields as in Figure 59.

2. Enter the 32-byte Activation ID that is shared via e-mail when the license is procured.

NOTE The Install and Run application option allows you to install the EtherNet/IP package and starts the
application. The EtherNet/IP package is built in the reader firmware. If the EtherNet/IP stack has already
been installed, uncheck the Install and Run application box.

NOTE To circumvent a firewall while contacting the cloud-based license server, set up a proxy server. To do this,
go to: https://supportcommunity.zebra.com/s/article/ZSL-Licensing-Server-Connectivity?language=en_US

3. Click Activate to acquire the license, and the license feature list is populated as shown in Figure 60:
• License Index: Place holder for license number.
• License Name: This is the feature name of license, such as fx-feature connect, nc-feature-ethernetip etc.
• License Version: Place holder to list the license version number.
• Expiry Date: An expiry date is displayed for the Evaluation license. For the Perpetual license, this field
shows permanent.
• License Count: Place holder to list the number of license allocated to the FX Reader.
• Host ID: A unique number for the license server to identify the device. This number has both model & mac
number of device. The example shown in Figure 60 is FX9600_84_24_8D_EE_57_34.

Figure 60 Available License - Production Server

100
 Administrator Console

4. The Application window shows the status and the progress of the package installation.

Figure 61 User Application Page

Acquiring License from UAT Server (ON-Line)

This method is for Internal Customer (Sales Engineer, Developers & Test Engineers). The FX Reader must be
connected to the Internet. The license server is hosted on the cloud and the FX reader contacts the UAT license
server to acquire licenses.

Figure 62 Manage License - UAT Server

To acquire licenses from the UAT server:

1. Select the appropriate option for the fields as in Figure 62.

2. Enter the 32-byte Activation ID that is shared via e-mail when the license is procured.

NOTE The Install and Run application option allows you to install the EtherNet/IP package and starts the
application. The EtherNet/IP package is built in the reader firmware. If the EtherNet/IP stack has already been
installed, uncheck the Install and Run application box.
If you are installing the FC Connect License, the firmware ignore the input from the check box.

3. Click Activate to acquire the license, and the license feature list is populated as shown in Figure 63.

Figure 63 Available Page - UAT server

101
 Administrator Console

Acquiring License from Local License Server (ON-Line)

This license acquisition method is available for both External & Internal Customers. Prior to acquiring the license
from the Local License Server (LLS), users must setup their own LLS within their LAN network (see How to Setup
and Manage the Local License Server on page 105 for the detailed procedures). Then, the FX Reader contacts the
Local License Server to acquire licenses.

Figure 64 Manage License - Local License Server

To acquire licenses from the Local License Server:

1. The Local License Server is ready in the local LAN Network. See How to Setup and Manage the Local License
Server on page 105 if the LSS is not set up yet.
2. Select the appropriate option for the fields as in Figure 64.
3. In the Server URL field, enter the LLS link with the format http://<Server_ip or host_name>:port_number/request

NOTE A LSS link is required to acquire and release a license.

4. Enter the 32-byte Activation ID that is shared via e-mail when license is procured.

NOTE The Install and Run application option allows you to install the EtherNet/IP package and starts the
application. The EtherNet/IP package is built in the reader firmware. If the EtherNet/IP stack has already
been installed, uncheck the Install and Run application box.

5. Click Activate to acquire the license, and the license feature list is populated as shown in Figure 63.

Figure 65 Available License - Local License Server

Acquiring License by Downloading Bin File (OFF-Line)

This method of acquiring license is also called the OFF-Line method. Use this method when the Internet
connection is not available. However, the user must download the Capability Response from the server prior to
acquiring license with this method. See the How to Download Capability Response from The Cloud Server on page
106 for more details.

102
 Administrator Console

Users must have the Device ID and the Activation ID before downloading the capability response.

Device ID
Device ID is the unique identification number of the FX device in Zebra Licensing Server. The FX License Features
Device ID must be in the format <Model Name>_<Mac_Address> (for example, FX9600_84_24_8D_EF_B2_BB),
where

• The Model Name is FX7500 or FX9600.

• The MAC/IEE address is a 12-digit number.

Look for the Model Name and the MAC/IEE address at the bottom of device.

Figure 66 Reader Label

Activation ID
Activation ID is the unique 32-bit alpha-numeric number shared to the user when the license is procured. This
number acts as the key to enable the FX Reader to activate the license. An example of the Activation ID is
8c88-d0e7-9f3c-435b-968b-69a8-7f8e-a302.

NOTE For External Customers, refer to the link shared via e-mail when the license is procured. The link is with
credentials. For Internal Customer such as Sales Engineer/Developer/Test Engineer, go to
https://zebra-licensing-uat.flexnetoperations.com/ with credentials provided.

To acquire license in the off-line mode:

1. See the How to Download Capability Response from The Cloud Server on page 106 to download the
Capability Response.
2. In the Manage License window, select the appropriate option for the fields as shown in Figure 4.

Figure 67 Manage License - OFF-line mode

103
 Administrator Console

3. At Upload License, select the Choose File button to locate the bin file downloaded in Step 1.
4. Click Activate button to activate the license.

NOTE The Install and Run application option allows you to install the EtherNet/IP package and starts the
application. The EtherNet/IP package is built in the reader firmware. If the EtherNet/IP stack has already been
installed, uncheck the Install and Run application box.
For FX Connect, the check box input is ignored.

How to Return License

NOTE The FX reader must be connected to Internet to return license.

Users can return the acquired license and it is to the cloud server only regardless of whether the license is acquired
OFF-Line or ON-Line.

1. Select the appropriate option for the fields as in Figure 68.

Figure 68 Manage License - Return License

2. In the Server Type field, select from which server type the license is acquired.

NOTE For licenses acquired from the Local License Server, in Server URL, enter the LLS link with the format
http://<Server_ip or host_name>:port_number/request.

3. Select Release.
4. Upon successful release and none of the license is available, the message window below is displayed.

104
 Administrator Console

How to Setup and Manage the Local License Server

Figure 69 illustrates the process of license acquisition from a local license server.

Figure 69 Local License Server Acquisition

Steps to setup the LLS within the LAN network are as follows:

NOTE The following steps are described in detail in the Local License Server Administration Guide (part
number, MN-003302-xx). Please refer to the Local License Server Administration Guide for installation
and registration instructions.

1. Install the local license server.

2. Configure the local license server.
3. Register the local license server.
4. Acquire licenses in the local license server.
5. Input activation ID to the reader.
6. Reader acquires the license from LLS.

Once the local license server is set up, set up FX Reader to acquire licenses from the local license server. This can
be done by changing the license_server_url field in HTML page file to the URL with format
http://<license_server_ip_or_hostname>:7070. The local license server by default listens on port 7070 which
can be changed in the license server configuration. If a non-default port is configured in local license server, then
ensure to update the license_server_url field in the HTML page to the same value. The license_activation_id
field must be updated to the appropriate value provided by Zebra.

105
 Administrator Console

How to Download Capability Response from The Cloud Server

The user must log in before entering the Zebra Licensing Server. Click the following link:
https://zebra-licensing-uat.flexnetoperations.com/ (This could be different if you are a external customer)

1. Enter the Username & Password.

2. A Home screen appears as follow:

106
 Administrator Console

3. Select the Device tab and create a New Device in the window. Fill ID according the format
<Model Name>_<Mac_Address> (See Device ID on page 103).
4. Fill Name to be same as ID. Do not select the Runs license server option and leave Site Name as empty.

NOTE FX9600_84_24_8D_EF_B2_BB in Figure 70 is an example.

Figure 70 Create New Device

Device

Name

ID

5. Click Save. The page shows Device created successfully when the device is successfully registered.

107
 Administrator Console

6. Select Action to expand the drop-down list. Select Map By Activation ID.

7. Key-in the Activation ID. If you have multiple IDs, make sure to key in one in a new line.

8. Click Validate.
9. Edit the Qty to add tab. Otherwise all the license will be mapped to a single device. For a standalone license,
the value is 1. For LLS it may require a quantity.

108
 Administrator Console

10. Click Save.

11. The page shows Entitlement successfully mapped.

109
 Administrator Console

12. Click Action to expand the drop-down list. Select Download Capability Response. The bin file will be
available in the Download folder.

13. Select the Device Type and provide the ID accordingly. The entitled devices will be listed.

110
 Administrator Console

14. To log out, select ZSL System Test > Logout.

111
 Administrator Console

System Time Management

Select Date Time to view the System Time Management window. Use this window to set the date and time value of
the reader, or to specify an NTP server for the reader to synchronize with.

Figure 71 System Time Management Window

To specify an SNTP server, enter the SNTP server's IP address or name in the SNTP Server Name or IP
Address box, and then select Set SNTP Parameters.

To adjust the time manually, select the appropriate value for the user's local time, and select the Set Date and
Time button. This adjusts the reader's clock to the value provided if the operation is successful. Otherwise, an
appropriate message indicates the reason for the failure.

You can also set the Time Zone (including use of Daylight Savings) using the drop-down menu.

NOTE: The date/time and time zone changes take effect immediately.

112
 Administrator Console

IPV6 IP Sec
Select IP Sec to view the IPV6 IP Sec window. IP Sec settings allow adding IP Sec pairing of the reader with a
partner with a pre-shared key.

Figure 72 IPV6 IP Sec Window

To add an IP Sec entry:

1. Select the Add IP Sec Entry radio button.

2. In the IP Address field, specify the IP address of the partner with whom the IP SEC communication is
intended.
3. In the Passkey field, enter the pre-shared passkey (from 6 to 15 characters) to use with the partner IP
address.
4. In the Access Level drop-down list, select the IP Sec access level. Options are Transport and Tunnel mode.
Currently the reader only supports Transport mode.
5. Select the Add IP Sec Entry button.

To delete an IP Sec entry:

1. Select Delete IP Sec Entry radio button.

2. In the IP Address field, specify the IP address of the partner with whom the IP SEC communication is
configured and is to be deleted.
3. Select the Delete IP Sec Entry button.

113
 Administrator Console

Change Password
To ensure the controlled and secured access to reader Administrator Console functions, designate which users
and computers are authorized to have system access by setting up authorized user accounts. Only users logging
in with a registered user name and password can successfully access Administrator Console functions.

FX Series User Accounts

The FX Series supports the following user accounts:

• admin - This user has web access but no shell access, with full privileges to make changes on the reader
using the Administrator Console interface and to access to the reader using the FTP interface.
• guest - This user has web access but no shell access, with read-only privileges in the Administrator
Console and can not make configuration changes. The guest user does not need a password to log in to
the Administrator Console.

NOTE The Change Password function is not supported for the guest user.

• rfidadm - This is the reader administrator, with shell access but no Administrator Console access. rfidadm
has full access to the /apps directory and read-only access to most of the other directories, including the
/platform, /usr, /lib, /etc, and /bin directories. The rfidadm user can use this account to install and
uninstall RFID programs and upload user applications.

Select Change Password to view the Change Password window.

Figure 73 Change Password Window

To set a user password:

1. In the User Name drop-down list, select the user for whom to change the password.
2. In the Old Password field, enter the existing password for that user.
3. In the New Password field, enter the new password, and again in the Re-Enter Password field.
4. Select Change Password. The password changes immediately.

114
 Administrator Console

Managing User Login and Logout

Users must log in and log out of the system to ensure that system access is granted only to authorized users, and
that only one user is logged in at a time to ensure that multiple users do not make conflicting changes to the
system.

If the user performs no action for a period of time, the system automatically logs him or her out. The user must log
in again to use the Administrator Console.

GPIO
Select GPIO to view the GPIO Control Page. This window allows viewing and setting the status for GPI pins.

NOTE: The FX7500 has two inputs and three outputs. The FX9600 has four inputs and four outputs.

Figure 74 FX7500 Example GPIO Control Page

• Settings - Map the reader GPI and/or GPO with the radio GPIO. Select either Radio or Host for GPIx or
GPOx where x = 0 or 1. An attempt to violate this condition changes the selection to either Host GPIx or
Host GPOx automatically. The settings are disabled if a configuration is not supported.
• Status - To set a GPO pin high or low, select on the image next to the required pin number:

• Green indicates GPIO HIGH

• Red indicates GPIO LOW

• Yellow indicates GPIO unknown

• GPI Debounce Time - Enter a value of up to 1000 milliseconds to minimize spikes that can occur when a
device connects to the GPIO port of the FX reader. The default is 50. Debounce time applies to all input
pins, and pins must work independently of each other. Events and callback functions occur only after the
debounce time expires, provided the pin state remains at the same level for the debounce time duration.
GPIO debounce does not impact GPO and input operations when set to 0.
• Set Properties - Select this when all selections are made.

115
 Administrator Console

Applications
Select Applications to view the User Application Page. This window allows installing applications on the reader
and provides details of the installed application.
Figure 75 User Application Page

The Existing Packages section includes the following options:

• List of Installed apps - The drop-down menu lists the current packages installed in the reader.
• Start/Stop - The image displays the running status as follows. Select the image to toggle the status.

• Green indicates application is running.

• Red indicates application is not running.

• AutoStart - Select this check box to run the application at startup.
• Uninstall - Removes the package from the reader.
• Install - Installs a new package in the reader.
To create packages for the FX Series readers, use any of the standard Debian package creation tools, or create
them manually. The FX Series SDK Programmers Guide provides details on creating application packages to
install on the reader.
• The package must contain a binary executable compatible with ELF 32-bit LSB executable, ARM, version
1, GNU Linux.
• The name of the binary executable must match the name of the package, excluding the version name. For
example, if the package name is package-1_2.1_all (package 1 version 2.1), the name of the binary
executable must be package-1. There can be more than one binary in the package.
• The package must contain a startup script in the name of start_packageName.sh to start the binary or
binaries in the package. For example, if the package name is package-1_2.1_all.deb (package 1 version
2.1), the name of the startup script must be start_package-1.sh.
• The package must contain a stop script in the name of stop_packageName.sh to stop the binary or
binaries in the package. For example, if the package name is package-1_2.1_all.deb (package 1 version
2.1), the name of stop script must be stop_package-1.sh.
NOTE: The reader executes the packages with the privileges of rfidadm user account. See the user accounts
section for information on rfidadm user privileges.

116
 Administrator Console

Reader Profiles
Select Profiles in the selection menu to view the Reader Profiles window, which shows the current profiles on the
reader and allows performing operations defined by the active profile.

The window displays a set of provided configuration files, or profiles, that a user can re-use and/or modify
depending on the reader application or use case. The profiles serve as configuration examples.

Figure 76 Reader Profiles Window

NOTE The user cannot make profile active if inventory is in progress.

The reader profile with the asterisk at the end is the active profile.

Out of the box, the Current Config profile is active.

The Current Config profile is the same as the Default profile until the user starts configuring the reader. When the
user overwrites the out of box configuration, the reader still shows Current Config as the active profile, however at
that point Current Config is not the same as the Default profile.

The Reader Profiles includes 5 build-in profiles:

• Default:
• Use this profile to return the reader to the out-of-box RFID configuration.
• The reader default settings in use include Session (S0), Target(A), Sel(SL All), Tag, and Population
(100).
• The RF mode is set to AutoMAC. In this RF mode, the radio scans RF environment to determine the
best RF link settings so that the reader is interference tolerant while at the same time maximizes
unique tag throughput.

117
 Administrator Console

• Maximum Data Rate:

• This profile demonstrates maximum tag read rate in low interference environments.
• The RF mode is set based on the reader module (see Table 12).
• Other parameters used in this mode are Session (S0), Target(A/B), Sel(SL All), and Tag Population
(300).
• This profile can be used to stress test the application ability to process large data rates.
• Dock Door with Motion Sensor:
• This profile can be used to monitor tag passing through the dock door.
• The RF mode is set based on the reader module (see Table 12).
• Other Parameters used in this mode are Session (S2), Target(A), Sel(SL All), and Tag Population
(300).
• This profile can be customized to include the additional GPI trigger to link door open/close.
• Conveyor:
• This profile can be used to detect single tag passing reading field on the conveyor.
• The RF mode is set based on the reader module (see Table 12).
• The tag population is set to 5 due to few tag in FOV.
• The antenna dwell time is set to 25 ms per antenna.
• Other parameters used in this mode are Session (S2), Target(A), and Sel(SL All).
• Transition Point:
• This profile can be used to detect tag status such as moving tag and stationary tag.
• It works with applications such as autonomous event mode or portal directionality.
• The RF mode is set based on reader module (see Table 12).
• Other parameters used in this mode are Session (S2), Target(A), Sel(SL All), and Tag Population
(300).

Table 12 lists the parameter setting of build-in profiles.

NOTE Refer to Table 23 on page 201, Table 24 on page 203, and Table 25 on page 205 for RF mode index
definitions.

Table 12 Parameter Settings of Build-in Profiles

RF Mode Index Tag
Profile Name Session Target Sel
US-FCC EU-ETSI JP-FX9600 JP-FX7500 Population

Default 23 21 11 5 S0 A SL ALL 100

Maximum Data 1 10 21 3 S0 A/B SL ALL 300

Rate

Dock Door with 1 10 21 3 S2 A SL ALL 300

Motion Sensor

Conveyor 1 10 21 3 S2 A SL ALL 5

Transition Point 1 10 21 3 S2 A SL ALL 300

118
 Administrator Console

The Reader Profiles window functions are:

• Available Profiles in the Reader - Displays the available reader profiles.

• Import - Select to open a file dialog and pick a profile (XML file) from the local PC and import it into the
reader.
• Export - Select an available profile and select Export to export profile information and save an XML file onto
the local drive.
• Set Active - Activates a selected profile. Select an available profile and select Set Active to load the profile
content in the reader.

CAUTION: Swapping profiles between readers using static IP addresses is not recommended. Activating a profile
with a static IP address changes the IP of the reader, and if not done properly can make the reader
inaccessible.

• Delete - Select an available profile and select Delete to delete the profile.

NOTE: Current Config is a special logical profile that can only be exported to the PC. This cannot be imported,
activated, or deleted. Only the profile name indicates that it is the active profile.

Profiles can specify a number of reader parameters, including RF air link profiles. Air link profiles cannot be
configured using LLRP or web page interface. See RF Air Link Configuration for more information about air link
profile configuration.

FIPS Support
The FX7500 and FX9600 supports FIPS 140-2 Level 1 for the following interfaces:
• HTTPS
• FTPS
• SSH
• LLRP Server
• IPSec
To enable or disable FIPS support in the reader profile, export the profile XML (CurrentConfig) from the reader
and set FIPS_MODE_ENABLED to 1 to enable FIPS, or 0 to disable FIPS. Then import the XML to the reader and
activate. Changing the FIPS mode restarts the reader. By default, FIPS is disabled.

119
 Administrator Console

Firmware Version/Update
The Firmware Version window displays the current software and firmware versions and allows upgrading to new
firmware. From the selection menu, select Firmware.

Figure 77 Firmware Version

Current Version indicates the binary versions currently running in the reader. Last Known Version indicates
binary image versions stored in the backup partition. This window provides version information on the following
firmware:
• Boot Loader
• OS
• File System
• Reader Application
• LLRP
• Radio Firmware
• Radio API
Select Revert Back to revert the firmware to last known version. The reader automatically reboots. This option is
not enabled if the reader detects an error in the previous firmware update.

NOTE: If an embedded application no longer runs due to the new tool chain and Linux kernel, recompile the
application with new embedded SDK or revert the reader to the older firmware which supports older
embedded applications.

120
 Administrator Console

Firmware Update
The Firmware Update window allows upgrading to new firmware. From the selection menu, select Update.

NOTE: You must be logged in with Administrator privileges in order to access this window.
See Change Password on page 114.

The reader supports three different methods of updating the firmware:

• Update using a USB drive.

• File-based update that allows uploading the firmware files from the PC (or a network location) to the reader
and running the update.
• FTP / FTPS / SCP server-based update.

For instructions on updating the firmware, see Firmware Upgrade.

Commit/Discard Functionality Changes

Firmware v3.0.35 or later includes a new auto commit functionality that no longer requires the user to manually
commit changes. The Commit/Discard menu was removed.

When the user changes any property and selects Set Properties on the web page, the commit function is
automatically executed in the reader.

Region Configuration Commit

The following steps are an example of how the commit/discard functionality works.

1. In the Configure Region Settings window, select the region from the drop-down menu.

Figure 78 Configure Region Settings

2. Select the Communication Standard, if applicable.

3. Select Frequency Hopping, if applicable.

121
 Administrator Console

4. Select the appropriate channel(s), if applicable.

5. Select the I understand check box.
6. Select Set Properties to complete the region selection. The Operation Successful window displays a
Saving. Please wait... message with a progress symbol until the commit completes.

Figure 79 Configure Region Settings, Operation Successful Window

7. When the commit completes, a gray floppy disk icon displays indicating that the commit completed
successfully.

Figure 80 Commit Complete

Floppy Disk
Icon

8. If after the successful completion of the commit any other action needs to be taken (for example, a reader
reboot), the web page displays the appropriate message above the main setting tab.

122
 Administrator Console

New Property Change Work Flow

The following steps are an example of how the commit/discard functionality works when changing a property.

1. Select Communication > Services. On the Configure Network Settings screen, select a new Web Server or
any other property from the appropriate drop-down menu.

Figure 81 Configure Network Settings

2. Select Set Properties to complete the new selection.

3. The message Saving.Please wait... displays with a progress symbol until the commit completes.

Figure 82 Configure Network Settings, Saving.Please wait... message Window

4. When the commit completes, a gray floppy disk icon displays indicating that the commit completed
successfully.
5. If after the successful completion of the commit any other action needs to be taken (for example, a reader
reboot), the web page displays the appropriate message above the main setting tab.

123
 Administrator Console

Figure 83 Action Message

IMPORTANT With the new version of software, the Discard Functionality option is no longer supported.
Changes automatically commit to the reader.

In addition, the reset reader to factory defaults option was moved to the System
Shutdown/Restart screen shown in Figure 84.

Figure 84 Reset Reader To Factory Defaults

124
 Administrator Console

System Log
The System Log window lists reader log information.
Figure 85 System Log Window

This window offers the following options:

• Apply Filter - Select a filter option from the drop-down menu to view logs for particular process and/or
severity:
• None - Do not apply a filter.
• Minimum Severity - When this option is used, the log severity level filters the log content. Logs having
severity levels equal or above the selected severity display.
• Process Selection - When this option is used, only the logs for the selected process(es) display. More
than one process can be listed, separated by a comma in the Other Process field.
• Minimum Severity & Process Selection - When this option is used, both severity level and process
are used to filter the logs. Only the logs that match the severity level filter and the process filter display.

When you select Process Selection only or Minimum Severity and Process Selection and no process is
specified, by default, logs from RM, LLRP, SNMP, and RDMP are considered and display (severity level must
match, if enabled).

• Minimum Severity - Select the severity level on which to filter.

• Process Selection - Select the types of processes to filter upon.
• Other process - To filter for specific processes, enter the process in this text box using a
comma-separated process list string with no spaces. If the log file is empty for the selected filter option, an
error message appears in the log text area. Select Save to save the filter settings, which persist upon
reader reboot.

125
 Administrator Console

• Log area - Select a radio button for one of the two types of log information offered:
• System Log - Includes the log information generated by the reader internal instructions. This stores up
to 1 MB of log information, and overwrites the oldest logs first. The log information is saved and
restored on proper system reboot (via the Administrator Console).
• Access History - Provides a history log for reader access, including every successful access to the
reader through the Administrator Console.
• Select Refresh Log to refresh the information in the log, or Purge Logs to clear the information.
• To export the system log select System Log from the Export: pull down menu, then select Export File.
This saves the syslog file (and a zip file if there is more than one log file) in the Downloads folder on the
PC.

To export the customer support data file select Customer Support Data File from the Export: pull down
menu, then select Export File. This saves the data file in the Downloads folder on the PC.

Configure System Log

This window configures system log settings. If the system log host is not set (or is not valid), log messages are not
sent.

Figure 86 Configure System Log Window

This window offers the following options:

• Remote Log Server IP - Configures the host IP address to which log messages are sent. IP address
0.0.0.0 indicates that no host is configured.
• Remote Log Server Port - Remote log server listening port. The default port is 514.
• System Log Minimum Severity - The minimum severity above which data is stored in the log file. This
option does not impact remote logging or the logs already stored in the log file.

Select Set Properties to apply the changes. The Operation Successful window displays a Saving. Please wait...
message with a progress symbol until the commit completes.

When the commit completes, a gray floppy disk icon displays indicating that the commit completed successfully.
See Commit/Discard Functionality Changes on page 121 for more information.

126
 Administrator Console

Reader Diagnostics
Select Diagnostics to view the Reader Diagnostics window, which allows running diagnostics and viewing the
diagnostics report.

Figure 87 Reader Diagnostics Window

Selecting Start Diagnostics clears the system log and displays the diagnostics report. The reader reboots when
the diagnostics completes. Return to the Diagnostics window to view the diagnostics report.

To export the diagnostics report to a file, on the System Log window, select Process Selection only in Apply
Filter, de-select all other processes, and in the Other Process text box enter:
rmserver.elf: N-D,llrpserver.elf: N-D

127
 Administrator Console

Shutdown
To protect the integrity of the reader data, gracefully reboot the reader via the Administrator Console when
necessary.

Figure 88 System Shutdown/Restart Window

To shut down or restart the reader:

1. Select the Shutdown link to display the System Shutdown/Restart window.

2. Check the Please Confirm check box to accept the system shut down and/or restart the system (this may
interrupt normal system operation).
3. Select one of the following options from the What do you want to do drop-down list:
• Restart Reader - saves the user data and then restarts.
• Shut down Reader server - the reader saves the user data, stops all reader functions, and waits to be
powered off.
4. Select Go.

This window also provides an option to enable or disable the reader watchdog.

The Enterprise Reset option clears all the customized user settings including the configuration and the installed
application in the reader. The license related information is preserved after the Enterprise reset. The Enterprise
reset will cause the reader to reboot.

128
Configure and Connect via
Wi-Fi and Bluetooth

Wireless Network Advanced Configuration

The FX Series uses the wpa_supplicant application to connect with wireless networks. Advanced users can place
their own configuration file in the /apps folder to connect to wireless networks. This configuration file is
wpa_supplicant.conf. The parameters of this file are well documented in the public domain. Refer to
http://linux.die.net/man/5/wpa_supplicant.conf for the most commonly used parameters and
http://www.daemon-systems.org/man/wpa_supplicant.conf.5.html for all available parameters.
Also see Appendix , Copying Files To and From the Reader for instructions on copying files to /apps directory.

If /apps/wpa_supplicant.conf is present in the reader, the reader uses this file to connect to a wireless network.
This supersedes the configuration in the Administrator Console, which changes to reflect the custom
configuration file.

Figure 89 Administrator Console Update

There are no text boxes in the user interface for ESSID and password. The console obtains these directly from the
custom configuration file.

129
 Wi-Fi Configuration

Sample Configuration Files

Wireless network with WPA2 encryption type (AP name is "DEV"):
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1

network={
ssid="DEV"
proto=RSN WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="my secret password"
}

Open wireless network (AP Name is DEV_Open):

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
network={
ssid="DEV_Open"
key_mgmt=NONE
}

Wireless network with WEP encryption type (AP Name is WEP128):

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1

network={
ssid="WEP128"
key_mgmt=NONE
wep_key0= "my secret password "
wep_tx_keyidx=0
priority=5
}

130
 Wi-Fi Configuration

Configuration file with multiple network blocks:

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="RFID_TNV"
psk="123456789"
priority=1
}
network={
ssid="RFID_TNV_WPA/WPA2"
psk="123456789"
priority=2
}

Refer to http://linux.die.net/man/5/wpa_supplicant.conf for further examples.

Preferred Configurations for Access Points

The FX Series readers support WPA/WPA2 (http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access) and WEP128
(http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy) by default over the Administrator Console.

Other supported protocols are explained in this guide. Refer to the Access Point configuration manual to configure
the Access Point to one of the following modes that match the reader configuration:

• WPA / TKIP
• WPA1 / CCMP
• WEP128
• Open Network

Figure 90 Example Open Network Mode

131
 Wi-Fi Configuration

Access Point Configuration for Android Device

Open Network
To configure the access point to an open network for an Android device:
1. Enable the wireless tethering from the settings menu.
2. Select Open from the Security drop-down menu.
3. Select Save.

Figure 91 Open Network Configuration for Android Device

WPA2 PSK
To configure the access point to WPA2 PSK for an Android device:
1. Select WPA2 PSK from the Security drop-down menu.
2. Enter a password.
3. Select Save to start the wireless hotspot.

Figure 92 WPA2 PSK Configuration for Android Device

132
 Wi-Fi Configuration

WPA PSK
To configure the access point to WPA PSK for an Android device:
1. Select WPA PSK from the Security drop-down menu.
2. Enter a password.
3. Select Save to start the wireless hotspot.

Figure 93 WPA PSK Configuration for Android Device

Internet Connection Configuration for iPhone

To configure the personal hotspot for an iPhone:
1. Select Setting.
2. Select the Personal Hotspot button to turn on the Internet connection.
3. Enter a password.

Figure 94 iPhone Device

133
 Wi-Fi Configuration

Connecting to a Wireless Network Using a Wi-Fi Dongle

NOTE: The screens in this chapter may differ from actual screens. The applications described may not be
available on (or applicable to) all devices. Procedures are not device-specific and are intended to
provide a functional overview.

To connect to a wireless network using a USB Wi-Fi dongle on the FX7500 and FX9600:

1. Plug the supported wireless dongle into the USB host port on the FX7500 and FX9600. Zebra provides native
support for USB Wi-Fi adapters with the Realtek chipset RTL 8187 and RTL 8812AU. See Table 7 on page 77
for a list of supported Wi-Fi dongles.

Figure 95 FX7500 USB Host Port Location for Dongle

Port 1 Port 2 Port 3 Port 4 GPIO 24 VDC

USB Host Port

Figure 96 FX9600 USB Host Port Location for Dongle

USB
Host

2. To confirm that the Wi-Fi dongle is detected properly, log in to the reader Administrator Console. On the Home
page ensure the USB Port Status displays Device Connected. Hover the mouse pointer over this link to display
the Wi-Fi dongle information shown in Figure 97.

134
 Wi-Fi Configuration

Figure 97 Wi-Fi Dongle Connected

3. Select Communication > Wireless.

Figure 98 Wireless Settings

The Wi-Fi dongle can connect to the wireless network in one of two ways:

• Manually entering the ESSID.

• Scanning the current list of APs and choosing the correct one to connect to.
4. Once the APs are scanned, enter the appropriate passkey and enable Connect Automatically (if required to
connect to the AP automatically if the connection is lost).

135
 Wi-Fi Configuration

Figure 99 Entering Connect Information

5. Select Connect. When the connection to the AP succeeds, an IP is assigned and appears in the
IP Address field.

Figure 100 Assigned IP Address

The reader is now accessible using the wireless IP shown in the IP Address field (157.235.207.24 in this case). The
Wi-Fi interface supports dynamic addressing mechanisms for both IPV4 and IPv6. There is no provision to set a
static IP address.

For wireless IP address details, select Communication > Wi-Fi tab.

136
 Wi-Fi Configuration

Figure 101 Wi-Fi Tab - IPV4

The reader can also be accessed via Wi-Fi using an IPV6 address if supported by the network to which the API is
connected.

Figure 102 Wi-Fi Tab - IPV6 Connecting to a Peer Device over Bluetooth Using a Bluetooth Dongle

137
 Wi-Fi Configuration

Connecting to a Peer Device over Bluetooth Using a Bluetooth Dongle

To connect to a peer device over Bluetooth using a USB Bluetooth dongle on the FX7500 and FX9600:

1. Plug the supported Bluetooth dongle into the USB host port on the FX Reader.
The Zebra FX9600 provides native support for USB Bluetooth dongles based on chipsets CSR8510 and
RT5370L. The following dongles were tested:

Table 13 Supported Bluetooth Dongles

Dongle Model Zebra FX7500 Zebra FX9600

Bluetooth CSR 4.0 dongle Qualcomm / Atheros CSR8510 Yes Yes

Bluetooth 3.0+HS Ralink RT5370L Yes Yes

Asus Mini Bluetooth Dongle USB-BT211 Yes Yes

MediaLink Bluetooth Dongle MUA-BA3 Yes Yes

Figure 103 USB Host Port Location for Dongle

Port 1 Port 2 Port 3 Port 4 GPIO 24 VDC

USB Host Port

2. To confirm that the Bluetooth dongle is detected properly, log in to the reader Administrator Console. On the
Home page ensure the USB Port Status displays Device Connected. Hover the mouse pointer over this link to
display the Bluetooth dongle information.

Figure 104 Bluetooth Dongle Connected Select Communication > Bluetooth.

138
 Wi-Fi Configuration

3. Change the Discoverable and Pairable properties to On.

Figure 105 Changing Discoverable and Pairable Properties

4. Optionally select Use Passkey and enter a passkey to validate the Bluetooth connection. The default passkey
for the FX7500 and FX9600 is 0000.
5. Discover the reader from a Bluetooth-enabled device (such as a laptop). Use the host name to identify the
reader among the discovered devices (for example: FX7500060C17).
6. After a successful connection, right-click the reader icon (for example: FX7500060C17) in the list of Bluetooth
devices and select Connect using > Ad hoc network. This establishes the network connection for later.

Figure 106 Connecting to the Reader

7. The IP address assigned to the Bluetooth interface is 192.168.XX.XX. The last 2 octets are the last 2 octets of
the Bluetooth MAC address (found in the Properties window on the PC once the Bluetooth connection is
established). Also find this in the Communication > Bluetooth page. Both IPV4 and IPV6 based IP address are
supported for adhoc Bluetooth connection between the reader and the client.

139
 Wi-Fi Configuration

Figure 107 Communication Bluetooth Tab

Open the web page or sample application to connect to the Bluetooth IP (192.168.67.21 in Figure 107) and read
tags.

Copying Files to the Reader

The FX7500 and FX9600 RFID readers support the SCP, FTP, and FTPS protocols for copying files.
See Copying Files To and From the Reader for instructions on copying files to /apps directory.

140
Application Development

Introduction
The FX Series RFID readers can host embedded applications, so data can be parsed directly on the reader. Since
data is processed in real time at the network edge, the amount of data transmitted to your back-end servers is
substantially reduced, increasing network bandwidth and improving network performance. Latencies are reduced,
improving application performance. And the integration of data into a wide variety of middleware applications is
simplified, reducing deployment time and cost. The FX Series also provides flexibility for host embedded
applications on the reader or on a separate PC.

141
Firmware Upgrade

Introduction
This chapter provides reader firmware update information on using the web-based Administrator Console. The
following methods are available to update the firmware on the FX Series readers.
• Update using a USB drive.
• File-based update that allows uploading the firmware files from the PC (or a network location) to the reader
and running the update.
• FTP / FTPS / SCP server-based update.
Use this procedure to update the following software components:
• uboot
• OS
• Reader Server Application (includes Radio API and Radio firmware)

Prerequisites
The following items are required to perform the update:
• Reader with power supply or PoE/PoE+ connection
• Laptop (or other host computer)
• An Ethernet cable
• An FTP server
• Current firmware file examples:
• OSUpdate.elf
• response.txt
• u-boot_X.X.X.X.bin (uBoot, X.X.X.X is a filename version)
• uImage_ X.X.X.X (OS, X.X.X.X is a filename variable)
• rootfs_ X.X.X.X.jffs2 (Root FileSystem, X.X.X.X is a filename variable)
• platform_ X.X.X.X.tar.gz (Platform partition, X.X.X.X is a filename variable)
Refer to the release notes to determine which files are updated; not all of the files are updated in every release.

142
 Firmware Upgrade

Failsafe Update
The FX Series readers provide true failsafe firmware updates. Each partition (such as OS and platform) has an
active and backup partition.

The firmware update process always writes the new images to the backup partition. This ensures that any power or
network outages in the middle of firmware update does not prevent the reader from being operational. In the case
of a firmware update failure, the power LED on the reader lights red.

Two-step firmware update

Due to the increase of firmware footprint in some circumstance, a 2-step update is necessary.

Depending on the update method, when upgrading from version 2.6.7 or earlier to an newer version, first upgrade
to 2.7.19, then upgrade to the required version. For example, if the reader current firmware version is 1.2.11 or
2.6.7 and is required to be upgraded to 3.0.35, first upgrade to 2.7.19, and then upgrade to 3.0.35.

Depending on the update method, when downgrading from version 3.0.35 or newer to an older version, first
downgrade to 3.0.35, then downgrade to the required version. For example, if the current version is 3.1.12 and is
required to be downgraded to 2.6.7, first downgrade to 3.0.35, and then downgrade to 2.6.7.

Table 14 summarizes the conditions when a 2-step is needed instead of the normal 1-step update.

Table 14 Firmware Update Support

Reader Update/Downgrade File-Based Update FTP-Based Update USB-Based Update

2.6.7 or earlier to 3.x.x 2-step upgrade 1-step 1-step

Upgrade
2.7.19 to 3.x.x 1-step 1-step 1-step
FX7500
3.x.x to 2.7.19 or earlier 2-step downgrade 2-step downgrade 2-step downgrade
Downgrade
3.x.x to 3.x.x 1-step 1-step 1-step

2.6.7 or earlier to 3.x.x 2-step upgrade 1-step 1-step

Upgrade
2.7.19 to 3.x.x 1-step 1-step 1-step
FX9600
3.x.x to 2.7.19 or earlier 2-step downgrade 2-step downgrade 2-step downgrade
Downgrade
3.x.x to 3.x.x 1-step 1-step 1-step

File-Based Update: The reader is updated with the web interface by using the file-based update instead of FTP update. This
method is also applicable to 123RFID application when the file-based option is used.

FTP-Based Update: The reader is updated with the web interface by using FTP or FPTS update. This method is also
applicable to 123RFID application when the FTP-based option is used.

USB-Based Update: This method uses an USB thumb drive.

1-step: The upgrade/downgrade is supported as usual.

2-step upgrade: Applicable to the file-based method, to upgrade to version 2.7.19 first and then upgrade to the latest 3.x.x
version.

2-step downgrade: Applicable to the file-based method, to downgrade to version 3.0.35 first and then to 2.7.19 or the earlier
version.

3.x.x: Any firmware version 3 followed by any major or minor number.

143
 Firmware Upgrade

NOTE: After the reader firmware is upgraded/downgraded from/to any other version prior to 3.0.35, some UI
pages will not work properly due to cache. Refresh the browser to update the browser web page after update or
downgrade.

Update Phases
The firmware update takes place in three phases:

• Phase 1 - The reader application retrieves the response.txt and OSUpdate.elf files from the ftp server.
• Phase 2 - The reader application shuts down and the OSUpdate starts. The files referenced in the
response.txt file are retrieved from the FTP server and written to flash.
• Phase 3 - The reader resets after all partitions update successfully. It may also update the RFID firmware if
it detects a different version in the platform partition.

A typical entry in the Response.txt is:

;platform partition

-t5 -fplatform_1.1.15.0.tar.gz -s8004561 -u8130879

NOTE: The Application Server, Radio API, and Radio firmware code all reside in the Platform partition.

The -t parameter is the file type, -f is the name of the file, and -s the size. Ensure the file size is correct.
";" comments out the rest of the line.

144
 Firmware Upgrade

Updating FX Series Reader Software

Verifying Firmware Version
To verify that the FX7500 and FX9600 reader firmware is outdated:

1. Log into the reader. In the User Login window, enter admin in the User Name: field and enter change in the
Password: field.

Figure 108 User Login Window

2. Select Firmware on the left side panel to verify that the current version of reader software is outdated (for
example, 1.1.66).

Figure 109 Firmware Version Window

Firmware option

Version
Number

145
 Firmware Upgrade

Updating Methods
Download the reader update files from www.zebra.com/support:, then use one of three methods to update the
reader software to a later version, e.g., 1.1.45.0 or higher:
• Update Using a USB Drive (Recommended)
• File-Based Update on page 147
• FTP-Based Update on page 150

Update Using a USB Drive (Recommended)

1. Copy all reader update files into the root folder of the USB drive.

Figure 110 USB Drive Root Folder

2. Insert the USB drive into the USB host port of the RFID reader.

Figure 111 FX7500 USB Host Port Window

USB Host Port

Port 1 Port 2 Port 3 Port 4 GPIO 24 VDC

Figure 112 FX9600 USB Host Port Window

USB Host Port USB Client Port

USB Host Port

146
 Firmware Upgrade

The reader starts the update process in 5 - 7 seconds, and indicates progress as follows:

• The reader continuously blinks the Power LED red.

• The reader blinks all four LEDs orange once.
• The reader Power LED remains steady orange.
• The reader Power LED settles to a steady green to indicate that the update is complete.

Figure 113 FX7500 Reader LEDs

Power LED

Figure 114 FX9600 Reader LEDs

Power LED

File-Based Update
1. Copy all reader update files into any folder on a host computer.

147
 Firmware Upgrade

Figure 115 Host Computer Folder

2. Log into the reader and navigate to the Firmware Update page.

Figure 116 Firmware Update Window

148
 Firmware Upgrade

3. Select File based Upload.

Figure 117 Firmware Update Window

4. Select Browse and navigate to the folder or files that contains the firmware update files.

Figure 118 Browsing Update Folders

149
 Firmware Upgrade

Figure 119 Browsing Update Files

5. Select all the files.

6. Select Start Update. The reader starts the update process and displays the update status as follows:
• The reader continuously blinks the power LED red.
• The reader blinks all four LEDs orange, one time.
• The reader power LED remains steady orange.
• The reader power LED remains solid green to indicate that the update is complete.
7. When the update completes, the reader reboots and returns to the login screen.

FTP-Based Update
Copy all the update files into an appropriate FTP location.

1. Log into the reader and navigate to the Firmware Update page.

Figure 120 Firmware Update Window

2. Select FTP/FTPS Server.

150
 Firmware Upgrade

3. Enter the FTP location where the files are located.

4. Enter the User Name and Password for the FTP server login.
5. Select Start Update. The reader starts the update process and displays the update status as follows:
• The reader continuously blinks the Power LED red.
• The reader blinks all 4 LEDs orange once.
• The reader Power LED remains steady orange.
• The reader Power LED settles to a steady green to indicate that the update is complete.
6. When the update completes, the reader reboots and returns to the FX login screen.

Verifying Firmware Version

To verify reader update success:

1. Log into the reader. In the User Login window, enter admin in the User Name: field and enter change in the
Password: field.

Figure 121 User Login Window

2. Select Firmware on the left side panel to verify that the current version of reader software is the new version
number, e.g., 1.1.68, which indicates that the update was successful.

151
 Firmware Upgrade

Figure 122 Firmware Version Window

Version
Number

152
EtherNet/IP

Introduction
This chapter provides the overview of EtherNet/IP for FX9600 RFID Reader.

EtherNet/IP
EtherNet/IP (IP = Industrial Protocol) is an industrial network protocol that adapts the Common Industrial Protocol
(CIP) to standard Ethernet. EtherNet/IP uses both of the most widely deployed collections of Ethernet standards -
the Internet Protocol suite and IEEE 802.3 - to define the features and functions for its transport, network, data link
and physical layers. EtherNet/IP performs at level session and above (level 5, 6 and 7) of the OSI model. CIP uses
its object-oriented design to provide EtherNet/IP with the services and device profiles needed for real-time control
applications and to promote consistent implementation of automation functions across a diverse ecosystem of
products (go to https://en.wikipedia.org/wiki/EtherNet/IP for more details).

Zebra FX9600 RFID Reader supports EtherNet/IP for the industrial automation purposes. EtherNet/IP for FX9600
RFID reader is provided as a licensed feature (see FX Series Licensing Mechanism on page 99 for more
information), through which PLCs can connect with the reader and perform RFID operations.

EtherNet/IP for FX9600 RFID reader is packaged with the reader firmware image and provided as an installable
application package. Users can install the EtherNet/IP application when enabling license from packaged version
available with firmware itself. Users can also install the EtherNet/IP application as the installable Debian package.
After install the application in the reader, users can Start/Stop it at the User Application Page window (see Figure
75 on page 116). The EtherNet/IP application enables the EtherNet/IP protocol adapter and uses standard
EtherNet/IP port 2222 and 44818 to communicate with readers via PLC.

Using EtherNet/IP
Ethernet/IP is enabled through the installable application as mentioned above. Users can Start/Stop the application
from the web console as per the requirement. See Applications on page 116 for more details.

EtherNet/IP application consists two parts:

• EtherNet/IP protocol stack: Communicates with other EtherNet/IP devices.

• RFID3 API: Communicated with LLRP for RFID operations.

Basic architecture of EtherNet/IP is explain in Figure 123.

153
 Firmware Upgrade

Figure 123 EtherNet/IP Application Block Diagram

PLC

Ethernet

EtherNet/IP
Application EtherNet/IP protocol
Stack

RFID 3 API

LLRP/TCP

RFID Radio
Module

Supported RFID Operations Through EtherNet/IP:

EtherNet/IP in FX9600 RFID Reader supports both implicit and explicit operations. Below is the list of implicit and
explicit operations which can be performed through EtherNet/IP.

Implicit Operations:

These are the synchronous operations to perform certain RFID operation. Each implicit/synchronous operation has
its corresponding reply which is executed per connection with configured RPI.

• Inventory Operation: Through this, user can perform inventory operation and get TAG data as reply of the
operation.
• Access Operation: Through this, user can perform Access operation on the TAGs and read memory bank
data which is received as reply packets.

Explicit Operations:

These are the asynchronous operation which can be executed as per the requirement. Explicit operations are
implemented to configure the reader with RFID parameters according to the end-user use case. Below are the
supported explicit operations which can be used to get and set the RFID configuration parameters from/to readers.

• Reader Capabilities: This operation reads the reader capabilities.

• Profile List: This operation is to get count and the name of the profiles installed in reader and also to
change the active profile through the EtherNet/IP interface itself. Reader configuration profiles can be
customized and activated via the reader web interface. This is useful when a EtherNet/IP data model does
not support a use case. In such case, it is possible to set the reader configuration via the reader profile
instead. Besides, once a custom profile is loaded in the reader via reader web interface, the custom profile
can be chosen via EtherNet/IP.

NOTE After changing active profile in a reader using this explicit operation, reset the reader for EtherNet/IP to
perform operation specified in the custom profile.

154
 Firmware Upgrade

• Antenna Configuration: The RFID antenna configuration can be modified using this explicit message
command. Parameters such as Sel, Session, Target, RF Mode, Tari, TAG population and Antenna Power
can also be configured.
• Pre-Filter Configuration: This explicit message is used to Add/Delete pre-filter for consecutive RFID
operation. Pre-filter has parameters such as Antenna ID, Memory Bank, Target, Action, Tag Pattern etc.
which is used to perform the RFID operation on specific group of TAGs.
• Post-Filter/Access-Filter Configuration: Post-filter is used to apply filtering on the tags received from
RFID radio module at API level. Access filter is used to apply filtering for access operation. This
configuration is used as the post-filter for inventory operation and as the Access filter for access operation.
Post/Access filter can be configured with parameters such as two sets of Tag Pattern for a specific
memory bank, match pattern criteria, and RSSI range filtering.
• Trigger Configuration: This explicit operation is to configure triggers and report criteria for a RFID
operation. Through this command, parameters such as start/stop triggers, event reporting, and periodic
reporting can be configured.
• GPIO Configuration: FX9600 RFID reader has external GPI and GPOs which can be configured using
this explicit message. GPI can be enabled/disabled and GPO values can be read via EtherNet/IP interface
with this configuration.
• Event Report: Users get the event information which is generated during the RFID operation through this
explicit message.The event can be form the GPI event, antenna event, temperature event or reader
exception event.

EtherNet/IP Package Content:

Detailed information for the EtherNet/IP data model supported by the FX9600 RFID reader, Sample Application
and other components are available at Zebra Support Central. The package includes:

• The EtherNet/IP application for FX9600 as a Debian package. The EtherNet/IP stack installed by the
Debian package is already available in the reader out of the box. Zebra provides updates on the support
site.
• Zebra FX9600 AOP for Studio 5000.
• EtherNet/IP Sample project for Studio 5000.
• The Sample Application user guide.
• Detailed Data Model document.
• Exported RUNGs and Data types from sample project to use with the older version of Studio 5000.

NOTE Our sample application project is created with Studio 5000 v32 and to work with CompactLogix
5069-L306ER PLC.

155
Cellular Connectivity with
Sierra Modem

Introduction
This chapter describes the configuration of Sierra Modem RV50X to provide cellular connectivity for Zebra FX9600
RFID Reader.

Cellular Connectivity with Sierra Modem

Figure 124 Cellular Connectivity with Sierra Modem

Sierra RV50X with GPS

receiver
Remote location or mobile truck

GPS data in RFID/GSP

Data out

Inventory
RFID antenna Ethernet Port

RFID data
RFID reader

Zebra FX9600 RFID Reader is enabled with cellular connectivity through Sierra Modem RV50X. The data from the
reader is send to the cloud via the Sierra Modem which has Global coverage 3G/4G LTE (Cat 6). The modem
requires a GNSS compatible antenna connected to the RV50X. This has been tested with the antenna AIRLINK®
ANTENNA: 3-IN-1 SHARKFIN. Zebra FX9600 RFID Reader along with RV50X is enabled to provide the GPS
coordinates.

This feature enables the following asset tracking features:

• Remote locations (e.g. Refinery plant)

• Delivery/Trucking Industries.

156
 Firmware Upgrade

Steps to Configure RV50X

Step 1: Configure RV50 for sending GPS coordinates.
• The GPS/Cellular cable from the antenna must be connected to RV50.
• To get GPS coordinates, users do not need a SIM card.
• Power on RV50 with the given power adapter.
• Connect RV50 to the PC for configuration. For more details on the RV50X configurations, go to:
https://www.scribd.com/document/448523280/4117313-AirLink-RV50-Series-Hardware-User-Guide-r5-pdf

Follow the configuration below to receive GPS data from RV50 modem.

Use the 10001 port for configuration. Follow the same configuration in the screen shots below. Connect to
ACEManager and log in with username: admin and password: 1234.

1. Status page

157
 Firmware Upgrade

2. Local/Streaming settings on the GPS Location page.

158
 Firmware Upgrade

3. WAN/Cellular page

4. Server settings on Location page. Defaults values used in this page.

159
 Firmware Upgrade

5. Serial settings on the Serial page

• Connect the serial cable (RS232) to host m/c.

• Open tera term, enter the correct serial port number and select connect.
• The coordinate messages is populated in the tera term automatically.

NOTE If the coordinates are not received, keep trying at different locations (preferably at open spaces).

Step 2: Connect RV50 with the Reader

• Connect the RV50 and Reader through the Ethernet cable.
• Power on RV50 (Ensure to complete all the configurations in Step1).

Step 3: Configure LLRP for GPS coordinates (This is also supported in RFID3 APIs):
• Enable GPS in ROReportSpec as follows:

<moto:MotoTagReportContentSelector>
<moto:EnableGPS>true</moto:EnableGPS>
</moto:MotoTagReportContentSelector>
Example of GSP meta data reported in LLRP:

<moto:MotoTagGPS>
<moto:longitude>776816</moto:longitude>
<moto:latitude>129245</moto:latitude>
<moto:altitude>9140000</moto:altitude>
</moto:MotoTagGPS>

160
 Firmware Upgrade

Steps to send reader data to cloud using Sierra Modem.

An easy way to send the reader data in public network via the sierra modem to cloud is by configuring the reader in
FX Connect HTTP post.

Step1: Configure the reader in HTTP post.

This is a licensed feature. Select the HTTP post from the FX Connect page. The server IP address to which the tag
data are posted should be in the URL field (see Figure 53 on page 84). The port number should be mentioned
along with the server IP, such as https://10.17.131.52:8081. See FX Connect on page 82. Please refer FX Connect
section of this document.

Step 2: There should be a server program running in the server which listens to the data posted by the
reader. The code below must be saved as a python file such as postServer.py and should be run in the
server.

from flask import Flask, request

app = Flask(__name__)

@app.route('/', methods = ['POST', 'GET'])

def message():
if request.method == 'POST':
app.logger.info('Request received.')
app.logger.info('Url: %s', request.url)
app.logger.info('Data: %s', (request.data).decode('utf-8'))
app.logger.info('Is JSON: %s', request.is_json)
else:
app.logger.info('GET request received.')
return 'OK\n'

if __name__ == '__main__':
app.run(host='0.0.0.0', port='8080', debug=1)

161
SOTI MOBI Client

Introduction
This chapter provides information on SOTI Mobicontrol and includes references to the appropriate guides.

SOTI MOBI Client

SOTI Mobicontrol is an enterprise mobile management solution to help user in managing and monitoring enterprise
devices.
Lists of supported APIs are as follows:

• Zebra Configuration:
• API setup
• Agent specific to Zebra
• Run time password change to access API
• Fix for HTTPS communication.
• Application life cycle management:
• Install application through packages.
• Uninstall applications.
• Installed Applications information panel.
• Identify whether an application is set to as auto start (as a custom application property in the
information panel).
• Actions:
• Soft Reset
• Firmware update
• Remote Maintenance:
• Remote Zebra Web Console access
• Remote terminal access
• File Transfer
• Alerts and actions
• Out of Contact payload.

162
 Firmware Upgrade

• Implemented custom data through Zebra APIs

• CPU Utilization
• Up time
• Connectivity type
• Time Zone
• Capture LLRP Server IP in client Mode
• Reader name
• Reader Serial number
• Location
• Radio Firmware Version
• Flash Available
• Ram Total
• Ram Used
• Ram Available
• Ram Info.
• Implemented custom data through Zebra APIs
• LLRP Server IP
• Ambient Temperature High Alarm Count
• Ambient Temperature Critical Alarm Count
• PA Temperature High Alarm Count
• PA Temperature Critical Alarm Count
• Forward Power High Alarm Count
• Forward Power Low Alarm Count
• Reverse Power High Alarm Count
• Echo Threshold Alarm Count
• Database Warning Count
• Database Error Count
• PIO Information Count
• Reader IP Address
• Device Info
• Client IP Address.

For the SOTI MOBI CONTROL help, go to https://www.soti.net/mc/help/v15.0/en/setup/setupindex.html.

By accessing the device info or properties and displaying it on Web console, users can generate alert and perform
an action based on these device properties. For more details, go to:
https://discussions.soti.net/kb/configuring-custom-data-on-zebra-fx7500-9600-1/.

For firmware upgrade, go to:

https://discussions.soti.net/kb/upgrading-zebra-fx7500-9600-firmware-from-mobicontrol.

To have more information on Remote Control (Web Console and Terminal access), go to:
https://discussions.soti.net/kb/take-remote-control-of-your-linux-devices.

163
 Firmware Upgrade

To have more information on Enrollment Utility for Zebra device to enroll in MobiControl, go to:
https://discussions.soti.net/kb/enrol-multiple-zebra-rfid-devices-using-zebra-rfid-enrolment-utility-1.

For troubleshooting, go to:

https://discussions.soti.net/kb/not-able-to-access-device-apis-exposed-by-zebra-fx7500-9600-via-custom-data/?p
ostbadges=true.

164
Gen2 V2 Enhancement

Introduction
This chapter describes the Gen2V2 commands supported by the FX Series RFID Reader.

Gen2 V2 Enhancement
The LLRP and RFID3 APIs extensions add four new access commands to support the GS1 Gen2 V2 standard
features. For more details on the following list of commands, go to:
https://www.gs1.org/standards/epc-rfid/uhf-air-interface-protocol.

• Authenticate:
• The Gen2 V2 standard command supports a variety of cryptographic suites.
• The end user application can perform tag authentication.
• ReadBuffer:
• The Gen2 V2 standard command reads response data of Authentication command.
• Untracable:
• The Gen2 V2 standard command hides a whole or partial tag memory bank for security and/or reading
efficiency.
• The Tag operation range can be reduced for security.
• Crypto:
• NXP custom extension uses ISO/IEC 29167-10 (AES-128) Crypto Suite.
• Contact NXP to get document 286910 How to use UCODE AES.

Above commands are tested with tags that have the following tag identifiers (TIDs)

• E2C06892200042021F0B3C21 (NXP DNA tag)

• E2C06F922000000200105CB3 (NXP AES tag)

Contact Zebra for a sample application.

165
Reader Configuration via
USB Thumb Drive

Introduction
This chapter provides the steps to transfer a reader configuration to another reader via a USB thumb drive.

Reader Configuration via USB Thumb Drive

A USB thumb drive can be used to transfer the reader configuration from one reader to another reader. More
specifically, swapping a reader is now very simple if a physical access to the reader is possible. This process
assumes reader is functional via the USB host port. At a high level, the use case and the work flow is as follows:

• The use case is when a reader replacement is required, a new reader is available to replace it.
• Copy the configuration from the reader to be replaced by using a USB flash drive.
• Reset the new reader and effectively assume the role of the replaced reader.

To enable this work flow, user must have a USB flash drive. The details are as follows:

1. Create a special XML control file in a USB flash drive:

a. Format the USB thumb drive using FAT.
b. Create a USBCommand directory in root.
c. Create a XML file with the file name USBCommand.xml.
d. Copy the following XML excerpt to the USB drive. The file directory is
/USBCommand/USBCommand.xml

<FX_USB_COMMAND>

<command name="configuration_one_to_one">

<Input>reader_to_usb</input>

<state></state>

<output></output>
</command>

</FX_USB_COMMAND>

2. The old reader retrieves (the reader APP LED blinks yellow) the XML control file when USB flash drive is
inserted.

166
 Reader Configuration via USB Thumb Drive

3. The old reader copies its configuration file AdvReaderConfig.xml to the USB flash driver. It is safe to
disconnect drive when yellow LED turns off.
4. The new reader parses the control file then loads the older reader configuration (the reader APP LED blinks
green for 10 seconds).
5. After the APP green LED turns off, restart the reader manually. It is safe to keep the USB flash drive connected
while the reader resets.
6. If there is an update issue, the APP LED blinks red for 10 seconds. Logs are written to the USB flash drive.
USB flash drive can be removed after the red APP LED stops blinking.

IMPORTANT: The used XML control file in the USB thumb drive cannot be used for a second new reader. Users
must always create a new XML control file (see Step 1 on page 166) in the USB flash drive to
transfer a reader configuration to each new reader.

167
GPS and Triggers for
Trucking and Delivery

Introduction
This chapter explains the GPS feature and three new added triggers for trucking and delivery.

GPS and New Triggers For Trucking and Delivery Use Cases
This feature requires that the reader must have a cellular connectivity for the RFID data and GPS data to be sent to
the cloud (see Cellular Connectivity with Sierra Modem on page 156).

With the cellular connectivity, the readers can send the RFID data and GPS data to the cloud at the instant they are
created. In addition, GPS data are updated only when vehicle moves This prevents transmission of redundant GPS
data if vehicle is not moving and RFID operations are enabled.

Deliver Driver Use Case

1. A delivery driver carrying baked goods in a van stops at 5 bakeries each morning to deliver fresh product.
2. The van is loaded up in the morning at a central warehouse. When the van door is open, the reader mounted
on the van is triggered by a GPI trigger makes to start tracking what product is going through each dock door
and on to the van.
3. The driver leaves the warehouse. GPS data is captured as part of the tag meta data.
4. Every x seconds/minutes the reader takes an inventory. GPS data is captured.
5. When driver gets to each bakery to deliver product, driver opens the door and the reader will perform another
inventory (GPI triggered). GPS data is captured.
6. Driver finishes delivery and continues on to the next bakery. Inventory is taken and GPS data is captured.
7. Repeat steps 4-6.

Government/Military Use Case

1. A convoy carrying top-secret tagged assets leaves the remote facility.
2. When truck door is opened, a GPI trigger makes reader starts capturing data reader boots up. GPS data is
captured.
3. After y km of travel distance, the reader takes an inventory to ensure assets are still with the convoy. GPS data
is captured.

Trucking Company Use Case

1. The tractor-trailer is loaded with product at a central warehouse.
2. The reader mounted in warehouse dock door tracks what gets loaded in the truck.

168
 GPS and Triggers for Trucking and Delivery

3. The reader mounted in the truck starts an inventory cycle at specific time of day (no date can be specified).
4. The truck completes delivery route, taking GPS readings at regular time intervals and returns to the warehouse
at 4PM.

There are 2 new start triggers and 1 stop trigger:

• Time lapse start trigger:

• Specific time of day (for example, 8:00am EST)
• Certain period (second unit, for example 10 seconds).
• GPS distance start trigger:
• Inventory starts after x km of moving.
• Time lapse stop trigger:
• Specific total duration (for example, 14400 seconds (4 hours to 2:00PM))
• Certain periodic duration (second unit, for example 5 seconds).

The new triggers can work along side existent/older triggers. For example, a GPI trigger (old trigger) can be
combined to work with the new time lapse stop trigger.

Table 15 shows the matrix of supported trigger combinations.

Table 15 Supported trigger combinations matrix

Stop Trigger

No Stop Duration1 Tag Attempt with GPI4 Time lapse

Trigger Observation Timeout3 Stop
defined or with Trigger5
configured Timeout2

Immediate6 Not
supported

GPI7 * Supported Supported

Periodic8 Not
Start Supported
Trigger
Time lapse Supported * * * Supported Supported
Start
Trigger9

Distance10 Supported * * * Supported Supported

1. (LLRP) ROSpecStopTrigger.DurationTriggerValue; (RFID3 API) STOP_TRIGGER.value.duration

2. (LLRP) AISpecStopTrigger.TagObservationTrigger.NumberOfTags; (RFID3 API) STOP_TRIGGER.value.tagObservation
3. (LLRP) AISpecStopTrigger.TagObservationTrigger.NumberOfAttempts; (RFID3 API) STOP_TRIGGER.value.numAttempts
4. (LLRP) AISpecStopTrigger.GPITriggerValue; (RFID3 API) STOP_TRIGGER.value.gpi
5. (LLRP) ZebraROSpecStopTrigger.ZebraTimelapseStop; (RFID3 API) STOP_TRIGGER.value.timelapse
6. (LLRP) ROSpecStartTrigger.ROSpecStartTriggerType.Immediate; (RFID3 API)
START_TRIGGER.type.START_TRIGGER_TYPE_IMMEDIATE
7. (LLRP) ROSpecStartTrigger.GPITriggerValue; (RFID3 API) START_TRIGGER.value.gpi
8. (LLRP) ROSpecStartTrigger.PeriodicTriggerValue; (RFID3 API) START_TRIGGER.value.periodic
9. (LLRP) ZebraROSpecStartTrigger.ZebraTimelapseStart; (RFID3 API) START_TRIGGER.value.timelapse

169
 GPS and Triggers for Trucking and Delivery

10. (LLRP) ZebraROSpecStartTrigger.ZebraDistance; (RFID3 API) START_TRIGGER.value.distance

* Trigger combination currently not supported.

Specific examples of trigger configuration

Single trigger pair: Timelapse Start/Timelapse Stop

Configuration:

Start trigger [Time of Day: “08:24:00”, Period: 10 seconds]

Stop trigger [TotalDuration: 14880 seconds (4 hours 8 minutes, on “16:32:00”), PeriodicDuration: 5 seconds]

Expected:

If time is lesser than “08:24:00”, OR greater than “16:32:00”, there is no inventory.

If time is greater than “08:24:00”, AND lesser than “16:32:00”, reader does inventory 5 seconds per 10 seconds.

Figure 125 Single Trigger Pair: Timelapse Start/Timelapse Stop

Single trigger pair: Timelapse Start/Timelapse Stop (TotalDuration = 0)

Configuration:

Start trigger [Time of Day: “08:24:00”, Period: 10 seconds]

Stop trigger [TotalDuration: 0 second, PeriodicDuration: 5 seconds]

Expected:

If time is lesser than “08:24:00”, there is no inventory.

If time is greater than “08:24:00”, reader does inventory 5 seconds per 10 seconds without termination.

Since TotalDuration is zero, inventory cycles repeat periodically indefinitely.

Figure 126 Single Trigger Pair: Timelapse Start/Timelapse Stop (TotalDuration = 0)

170
 GPS and Triggers for Trucking and Delivery

Single trigger pair: Timelapse Start/Timelapse Stop (Period = 0, PeriodicDuration = 0)

Configuration:

Start trigger [Time of Day: “08:24:00”, Period: 0 seconds]

Stop trigger [TotalDuration: 14880 seconds (4 hours 8 minutes, on “16:32:00”), PeriodicDuration: 0 second]

Expected:

If time is lesser than “08:24:00”, OR greater than “16:32:00”, there is no inventory.

If time is greater than “08:24:00”, AND lesser than “16:32:00”, reader does inventory constantly.

Figure 127 Single Trigger Pair: Timelapse Start/Timelapse Stop (Period = 0, PeriodicDuration = 0)

Single trigger pair: Timelapse Start/Timelapse Stop (Period = 0, TotalDuration = 0, PeriodicDuration = 0)

Configuration:

Start trigger [Time of Day: “08:24:00”, Period: 0 seconds]

Stop trigger [TotalDuration: 0 second, PeriodicDuration: 0 second]

Expected:

If time is lesser than “08:24:00”, there is no inventory.

If time is greater than “08:24:00”, reader does inventory constantly without termination.

Figure 128 Single Trigger Pair: Timelapse Start/Timelapse Stop (Period = 0, TotalDuration = 0, PeriodicDuration
= 0)

171
 GPS and Triggers for Trucking and Delivery

Single trigger pair: Displacement Start/Timelapse Stop

Configuration:

Start trigger (Distance: value 2 km)

Stop trigger [TotalDuration: 14880 seconds (4 hours 8 minutes), PeriodicDuration: 5 seconds]

Expected:

When reader moves 2 km, will do inventory 5 seconds till duration over 14880 seconds (count 4 hours 8 minutes
from trigger’s creation). In below graph th horizontal line represents time. Truck displacement of 2K in time varies.

Figure 129 Single Trigger Pair: Displacement Start/Timelapse Stop

Single trigger pair of Distance/Timelapse (TotalDuration = 0)

Configuration:

Start trigger (Distance: value 2 km)

Stop trigger [TotalDuration: 0 seconds (4 hours 8 minutes), PeriodicDuration: 5 seconds]

Expected:

When reader moves 2 km, will do inventory 5 seconds

Since TotalDuration is zero, inventory cycles repeat periodically indefinitely.

In below graph the horizontal line represents time. Truck displacement of 2K in time varies.

Figure 130 Single Trigger Pair of Distance/Timelapse (TotalDuration = 0)

172
 GPS and Triggers for Trucking and Delivery

Two trigger pair: GPI Start/GPI Stop; Timelapse Start/No Stop

GPI trigger has higher prioritiy, and it can preempt Timelapse trigger.

Priority is determined by the order of trigger configuration. First trigger configured gets higher priority.

Configuration:

First trigger pair (high priority)

Start trigger (GPI1: low value)

Stop trigger (GPI1: high value)

Second trigger pair (low priority)

Start trigger [Time of Day: “08:24:00”, Period: 0 seconds]

Stop trigger [TotalDuration: 0 second, PeriodicDuration: 0 second]

Expected:

After 8:24AM, reader begins inventory due to second trigger.

The high priority GPI trigger can preempt the low priority timelapse trigger.

Figure 131 Two Trigger Pair: GPI Start/GPI Stop; Timelapse Start/No Stop

173
 GPS and Triggers for Trucking and Delivery

Two trigger pair: Timelapse Start; GPI Start/GPI Stop

GPI (second trigger) has lower priority, and it can’t preempt Timelapse (first).

Configuration:

First trigger pair (high priority)

Start trigger [Time of Day: “08:24:00”, Period: 0 seconds]

Stop trigger [TotalDuration: 0 second, PeriodicDuration: 0 second]

Second trigger pair (low priority)

Start trigger (GPI1: low value)

Stop trigger (GPI1: high value)

Expected:

After 8:24AM, reader begins inventory due to the first trigger.

The low priority GPI trigger can’t preempt the high priority timelapse trigger.

Figure 132 Two Trigger Pair: Timelapse Start; GPI Start/GPI Stop

174
Moving and Stationary
Tags

Introduction
This chapter recommends the settings in LLRP and RFID3 APIs to read the moving and stationary tags.

Moving vs Stationary
Some use cases require to monitor moving and stationary tags in a read zone which are defined by strategically
installed antennas. This feature does not report tag direction, but provides information if new tags come in, return,
or leave the monitored zone. An application can also query tags that are detected as not moving by the reader. If
the tag direction through a transition point is required, users can consider the transition readers offered by the
SmartLens solution.

This feature can be enabled and leveraged via LLRP and RFID3 APIs.

This feature works reliably if the read zone does not have stray tags that are hard to read. Reader configuration
can minimize reporting stray tags as moving tags.

Assuming that the environment does not have stray tags (the environment can have static tags that are
consistently read), see the following recommendations:

• If the number of stationary tags is large (> 500) and the number moving tags through the read zone is
small (< 10), it is recommended to set the new tag event moderated timeout (LLRP:
NewTagEventModeratedTimeout; RFID3: newTagEventModeratedTimeoutMilliseconds) value to 3
seconds. The stray tag moderate timeout (LLRP: StrayTagModeratedTimeout; RFID3:
tagStationaryModeratedTimeoutMilliseconds) should be set to 6 seconds.
• If the number of stationary tags is large (> 500) and the number moving tags through the read zone is
large, (> 100) it is recommended to set the new tag event moderated timeout (LLRP:
NewTagEventModeratedTimeout; RFID3: newTagEventModeratedTimeoutMilliseconds) value to 3
seconds. The stray tag moderate timeout (LLRP: StrayTagModeratedTimeout; RFID3:
tagStationaryModeratedTimeoutMilliseconds) should be set to 6 seconds.
• If the number of stationary tags is small (< 100) and the number moving tags through the read zone is
large, (> 100) it is recommended to set the new tag event moderated timeout (LLRP:
NewTagEventModeratedTimeout; RFID3: newTagEventModeratedTimeoutMilliseconds) value to 1
second. The stray tag moderate timeout (LLRP: StrayTagModeratedTimeout; RFID3:
tagStationaryModeratedTimeoutMilliseconds) should be set to 6 seconds.
• If the number of stationary tags is small (< 100) and the number moving tags through the read zone is
small (<10), it is recommended to set the new tag event moderated timeout (LLRP:
NewTagEventModeratedTimeout; RFID3: newTagEventModeratedTimeoutMilliseconds) value to 1

175
 Moving and Stationary Tags

second. The stray tag moderate timeout (LLRP: StrayTagModeratedTimeout; RFID3:

tagStationaryModeratedTimeoutMilliseconds) should be set to 6 seconds.
• If the read zone contains stray tags that are hard to read, it is recommended to remove them from the
zone.

To minimize the possibility of reporting stray tags as moving tags, the following guidelines may help:

• Set the stray tag moderate timeout (LLRP: StrayTagModeratedTimeout; RFID3:

tagStationaryModeratedTimeoutMilliseconds) to a larger value (for example, greater than 10 seconds).
The side effect of larger timeout value is that the report is delayed
• Set the new tag moderated timeout (LLRP: NewTagEventModeratedTimeout; RFID3:
newTagEventModeratedTimeoutMilliseconds) to greater than 5 seconds.

LLRP Configuration

This feature can be configured in the MovingStationaryTagReport parameter. This parameter has two fields to
be configured. The ReportMovingTag field can enable/disable moving tag reporting event. The
StrayTagModeratedTimeout field sets timeout in milliseconds for the change of tag from moving state to
stationary state. The timeout value needs optimization as described earlier. The MovingStationaryTagReport
parameter is a custom parameter of ROReportSpec.

<customParameterDefinition name="MovingStationaryTagReport"

<fieldtype="u8" name="ReportMovingTag "enumeration="TagEventSelectorReportMovingTag"/>

<fieldtype="u16" name="StrayTagModeratedTimeout"/>

<allowedIntype="ROReportSpec" repeat="0-1"/>

</customParameterDefinition>

<customEnumerationDefinition name="TagEventSelectorReportMovingTag">

<entry value="0" name="Disable"/>

<entry value="1" name="Enable"/>

</customEnumerationDefinition>

The new tag moderated timeout parameter also plays an important role as described earlier.

For this feature, the following moderated timeout settings affect the result.

It is recommended to set the tag invisible moderated timeout to 3 seconds.

176
 Moving and Stationary Tags

It is recommended to set the tag visibility change moderated timeout to 1 second.

<customParameterDefinition name="MotoTagEventSelector">

<field type="u8" name="ReportNewTagEvent"

enumeration="MotoTagEventSelectorReportNewTagEvent"/>

<field type="u16" name="NewTagEventModeratedTimeout"/>

<field type="u8" name="ReportTagInvisibleEvent"

enumeration="MotoTagEventSelectorReportTagInvisibleEvent"/>

<field type="u16" name="TagInvisibleEventModeratedTimeout"/>

<field type="u8" name="ReportTagVisibilityChangeEvent"

enumeration="MotoTagEventSelectorReportTagVisibilityChangeEvent"/>

<field type="u16" name="TagVisibilityChangeEventModeratedTimeout"/>

<allowedIn type="ROReportSpec" repeat="0-1"/>

</customParameterDefinition>

LLRP Report

The MotoTagEventTypeEnum enumeration adds 2 new entries Tag_Moving and Tag_Stationary to extend the
event type in tag event report. If TagEventSelectorReportMovingTag is enabled, the Tag Moving event is used to
report tags whenever the New Tag Visible, Tag Not Visible, and Tag Visibility Changed events take place.
Stationary tags can be obtained by sending the GET_REPORT command to the reader. The moving/stationary
event is in TagReportData > MotoTagEventList > MotoTagEventEntry > EventType > Tag_Moving.

<parameterDefinition name="TagReportData">

<choice repeat="1" type="EPCParameter"/>

<parameter repeat="0-1" type="ROSpecID"/>

<parameter repeat="0-1" type="SpecIndex"/>

..........................

<parameter repeat="0-1" type="MotoTagEventList"/>

</parameterDefinition>

<customParameterDefinition name="MotoTagEventList">

<parameter repeat="0-N" type="MotoTagEventEntry"/>

</customParameterDefinition>

177
 Moving and Stationary Tags

<customParameterDefinition name="MotoTagEventEntry">

<field type="u8" name="EventType"

enumeration="MotoTagEventTypeEnum"/>

<field type="u64" name="Microseconds" format="Datetime"/>

</customParameterDefinition>

<customEnumerationDefinition name="MotoTagEventTypeEnum"

namespace="moto">

<entry value="0" name="Unknown"/>

<entry value="1" name="New_Tag_Visible"/>

<entry value="2" name="Tag_Not_Visible"/>

<entry value="3" name="Tag_Visibility_Changed"/>

<entry value="4" name="Tag_Moving"/>

<entry value="5" name="Tag_Stationary"/>

</customEnumerationDefinition>

RFID3 API Configuration

The structure TAG_EVENT_REPORT_INFO adds 2 new member variables. reportTagMovingEvent can

enable/disable this feature. tagStationaryModeratedTimeoutMilliseconds is a timeout setting in milliseconds for
moderating tag stationary status transition. The timeout value needs optimization as described earlier.

typedef enum _TAG_MOVING_EVENT_REPORT

TAG_MOVING_EVENT_DISABLE = 0,/**< Disable moving event reporting. */

TAG_MOVING_EVENT_ENABLE = 1,/**< Enable moving event reporting. */

}TAG_MOVING_EVENT_REPORT;

The new tag moderated timeout parameter also plays a role as described earlier.

For this feature, the following moderated timeouts setting affects the result.

It is recommended to set the tag invisible moderated timeout to 3 seconds.

178
 Moving and Stationary Tags

It is recommended to set the tag visibility change moderated timeout to 1 second.

typedef struct _TAG_EVENT_REPORT_INFO

TAG_EVENT_REPORT_TRIGGER reportNewTagEvent;/**< Report criteria when a new Tag is visible.*/

UINT16 newTagEventModeratedTimeoutMilliseconds;/**< Timeout in milliseconds for moderating new tag

event reporting. Use this only when reportNewTagEvent is set to MODERATED.*/

TAG_EVENT_REPORT_TRIGGER reportTagInvisibleEvent;/**< Report criteria when a Tag is invisible.*/

UINT16 tagInvisibleEventModeratedTimeoutMilliseconds;/**< Timeout in milliseconds for moderating tag

invisible event reporting. Use this only when reportTagInvisibleEvent is set to MODERATED.*/

TAG_EVENT_REPORT_TRIGGER reportTagBackToVisibilityEvent;/**< Report criteria when a Tag is back to

visibility.*/

UINT16 tagBackToVisibilityModeratedTimeoutMilliseconds;/**< Timeout in milliseconds for moderating tag

back to visibility event reporting. Use this only when reportTagBackToVisibilityEvent is set to MODERATED.*/

TAG_MOVING_EVENT_REPORT reportTagMovingEvent;/**< Report criteria when a Tag is in moving.*/

UINT16 tagStationaryModeratedTimeoutMilliseconds;**< Timeout in milliseconds for moderating tag stationary

status transition. Use this only when reportTagMovingEvent is enabled.*/

}TAG_EVENT_REPORT_INFO, *LPTAG_EVENT_REPORT_INFO;

RFID3 API Report:

The TAG_EVENT adds 2 new event type TAG_MOVING and TAG_STATIONARY. If this feature is enabled by
reportTagMovingEvent, the moving event can be generated and send to application from reader. The stationary
event needs RFID_GetReadTag() function to do polling. The moving/stationary event is in TAG_DATA >
TAG_EVENT > TAG_MOVING.

typedef struct _TAG_DATA

UINT8* pTagID; /**< Tag ID, for C1G2 this field refers EPC Data.*/

UINT32tagIDLength; /**< Tag ID Length (Number of Bytes).*/

......

TAG_EVENTtagEvent;

......

} TAG_DATA, *LPTAG_DATA;

typedef enum _TAG_EVENT

179
 Moving and Stationary Tags

UNKNOWN_STATE = 0, /**< This implies that the Tag is a result of autonomous mode operation and but the
state of the tag is not known.*/

NEW_TAG_VISIBLE = 1, , /**< This implies that the Tag is a result of autonomous mode operation and the
tag is visible for the first time.*/

TAG_NOT_VISIBLE = 2, This implies that the Tag is a result of autonomous mode operation and the tag is not
visible.*/

TAG_BACK_TO_VISIBILITY = 3, , /**< This implies that the Tag is a result of autonomous mode operation
and the tag is back to visibility.*/

TAG_MOVING = 4, /**< This implies that the Tag is moving generated by moving/stationary check */

TAG_STATIONARY = 5, /**< This implies that the Tag is stationary generated by moving/stationary check */

NONE = 6
}TAG_EVENT;

180
REST RCI Support

Introduction
The RAIN Reader Communication Interface (RCI) is a simple interface for communicating with UHF RFID readers
and eliminates the need for using traditional APIs where in application development is required.

REST RCI Support

FX Series Readers supports sending and receiving RCI based data using the REST interface to the reader using
http(s). The current version supports basic commands that allow interrogation of the reader.

# RCI Command Description

1 GetInfo Get Reader Information

2 GetCfg / SetCfg Gets / Sets Reader Global Configuration

3 GetRZ / SetRZ Gets / Sets Read Zone, typically refers to the Antenna

4 StartRZ Activates Read Zone and reports tags to a configured Post Server configured using
SetCfg

5 StopRz Stops reading tags on the Read Zone

6 GetGPIOs Obtains the values of the listed GPIOs in the same order as the request list. The
GPIO identifier 0 (ALL) will result in the values of all the available GPIOs to be
reported. GetGPIOs also configure when to report the values.

7 SetGPIOS Sets the GPIO values. The command assumes the application knows the GPIO
types by using the GetGPIOs command.

8 GetProf Obtains the fields and values of a SpotProfile. Current implementation supports only
two Pre-Filters

9 SetProf Set the Spot Profile Filter values. Current implementation supports only two
Pre-Filters

10 _GetTags This is custom command to get the list of unique tags in the field of view of all the
antennas connected to the readers

For more details on RCI including the commands and parameter specifications, refer to the RAIN Reader
Communication Interface (RCI) guideline which is available at:
https://rainrfid.org/technology/rain-communication-interface-rci/

181
 REST RCI Support

Communication
FX Series Readers support RCI payload to the REST interface that is accessible on the reader using the URL
http(s)://IPAddress/restrci.

Figure 133 shows an example of RCI command (GetInfo) and its response using the Postman tool. JSON form
examples are available upon request.

Figure 133 RCI Command

182
Troubleshooting

Troubleshooting
Table 16 provides FX Series troubleshooting information.

NOTE: If problems still occur, contact the distributor or call the local contact. See page 14 for contact
information.

Table 16 Troubleshooting
Problem/Error Possible Causes Possible Solutions
Reader error LED lights after the The CPU cannot Refer to the system log for error messages.
reader is in operation. communicate.
Reader error LED stays lit on An error occurred during the Refer to the system log for error messages.
power up. power up sequence.
Cannot access the Administrator User name and password is The default user name is admin and the
Console. unknown. default password is change. To change the
user name and password, see
Communications and Power Connections
on page 33.
Reader is not reading tags. The tag is out of its read Move the tag into read range.
range. See Read Tags on page 71.
Antennas are not connected. Connect antennas.
Tags are damaged. Confirm that tags are good.
Tags are not EPCgen2. Confirm that tags are EPCgen2.
Cannot connect to the reader. The IP address is unknown. See Communications and Power
Connections on page 33 to view the IP
address, or use the host name to connect to
the reader.

183
 Troubleshooting

Table 16 Troubleshooting (Continued)

Problem/Error Possible Causes Possible Solutions
Certain real time applications are The node address, IP Update the settings within the application.
no longer functional. address, or other reader Refer to the application manual.
configuration parameter(s)
were changed using the
Administrator Console, and
the application expects the
previous configuration.
The user closed the browser Log out of the Administrator Console. The
without logging out of the applications can use the Force Login option
Administrator Console, so to log in even when the user closes the
other applications cannot browser without logging out. Force Login
connect to the reader. option is supported for the administrative
user.
Cannot log into Administrator The user forgot the Press and hold the reset button for more
Console. password. than 8 seconds. This resets the reader
configuration to factory defaults, including
the password. This also removes the
contents of the apps partition.
Unable to add SNTP server, SNTP server is not Ensure the SNTP server is accessible.
reader returning error: reachable.
Error: Cannot find the specified
SNTP server name is not Ensure the DNS server name is configured
Host Address
resolvable via DNS server. in TCP/IP configuration.
DNS server is not reachable. Ensure the DNS server is accessible.
Operation failed. A user operation did not Validate all inputs and retry the operation. If
complete, typically due to it is not successful, see Service Information
invalid input. on page 14.
Invalid User Name and/or The user name and/or Accurately retype login information. If this is
Password - Try again. password were not found in not successful, see Service Information on
the system, or do not match page 14.
the current user registry.
Session has Timed-out - Log in The current session was Log in again. As a security precaution to
again. inactive beyond the time-out protect against unauthorized system
period (15 minutes), so the access, always log out of the system when
system automatically logged finished.
out.

184
 Troubleshooting

Table 16 Troubleshooting (Continued)

Problem/Error Possible Causes Possible Solutions
User name is not correct. The user name does not Accurately retype the user name.
match the current user
registry (illegal characters,
too long, too short, unknown,
or duplicate).
User forgot the user ID. Reset the reader to factory defaults and
Web console supports the select Admin for user name and enter
following users: change in the password field to regain
- Admin (default password access.
is change) See Reset to Factory Defaults LED
Sequence on page 38.
- Guest (no password
required)
- rfidadm - supported over
SSH,FTP/FTPS, SCP, but
not over Administrator
Console.
Not a legal IP address The IP address entered is Accurately retype the IP address, and make
(1.0.0.0 - 255.255.255.255). either formatted inaccurately sure the host device is connected and
Cannot reach the specified IP or cannot be accessed online. If this is not successful, see Service
address. (pinged). Information on page 14.
The SNMP Host Link is not valid.
Invalid network mask. The network mask entered is Confirm the correct network mask from the
not formatted correctly. network administrator and enter it correctly.
Invalid SNMP version number. The version number for Use version number 1 for SNMP version 1,
SNMP protocol is not a and 2 for SNMP version 2c.
supported version.
Invalid description. The description contained Correct the description.
invalid characters (<,>,or').
Invalid password. The password does not Accurately retype the password.
match the current user
registry (illegal characters,
too long, or too short).
User forgot the password. Reset the reader to factory defaults and
select Admin for user name and enter
change in the password field to regain
access. See Reset to Factory Defaults LED
Sequence on page 38.
The name, serial number, or IP The name, serial number, or Enter a unique value for the new name,
address entered already exists in IP address entered was serial number, or IP address.
the system. already used.
Another administrator is currently The system does not allow Wait until the other administrator logs out (or
logged in. Try again later. more than one administrator times out) before logging in or override the
to log in at a time. current session with the new one.

185
 Troubleshooting

Table 16 Troubleshooting (Continued)

Problem/Error Possible Causes Possible Solutions
Backup configuration file does not The system cannot revert to Commit the new configuration to create a
exist. a backup configuration backup file.
unless a backup file exists.
Failed to confirm the new The system requires Accurately retype the password twice.
password. entering the password
identically two times.
Network configuration change(s) The user requested log out Select Set Properties to update the
have not been saved. prior to setting and storing network configuration.
the changes made during
the session.
New password is the same as the The system requires Enter a password that is different from the
old one. entering a new password existing password.
(different from the existing
password) during the
Change Password operation.
Old password is not correct. The system requires Accurately retype the existing password.
entering the existing
password during the Change
Password operation.

Unspecified error occurred - A specific error message is Note the code number, and contact Zebra
code: #### missing for the given status support.
code. See Service Information on page 14.
The requested page was not The system experienced an Contact Zebra support.
found. internal web server error. See Service Information on page 14
Internal Web Server Error.
Request method was NULL. The system does not permit No action required. The system is reporting
No query string was provided. executing a proxy program that this action is not permitted.
from the command line
rather than the web server.
Content length is unknown. The system cannot accept Use a GET request instead, or update the
an incorrectly formatted software.
HTTP POST request (from
an unsupported browser
application).
Couldn't read complete post The system stopped a POST Retry the operation, and allow it to
message. operation before completion. complete.
Unhandled reply type. The system generated an Contact Zebra support.
unexpected value. See Service Information on page 14.
Failed to open port. Error during receive of Contact Zebra support.
Failed to connect. command. See Service Information on page 14.

Failed to transmit.
Failed to receive.
Error during Receive of
Command.

186
 Troubleshooting

Table 16 Troubleshooting (Continued)

Problem/Error Possible Causes Possible Solutions
Invalid Device Address. The device address Contact Zebra support.
information (parent) is See Service Information on page 14.
invalid, missing, or formatted
inaccurately.
Command parsing state error. A command was formatted Contact Zebra support.
Missing argument for the inaccurately. See Service Information on page 14.
command.
Command internal type cast error.
Missing operator.
Unknown operator.
The action must be confirmed. The user must confirm the Select the confirmation option when issuing
requested action before it is this request.
executed.
Invalid network adapter when The Bluetooth dongle is not Plug in a supported Bluetooth dongle and
navigating to the Bluetooth plugged in or not supported. refresh the browser.
configuration page.
Wireless scan error. Wireless dongle is not Plug in a supported wireless dongle and
plugged in or not supported. repeat the wireless scan.
Unable to connect to the wireless Access point is off or Turn on the access point and make sure it is
network. unreachable. accessible.
Encryption type is not Use one of the following supported
supported in the access encryption types: WEP128, WPA/WPA2
point. and Open.
The wireless page displays Connect the wireless adapter to the reader.
Adapter not found.
Wireless connection is complete, No DHCP server is running Add a DHCP server to the network.
but no IP address. in the network.
OS update in progress. Firmware update on the Wait for the firmware update to complete
reader is ongoing. The and then retry the operation.
current operation is not
permitted.
Cannot change password. Cannot change password for Guest does not need a password to log in to
guest. the Administrator Console.

187
 Troubleshooting

Table 16 Troubleshooting (Continued)

Problem/Error Possible Causes Possible Solutions
The following reader web console Port 8001 is not accessible. Allow port 8001 to be accessible across the
pages do not load correctly: networks.
• Advanced Antenna These web pages all use port 8001 to
Configuration communicate to the reader and without this
port the pages cannot function.
• ReadTags
• Services
• Serial Port
Communication
• FXConnect
• License Manager
• User Application
• Profiles
• File based firmware
upload
• Syslog Export
Serial Port Push Data: Unable to The Serial Port configuration The configuration on the receiving end
get TAG data over the serial port between the host and target should be same as in the Serial Port
in Push Data mode. is not matched. Configuration window.
Serial cable is not connected Serial cable must be attached to the reader
when inventory started and and host machine when inventory started.
the serial port buffer full. Stop and start the inventory again after
connecting the serial cable.

Troubleshooting for Licensing Errors

Refer to the troubleshooting information related to licensing in Table 17 before contacting the Zebra Customer
Care executives for help

Table 17 Troubleshooting for Licensing Errors

Problem/Error Possible Causes Possible Solutions

No license is displayed although The reader does not have Configure the reader date & time, refresh
the license activation is the current date and time. the Manage License page.
completed. See Time Tampering on page 98.
Message Please Input Activation ID is not Enter the Activation ID which is shared
Activation ID provided. when license is procured.
See Activation ID on page 103.
Message Please Input Server When Local License Server Enter a valid LLS link with the format
URL is selected as the Server http://<Server_ip or
Type to acquire licenses, the host_name>:port_number/request
Server URL is not provided. See Figure 64 on page 102.

188
 Troubleshooting

Problem/Error Possible Causes Possible Solutions

Message Error:Application is Users activate new Activate new license(s) when EtherNet/IP
running, cannot be installed license(s) when the application is not running.
again EtherNet/IP application is
running on the reader.
Message Error:Application The license is activated License will be activated but the EtherNet/IP
Install & Run Disabled without selecting the Install application will not be installed.
and Run application option Manually install the EtherNet/IP via
application web page if you have a debain
package.
Return the license and re-install the license
again. Select the Install and Run
application option before activating the
license.
Message Error:Invalid Different product license Make sure the Activation ID provided is the
Activation ID, Please provide Activation ID is provided one which is shared when license is
valid activation ID for License when users returning the procured.
Return license(s).

189
Technical Specifications

Technical Specifications
The following tables summarize the RFID reader intended operating environment and technical hardware
specifications.

Table 18 Technical Specifications

Item Description

Physical and Environmental Characteristics

Dimensions
FX7500 7.7 in. L x 5.9 in. W x 1.7 in. D
(19.56 cm L x 14.99 cm W x 4.32 cm D)
FX9600 9.72 in. L x 7.25 in. W x 2.2 in. D
(24.67 cm x 18.42 cm W x 5.56 cm D mm)

Weight
FX7500 1.9 lbs ± 0.1 lbs (0.86 kg +/- 0.05 kg)
FX9600 4.5 lbs (2.1 kg)

Base Material
FX7500 Die cast aluminum, sheet metal and plastic
FX9600 Die cast aluminum

Visual Status Indicators Multi-color LEDs: Power, Activity, Status, and Applications

Mounting
FX7500 Keyhole and standard VESA (75 mm x 75 mm)
FX9600 Four mounting flanges and Four 100 mm x 100 mm VESA holes for 10-32 screw.

FX Environmental Specifications

Operational Temperature -4° to +131° F / -20° to +55° C

Storage Temperature -40° to +158° F / -40° to +70° C

Humidity 5 to 95% non-condensing

190
 Technical Specifications

Table 18 Technical Specifications (Continued)

Item Description

Shock and Vibration

FX7500 MIL-STD-810G
FX9600 MIL-STD-810G

Connectivity

Communications 10/100 BaseT Ethernet (RJ45) w/ PoE support, PoE+, USB Client (Type B), USB
Host (Type A)

General Purpose I/O

FX7500 2 inputs, 3 outputs, optically isolated (terminal block)
External 12V ~ 48 VDC power available for GPIO
FX9600 4 inputs, 4 outputs, optically isolated (terminal block)
External 12V ~ 24 VDC power available for GPIO

Power
FX7500 PoE (802.3af), PoE+ (802.3at)
12 VDC to 48 VDC, or 24 VDC Universal Power Supply
FX9600 PoE (802.3af), PoE+ (802.3at)
12 VDC to 24 VDC, or 24 VDC Universal Power Supply

Antenna Ports
FX7500 FX7500-2: 2 mono-static ports (reverse polarity TNC)
FX7500-4: 4 mono-static ports (reverse polarity TNC)
FX9600 FX9600-4: 4 mono-static ports (reverse polarity TNC)
FX9600-8: 8 mono-static ports (reverse polarity TNC)

Hardware/OS and Firmware Management

Memory Flash 512 MB; DRAM 256 MB

Operating System Linux

Firmware Upgrade Web-based and remote firmware upgrade capabilities

Management Protocols RM 1.0.1 (with XML over HTTP/HTTPS and SNMP binding)

Network Services DHCP, HTTPS, FTPS, SFPT, SCP, SSH, HTTP, FTP, SNMP and NTP

Network Stack IPv4, IPv6

Security Transport Layer Security Ver. 1.2, FIPS 140-2 Level 1

Air Protocols EPCglobal UHF Class 1 Gen2, ISO/IEC 18000-63

Frequency (UHF Band) Global Reader: 902 MHz to 928 MHz (Maximum, supports countries that use a part
of this band)
865 MHz to 868 MHz
US (only) Reader: 902 MHz to 928 MHz

191
 Technical Specifications

Table 18 Technical Specifications (Continued)

Item Description

Transmit Power Output

FX7500 10dBm to +31.5dBm (PoE+, 12V ~ 48V External DC,
Universal 24 VDC Power Supply;
+10dBm to +30.0dBm (PoE)
0dBm to +33.0dBm (PoE+, 12V ~ 24V External DC,
FX9600 Universal 24 VDC Power Supply;
+0dBm to +31.5dBm (PoE)

Max Receive Sensitivity

FX7500 -82dBm
FX9600 -86dBm

IP Addressing Static and Dynamic

Host Interface Protocol LLRP v1.0.1

API Support Host Applications – .NET, C and Java EMDK;

Embedded Applications – C & Java SDK

Warranty

For the complete Zebra hardware product warranty statement, go to:

www.zebra.com/warranty

Recommended Services

Support Services Zebra One Care Select and Zebra One Care On Site

Advanced Services RFID Design and Deployment Services

Cable Pinouts
10/100bT Ethernet / PoE Connector
The 10/100BT Ethernet / PoE connector is an RJ45 receptacle. This port complies with the IEE 802.3af
specification for Powered Devices.

Figure 134 Ethernet Connections

192
 Technical Specifications

USB Client Connector

The USB Client port is supplied on a USB Type B connector.

Figure 135 USB Client Connector

Pin 2 Pin 1

Pin 3 Pin 4

Table 19 USB Client Port Connector Pinout

Pin Pin Name Direction Description

Pin 1 5.0V_USB I 5.0V USB Power Rail

Pin 2 USB_DN I/O Data Negative

Pin 3 USB_DP I/O Data Positive

Pin 4 GND - Ground

USB Host Connector

The USB Host port is supplied on a USB Type A flag connector.

Figure 136 USB Host Connector (J22)

Pin 4

Pin 1

Table 20 USB Host Port Connector (J22) Pinout

Pin Pin Name Direction Description

Pin 1 V_USB I 5.0V USB Power Rail

Pin 2 USBH_DN I/O Data Negative Rail

Pin 3 USBH_DP I/O Data Positive Rail

Pin 4 GND - Ground

193
 Technical Specifications

FX7500 GPIO Port Connections

The FX7500 GPIO connector pinouts include the following:

Figure 137 FX7500 RFID Reader GPIO Connection

Pin 1 Pin 8

Table 21 FX7500 GPIO Pinouts

Pin # Pin Name Direction Description

1 +24V DC Power O Supplies +24V DC at up to 1 Amp

2 GP output #1 O Signal for GP output #1

3 GP output #2 O Signal for GP output #2

4 GP output #3 O Signal for GP output #3

5 GND - Ground connection

6 GP input #1 I Signal for GP input #1

7 GP input #2 I Signal for GP input #2

8 GND - Ground connection

FX9600 GPIO Connections

The FX9600 GPIO connector pinouts include the following:

Figure 138 FX9600 RFID Reader GPIO Connection

Pin 1 Pin 12

Table 22 FX9600 GPIO Pinouts

Pin # Pin Name Direction Description

1 +24V DC Power O Supplies +24VDC At up to 1 Amp

2 GND - Ground connection

3 GP output #1 O Signal for GP output #1

4 GP output #2 O Signal for GP output #2

5 GP output #3 O Signal for GP output #3

194
 Technical Specifications

Table 22 FX9600 GPIO Pinouts (Continued)

Pin # Pin Name Direction Description

6 GP output #4 O Signal for GP output #4

7 GND - Ground connection

8 GP input #1 I Signal for GP input #1

9 GP input #2 I Signal for GP input #1

10 GP input #3 I Signal for GP input #1

11 GP input #4 I Signal for GP input #1

12 GND - Ground connection

The Figure 139 provides an example of a typical GPIO setup with the power derived from an external power
supply.

Figure 139 FX9600 GPIO Setup Example with Power Derived from External Power Supply

195
 Technical Specifications

The Figure 140 provides an example of a typical GPIO setup with the power derived from GPIO 24V Pin.

Figure 140 FX9600 GPIO Setup Example with Power Derived from GPIO 24V Pin

196
Static IP Configuration

Introduction
This chapter describes three methods of setting the static IP address on an FX7500 and FX9600 RFID Readers.

Reader IP Address or Host Name is Known

Set the Static IP Using the Web Console

1. Browse the device using the host name, for example: FX7500CD3B1E.
2. Log onto the device.

Figure 141 Reader Administration Console Login Window

3. Select Communication.
4. Set Obtain IP Address via DHCP to Off and enter all required information.

197
 Static IP Configuration

Figure 142 Reader Communication Parameters Window

5. Select Set Properties. You can set a static IP that doesn't belong to this DHCP network.
6. The window displays a Saving. Please wait... message with a progress symbol until the commit completes.
7. When the commit completes, a gray floppy disk icon displays indicating that the commit completed
successfully. The new selection is now set and stored in the reader.
8. The message Reader IP Address config has changed. Needs reader reboot to take effect appears. Reset the
device and use the reader with the static IP network.

198
 Static IP Configuration

Reader IP is Not Known (DHCP Network Not Available)

Set the Static IP Using the Web Console

1. Connect the device and a PC running Windows XP to the same network that doesn't have a DHCP server, or
connect the device directly to the PC.
2. Ensure both the device and PC Ethernet jack use at least one LED to indicate network connection detect.
3. If the PC uses an assigned static IP, update it to use DHCP. The PC obtains an IP that starts with 169.

Figure 143 Obtain IP Address

4. When possible, ping the host name of the device.

Figure 144 Ping the Host Name

5. Use a browser to connect to the device with the host name, for example: FX7500CD3B1E, or use the IP
address obtained from ping replies (for example, 169.254.62.74).
6. Log onto the device.
7. Select Communication.
8. Set Obtain IP Address via DHCP to Off and enter all required information.

199
 Static IP Configuration

Figure 145 Reader Communication Parameters Window

9. Select Set Properties.

10. The window displays a Saving. Please wait... message with a progress symbol until the commit completes.
11. When the commit completes, a gray floppy disk icon displays indicating that the commit completed
successfully. The new selection is now set and stored in the reader.
12. The message Reader IP Address config has changed. Needs reader reboot to take effect appears. Reset the
device and use the reader with the static IP network.

200
RF Air Link Configuration

Introduction
This appendix lists the different air link configurations supported. The air link configuration is available through
LLRP and RFID3 API interfaces.

Radio Modes
The supported modes are exposed as a list of individual UHFC1G2RfModeTableEntry parameters in regulatory
capabilities as shown in Table 23 and Table 24. The Mode Index column refers to the index used to walk the
C1G2UHFRFModeTable. Refer to the EPCglobal Low Level Reader Protocol (LLRP) Standard.

Table 23 Radio Modes for FCC Readers

M Value
EPC HAG
M2=2, Spectral
RF Mode Divide BDR FLM PIE Min Max Step T&C
FM0=1, Mask
Index Ratio Value Value Value Tari Tari Tari Conform-
M4=4, Indicator**
ance
M8=8

1 64/3 640000 1 PR_ASK 1500 6250 6250 0 Dense false

2 64/3 640000 1 PR_ASK 2000 6250 6250 0 Dense false

3 64/3 120000 2 PR_ASK 1500 25000 25000 0 Dense false

4 64/3 120000 2 PR_ASK 1500 12500 23000 2100 Dense false

5 64/3 120000 2 PR_ASK 2000 25000 25000 0 Dense false

6 64/3 120000 2 PR_ASK 2000 12500 23000 2100 Dense false

7 64/3 128000 2 PR_ASK 1500 25000 25000 0 Dense false

8 64/3 128000 2 PR_ASK 1500 12500 23000 2100 Dense false

9 64/3 128000 2 PR_ASK 2000 25000 25000 0 Dense false

10 64/3 128000 2 PR_ASK 2000 12500 23000 2100 Dense false

*RF Mode 23 is the automac air link profile which is also the default.
**Spectral mask indicator may vary for certain Tari values. Detailed information is available upon request.
Empty bracket [ ] indicates that this RF mode is not supported in FX7500; A number in the bracket indicates the
RF Mode for the FX7500; No bracket indicates RF mode supported by both FX9600 and FX7500.

201
 RF Air Link Configuration

Table 23 Radio Modes for FCC Readers (Continued)

M Value
EPC HAG
M2=2, Spectral
RF Mode Divide BDR FLM PIE Min Max Step T&C
FM0=1, Mask
Index Ratio Value Value Value Tari Tari Tari Conform-
M4=4, Indicator**
ance
M8=8

11 64/3 160000 2 PR_ASK 1500 12500 18800 2100 Dense false

12 64/3 160000 2 PR_ASK 2000 12500 18800 2100 Dense false

13 64/3 60000 4 PR_ASK 1500 25000 25000 0 Dense false

14 64/3 60000 4 PR_ASK 1500 12500 23000 2100 Dense false

15 64/3 60000 4 PR_ASK 2000 25000 25000 0 Dense false

16 64/3 60000 4 PR_ASK 2000 12500 23000 2100 Dense false

17 64/3 64000 4 PR_ASK 1500 25000 25000 0 Dense false

18 64/3 64000 4 PR_ASK 1500 12500 23000 2100 Dense false

19 64/3 64000 4 PR_ASK 2000 25000 25000 0 Dense false

20 64/3 64000 4 PR_ASK 2000 12500 23000 2100 Dense false

21 64/3 80000 4 PR_ASK 1500 12500 18800 2100 Dense false

22 64/3 80000 4 PR_ASK 2000 12500 18800 2100 Dense false

*23 64/3 variable variable PR_ASK variable 6250 25000 variable variable false

24 64/3 320000 1 PR_ASK 1500 12500 18800 2100 Dense false

25 64/3 320000 1 PR_ASK 2000 12500 18800 2100 Dense false

26 64/3 30000 8 PR_ASK 1500 25000 25000 0 Dense false

27 64/3 30000 8 PR_ASK 1500 12500 23000 2100 Dense false

28 64/3 30000 8 PR_ASK 2000 25000 25000 0 Dense false

29 64/3 30000 8 PR_ASK 2000 12500 23000 2100 Dense false

30 64/3 32000 8 PR_ASK 1500 25000 25000 0 Dense false

31 64/3 32000 8 PR_ASK 1500 12500 23000 2100 Dense false

32 64/3 32000 8 PR_ASK 2000 25000 25000 0 Dense false

33 64/3 32000 8 PR_ASK 2000 12500 23000 2100 Dense false

34 64/3 40000 8 PR_ASK 1500 12500 18800 2100 Dense false

35 64/3 40000 8 PR_ASK 2000 12500 18800 2100 Dense false

36 [ ] 64/3 120000 4 PR_ASK 1500 10400 10400 0 Dense false

*RF Mode 23 is the automac air link profile which is also the default.
**Spectral mask indicator may vary for certain Tari values. Detailed information is available upon request.
Empty bracket [ ] indicates that this RF mode is not supported in FX7500; A number in the bracket indicates the
RF Mode for the FX7500; No bracket indicates RF mode supported by both FX9600 and FX7500.

202
 RF Air Link Configuration

Table 23 Radio Modes for FCC Readers (Continued)

M Value
EPC HAG
M2=2, Spectral
RF Mode Divide BDR FLM PIE Min Max Step T&C
FM0=1, Mask
Index Ratio Value Value Value Tari Tari Tari Conform-
M4=4, Indicator**
ance
M8=8

37 [36] 64/3 120000 4 PR_ASK 2000 10400 10400 0 Dense false

38 [ ] 64/3 160000 4 PR_ASK 1500 6250 10400 4150 Dense false

[37] 64/3 160000 4 PR_ASK 2000 6250 6250 0 Dense false

39 [38] 64/3 668 1 PR_ASK 668 668 668 0 Dense false

*RF Mode 23 is the automac air link profile which is also the default.
**Spectral mask indicator may vary for certain Tari values. Detailed information is available upon request.
Empty bracket [ ] indicates that this RF mode is not supported in FX7500; A number in the bracket indicates the
RF Mode for the FX7500; No bracket indicates RF mode supported by both FX9600 and FX7500.

Table 24 Radio Modes for ETSI Readers

M Value
Spectral
M2=2, EPC HAG T&C
RF Mode Divide BDR FLM PIE Min Max Step Mask
FM0=1, Conform-
Index Ratio Value Value Value Tari Tari Tari Indica-
M4=4, ance
tor**
M8=8

1 64/3 120000 2 PR_ASK 1500 25000 25000 0 Dense false

2 64/3 120000 2 PR_ASK 1500 12500 23000 2100 Dense false

3 64/3 120000 2 PR_ASK 2000 25000 25000 0 Dense false

4 64/3 120000 2 PR_ASK 2000 12500 23000 2100 Dense false

5 64/3 128000 2 PR_ASK 1500 25000 25000 0 Dense false

6 64/3 128000 2 PR_ASK 1500 12500 23000 2100 Dense false

7 64/3 128000 2 PR_ASK 2000 25000 25000 0 Dense false

8 64/3 128000 2 PR_ASK 2000 12500 23000 2100 Dense false

9 64/3 160000 2 PR_ASK 1500 12500 18800 2100 Dense false

10 64/3 160000 2 PR_ASK 2000 12500 18800 2100 Dense false

11 64/3 60000 4 PR_ASK 1500 25000 25000 0 Dense false

12 64/3 60000 4 PR_ASK 1500 12500 23000 2100 Dense false

13 64/3 60000 4 PR_ASK 2000 25000 25000 0 Dense false

14 64/3 60000 4 PR_ASK 2000 12500 23000 2100 Dense false

*RF Mode 21 is the automac air link profile which is also the default.
**Spectral mask indicator may vary for certain Tari values. Detailed information is available upon request.

203
 RF Air Link Configuration

Table 24 Radio Modes for ETSI Readers (Continued)

M Value
Spectral
M2=2, EPC HAG T&C
RF Mode Divide BDR FLM PIE Min Max Step Mask
FM0=1, Conform-
Index Ratio Value Value Value Tari Tari Tari Indica-
M4=4, ance
tor**
M8=8

15 64/3 64000 4 PR_ASK 1500 25000 25000 0 Dense false

16 64/3 64000 4 PR_ASK 1500 12500 23000 2100 Dense false

17 64/3 64000 4 PR_ASK 2000 25000 25000 0 Dense false

18 64/3 64000 4 PR_ASK 2000 12500 23000 2100 Dense false

19 64/3 80000 4 PR_ASK 1500 12500 18800 2100 Dense false

20 64/3 80000 4 PR_ASK 2000 12500 18800 2100 Dense false

*21 64/3 variable variable PR_ASK variable 12500 25000 variable variable false

22 64/3 30000 8 PR_ASK 1500 25000 25000 0 Dense false

23 64/3 30000 8 PR_ASK 1500 12500 23000 2100 Dense false

24 64/3 30000 8 PR_ASK 2000 25000 25000 0 Dense false

25 64/3 30000 8 PR_ASK 2000 12500 23000 2100 Dense false

26 64/3 32000 8 PR_ASK 1500 25000 25000 0 Dense false

27 64/3 32000 8 PR_ASK 1500 12500 23000 2100 Dense false

28 64/3 32000 8 PR_ASK 2000 25000 25000 0 Dense false

29 64/3 32000 8 PR_ASK 2000 12500 23000 2100 Dense false

30 64/3 40000 8 PR_ASK 1500 12500 18800 2100 Dense false

31 64/3 40000 8 PR_ASK 2000 12500 18800 2100 Dense false

32 64/3 668 1 PR_ASK 668 668 668 0 Dense false

*RF Mode 21 is the automac air link profile which is also the default.
**Spectral mask indicator may vary for certain Tari values. Detailed information is available upon request.

204
 RF Air Link Configuration

Table 25 Radio Modes for Japan Readers

M Value
EPC HAG
M2=2, Spectral
RF Mode Divide BDR FLM PIE Min Max Step T&C
FM0=1, Mask
Index Ratio Value Value Value Tari Tari Tari Conform-
M4=4, Indicator**
ance
M8=8

1 [1] 64/3 120000 2 PR_ASK 2000 25000 25000 0 Dense false

2 64/3 120000 2 PR_ASK 2000 12500 23000 2100 Dense false

3 [2] 64/3 128000 2 PR_ASK 2000 25000 25000 0 Dense false

4 64/3 128000 2 PR_ASK 2000 12500 23000 2100 Dense false

5 64/3 160000 2 PR_ASK 2000 12500 18800 2100 Dense false

6 [3] 64/3 60000 4 PR_ASK 2000 25000 25000 0 Dense false

7 64/3 60000 4 PR_ASK 2000 12500 23000 2100 Dense false

8 [4] 64/3 64000 4 PR_ASK 2000 25000 25000 0 Dense false

9 64/3 64000 4 PR_ASK 2000 12500 23000 2100 Dense false

10 64/3 80000 4 PR_ASK 2000 12500 18800 2100 Dense false

11 64/3 320000 1 PR_ASK 2000 12500 18800 2100 Dense false

12 [5] 64/3 30000 8 PR_ASK 2000 25000 25000 0 Dense false

13 64/3 30000 8 PR_ASK 2000 12500 23000 2100 Dense false

14 [6] 64/3 32000 8 PR_ASK 2000 25000 25000 0 Dense false

15 64/3 32000 8 PR_ASK 2000 12500 23000 2100 Dense false

16 64/3 40000 8 PR_ASK 2000 12500 18800 2100 Dense false

**Spectral mask indicator may vary for certain Tari values. Detailed information is available upon request.
Empty bracket [ ] indicates that this RF mode is not supported in FX7500; A number in the bracket indicates the
RF Mode for the FX7500; No bracket indicates RF mode supported by both FX9600 and FX7500.

205
Copying Files To and From
the Reader

Introduction
The FX7500 and FX9600 RFID readers support the SCP, FTP, and FTPS protocols for copying files.

SCP
The following examples illustrate SCP use:
scp SourceFileName rfidadm@MyReaderIP:/apps
scp rfidadm@MyReaderIP:/apps/SourceFileName userid@MyLinuxMachineIP:/MyFolderName

FTP
The following examples illustrate FTP use:
ftp> open
To 157.235.207.146
Connected to 157.235.207.146.
220 Welcome to Thredbo FTP service.
User (157.235.207.146:(none)): rfidadm
331 Please specify the password.
Password:
230 Login successful.
ftp>
Use FTP commands such as is, get, and put to manage files. For more information on FTP commands refer to
www.cs.colostate.edu/helpdocs/ftp.html. GUI applications such as FileZilla are also supported on Windows and
Linux machines to connect to the FX7500 and FX9600.

FTPS
Use any standard GUI tool such as FileZilla, to connect to the FX7500 and FX9600 RFID readers over FTPS.

206
Data Protection

Introduction
The FX7500 and FX9600 RFID readers store data in transition when it detects a network condition that prevents
the reader from sending data. This applies to RFID tag data that the reader application is transmitting to the
outbound TCP socket, and is no longer owned by the RFID application because it was sent to the network layer for
transmission.

When the reader cannot queue RFID data in the outbound TCP socket when an LLRP connection is already
established, it stores all outbound LLRP messages in the data protection queue. The queue can store up to 66,000
messages, which represents more than 5 minutes worth of data when reading 200 tags/second (the nominal data
rate in DRM (dense reader mode) configuration). If the network is still unavailable when the data protection queue
is full, the oldest messages are discarded to accommodate the most recent tag reports.

This feature can not be disabled and operates regardless of the physical network interface used, meaning RFID
data over Wi-Fi and Bluetooth is also protected.

207
Index

Numerics C
10/100BaseT Ethernet . . . . . . . . . . . . . 16, 22, 24, 25, 26 cable pinouts
123RFID Desktop ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
USB client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
USB host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
A chapter descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 12
administrator console . . . . . . . . . . . . . . . . . . . . . . . . . 42 commit region change . . . . . . . . . . . . . . . . . . . . . . . . . 18
applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 committing changes . . . . . . . . . . . . . . . . . . . . . . . . . 121
committing changes . . . . . . . . . . . . . . . . . . . . . . 121 communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 23, 26
communication settings . . . . . . . . . . . . . . . . . . . . 72 ethernet, wired . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
configure network services . . . . . . . . . . . . . . . . . . 78 communication settings . . . . . . . . . . . . . . . . . . . . . . . . 72
configure network settings . . . . . . . . . . . . 72, 73, 74 configure
configuring system log . . . . . . . . . . . . . . . . . . . . 126 antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
discarding changes . . . . . . . . . . . . . . . . . . . . . . . 121 LLRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
firmware version . . . . . . . . . . . . . . . . . . . . . 120, 121 read points . . . . . . . . . . . . . . . . . . . . . . . . . . . 58, 59
GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
IPV6 sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 static IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
managing login . . . . . . . . . . . . . . . . . . . . . . . . . . 115 static IP via web console . . . . . . . . . . . . . . 197, 199
reader diagnostics . . . . . . . . . . . . . . . . . . . . . . . . 127 wireless . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
reader profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 configuring network
scan control . . . . . . . . . . . . . . . . . . . . . . . . . . . 20, 71 bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
set password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
setting date and time . . . . . . . . . . . . . . . . . . . . . . 112 services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
shutting down . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 wi-fi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 connecting
system log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 to reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
air link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 via bluetooth . . . . . . . . . . . . . . . . . . . . . . . . 137, 138
antennas via host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 via IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 via wi-fi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
ports . . . . . . . . . . . . . . . . . . . . . . . 16, 22, 23, 25, 26 connection
applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
port diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
B ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22, 25
bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137, 138 wired ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
connecting . . . . . . . . . . . . . . . . . . . . . . . . . . 137, 138 conventions

208
 Index

notational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 G
copying files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140, 206
country list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16, 22, 25
GPIO connections . . . . . . . . . . . . . . . . . . . . . . . .194
pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
D port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23, 26
data protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 GPIO control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 H
discarding changes . . . . . . . . . . . . . . . . . . . . . . . . . . 121
host communication
ethernet, wired . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
E host name connect . . . . . . . . . . . . . . . . . . . . . . . . . . .17
ethernet
pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 I
POE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 26 information, service . . . . . . . . . . . . . . . . . . . . . . . . . . .14
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33, 34 initiating reads . . . . . . . . . . . . . . . . . . . . . . . . . . . .20, 71
wired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 installation
event statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
communication connection . . . . . . . . . . . . . . . . . .33
mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
F IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
files IP ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140, 206
firmware L
version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120, 121
firmware update . . . . . . . . . . . . . . . . . . . . . 120, 121, 145 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24, 26
prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 LLRP
first time login . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17, 47 configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
FTP radio modes . . . . . . . . . . . . . . . . . . . . . . . . .201, 203
copying files . . . . . . . . . . . . . . . . . . . . . . . . 140, 206 log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
FTPS configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
copying files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
FX Connect first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
http proxy server . . . . . . . . . . . . . . . . . . . . . . . . . . 93 managing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
license type
evaluation license . . . . . . . . . . . . . . . . . . . . . . 98 M
perpetual license . . . . . . . . . . . . . . . . . . . . . . 98
licensing mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29, 31
acquisition modes . . . . . . . . . . . . . . . . . . . . . . 99 concrete wall mounting . . . . . . . . . . . . . . . . . . . . .31
activation id . . . . . . . . . . . . . . . . . . . 97, 100, 103 drywall mounting . . . . . . . . . . . . . . . . . . . . . . . . . .31
device id . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 wood or metal wall mounting . . . . . . . . . . . . . . . . .31
download from bin file . . . . . . . . . . . . . . . . . . 102 mounting plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
local license server . . . . . . . . . . . . . . . . . . . . 102 multiple reader deployments . . . . . . . . . . . . . . . . . . . .43
offline . . . . . . . . . . . . . . . . . . . . . . . . . . 102, 103
production server . . . . . . . . . . . . . . . . . . . . . . 99 N
UATserver . . . . . . . . . . . . . . . . . . . . . . . . . . 101
licensing evaluation NXP
enabling license . . . . . . . . . . . . . . . . . . . . . . . 98 statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54, 56
licensing model . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
running inventory . . . . . . . . . . . . . . . . . . . . . . . . . 90
O
USB HID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 obtain reader IP address . . . . . . . . . . . . . . . . . . . . . . .45

209
 Index

P wired ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

wired ethernet AC outlet . . . . . . . . . . . . . . . . . . . .33
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . 17, 145, 151 wired ethernet, power-over . . . . . . . . . . . . . . . . . .34
password . . . . . . . . . . . . . . . . . . . . . . . . 17, 47, 145, 151 shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
changing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 SNMP
pinouts configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 software update . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190
USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
USB client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 static IP configuration . . . . . . . . . . . . . . . . . . . . . . . . .197
USB host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 via web console . . . . . . . . . . . . . . . . . . . . . .197, 199
POE . . . . . . . . . . . . . . . . . . . . 16, 22, 24, 25, 26, 34, 192 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22, 25 statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 23, 26 event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 GEN2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16, 22, 25 NXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54, 56
POE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 26 system log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
system time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
R
read points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58, 59 T
reader tags
configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39, 71
connecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 technical specifications . . . . . . . . . . . . . . . . . . . . . . .190
GEN2 statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 tool for RFID readers - 123RFID Desktop . . . . . . . . . .40
statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
NXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54, 56
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
reading tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 U
initiating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20, 71 unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16, 25 updating firmware . . . . . . . . . . . . . . . . . . .120, 121, 145
reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 updating software . . . . . . . . . . . . . . . . . . . . . . . . . . .145
region configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 USB . . . . . . . . . . . . . . . . . . . . . . . . .16, 22, 25, 134, 146
region control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 client pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
region setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 host pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
region settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 16, 22, 23, 25, 26 user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
RFID user name . . . . . . . . . . . . . . . . . . . . . . . . . .17, 145, 151
FX reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21, 25 user password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
RJ45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 26

V
S
version control . . . . . . . . . . . . . . . . . . . . . . . . . .120, 121
SCP vice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
copying files . . . . . . . . . . . . . . . . . . . . . . . . 140, 206
service information . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
set region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18, 48 W
setting date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
wi-fi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
setting time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
connecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
setup
wired ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

210
 Index

wireless
configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Z
zero-configuration networking . . . . . . . . . . . . . . . . . . . 46

211
www.zebra.com