Fxseries Ig en

FX SERIES
RFID FIXED
READER
Integration Guide
MN000026A15EN Rev. A
FX SERIES RFID READER
INTEGRATION GUIDE
MN000026A15EN
Revision A
Mar 2022
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
zebra.com/copyright.
WARRANTY: For complete warranty information, go to zebra.com/warranty.

END USER LICENSE AGREEMENT: For complete EULA information, go to 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: 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
-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.
-13EN Rev A 9/2020 Added:
- An important note at the FX Series Licensing Management introduction section.
- A note in the Acquiring License from Production Server (ON-Line) section.
- Licensing Error Logs.
Updated the Troubleshooting section.

-14EN Rev A 5/2021 Updated the SFDC Forms link in the Procuring Licenses section.
5
-15EN Rev A 3/2022 Updated:

- Changed Zero-Configuration to Link Local
- Certificate Configuration
- Configure LLRP Settings Window
- Supported Wi-Fi Dongles in Wireless Settings
- Defaults in FX9600 Serial Port Configuration
- FX Connect
- Modified Reset Reader to Factory Defaults to Enterprise Reset the Reader
- Supported Bluetooth Dongles in Connecting to a Peer Device Over Bluetooth
Using a Bluetooth Dongle
- Cellular Connectivity with Sierra Modem
- Header in Cellular Connectivity with Sierra Modem
- Moving and Stationary Tags
Added:
- Section NTP Statistics
- Bullets for the following in Administrator Console Option Selections:
Zebra IoT Connector
Configuration
Connection
802.1x EAP
- Reconnect to Server bullet in Configure LLRP Settings
- 802.1x EAP Configuration in Administrator Console
6
Table of Contents
Copyright ........................................................................................................................................... 3
For Australia Only ....................................................................................................................... 3
Terms of Use .................................................................................................................................... 3
Revision History ................................................................................................................................ 4
About This Guide

Introduction ..................................................................................................................................... 14
Chapter Descriptions ...................................................................................................................... 14
Notational Conventions ................................................................................................................... 15
Related Documents and Software .................................................................................................. 15
Service Information ......................................................................................................................... 16
Quick Start
Introduction ..................................................................................................................................... 17
Requirements .................................................................................................................................. 17
Quick Start Demonstration .............................................................................................................. 17
Step 1, Setup ............................................................................................................................ 18
Step 2, Connecting to the Reader ............................................................................................. 19
Step 3, First Time or Start-Up Login ......................................................................................... 19
Step 4, Set Region .................................................................................................................... 22
Step 5, Read Tags .................................................................................................................... 24
Getting Started
Introduction ..................................................................................................................................... 25
FX Series Features ......................................................................................................................... 25
FX7500 Parts ............................................................................................................................ 26
FX7500 Rear Panel ................................................................................................................... 27
FX7500 LEDs ............................................................................................................................ 28
FX9600 Parts ............................................................................................................................ 29
FX9600 Rear Panel ................................................................................................................... 30
FX9600 LEDs ............................................................................................................................ 31
Installation and Communication

Introduction ..................................................................................................................................... 32
7
Table of Contents
Unpacking the Reader .................................................................................................................... 32

Mounting and Removing the FX Series Readers ............................................................................ 33
Mounting Tips ...................................................................................................................... 33
Mounting the FX7500 With a Mounting Plate ..................................................................................... 33
FX7500 Direct Mounting ........................................................................................................... 34
Mounting the FX9600 Reader ......................................................................................................... 35
Concrete Wall Mounting ...................................................................................................... 35
Wood or Metal Wall Mounting ............................................................................................. 35
Drywall Mounting ................................................................................................................. 35
VESA Mounting ................................................................................................................... 36
Connecting FX7500 and FX9600 RFID Reader Antennas ............................................................. 36
Communications and Power Connections ...................................................................................... 37
Ethernet Connection ................................................................................................................. 37
Ethernet: Power through AC Outlet ..................................................................................... 37
Ethernet: Power through Standard PoE or PoE+ ................................................................ 38
USB Connection ........................................................................................................................ 38
Zebra USB RNDIS Driver .................................................................................................... 38
Microsoft RNDIS Driver for Windows 7 ............................................................................... 39
Sample Implementation ...................................................................................................... 40
GPIO Interface Connection ....................................................................................................... 41
LED Sequences .............................................................................................................................. 42
System Start-up/Boot LED Sequence ....................................................................................... 42
PWR LED Sequence to Indicate IPv4 Status after Booting ...................................................... 42
Reset to Factory Defaults LED Sequence ................................................................................ 42
LED Sequence for Software Update Status .............................................................................. 42
Reading Tags ................................................................................................................................................. 43
123RFID Desktop
Introduction ..................................................................................................................................... 44
Features .......................................................................................................................................... 45
Communication with 123RFID Desktop .......................................................................................... 45
123RFID Desktop Requirements .................................................................................................... 45
Administrator Console
Introduction ..................................................................................................................................... 46
Reader Administrator Console Selections ...................................................................................... 46
Profiles ...................................................................................................................................... 47
Resetting the Reader ................................................................................................................ 47
Auto Discovery .......................................................................................................................... 48
Connecting to the Reader ............................................................................................................... 49
Obtaining the IP Address via Command Prompt ...................................................................... 49
Connecting via Host Name ....................................................................................................... 50
Connecting via IP Address ........................................................................................................ 50
Using Link Local Networking when DHCP Server is Not Available ........................................... 50
Administrator Console Login ....................................................................................................................... 51
First Time / Start-Up Login ........................................................................................................ 51
Logging In with Default User ID and Password ................................................................... 51
Setting the Region ..................................................................................................................... 52
Reader Administrator Console ........................................................................................................ 53
8
Table of Contents
Administrator Console Option Selections ........................................................................................... 53

Status .............................................................................................................................................. 55
Reader Statistics ............................................................................................................................. 56
Reader Gen2 Optional Operation Statistics .............................................................................. 57
NXP Custom Command Operation Statistics ............................................................................ 58
Event Statistics .......................................................................................................................... 59
Other Custom Command Operation Statistics .......................................................................... 60
NTP Statistics ............................................................................................................................ 61
Configure Reader ............................................................................................................................ 62
Reader Parameters ................................................................................................................... 62
Read Points ............................................................................................................................... 63
Antenna Status .................................................................................................................... 63
Antenna Configuration ........................................................................................................ 64
Read Points - Advanced ........................................................................................................... 64
Configure Region ...................................................................................................................... 65
Certificates ................................................................................................................................ 66
Certificate Configuration ...................................................................................................... 67
Creating a Custom Certificate ............................................................................................. 69
Script Usage ........................................................................................................................ 76
Read Tags ...................................................................................................................................... 77
Communication Settings ................................................................................................................. 78
Configure Network Settings - Ethernet Tab .............................................................................. 78
IPV4 .................................................................................................................................... 78
IPV6 .................................................................................................................................... 79
Configure Network Settings - Wi-Fi Tab .................................................................................... 79
IPV4 .................................................................................................................................... 79
IPV6 .................................................................................................................................... 80
Configure Network Settings - Bluetooth Tab ............................................................................. 80
Configure LLRP Settings ........................................................................................................... 81
SNMP Settings .......................................................................................................................... 82
Wireless Settings ...................................................................................................................... 83
Network Services Settings ........................................................................................................ 84
802.1x EAP Configuration ......................................................................................................... 85
FX Series Reader 802.1x EAP configuration/Testing with FreeRADIUS ............................ 86
Cisco Switch (Cisco C1000-24FP-4G-L) Configuration ...................................................... 87
Fx Reader 802.1 EAP authentication testing with RADIUS server (FreeRADIUS) ............. 88
FX9600 Serial Port Configuration ............................................................................................. 88
Serial Port Configuration - Debug Port ................................................................................ 88
Serial Port Configuration - Push Data Port 89
Serial Port Configuration - Free Port ................................................................................... 91
FX Connect ............................................................................................................................... 92
Using FX Connect ............................................................................................................... 92
Running Inventory on FX Connect ...................................................................................... 98
Example JSON format of Tag Data ..................................................................................... 99
Example Key-Value Pair Format of Tag Data ..................................................................... 99
Configuring the HTTP Post Server .................................................................................... 101
Configuring the HTTP Proxy Server .................................................................................. 101
Configuring USB HID ..................................................................................................................... 102
Configuring the TCP/IP Socket ......................................................................................... 103
Configuring the USB Flash Drive ...................................................................................... 105
FX Series Licensing Management ................................................................................................ 106
9
Table of Contents
FX Series Licensing Model ..................................................................................................... 106

Procuring Licenses .................................................................................................................. 106
Types of Licenses ................................................................................................................................. 106
Trial License ...................................................................................................................... 107
Perpetual License ............................................................................................................. 107
Enabling a License .................................................................................................................. 107
Time Tampering ...................................................................................................................... 107
FX Series Licensing Mechanism ................................................................................................... 108
License Acquisition Modes ...................................................................................................... 108
Acquiring License from Production Server (ON-Line) ....................................................... 108
Acquiring License from UAT Server (ON-Line) ................................................................. 110
Acquiring License from Local License Server (ON-Line) .................................................. 111
Acquiring License by Downloading Bin File (OFF-Line) .................................................... 111
Device ID ........................................................................................................................... 112
Activation ID ...................................................................................................................... 112
Returning a License .............................................................................................................................. 113
Setting Up and Managing the Local License Server ............................................................... 114
Downloading Capability Response from the Cloud Server ..................................................... 115
System Time Management ........................................................................................................... 122
IPV6 IP Sec ................................................................................................................................... 123
Change Password ......................................................................................................................... 124
FX Series User Accounts ........................................................................................................ 124
Managing User Login and Logout ........................................................................................... 125
GPIO ............................................................................................................................................. 125
Applications ................................................................................................................................... 126
Reader Profiles ............................................................................................................................. 127
FIPS Support ........................................................................................................................... 129
Firmware Version and Update ...................................................................................................... 130
Firmware Update ..................................................................................................................... 131
Commit/Discard Functionality Changes ........................................................................................ 131
Region Configuration Commit ................................................................................................. 131
New Property Change Work Flow ........................................................................................... 133
System Log ................................................................................................................................... 136
Configure System Log ............................................................................................................. 137
Reader Diagnostics ....................................................................................................................... 138
Shutdown ...................................................................................................................................... 139
Configure and Connect via Wi-Fi and Bluetooth

Wireless Network Advanced Configuration ................................................................................... 140
Sample Configuration Files ..................................................................................................... 141
Preferred Configurations for Access Points .................................................................................. 142
Access Point Configuration for Android Device ...................................................................... 143
Open Network ................................................................................................................... 143
WPA2 PSK ........................................................................................................................ 143
WPA PSK .......................................................................................................................... 144
Internet Connection Configuration for iPhone ......................................................................... 144
Connecting to a Wireless Network Using a Wi-Fi Dongle ..................................................................... 145
Connecting to a Peer Device over Bluetooth Using a Bluetooth Dongle ...................................... 149
Copying Files to the Reader ......................................................................................................... 151
10
Table of Contents
Application Development
Introduction ................................................................................................................................... 152
Firmware Upgrade
Introduction ................................................................................................................................... 153
Prerequisites ................................................................................................................................. 153
Failsafe Update ............................................................................................................................. 154
Two-step Firmware Update ........................................................................................................................ 154
Update Phases ............................................................................................................................. 155
Updating FX Series Reader Software ........................................................................................... 156
Verifying Firmware Version ..................................................................................................... 156
Updating Methods ................................................................................................................... 157
Using a USB Drive (Recommended) ................................................................................ 157
File-Based Update ............................................................................................................ 159
FTP-Based Update ........................................................................................................... 161
Verifying Firmware Version ..................................................................................................... 162
EtherNet/IP
Introduction ................................................................................................................................... 164
EtherNet/IP ................................................................................................................................... 164
Using EtherNet/IP ................................................................................................................... 164
Supporting RFID Operations Through EtherNet/IP ................................................................. 165
Cellular Connectivity with Sierra Modem

Introduction ................................................................................................................................... 167
Cellular Connectivity with Sierra Modem ...................................................................................... 167
Steps to be followed for receiving GPS coordinates. .................................................................... 168
Configure RV50 for sending GPS coordinates: ....................................................................... 168
Sierra Modem and reader can be connected in two different ways. ............................................. 170
Connection Via RNDIS ............................................................................................................ 170
Connection via network hub: ................................................................................................... 171
Steps to be followed to send reader data to cloud using Sierra Modem. ...................................... 173
SOTI MOBI Client

Introduction ................................................................................................................................... 177
SOTI MOBI Client ......................................................................................................................... 177
Gen2 V2 Enhancement
Introduction ................................................................................................................................... 180
Gen2 V2 Enhancement ................................................................................................................. 180
Reader Configuration via USB Thumb Drive

Introduction ................................................................................................................................... 181
Configuring Reader with USB Thumb Drive ................................................................................. 181
11
Table of Contents
GPS and Triggers for Trucking and Delivery

Introduction ................................................................................................................................... 183
GPS and New Triggers for Trucking and Delivery Use Cases ..................................................... 183
Specific Examples Of Trigger Configuration ..................................................................... 185
Moving and Stationary Tags

Introduction ................................................................................................................................... 190
Moving vs Stationary ..................................................................................................................... 190
REST RCI Support

Introduction ................................................................................................................................... 196
REST RCI Support ........................................................................................................................ 196
Communication ....................................................................................................................... 197
Troubleshooting
Troubleshooting ............................................................................................................................ 198
Troubleshooting for Licensing Errors ............................................................................................ 203
Licensing Error Logs

Licensing Error Logs ..................................................................................................................... 207
Technical Specifications
Technical Specifications ............................................................................................................... 214
Cable Pinouts ................................................................................................................................ 216
10/100bT Ethernet / PoE Connector ....................................................................................... 216
USB Client Connector ............................................................................................................. 217
USB Host Connector ............................................................................................................... 217
FX7500 GPIO Port Connections ............................................................................................. 218
FX9600 GPIO Connections ..................................................................................................... 218
Static IP Configuration
Introduction ................................................................................................................................... 221
Reader IP Address or Host Name is Known ................................................................................. 221
Reader IP is Not Known (DHCP Network Not Available) .............................................................. 223
RF Air Link Configuration

Introduction ................................................................................................................................... 225
Radio Modes ................................................................................................................................. 225
Copying Files To and From the Reader

Introduction ................................................................................................................................... 230
SCP ............................................................................................................................................... 230
FTP ............................................................................................................................................... 230
12
Table of Contents
FTPS ............................................................................................................................................. 230
Data Protection
Introduction ................................................................................................................................... 231
Index
13
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.
14
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 (for example, 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 (describes Low Level Reader Protocol (LLRP) and
Reader Management (RM) extensions for the reader), p/n 72E-131718-xx
• RFID Demo Applications User Guide (provides instructions for using sample applications which
demonstrate how to use Zebra RFID readers), p/n 72E-160038-xx
• 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: zebra.com/support.
15
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: 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.
16
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 18
• Step 2, Connecting to the Reader on page 19
• Step 3, First Time or Start-Up Login on page 19
• Step 4, Set Region on page 22
• Step 5, Read Tags on page 24
17
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 32.
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 42 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
18
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 or Start-Up Login

When starting the reader for the first time the reader will force the user to change the admin password. To log in for
the first time, and change the password, follow the steps below:
1. In the User Login window, select admin in the User Name drop-down menus and enter change in the
Password field and click Login.
Figure 3 User Login Window
19
Quick Start
2. A dialog will appear, indicating that the reader login is performed using the default password and the reader
needs to switch to HTTPS mode to allow the user to change the password. Click OK.
3. Reader will now switch to HTTPS mode and display the message asking the user to log in again using HTTPS
mode.
4. Change the URL in the browser address box to use HTTPS instead of HTTP and press Enter. Since the reader
starts up with a self signed certificate, the browser might issue a warning about it not being able to verify the
certificate. Accept any risks and continue.
5. Type change in the Password field again and click on Login. Click OK on the web dialog, when it says that it
will redirect you to change password page.
6. A Change Password page will appear. Enter the Old Password as change and enter the New Password.
Re-enter new password to confirm.
20
Quick Start
Enter your password that should satisfy the following criteria:

• Should contain minimum of 8 and maximum of 15 characters
• English uppercase characters (A through Z)
• English lowercase characters (a through z)
• Base 10 digits (0 through 9)
• Non-alphabetic characters (for example, !, $, #, %)
• Should not use previously used five passwords
21
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. On the Configure Region Settings window (see Figure 4):
a. Select the region from the drop-down menu.
b. Select the Communication Standard, if applicable.
c. Select Frequency Hopping, if applicable.
d. Select the appropriate channel(s), if applicable.
e. Select the I understand check box.
2. 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.
3. When the commit completes, a gray floppy disk icon displays indicating that the commit completed
successfully. See Commit/Discard Functionality Changes on page 131 for more information.
Figure 4 Selecting the Region
22
Quick Start
Figure 5 Region Configuration, Operation Successful Window
23
Quick Start
Step 5, Read Tags

Select Read Tags to view the Reader Operation window.
Figure 6 Read Tags Window
Read Tags
On the Reader Operation window (see Figure 6):
• 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 is first seen.
24
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
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.
25
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
Antenna Ports (Four Ports, Reverse TNC) Reset GPIO USB USB 10/100BaseT Power
Client Host Ethernet (with PoE)
26
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 19 on page 214 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
36 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 41 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 38 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.
27
Getting Started

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 37 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 42.
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
28
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
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.
29
Getting Started
FX9600 Rear Panel

Port Description
Antenna Ports Four port version: Connect up to four antennas.
(Reverse TNC) Eight port version: Connect up to eight antennas.
See Table 19 on page 214 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 36 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 41 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 38 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 37 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.
30
Getting Started
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 42.
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
31
Installation and
Communication
Introduction
This chapter includes the following FX7500 and FX9600 RFID reader installation and communication procedures:
• Unpacking the Reader on page 32

• Mounting and Removing the FX Series Readers on page 33
• Mounting Tips on page 33
• Mounting the FX7500 With a Mounting Plate on page 33
• FX7500 Direct Mounting on page 34
• Connecting FX7500 and FX9600 RFID Reader Antennas on page 36
• Communications and Power Connections on page 37
• Ethernet Connection on page 37
• USB Connection on page 38
• GPIO Interface Connection on page 41
• System Start-up/Boot LED Sequence on page 42.
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.
32
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
on page 34.
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 in. diameter by 7/8 in. deep holes. For drywall/masonry
surfaces, drill two 3/16 in. diameter by 7/8 in. deep (min) holes and install using the provided
anchors.
33
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 in. centers,
+/- 1/32 in.
2. For wood surfaces, drill two 1/8 in. diameter by 7/8 in. deep holes on 4.192 in. centers. For drywall/masonry
surfaces, drill two 3/16 in. diameter by 7/8 in. deep (min) holes on 4.192 in. 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.
34
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.
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 in.)
Mounting
Tab (4)
110.7 mm
(4.4 in.)
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.
35
VESA Mounting
The FX9600 may be mounted via four VESA hole on 100 mm x 100 mm pattern using 10-32 screw.
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
1
Antenna 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 on page 37):

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.
36
Figure 15 FX7500 RFID Reader Antenna Connection
Rear Panel
Figure 16 FX9600 RFID Reader Antenna Connection
Rear Panel
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 26) or FX9600 reader
(see Figure 10 on page 29).
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 42.
37
9. On a networked computer, open an Internet browser and connect to the reader.

See Connecting to the Reader on page 49.
10. Log in to the Administrator Console. See Administrator Console Login on page 51.
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 26 or Figure 10 on page 29.
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 42.
4. On a networked computer, open an Internet browser and connect to the reader.
See Connecting to the Reader on page 49.
5. Log in to the Administrator Console. See Administrator Console Login on page 51.
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 40 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 26 or for the FX9600, see Figure 10 on page 29. 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 39).
To install the RNDIS driver on the host.
1. Download the installer file Zebra RNDIS.msi from 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.
38
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.
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.
39
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.
40
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 22 on page 218 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.
41
LED Sequences
System Start-up/Boot LED Sequence
For LED locations, see Figure 9 on page 28 for the FX7500 and Figure 12 on page 31 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 Link Local 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.
42
Reading Tags
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.
After the reader powers up, test the reader. See System Start-up/Boot LED Sequence on page 42.
1. Enable tag reading using the web-based Administrator Console (see Read Tags on page 77) 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 28. The distance between the tag and the
antenna is the approximate read range.
43
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 zebra.com/123rfid.
Figure 20 123RFID Desktop Reader Screen
44
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 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.
45
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.
46
• 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 127.
Resetting the Reader

To reset the reader, press and hold the reset button for not more than 2 seconds. See Figure 8 on page 27 for the
reset button location. The reader reboots but retains the user ID and password.
See System Start-up/Boot LED Sequence on page 42.
NOTE: Hard rebooting the reader (disconnecting power) is not recommended as this discards all
the tag events and system log information.
47
Auto Discovery
The FX7500 and FX9600 readers supports WS-Discovery and Bonjour (Link Local 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
48
Connecting to the Reader

NOTE: This section describes procedures in a Windows environment.
To use the Administrator Console to manage the reader, 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 47.
Connect to the reader in one of two ways:
1. Connecting via Host Name on page 50.

2. Connecting via IP Address on page 50. (To obtain the IP address, see Obtaining the IP Address via Command
Prompt on page 49)
There are three ways to assign an IP address to the reader:
1. Using DHCP on the network.

2. Using Link Local Networking when DHCP Server is Not Available on page 50.
3. Statically assigning an IP. See Static IP Configuration on page 221.
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 Link Local Networking when
DHCP Server is Not Available on page 50.
NOTE: When using Link Local 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 47. 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 50.
Figure 23 IP Ping Window
49
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. The 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 51 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 recommended browsers are IE11 (disabling Compatibility View is recommended),
Chrome v58, and FireFox v54.
2. Enter the IP address in the browser (for example, 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 51 to login to the reader.
Using Link Local Networking when DHCP Server is Not Available

If a DHCP server is not available, the FX7500 and FX9600 readers can use Link Local networking to automatically
provide a unique network IP address. The reader can then use TCP/IP to communicate with other computers also
using a Link Local networking-generated IP address.
NOTE: When using Link Local 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 Link Local 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.
50
When Link Local 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 Link Local algorithm is 169.254.85.148.
Windows-based computers support APIPA/Link Local networking by default when DHCP fails. To enable APIPA
for a Windows PC, go to http://support.microsoft.com/ and search for APIPA.
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 as shown in Figure 24.
In the User Login window, select admin in the User Name drop-down menus and enter change in the Password
field.
• For global reader configurations, the Configure Region Settings window appears
• For the US reader configurations, the Reader Administration Console main window appears
51
Setting the Region

For the 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 the readers to operate in the United States (under
FCC rules). Skip this step if you are configuring the readers to be used in the US.
1. On the Configure Region Settings window:

a. Select the region from the Region of operation drop-down menu.
2. Select Set Properties. The Operation Successful window appears. Commit step is no longer required to
save configuration. See Commit/Discard Functionality Changes on page 131.
Figure 25 Selecting the Region
52
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 display 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 55

• Operation Statistics - see Reader Statistics on page 56
• Gen2 Optional - see Reader Gen2 Optional Operation Statistics on page 57
• NXP - see NXP Custom Command Operation Statistics on page 58
• Events - see Event Statistics on page 59
• Other Custom - see Other Custom Command Operation Statistics on page 60
• NTP Statistics - see NTP Statistics on page 61
• Configure Reader - see Configure Reader on page 62
• Read Points - see Read Points on page 63
• Advanced - see Read Points - Advanced on page 64
• Region - see Configure Region on page 65
• Certificates - see Certificates on page 66
• Read Tags - see Read Tags on page 77
53
• Communication - see Communication Settings on page 78

• LLRP - see Configure LLRP Settings on page 81
• SNMP - see SNMP Settings on page 82
• Wireless - see Wireless Settings on page 83
• Serial Port Configuration - see FX9600 Serial Port Configuration on page 88
• FX Connect - see FX Connect on page 92
• Services - see Network Services Settings on page 84
• Zebra IoT Connector
• Configuration
• Connection
• 802.1x EAP
• Date/Time - see System Time Management on page 122
• IP Sec - see IPV6 IP Sec on page 123
• License Manager - see FX Series Licensing Management on page 106
• Change Password - see Change Password on page 124
• GPIO - see GPIO on page 125
• Applications - see Applications on page 126
• Profiles - see Reader Profiles on page 127
• Firmware - see Firmware Version and Update on page 130
• Update - see Firmware Update on page 131
• System Log - see System Log on page 136
• Configure - see Configure System Log on page 137
• Diagnostics - see Reader Diagnostics on page 138
• Shutdown - see Shutdown on page 139
• Logout - select Logout to log out from the Administrator Console.
54
Status
Select Status from 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
Status
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.
55
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
Operation
Statistics
• 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.
56
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
Gen2
Optional
• 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.
set a new interval.
57
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
NXP
• 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.
set a new interval.
58
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
Event
• 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.
set a new interval.
59
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
Other
Custom
• 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.
set a new interval.
60
NTP Statistics
Select NTP Statistics to view the NTP Statistics window. This window provides options to view the reader NTP
statistics.
Figure 33 NTP Statistics Window
NTP
Statistics
NTP statistics provide information to the user about how often the Reader communicated with NTP server to
synchronize date and time. User can take appropriate action depending upon the results of last synchronization
attempt.
Time Elapsed Since Last Poll: This value indicates the time that has elapsed since the reader last attempted to
sync its time from the NTP server.
Polling Rate: This Values indicates the frequency at which the reader is polling the NTP Server.
Last 8 Sync Status: This Value indicates the status (success/failure) to reach source of the last 8 attempts. A
value of 0 indicates a failure for sync time on all of the last 8 attempts. And a value of 377 indicates success on all
of the last 8 attempts.
Offset: Indicates the time difference, in milliseconds, between the reference time and system clock.
61
Configure Reader
Use the Configure Reader menus to access the following functions.
Reader Parameters
Select Configure Reader from the selection menu to configure reader settings using this window.
Figure 34 Reader Parameters
Configure
Reader
• 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 non-zero value to enable this feature for the following purposes:
• To save the battery capacity when charging the reader with a vehicle power outlet.
• To lower the reader temperature by turning off the radio function.
• 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.
62
• 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 from the selection menu to configure the read point settings and view the
current read points state.
Figure 35 Configure Read Points
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.
63
• 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 36 Advanced Antenna Configuration
Advanced
NOTE: This page is not supported when LLRP is configured in secure mode.
64
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 37 Configure Region Settings Window
Region
• 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.
65
• 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 84.
• File Transfer Service (FTPS - explicit SSL/TLS over FTP). See Network Services Settings on page 84.
• 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 81.
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 81 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.
66
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 38 Setting HTTPS Mode
NOTE: The user cannot change Web Server mode if Inventory is in progress.
Services
Select Configure Reader > Certificates. The Certificate Configuration page provides the details of certificates
and an option to download custom certificates.
Figure 39 Certificate Configuration Page
Certificates
67
FX readers allow the user to import and install multiple certificates on the reader. The reader makes a
distinction between three kinds of certificates.
• Server
• Client
• App
Server Certificate
Reader allows installation of only one server certificate. The installed Certificate is used on the reader for
securing communication interfaces like HTTPS, FTPS Secure LLRP and Secured Shell.
Server certificate can undergo certificate operations like refresh/view public key. Delete operation is not
applicable.
update
Client Certificate
Reader allows installation of a multiple client certificates. For example, one such installed Certificate can be
used by the reader to connect to 802.1x networks if configured with RADIUS server.
Client certificate can undergo certificate operations like update/refresh/delete/view public key.
App Certificate
Reader allows installation of multiple app certificates. The installed app Certificates can be used by any
installed user app for its own purposes.
App certificate can undergo certificate operations like update/refresh/delete/view public key.
By default, the reader uses self-signed certificates for server certificate (characterized by Subject name and
Issuer in Installed Certificates(s) section) 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 81.
• 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 84. 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 Installed Certificates(s) section displays the details of installed certificates such as issuer, serial number,
type, name, and validity information.
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), Root CA bundled into a single file. The certificate must be
68
hosted on a secure FTPS/HTTPS/SFTP server. The following options are used to perform the update:FTPS URL:
Full path to server, including ftps:// prefix, where the .pfx file is hosted.
Certificate Type: Type of the Certificate being installed.
Name: A friendly name for the Certificate.
URL: URL from where to pull the certificate. HTTPS/FTPS/SFTP URLs are supported.
User ID: The user name to be used for authenticating to the server hosting the certificate.
Password: The password for the above mentioned user name.

PFX Password: The password to the imported PFX f il e.
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

The 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
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.
69
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
#
#
# 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.
70
#
[ 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
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 = ca@xyz.com
organizationName = XYZ
71
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
extendedKeyUsage = serverAuth, clientAuth, nsSGC, msSGC
nsComment = "SSL/TLS Certificate"
72
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
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
countryName = US
emailAddress = root@clienthostname.mycompany.com
organizationName = Company Name
organizationalUnitName = Department Name
73
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'
74
CreateReaderCert.sh
#Make sure passwords are unique and secret
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....'
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
75
CreateClientCert.sh
#Make sure passwords are unique and secret
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....'
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.
76
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 40 Read Tags Window
Read Tag
• 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 is first seen.
77
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 41 Configure Network Settings - Ethernet Tab
Communication
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.
78
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 42 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.
79
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 43 Configure Network Settings - Bluetooth Tab
Communication
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.
80
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 44 Configure LLRP Settings Window
LLRP
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.
81
• 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.
• Reconnect to Server: This allows the reader to reconnect to llrp server when the reader is configured as
llrp client if the connection to the server is lost. This option has no effect when the reader is configured as
llrp server.
SNMP Settings
Select SNMP to view the Configure SNMP Settings window.
Figure 45 Configure SNMP Settings Window
SNMP
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.
82
Wireless Settings
Select Wireless to view the Reader Wireless Setting Parameters window.
Figure 46 Wireless Settings Window
Wireless
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
Dongle Model Zebra Zebra

FX7500 FX9600
BELKIN F7D2102 N300 MICRO WIRELESS N USB ADAPTER Yes Yes
PANDA WIRELESS PAU06 300MBPS WIRELESS N USB ADAPTER Yes Yes

ASUS (USB-AC56) DUAL-BAND WIRELESSAC1300 USB 3.0 Yes Yes
WI-FI ADAPTER
TP-Link TLWN821N N300 USB Wireless Netgear Nighthawk Yes Yes

AC1900 Wi-Fi USB Adapter (A7000)
TP-Link Nano USB Wifi Dongle 150Mbps (TLWN772N) Yes Yes
TP-Link Archer T2U 11AC USB WiFi Adapter - AC600 Yes Yes
AC1750 Dual-Band Wi-Fi USB 3.0 Adapter Yes Yes

TP-Link AC 1200 - Alfa Network AWUS036H(Realtek Yes Yes
RTL8187L chipset) Yes Yes
CCrane Versa Wifi 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.
83
• 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.
Network Services Settings

Select Services to view the Configure Network Service Settings window.
NOTE: The user cannot change Web Server mode if Inventory is in progress.
Figure 47 Configure Network Service Settings Window
Services
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.
84
• 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.
802.1x EAP Configuration

Select 802.1x EAP to view the 802.1x EAP configuration.
NOTE: The FX Series readers support 802.1x over Ethernet interface only.
NOTE: 802.1x Configuration is allowed in HTTPS mode only.
To configure 802.1x User must pick an outer authentication and inner authentication method from the supported
list of methods. Based on the inner authentication method picked, user will be required to either enter a
username/password or pick a certificate to use from the installed list of certificates. To install a certificate from the
reader, please refer to the Certificates section of this document.
Figure 48 Configure 802.1x Window
802.1x EAP
The reader supports the following combinations for the inner and outer methods of authentication for 802.1x EAP.
Outer Method Inner Method
PEAP TLS, MSCHAPV2

TTLS TLS, MSCHAPV2
TLS NA
The following configuration options are available:
• Interface: Selects network interface for 802.1x EAP authentication. Currently 802.1x is supported on
Ethernet interface only.
• Status: Indicates the current 802.1x connection status.
85
• Outer: The Outer method of authentication to be used.

• Inner: The Inner method of authentication to be used.
• UserName: provide username if the inner method selected in MSCHAPV2.
• Password: provide password if the inner method selected is MSCHAPV2
• Cert: Select the cert to be used from the list of installed certificates on the reader.
• Auto Connect: Enabling Auto Connect will ensure the reader connects back to 802.1x network on reboot.
FX Series Reader 802.1x EAP configuration/Testing with FreeRADIUS

This section is for configuring and testing Fx Reader 802.1x EAP authentication with FreeRADIUS server.
RADIUS Server (FreeRADIUS) Configuration

1. Install FreeRADIUS on Ubuntu x86_64 host.
$ sudo apt-get install freeradius
2. Add sample user ‘user1’ with password ‘user123’ like below at file ‘/etc/freeraidus/3.0/users’:
"User1" Cleartext-Password := "password123"
Reply-Message = "Hello, %{User-Name}"
NOTE: The username ‘user1’ and password ‘password123’ is given for inner method ‘MSCHAPV2’ of outer
method ‘PEAP/TTLS’. See 802.1x EAP Configuration on page 85.
3. Update IP address and secret password of Cisco switch at file ‘/etc/freeradius/3.0/clients.conf’ under section
‘client localhost’ as below:
client localhost {
ipaddr = 192.168.1.100
secret = testing123
}
4. Modify the following lines change at file ‘/etc/freeradius/3.0/mods-enabled/eap’ by uncomme nting or appl
the changes wherever are possible.
eap
{
default_eap_type = peap
tls-config tls-common
{
private_key_file = ${certdir}/server.key
certificate_file = ${certdir}/server.pem
ca_file = ${certdir}/ca.pem
disable_tlsv1_2 = no
dh_file = ${certdir}/dh
tls_min_version = "1.0"
tls_max_version = "1.2"
}
}
5. Create Signed Certificates.
86
a. Change to directory ‘/etc/freeradius/3.0/certs/’ and remove existing certificate

$ sudo -i; cd /etc/freeradius/3.0/certs/
$ rm -f *.pem *.der *.csr *.crt *.key *.p12 serial* index.txt*
b. Execute following commands for creat i ng Root CA, ser ver and cli ent cer ti f i cates
$ sudo make ca.pem
$ sudo make server.pem
$ sudo make client.pem
$ chown freerd:freerd server.key server.pem client.pem ca.pem
c. Execute the below command for generating PFX file ‘client.pfx
$ openssl pkcs12 -export -out client.pfx -inkey client.key -in client.pem -certfile ca.pem -passin
pass:whatever -passout pass:whatever
NOTE: The sample password ‘whatever’ provided here is given for PFX password during update
certificate. See Certificate Configuration on page 67.
6. Start FreeRADIUS server.
$ sudo freeradius -X
Cisco Switch (Cisco C1000-24FP-4G-L) Configuration

1. Below figure show configuring switch with IP address details under menu “ConfiguraSwitchSwitch”:
2. Below figures show configuring Radius server details in switch under menu “servisecurityAAA
ServerServerAdd”:
NOTE: For “Server Address” add IP address of FreeRADIUS and Shared Secret “testing123” with port details as
above. The shared secret is already mentioned in file ‘/etc/freeradius/3.0/clients.conf’ under secti
“client localhost” while configuring FreeRADIUS at Ubuntu 18.04 x86_64 host
87
Cisco C1000-24FP-4G-L
Fx Reader 802.1 EAP authentication testing with RADIUS server (FreeRADIUS)

1. Install the generated PFX file at Fx Reader. See Certificate Configuration on page 67.
2. Connect Fx Reader at dotx (not MAB) configured network port through ethernet of Cisco switch.
3. Connect DSL Modem with DHCP server running to yet another ethernet network port of Cisco switch.
4. Connect Ubuntu 18.04 host (which has FreeRADIUS configured) ethernet into yet another network port of
Cisco switch.
5. Connect to 802.1x EAP network authentication. See 802.1x EAP Configuration on page 85.
NOTE: - Both Fx Reader and FreeRADIUS server must be synchronized for date and t i mef or cer ti f i cat e based
802.1x authent i c at i onl i ke TLS for to work and on generat in g cert if icate at Ubunt u x86_64 h
- Following 802.1x EAP outer/inner authent i c at i ons are success ful wi th Fr eeRADI US ser ver:
1. PEAP/MACHAPv2
2. TTLS/MSCHAPv2
3. TLS
4. TTLS/TLS
FX9600 Serial Port Configuration

The external FX9600 serial port can be configured to one of the following three modes:
• Debug port.
• Push data - Allows a connected client to receive tag data when inventory starts from the web console.
• Free port (default) - 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.
88
Figure 49 Serial Port Communication - Debug
Serial port
Configuration
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 50).
Figure 50 Serial Port Communication - Push Data Configuration
Save
Connect
2. Select Save to save the current settings.
89
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 52.
Figure 51 Serial Port Communication - Push Data Inventory Started
90
Figure 52 Tag Data
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 53 Serial Port Communication - Free Port
91
FX Connect
FX Connect is a licensed feature which enables users to collect data from FX series RFID readers (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 106 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
17 for the 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.

Figure 54 FX Connect
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.
92
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.
Figure 55 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 101 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.
93
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 101.
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.
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).
94
Table 8 HTTP Post Configurable Options (Continued)

Option Description
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.
• TID - TID Memory Bank of the Tag read.
• User Bank - User Memory Bank of the Tag read.
• 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.
GPO Event Selection These are control options for GPO Ports. This section has options for
changing GPO port from High to Low or Low to High during inventory.
GPO Event Selection description is as follows:
• Inventory Start - in this condition the port number, port state it

should be changed to, time in seconds to reset the port state
should be mentioned, to change the port state on start of
inventory.
• Inventory Stop - in this condition the port number, port state it
should be changed to, time in seconds to reset the port state
should be mentioned, to change the port state on stop of
inventory.
• TAG(s) being read - To change the port state to specified state
and reset it back within the time mentioned in seconds, if tag
matching the given tag pattern is read.
• No Tag in the field of view (FOV) - To change the port state to
specified state and reset it back within the time mentioned in
seconds, if no tag in FOV for duration mentioned in seconds.
95
Figure 56 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).
GPO Event Selection See Table 8.
96
Figure 57 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.
97
Figure 58 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.
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.
98
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","see
nCount":"4","timeStamp":"30/3/2020
17:7:23:67","phase":"0.00","channelIndex":"1","TID":"E2806D122000550224D7E6B3","User":"55660000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000","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","TID":"E2806D122000400224D7E6B4","User":"55660000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000","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"}]}
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,
99
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,
TID=E2806D122000400224D7E6B4,User=55660000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000,
3. With EPC only in Tag Field Selection and Line Ending as LF (Line Feed).
303800000333f10000000039,
ad72120544894bb660000059,
ad72120643c065b4867e00ab,
e280689000000000182a55b1,
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
epc=e280689000000000182a55b1,pc=3000,antennaport=2,peakrssi=-60,seencount=1,timestamp=15112019
epc=ad72120544894bb660000059,pc=3000,antennaport=2,peakrssi=-55,seencount=44,timestamp=1511201 9
TID=E2806D122000400224D7E6B4,User=556600000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000,
NOTE: In all the examples shown in from No. 1 to 4, Comma (,) is selected as the Delimiter.
100
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.')
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 starts 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
101
$ 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.
To run FX Connect in Keyboard Emulation:

1. Open the reader web console to FX Connect (see Figure 54 on page 92).
2. Connect the reader to the host machine through the USB Client port (same as RNDIS).
See Figure 7 on page 26 and Figure 10 on page 29 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.
102
Figure 59 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 needs to be compiled on the host machine:
/*
* tcpclient.c - A simple TCP client
* usage: tcpclient <server IP> <port>
*/
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <netdb.h>
#include <sys/ioctl.h>
103
#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);
if (server == NULL) {
fprintf(stderr,"ERROR, no such host as %s\n", hostname);
exit(0);
}
printf("Connecting to server : %s\n", server->h_name);
104
/* 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;
}
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 no configuration is required. The user just needs to attach the USB flash drive in
the 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.
105
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. Topics covered in this section are
as follows:
• License activation in the ON-Line and OFF-Line modes. See License Acquisition Modes on page 108.
• How to return licenses. See Returning a License on page 113.
• Setup and administration of the license server. See Setting Up and Managing the Local License Server on
page 114.
• How to download capability response from the cloud server. See Downloading Capability Response from
the Cloud Server on page 115.
See Troubleshooting for Licensing Errors on page 203 to troubleshoot errors related to licensing.
IMPORTANT: Prior to license acquisition, the FX Readers date and time must be correctly
synchronized. See Time Tampering on page 107 for more details.
Clear the Chrome/FireFox browser cache after upgrading the current firmware version
3.0.35/3.1.12 to 3.6.28 or newer because the cache is not cleared automatically. The
browser cache may cause issues to the web UI pages. You can also right-click on the
web UI page, then select Reload Frame in the menu.
NOTE: The FX7500 does not support Network Connect. The FX9600 supports both FX Connect
and Network Connect.
FX Series Licensing Model

FX Connect and Network Connect features require a valid license to be installed in the reader. The FX Connect or
Network Connect licenses purchased from Zebra determines the number of FX7500 and 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 a trial license 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 or return the license on the readers.
Procuring Licenses
For the customers, partners, and distributors require that a FX Series product license for FX Connect and Network
Connect, request a trial license through your Account Manager.
Account Manager and Sales Engineers can request a trial license for FX Connect and Network Connect for
customers, partners, or distributors via SFDC Forms.
Zebra Engineering can request a trial license for FX Connect and Network Connect via Service NOW.
Types of Licenses
NOTE: The FX7500 does not support Network Connect (EtherNet/IP).
There are four type of licenses for FX Readers:
106
• FX Connect Trial License

• FX Connect Perpetual License
• Network Connect (EtherNet/IP) Trial License
• Network Connect (EtherNet/IP) Perpetual License.
Trial License
The trial 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 deactivated 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 the FX Reader, procure the appropriate license (trial 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 licenses are time dependent operations The FX Reader must
be configured with the current date and time. Failing to do so results in errors when 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
NOTE: Clock Wind Back is enabled in the firmware. Any back tracing of date or time results in a
license error.
107
Figure 60 System Time Management
FX Series Licensing Mechanism

License Acquisition Modes
A license for the FX Readers may be acquired in an ON-Line or OFF-Line modes.
There are three servers for the ON-Line mode, which are as follows:
NOTE: The On-Line mode license acquisition (from the Production, UAT, and Local License
servers) requires an Internet connectivity.
• Production Server (ON-Line Mode). See Acquiring License from Production Server (ON-Line)
• UAT Server (ON-Line Mode). See Acquiring License from UAT Server (ON-Line) on page 110.
• Local License Server (ON-Line Mode). See Acquiring License from Local License Server (ON-Line) on
page 111.
See Acquiring License by Downloading Bin File (OFF-Line) on page 111 to acquire licenses in the OFF-Line mode.
Acquiring License from Production Server (ON-Line)

This method is for the external customer. This is the default license acquisition with minimal setup and
configuration. The FX Reader must have an Internet connection to acquire a license from the Production server.
The license server is hosted on the cloud and the FX Reader contacts the cloud-based license server to acquire
licenses.
NOTE: If the Install and Run application option is selected (see Figure 61 on page 109) when you
are installing the EtherNet/IP license, after the license is installed, the EtherNet/IP
application forces a login to the FX Reader and the current web session is logged out. Log
in again to use the web browser.
108
Figure 61 Manage License - Production Server
To acquire licenses from the Production server:

1. Select the appropriate options from the drop-down boxes as shown in Figure 61.
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 is already installed, uncheck the Install and Run application box.
2. Enter the 32-byte Activation ID that is provided via e-mail when the license is procured.
NOTE: To circumvent a firewall while contacting the cloud-based license server, set up a proxy
server. For detailed instructios, go to:
https://supportcommunity.zebra.com/s/article/ZSL-Licensing-Server-Connectivity?language
=en_US.
3. Click Activate to acquire the license. An Available License(s) list displays (see Figure 62) and includes the
following information:
• License Index: Lists the license number.
• License Name: This is the feature name of license, such as fx-feature connect and nc-feature-ethernetip.
• License Version: Lists the license version number.
• Expiry Date: Expiry date for the trial license. For the Perpetual license, this field shows permanent.
• License Count: Lists 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 and
mac number of device. The example shown in Figure 62 is FX9600_84_24_8D_EE_57_34.
Figure 62 Available License - Production Server
4. Click Application on the selection menu (see Figure 21 on page 47). The User Application Page window
shows the status and the progress of the package installation (see Figure 63 on page 110).
109
Figure 63 User Application Page
Acquiring License from UAT Server (ON-Line)

This method is for Zebra Engineering, such as 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 64 Manage License - UAT Server
To acquire licenses from the UAT server:
2. Enter the 32-byte Activation ID that is provided via e-mail when the license is procured.
If you are installing the FX Connect license, the firmware ignores the Install and Run
application selection.
3. Click Activate to acquire the license. An Available License(s) list displays (see Figure 65).
Figure 65 Available Page - UAT server
110
Acquiring License from Local License Server (ON-Line)

This license acquisition method is for both external customers and Zebra Engineering. To acquire the license from
the Local License Server (LLS), setup a LLS within your LAN network (see Setting Up and Managing the Local
License Server on page 114 for the detailed procedures) and the FX Reader contacts the Local License Server to
acquire licenses.
Figure 66 Manage License - Local License Server
To acquire licenses from the LLS:
1. The LLS is available in the local LAN Network. If the LLS is not set up, see Setting Up and Managing the Local
License Server on page 114.
3. In the Server URL field, enter the LLS link with the format
http://<Server_ip or host_name>:port_number/request.
NOTE: A LLS 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.
5. Click Activate to acquire the license. An Available License(s) list displays (see Figure 67).
Figure 67 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. The Capability Response must be downloaded from the server to acquire license with
this method. See Downloading Capability Response from the Cloud Server on page 115 for more details.
Have the Device ID and the Activation ID before downloading the capability response.
111
Device ID
The Device ID is the unique identification number of the FX device on the Zebra Licensing Server. The 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 68 Reader Label
Activation ID
The Activation ID is the unique 32-bit alpha-numeric number provided 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 for
credentials. For Zebra Engineering such as Sales Engineers, Developers, Test Engineers,
go tohttps://zebra-licensing-uat.flexnetoperations.com/ for credentials.
To acquire license in the OFF-Line mode:
1. Download the Capability Response (see Downloading Capability Response from the Cloud Server on page
115).
2. On the Manage License screen (see Figure 69):
• Select the desired options from the License Operation and the Device drop-down menus.
• Select the Install and Run application check box to install the EtherNet/IP package and start the
application.
Ignore the Install and Run application check box if you are installing the FX Connect
licenses.
112
Figure 69 Manage License - OFF-Line Mode
3. Next to Upload License, click on Choose File and locate the bin file downloaded in Step 1.
4. Click Activate button to activate the license. An Available License(s) list displays (see Figure 70).
Figure 70 Available License - OFF-Line
Returning a License
NOTE: The FX reader must be connected to the Internet to return a license.
Users can return the acquired license to the cloud server only regardless of whether the license is acquired
OFF-Line or ON-Line.
1. On the Manage License screen (see Figure 71), select the desired options from the License Operation and
the Device drop-down menus.
Figure 71 Manage License - Return License
2. In the Server Type drop-down menu, select the server type from which the license is acquired.
3. 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.
4. Select Release. If there are no licenses available, a License Unavailable window displays (see Figure 72 on
page 114).
113
Figure 72 License Unavailable Screen
Setting Up and Managing the Local License Server

Figure 73 illustrates the process of license acquisition from a local license server (LLS).
Figure 73 Local License Server Acquisition
To setup the LLS within the LAN network:
NOTE: Refer to the Local License Server Administration Guide, p/n MN-003302-xx for detailed
installation and registration instructions.
1. Install the LLS.

2. Configure the LLS.
3. Register the LLS.
4. Acquire licenses in the LLS.
5. Input the Activation ID to the reader.
6. The reader acquires the license from LLS.
114
Once the local license server is set up, set up the FX Reader to acquire licenses from the LLS by changing the
license_server_url field in HTML page file to the URL with the format
http://<license_server_ip_or_hostname>:7070. The LLS by default listens on port 7070 which can be changed
in the license server configuration. If a non-default port is configured in the LLS, 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.
Downloading Capability Response from the Cloud Server

To download the Capability Response from the Cloud server:
1. Log in before entering the Zebra Licensing Server at https://zebra-licensing-uat.flexnetoperations.com/.
NOTE: External customers may need to use a different URL.
2. Enter the Username and Password.
Figure 74 Zebra Licensing Server Login Window
115
3. A Home screen displays (as shown in Figure 75).
Figure 75 Software Licenses Portal Home Screen
4. Select the Devices tab drop-down arrow to select Create Device. A New Device screen displays
(see Figure on page 117).
NOTE: FX9600_84_24_8D_EF_B2_BB in Figure on page 117 is an example.
5. On the New Device screen:

• Enter the ID in the format <Model Name>_<Mac_Address> (see Device ID on page 112 for more details).
• Enter the Name which is same as the ID. Do not select the Runs license server check box and leave Site
Name as empty.
116
Figure 76 Create New Device
Devices
Name
ID
6. Click Save. The page displays Device created successfully message when the device is successfully
registered.
Figure 77 View Device Screen
117
7. Select Action to expand the drop-down list. Select Map By Activation ID (see Figure 78).
Figure 78 View Device Action Drop-Down Menus
8. In the Map by Activations IDs screen, enter the Activation ID (see Figure 79). If you have multiple IDs, make
sure to enter each ID on a new line.
Figure 79 Map by Activation IDs Screen
9. Click Validate. The page displays Validation successful message when the Activation ID is successfully
validated.
118
10. Edit the Qty to add (see Figure 80) or all the licenses are mapped to a single device. For a standalone license,
the value is 1. For LLS, a quantity is required.
11. Click Save.
Figure 80 Activation ID Validation Successful
12. The page displays a Entitlement successfully mapped message (see Figure 81).
Figure 81 Device Entitlement Successfully Mapped
119
13. Click Action to expand the drop-down list (see Figure 82). Select Download Capability Response. The bin
file is available in the Download folder.
Figure 82 View Device Action Drop-Down Menus
14. Click the Devices tab to enter Devices screen.

15. On the Devices screen (see Figure 83):
a. Click the drop-down arrow next to the Filter icon to select Device ID.
b. Enter the Activation ID next to Search.
c. Click Search and the entitled devices are listed.
Figure 83 Device Screen
Drop-Down Arrow Activation ID Field Search

Devices
120
16. To log out, select ZSL System Test > Logout.
Figure 84 Log Out
121
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 85 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.
122
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 86 IPV6 IP Sec Window
Date Time
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.
123
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 87 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.
124
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 88 FX7500 Example GPIO Control Page
GPIO
• 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.
125
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 89 User Application Page
Applications
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.
126
NOTE: The reader executes the packages with the privileges of rfidadm user account. See the user
accounts section for information on the rfidadm user privileges.
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.
NOTE: You cannot activate any profiles if the inventory is in progress.
Figure 90 Reader Profiles Window
Profiles
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.
127
• 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.
• 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 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 24 on page 225, Table 25 on page 227, and Table 26 on page 229 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
128
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.
129
Firmware Version and Update

Select Firmware from the selection menu to view Firmware Version window. This window displays the current
software and firmware versions and allows users to upgrade the firmware.
Figure 91 Firmware Version
Firmware
Current Version displays the binary versions currently running in the reader. Last Known Version displays the
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.
130
Firmware Update
Select Update from the selection menu to view Firmware Update window. This window allows users to upgrade
the firmware of the readers.
NOTE: You must log in as Administrator to have the access to this window.
See Change Password on page 124.
The FX readers support three firmware update methods:
• 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, or SCP server-based update.
To upgrade the firmware of the readers, see Firmware Upgrade.
Commit/Discard Functionality Changes

The Commit/Discard menu is removed in the firmware version 3.0.35 or newer. After making changes to the
reader configuration, you must select Set Properties for the changes to take effect.
This sections includes two examples on how to save the changes to the reader configuration.
Region Configuration Commit

The following is an example of how the commit/discard functionality works.
1. On the Configure Region Settings window (see Figure 92 on page 132):
a. Select the region from the Region of operation drop-down menu.
2. Select Set Properties to save the new region configuration. The Operation Successful window displays a
Saving. Please wait... message with a progress symbol (see Figure 93 on page 132).
3. When the commit completes, the page displays a gray floppy disk icon (see Figure 94 on page 133). The
settings are now set and stored in the reader. If other actions are required to complete the changes (for
example, a reader reboot), the action message displays at the top of the window.
131
Figure 92 Configure Region Settings
Figure 93 Configure Region Settings - Saving Message
132
Figure 94 Configure Region Settings - Commit Complete
Floppy Disk
Icon
New Property Change Work Flow

The following explains the example of how the commit/discard functionality works when changing a property.
1. On the Configure Network Settings screen, select the appropriate options from the drop-down menus as
shown in Figure 95.
Figure 95 Configure Network Settings
2. Select Set Properties. The message Saving.Please wait... displays with a progress symbol (see Figure 96 on
page 134).
133
Figure 96 Configure Network Settings - Saving Message
3. When the commit completes, the page displays a gray floppy disk icon. The settings are now set and stored in
the reader. If other actions are required to complete the changes (for example, a reader reboot), the action
message displays at the top of the window (see Figure 97 on page 134).
Figure 97 Action Message
IMPORTANT: With the new software version, the Discard Functionality option is no longer supported.
Changes are automatically commit to the reader after selecting Set Properties.
The reset reader to factory defaults option is on the System Shutdown/Restart screen
(see Figure 98).
134
Figure 98 Enterprise Reset the Reader
135
System Log
Select System Log from the selection menu to view the System Log window. This window lists the reader log
information.
Figure 99 System Log Window
System
Log
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 selected, the log severity level filters the log content. Logs
that have severity levels equal or above the selected severity display.
• Process Selection - When this option is selected, 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 selected, 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.
136
• 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 drop-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 drop-down
menu, then select Export File. This saves the data file in the Downloads folder on the PC.
Configure System Log

Select System Log > Configure to view Configure System Log window. This window configures system log
settings. If the system log host is not set (or is not valid), log messages are not sent.
Figure 100 Configure System Log Window
Configure
This window includes 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 131 for more information.
137
Reader Diagnostics
Select Diagnostics to view the Reader Diagnostics window, which allows running diagnostics and viewing the
diagnostics report.
Figure 101 Reader Diagnostics Window
Start
Diagnostics
System Log
Diagnostics
Select Start Diagnostics to clear the system log and display 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:
1. Select System Log (see Figure 101).

2. On the System Log window (see System Log on page 136):
a. Select Process Selection only in the Apply Filter drop-down menu.
b. De-select all other processes.
c. In the Other Process text box enter:
rmserver.elf: N-D,llrpserver.elf: N-D.
138
Shutdown
To protect the integrity of the reader data, reboot the reader via the Administrator Console when necessary.
Figure 102 System Shutdown/Restart Window
Shutdown
To shut down or restart the reader:
1. Select the Shutdown from the selection menu 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 reader
reboots after the Enterprise reset is complete.
139
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 103 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.
140
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):

ap_scan=1
network={
ssid="DEV_Open"
key_mgmt=NONE
}
Wireless network with WEP encryption type (AP Name is WEP128):

ap_scan=1
network={
ssid="WEP128"
key_mgmt=NONE
wep_key0= "my secret password "
wep_tx_keyidx=0
priority=5
}
141
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 104 Example Open Network Mode
142
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 105 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 106 WPA2 PSK Configuration for Android Device
143
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.
3. Select Save to start the wireless hotspot.
Figure 107 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.
Figure 108 iPhone Device
144
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 83
for a list of supported Wi-Fi dongles.
Figure 109 FX7500 USB Host Port Location for Dongle
USB Host Port
Figure 110 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 111.
145
Wi-Fi Configuration
Figure 111 Wi-Fi Dongle Connected
3. Select Communication > Wireless.
Figure 112 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).
146
Wi-Fi Configuration
Figure 113 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 114 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.
147
Wi-Fi Configuration
Figure 115 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 116 Wi-Fi Tab - IPV6 Connecting to a Peer Device over Bluetooth Using a Bluetooth Dongle
148
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
Broadcom BCM20702A0 Yes Yes
Figure 117 USB Host Port Location for Dongle
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.
149
Wi-Fi Configuration
Figure 118 Bluetooth Dongle Connected Select Communication > Bluetooth.
3. Change the Discoverable and Pairable properties to On.
Figure 119 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.
150
Wi-Fi Configuration
Figure 120 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.
Figure 121 Communication Bluetooth Tab
Open the web page or sample application to connect to the Bluetooth IP (192.168.67.21 in Figure 121) 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.
151
Application Development
Introduction
The FX Series RFID readers can host embedded applications, so data can be parsed directly on the reader. Since
data are 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.
152
Firmware Upgrade
Introduction
This chapter provides the reader firmware update information using the web-based Administrator Console. The
following methods are available to update the firmware of the FX Series Readers:
• Using a USB drive. See Using a USB Drive (Recommended) on page 157.
• File-based update that allows uploading the firmware files from the PC (or a network location) to the reader
and running the update. See File-Based Update on page 159.
• FTP, FTPS, or SCP server-based update. See FTP-Based Update on page 161.
Use this procedure to update the following software components:
• uboot
• OS
• Reader Server Application (includes the 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.
153
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 displays red.
Two-step Firmware Update

NOTE: After the reader firmware is upgraded or downgraded from or to any other versions that are
earlier than 3.0.35, some UI pages do not work properly due to cache. Refresh the browser
to update the browser web page after update or downgrade.
Due to the increase of firmware footprint in some circumstances, a 2-step update is necessary.
Depending on the update method, to upgrade the firmware from version 2.6.7 or earlier to newer:
1. Upgrade to version 2.7.19.
2. After the version 2.7.19 is successfully installed, upgrade again to the required version.
For example, if the reader current firmware version is 1.2.11 or 2.6.7. To upgrade to 3.0.35, first upgrade to 2.7.19,
and then upgrade to 3.0.35.
Depending on the update method, to downgrade the firmware from version 3.0.35 or newer to older:
1. Downgrade to version 3.0.35.

2. After the version 3.0.35 is successfully installed, downgrade again to the required version.
For example, if the reader current firmware version is 3.1.12. To downgrade to 2.6.7, first downgrade to 3.0.35, and
then downgrade to 2.6.7.
Table 14 details the 2-step and 1-step upgrade or downgrade requirements that corresponds to the firmware
installation methods for the FX7500 and FX9600.
Table 14 Firmware Update Support

Reader Update/Downgrade File-Based FTP-Based With USB
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
154
Firmware Upgrade
File-Based Update: The reader is updated with the web interface by using the file-based 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: The reader is updated with 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.
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.
155
Firmware Upgrade
Updating FX Series Reader Software

Verifying Firmware Version
To check the FX7500 and FX9600 reader current firmware version:
Password field.
2. Select Firmware from the selection menu to verify if the current version of reader software is outdated (for
example, 1.1.66).
Figure 123 Firmware Version Window
Firmware Version
Number
156
Firmware Upgrade
Updating Methods
Download the reader update files from zebra.com/support, then use one of three methods listed below to update
the reader software to a later version, such as 1.1.45.0 or higher:
• Using a USB Drive (Recommended)
• File-Based Update on page 159
• FTP-Based Update on page 161.
Using a USB Drive (Recommended)

1. Copy all the reader update files into the root folder of the USB drive.
Figure 124 USB Drive Root Folder
2. Insert the USB drive into the USB host port of the RFID reader (see Figure 125 and Figure 126).
Figure 125 FX7500 USB Host Port Window

USB Host Port
Figure 126 FX9600 USB Host Port Window

USB Host Port USB Client Port
USB Host Port
157
Firmware Upgrade
The reader starts the update process in 5 - 7 seconds, and indicates the 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 127 FX7500 Reader LEDs

Power LED
Figure 128 FX9600 Reader LEDs
Power LED
158
Firmware Upgrade
File-Based Update
1. Copy all reader update files into any folder on a host computer.
Figure 129 Host Computer Folder
2. Log into the reader and navigate to the Firmware Update page.
Figure 130 Firmware Update Window
159
Firmware Upgrade
3. Select File based Upload (see Figure 131).
4. Select Browse and navigate to the folder or files that contains the firmware update files.
Figure 132 Browsing Update Folders
160
Firmware Upgrade
5. Select all the files (see Figure 133).
Figure 133 Browsing Update 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.
161
Firmware Upgrade
2. Select FTP/FTPS Server.

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 if the firmware update is successful:
Password field.
2. Select Firmware from the selection menu to verify if the current reader software displays a newer version
number, which indicates the update is successful.
162
Firmware Upgrade
Figure 136 Firmware Version Window
Version
Number
163
EtherNet/IP
Introduction
This chapter provides the overview of EtherNet/IP for the 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 en.wikipedia.org/wiki/EtherNet/IP for more details).
Zebra FX9600 RFID Reader supports EtherNet/IP for the industrial automation purposes. The EtherNet/IP for the
FX9600 RFID reader is provided as a licensed feature (see FX Series Licensing Mechanism on page 108 for more
information), through which PLCs can connect with the reader and perform RFID operations.
The EtherNet/IP for the 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 installing the application in the reader, users can start or stop it at the User Application Page
window (see Figure 89 on page 126). 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
The Ethernet/IP is enabled through the installable application as mentioned above. Users can start or stop the
application from the web console as per the requirement. See Applications on page 126 for more details.
The EtherNet/IP application consists of two parts:
• EtherNet/IP protocol stack: Communicates with other EtherNet/IP devices

• RFID3 API: Communicated with LLRP for RFID operations.
The basic architecture of EtherNet/IP is explained in Figure 137 on page 165.
164
Firmware Upgrade
Figure 137 EtherNet/IP Application Block Diagram
PLC
Ethernet
EtherNet/IP
Application EtherNet/IP protocol
Stack
RFID 3 API
LLRP/TCP
RFID Radio
Module
Supporting RFID Operations Through EtherNet/IP

The EtherNet/IP in the 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 operations specified in the custom profile.
• 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.
165
Firmware Upgrade
• 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.
166
Cellular Connectivity with
Sierra Modem
Introduction
This chapter describes the configuration of Sierra Modem RV50X to provide the cellular connectivity for Zebra
FX9600 RFID Reader.

Figure 138 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 the Sierra Modem RV50X. The data from
the reader is sent to the cloud via the Sierra Modem which has the 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 (for example, Refinery plant)

• Delivery/Trucking Industries.
167
Steps to be followed for receiving GPS coordinates.

Configure RV50 for sending GPS coordinates:
1. Access the Sierra Modem.
a. Connect the Modem and PC back-to-back with network cable. For more details to configure the RV50X
follow the link
https://www.scribd.com/document/448523280/4117313-AirLink-RV50-Series-Hardware-User-Guide-r5-pd
f
b. Factory reset the modem by pressing the reset button for 7 to 10 seconds until the power LED blinks red.
(Sequence is blinking red, fast blinking green, then while fast blinking red release the reset button)
c. Access http://192.168.13.31:9191/ in the PC with username "user" and Password as 12345 (should be
changed after login)
2. GPS data in Serial Port.
a. Open the modem web page, Go to Locat i onand Enable the Locat i on Ser vi ce(default is disabled) and
Apply. Local/Streaming set t i ngs on GPSLocat i onset t i ng Page .
b. In Local/streaming, Set Location Reports Port as DB9 Serial. Then Apply and Reboot the modem.
c. Connect Serial cable between modem and PC.

d. Open tera term with the COM available, with baudrate 115200.
e. Place the Sierra modem dolphin wing antenna facing open space.
168
f. To get the GPS coordinates through LLRP and API3, 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>
g. Use the following code snippet below is for retrieving GPS data using .net API.
using System;
using Symbol.RFID3;
using System.Threading;
namespace GPSdata
{
class Program
{
static RFIDReader reader = new RFIDReader("X.X.X.X", 5084, 0);
static void Main(string[] args)
{
// Establish connection to the reader

reader.Connect();
Console.WriteLine("Press any key to start inventory... and press again any
key to stop");
Console.ReadLine();
// Register for Read Notification
reader.Events.ReadNotify += Events_ReadNotify;
reader.Events.AttachTagDataWithReadEvent = true;
//This is optional by default all tag fields will be enabled

TagStorageSettings tagStorageSettings =
reader.Config.GetTagStorageSettings();
tagStorageSettings.TagFields = TAG_FIELD.GPS_COORDINATES |
TAG_FIELD.PEAK_RSSI | TAG_FIELD.TAG_SEEN_COUNT | TAG_FIELD.CRC;
reader.Config.SetTagStorageSettings(tagStorageSettings);
reader.Actions.PurgeTags();
reader.Actions.Inventory.Perform();
Thread.Sleep(3000);
reader.Actions.Inventory.Stop();
reader.Disconnect();
169
Console.ReadLine();
System.Environment.Exit(0);
private static void Events_StatusNotify(object sender, Events.StatusEventArgs

e)
{
private static void Events_ReadNotify(object sender, Events.ReadEventArgs e)

{
// fetch tags from the Dll by specifying the number of expected tags
TagData[] myTags = reader.Actions.GetReadTags(100);
if (myTags != null)
{
for (int nIndex = 0; nIndex < myTags.Length; nIndex++)
{
Console.WriteLine("TagID/EPC : " + myTags[nIndex].TagID + " Lat:
" + myTags[nIndex].GPSLocation.Latitude + " Long: " +
myTags[nIndex].GPSLocation.Longitude + " Alt: " + myTags[nIndex].GPSLocation.Altitude
);
}
}
}
Sierra Modem and reader can be connected in two different ways.

Connection Via RNDIS
1. In Location Tab under Local/Streaming link expand Local IP Report. Local Reporting Time Interval (seconds) should
be set to non-zero value(as zero is disable).
2. Set Local Report Type as NMEA GGA+VTG+RMC.
3. Set Starting Destination Port to 10001.
4. Then Apply and Reboot the Modem.
170
5. The reader and Sierra modem are connected via network cable. Reader and PC are connected via RNDIS
cable. Perform inventory with GPS data enabled, Coordinates will be reported.
Connection via network hub:

1. Connect Modem, Reader and PC to a network hub or unmanaged switch.
171
2. In Local Streaming Tab Local Reporting Time Interval (seconds) should be set to non-zero value.as zero is disable under
Local IP Report
3. Set Local Report Type as NMEA GGA+VTG+RMC.
4. Set Starting Destination Port to 10001.
5. Then go to Server1 and set Report Interval time as 1 under Events.
6. Set Location Report Type as NMEA GGA+VTG+RMC under Report Type.
7. Set Report Server 1 IP Address as <reader IP> and Report Server 1 Port Number as 10001.
8. Then Apply and Reboot the Modem.
9. While rebooting the modem disconnect the modem from the network by removing the network cable from the
modem. After the modem comes up connect the network cable to the modem. By doing this the default ip
address in local reporting will be set to 192.168.13.100 which will be the ip of the reader. After then connect the
reader to the network hub , finally connect the PC to the network hub
10. Once the modem comes up perform the inventory with GPS data enabled, Coordinates will be reported.
172
Steps to be followed to send reader data to cloud using Sierra Modem.

SIM card should be added in the Modem for cellular connectivity. Once the Sim card is added the Status and
WAS/Cellular tab looks like below.
173
Easy way of sending the reader data which is in public network via the sierra modem to cloud is achieved by the
configuring the reader in FX Connect http post.
• 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 should be posted should be mentioned in the URL text
box. The port number should be mentioned along with the server ip as below. Eg:
https://10.17.131.52:8081
• There should be a server program running in the server which listens to the data posted by the reader. The
below code must be saved as python file like 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)
174
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)
• We can also send the data through web hook which can be configure as below.
• Start the inventory from FX Connect page by clicking the “Connect” as below.
• In the webhook site the data gets posted as below.
175
176
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 users 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.
177
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 the 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.
178
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.
179
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:
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.
180
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.
Configuring Reader with USB Thumb Drive

A USB thumb drive can be used to transfer the reader configuration from a 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 and 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, you 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>
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 following Step 1 and save it in
the USB flash drive to transfer a reader configuration to each new reader.
181
Reader Configuration via USB Thumb Drive
2. The old reader retrieves (the reader APP LED blinks yellow) the XML control file when USB flash drive is
inserted.
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. The
USB flash drive can be removed after the red APP LED stops blinking.
182
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
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 167).
With the cellular connectivity, the readers send the RFID data and GPS data to the cloud at the instant they are
created. In addition, the GPS data are updated only when vehicle moves. This prevents transmission of redundant
GPS data when vehicle is not moving and the 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 to track the products that are going through each dock door and onto
the van.
3. The driver leaves the warehouse. The GPS data are captured as part of the tag meta data.
4. The GPS data are captured every x seconds/minutes when the reader takes an inventory.
5. When the driver stops at the first bakery to deliver product, the driver opens the door and the reader performs
another inventory (the GPI is triggered). The GPS data are captured.
6. The driver finishes delivery and continues to the next bakery. The inventory is taken and GPS data are
captured.
7. Steps 4 to 6 are repeated for the next deliveries.
Government or Military Use Case

1. A convoy carrying top-secret tagged assets leaves the remote facility.
2. When truck door is opened, the GPI triggers the reader to start capturing data. The GPS data are captured.
3. After y km of travel distance, the reader takes inventory to ensure assets are still with the convoy. The GPS
data are also captured.
Trucking Company Use Case

1. The tractor-trailer is loaded with product at a central warehouse.
2. The reader mounted at the warehouse dock door tracks the products that are loaded in the truck.
183
3. The reader mounted in the truck starts an inventory cycle at a specific time of day (no date can be specified).
4. The truck completes delivery route. The GPS readings are taken at regular time intervals and when the truck
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 works with some existing triggers. For example, a GPI trigger (old trigger) can work with the new
time lapse stop trigger. The matrix of supported triggers is shown in Table 15.
Table 15 Supported Trigger and Combinations Matrix

Stop Trigger
No Stop Duration1 Tag Attempt with GPI4 Time lapse

Trigger Observation Timeout3 Stop Trigger5
defined or with Timeout2
configured
Immediate6 Not
supported
GPI7 * Supported Supported
Start Periodic8 Not

Trigger Supported
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
10. (LLRP) ZebraROSpecStartTrigger.ZebraDistance; (RFID3 API) START_TRIGGER.value.distance
* Trigger combinations that are currently not supported.
184
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”, the reader does inventory 5 seconds per 10
seconds.
Figure 139 Single Trigger Pair: Timelapse Start/Timelapse Stop
Single trigger pair: Timelapse Start/Timelapse Stop (TotalDuration = 0)

Configuration:
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 and indefinitely.
Figure 140 Single Trigger Pair: Timelapse Start/Timelapse Stop (TotalDuration = 0)
185
Single trigger pair: Timelapse Start/Timelapse Stop (Period = 0, PeriodicDuration = 0)

Configuration:
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 141 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:
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 142 Single Trigger Pair: Timelapse Start/Timelapse Stop (Period = 0, TotalDuration = 0, PeriodicDuration
= 0)
186
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 143 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 144 Single Trigger Pair of Distance/Timelapse (TotalDuration = 0)
187
Two trigger pair: GPI Start/GPI Stop; Timelapse Start/No Stop

The GPI trigger has higher priority, and it can preempt Timelapse trigger.
Priority is determined by the order of the trigger configuration. The first trigger gets higher priority.
Configuration:
First trigger pair (high priority)
Start trigger (GPI1: low value)
Stop trigger (GPI1: high value)
Second trigger pair (low priority)
Expected:
After 8:24AM, reader begins inventory due to second trigger.
The high priority GPI trigger can preempt the low priority timelapse trigger.
Figure 145 Two Trigger Pair: GPI Start/GPI Stop; Timelapse Start/No Stop
188
Two trigger pair: Timelapse Start; GPI Start/GPI Stop

The GPI of second trigger has lower priority, and it can’t preempt Timelapse (first).
Configuration:
First trigger pair (high priority)
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 146 Two Trigger Pair: Timelapse Start; GPI Start/GPI Stop
189
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 the readers 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 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.
The result accuracy is very sensitive with the number of stationary tags in FOV, the moving tag is not big factor in
algorithm. Tag stationary moderated timeout could be adjusted according to the number of stationary tags within
range from 5 to 10 seconds. Timeout could be 5 seconds if 10 stationary tags, On the contrary, 500 stationary tags
can set timeout to 10 seconds.
This feature can be enabled and leveraged via LLRP and RFID3 APIs.
This feature works reliably if the read zone does not have tags that are hard to read.
To get the stationary tags (which are present in the reader FOV for a defined time) the configuration required is as
follows.
Let us assume if we have first set of 10 tags which are not moving and are stationary in the reader FOV. And, there
is a second set of 10 tags that enter and exit the reader FOV.
First, we need to enable the feature by
tInfo.TagEventReportInfo.setReportTagMovingEvent(TAG_MOVING_EVENT_REPORT.ENABLE);
We need to set the setTagStationaryModeratedTimeoutMilliseconds parameter to 10 secs
setReportNewTagEvent, setReportTagInvisibleEvent, setReportTagBackToVisibilityEvent to MODERATED

and their respective timeouts to 3000ms
Perform inventory for more than 30 secs and then call reader.Actions.getStationaryTags();. This will only report
the tags which have stayed in the reader FOV for more than 10secs(setTagStationaryModeratedTimeoutMilliseconds) and
will not report the tags which came in reader FOV and left with in 10secs(setTagStationaryModeratedTimeoutMilliseconds).
MOVING_TAG event will be generated for second set of 10 tags.
190
If the tag has stayed for 10secs(setTagStationaryModeratedTimeoutMilliseconds) in reader FOV and then moved
out of Reader FOV within 30secs of inventory, even then the tags are reported as stationary as it stayed in Reader
FOV for 10secs(setTagStationaryModeratedTimeoutMilliseconds)
So depending on the value set in setTagStationaryModeratedTimeoutMilliseconds we need to set the duration of
inventory to get best results.
Recommendation:
1. Few moving tags / few stationary tags

If the number of both stationary tags and moving tags are less (< 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) could be set to 5 secconds.
2. Few moving tags / many stationary tags
If the number of stationary tags is large (> 500) and the number moving tags through the read zone is less (<
10), it is recommended to set the new tag event moderated timeout (LLRP:
tagStationaryModeratedTimeoutMilliseconds) should be set to larger value > 10 secs. So that the reader
will read all the 500 tags within 10 seconds(for the reader to identify it is stationary)
3. Many moving tags / few stationary tags
If the number of stationary tags is less (<10) and the number moving tags through the read zone is large
(>500), it is recommended to set the new tag event moderated timeout (LLRP:
tagStationaryModeratedTimeoutMilliseconds) could be set to value 6 secconds.
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.
191
For this feature, the following moderated timeout settings affect the result.
It is recommended to set the tag invisible moderated timeout to 3 seconds.
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"/>
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"/>
192
<customParameterDefinition name="MotoTagEventEntry">
<field type="u8" name="EventType"
enumeration="MotoTagEventTypeEnum"/>
<field type="u64" name="Microseconds" format="Datetime"/>
<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.
193
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

{
194
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;
195
REST RCI Support
Introduction
The RAIN Reader Communication Interface (RCI) is a simple interface to communicate with the UHF RFID
readers. It eliminates the need to use the traditional APIs where in application development is required.
REST RCI Support

The FX Series Readers supports sending and receiving RCI based data using the REST interface to the reader by
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/
196
REST RCI Support
Communication
The FX Series Readers support RCI payload to the REST interface that is accessible on the reader using the URL
http(s)://IPAddress/restrci.
Figure 147 shows an example of RCI command (GetInfo) and its response using the Postman tool. JSON form
examples are available upon request.
Figure 147 RCI Command
197
Troubleshooting
Troubleshooting
Table 16 provides FX Series troubleshooting information.
Contact the distributor or call the local support if problems persists. See page 16 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 37.
Reader is not reading tags. The tag is out of its read Move the tag into read range.
range. See Read Tags on page 77.
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 37 to view the IP
address, or use the host name to connect to
the reader.
198
Troubleshooting
Table 16 Troubleshooting (Continued)

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
Administrator Console, so option to log in even when the user closes
other applications cannot the browser without logging out. Force
connect to the reader. Login 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 16.
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 16.
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.
199
Troubleshooting

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 42.
- 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 16.
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 42.
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.
200
Troubleshooting

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 16.
The requested page was not The system experienced an Contact Zebra support.
found. internal web server error. See Service Information on page 16
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 16.
201
Troubleshooting

Failed to open port. Error during receive of Contact Zebra support.
Failed to connect. command. See Service Information on page 16.
Failed to transmit.
Failed to receive.
Error during Receive of
Command.
Invalid Device Address. The device address Contact Zebra support.
information (parent) is See Service Information on page 16.
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 16.
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.
202
Troubleshooting

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 Zebra Customer Care for
assistance.
Table 17 Troubleshooting for Licensing Errors

No license is displayed although The reader is not Configure the reader date and time, then
the license activation is synhronized to the current refresh the Manage License page.
completed. date and time. See Time Tampering on page 107.
Message Please Input Act i v at i on IDis not Enter the Activation ID provided when the
Activation ID. provided. license is procured.
See Activation ID on page 112.
Message Please Input Server Local License Server is Enter a valid LLS link with the format
URL. selected as the server to http://<Server_ip or
acquire licenses, but the host_name>:port_number/request
server URL is not provided. See Setting Up and Managing the Local
License Server on page 114.
203
Troubleshooting

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 The license is activated but the EtherNet/IP
Install & Run Disabled. without selecting the Install application is not installed.
and Run application option Manually install the EtherNet/IP via the
application web page if you have a debian
package.
Return the license and install the license
again. Select the Install and Run
application option before activating the
license.
Message Error:Invalid A different product license Ensure the Activation ID is the ID provided
Activation ID, Please provide Activation ID is provided when the license is procured.
valid activation ID for License when users return the
Return. license(s).
Message Error:Broken trusted The license trusted storage Click the Repair button to repair the trusted
storage, in license detected. is corrupted. storage. Acquire the license again after the
Press Repair button to fix the trusted storage is fixed.
issue and then acquire licenses
again on the License Manager
window. Also, the window shows
the Repair option in the License
operation field. See Figure 148 on
page 205.
Message Error:Broken trusted The Web browser cache is Right-click on the web UI page, then select
storage, in license detected. not cleared. Reload Frame in the menu.
Press Repair button to fix the See Figure 150 on page 205.
issue and then acquire licenses
again on the License Manager
window. See Figure 149 on page
205.
Message Unable to upload The Web browser cache is Clear the Chrome/FireFox browser cache
license file.SyntaxError: Failed not cleared which may after upgrading the current firmware version
to execute 'open' on cause issues to the web UI 3.0.35/3.1.12 to 3.6.28 or newer.
'XMLHttpRequest':Invalid URL. pages. Or, right-click on the web UI page, then
See Figure 151 on page 206. select Reload Frame in the menu.
Message Error:expected The Web browser cache is Clear the Chrome/FireFox browser cache
element not encountered. not cleared which may after upgrading the current firmware version
See Figure 152 on page 206. cause issues to the web UI 3.0.35/3.1.12 to 3.6.28 or newer.
pages. Or, right-click on the web UI page, then
select Reload Frame in the menu.
204
Troubleshooting
Figure 148 Broken Trusted Storage Message and Repair
Figure 149 Broken Trusted Storage Message and Browser Cache
Figure 150 Reload Frame
205
Troubleshooting
Figure 151 Invalid URL Error
Figure 152 Expected Element Not Encountered Error
206

The reader’s licensing error logs are listed in the System Log window (see Figure 153).
Figure 153 System Log Window
Listed
Logs
System
Log
The licensing error logs in the System Log window display error codes. Refer to the code number in Table 18 for
the error descriptions. The following shows an example of the error log:
July 13 13:18:43 FX7500F18F81 user.info rmserver.elf: I-RESPONSE STATUS RESPONSE STATUS:
CODE = 1, CAT = 1, DETAIL = xxxx-1639-583c-40e2-9cd4-abc3-1a9d-xxxx
The code number in this example is 1. Code 1 in Table 18 indicates that one of the input parameters is bad. For
this example, the Activation ID is incorrect.
Table 18 System Log Error Code Descriptions
Code Error Code Message
0 Success.
1 One of the input parameters is bad.
207
Troubleshooting
Table 18 System Log Error Code Descriptions (Continued)

2 Provided buffer is not big enough to hold the data.
3 Callout failed but did not set error information.
4 Data corruption found.
5 Provided data exceeds maximum size allowed.
6 The size of provided data is incorrect.
7 Information for the date is invalid.
8 (No longer used.)
9 Requested feature has expired.
10 Requested feature's host ID does not match system host ID.
11 Requested feature is not found.
12 Start date for the requested feature is in the future.
13 Feature is issued by a different vendor.
14 Feature with the requested version is not found.
15 Type of the host ID is currently unsupported.
16 Version of identity is not supported.
17 Item already exists in the collection.
18 Provided item is not found in the collection.
19 Item's value has a different type than expected.
20 Provided index is out of bounds.
21 Key already exists in the collection.
22 Provided key is not found in the collection.
23 License not found in acquired list, possibly already returned.
24 License source type is invalid for operation.
25 (No longer used.)
26 The allowed time to process response has expired.
27 Response does not match system host ID.
28 Server is not able to process request correctly.
29 Response is out of order with previous responses.
30 Signature did not pass validation.
31 Inconsistent signature type used.
32 This trial is already loaded.
208
Troubleshooting

33 Trial duration has expired.
34 Trial ID is invalid.
35 Storage anchor break found.
36 Storage binding break found.
37 Trusted storage is corrupted.
38 Trusted storage contains inconsistent data.
39 This version of trusted storage is not supported.
40 Storage implementation class provided is not complete.
41 Vendor keys have expired.
42 Vendor keys are invalid.
43 Vendor keys do not support this platform.
44 Identity data has changed; unable to decrypt trusted storage or anchor data.
45 Clock wind back is detected.
46 Clock wind back is disabled; unable to test if wind back has happened.
47 Data version is not supported.
48 Insufficient count for the requested feature.
49 Object cannot be modified because it is being used by another object.
50 Version string is invalid.
51 A signature signed with a revision of key which is not present in identity data.
52 Requested feature's server host ID does not match system host ID.
53 No server data found in TS. The Client probably never receives a capability response.
54 Regular update from the server is not needed as renew interval is set to 0 by the server.
55 Feature is node locked and cannot be served by the server.
56 Feature is a duplicate on the server and cannot be served.
57 Input type mismatch.
58 Failed to get a response from any of the servers.
59 New servers sent by the configuration server are not responding.
60 Required data is missing from capability response.
61 Capability response is not available - sync from the back office is not completed.
62 Identity is of different type than expected.
63 System machine type does not match expected machine type.
209
Troubleshooting

64 Requested unique identifier is not found.
65 Callout error is set using an inappropriate error code.
66 Callout error is set using an inappropriate unit identifier.
67 Tolerance specifier version is not supported.
68 A non-client tolerance specifier is specified by the client.
69 A badly formed tolerance specifier is encountered.
70 A tolerance specifier is rejected as not valid for this client.
71 An unsupported tolerance specifier type is specified.
72 A bad tolerance specifier ratio is specified.
73 Information message can hold either existing or usage-based features, but not both.
74 Trusted storage host ID does not match system host ID.
75 Response UUID does not match system UUID.
76 Trusted storage does not exist.
77 The UUID in a message can originate from the back office or can be explicitly set, but not both.
78 Character set is invalid.
79 Short code license has expired.
80 Requested publisher data is not set.
81 Checksum segment length mismatch.
82 Short code scheme is not supported.
83 CRC validation of short code failed.
84 Request host ID does not match host ID recorded by server.
85 Checksum validation failed.
86 The host ID in an info message can originate from trusted storage or can be explicitly set, but not
both.
87 Feature is metered and cannot be used in the buffer license source.
88 Unsupported certificate keyword.
89 Unknown certificate keyword.
90 Vendor dictionary can be requested as a whole, or by key; but not both.
91 Flag to include vendor dictionary is not set.
92 The specified capability request option conflicts with an option previously set.
93 Feature count exceeds the maximum supported value.
94 Features with an overdraft count are not supported on the client.
210
Troubleshooting

95 Features with an overdraft count are not supported on the server.
96 Features with a metered license model are not supported on the server.
97 The same feature name cannot be used in both metered and concurrent license model.
98 Acquired feature uses a metered non-reusable license model and cannot be returned.
99 Metered features with the same name must have identical metered attributes.
100 Undo interval for the acquired feature has expired.
101 Metered functionality is not enabled.
102 A short-code license matching the specified license template ID cannot be found.
103 Capability response type is invalid for operation.
104 License source type and response type is incompatible.
105 License source contains a different server host ID from the response server host ID.
106 License source contains a different server instance than the capability request or response server
instance.
107 Capability response contains a different server instance than the capability request.
108 Trusted storage already contains data from one of the capability response server host IDs stored in a
different instance location.
109 The specified information message option conflicts with an option previously set.
110 Preview response cannot be processed into the license source.
111 Feature from a preview response cannot be acquired.
112 Server received a request of unknown type.
113 Required data is missing from capability request.
114 Vendor name in capability request does not match server vendor name.
115 No server records are found for the device.
116 Server signing key not found; can be caused by license server using client identity instead of
client-server identity, or by corrupted identity data.
117 Required data is missing from information message.
118 Request type is invalid for operation.
119 Vendor name in information message does not match server vendor name.
120 Server is not a designated backup server.
121 Server maintenance interval is not set.
122 Server maintenance interval is not started.
123 Server maintenance interval has passed.
211
Troubleshooting

124 Backup server is performing active fail-over support.
125 Information message is out of order with previous messages.
126 No detailed usage info.
127 Host ID that enabled server is not connected.
128 No reservations are found for the device.
129 Device is not served any features and does not have any reservations.
130 Required data is missing from the sync related message.
131 Vendor name in sync related message does not match server vendor name.
132 Identity name in sync related message does not match server identity name.
133 Target id in the sync related message is invalid.
134 Source id in the sync related message is invalid.
135 Time units mismatch in the sync related messages.
136 Desired feature is not available and cannot be served by the server.
137 Device is dropped from the server.
138 Device licenses have expired.
139 Device has returned all its licenses.
140 Sync time mismatch in the sync related messages.
141 Host ID in information message is invalid.
142 Host ID in capability request message is invalid.
143 Virtual clients are not supported.
144 Unexpected information message type received.
145 Usage based information message support is not enabled.
146 Collection of the sync data offline is not supported.
147 Offline sync to FNO cannot be performed due to other sync in progress.
148 The message UUID does not match the device record UUID.
149 Unable to parse malformed or incorrect XML version.
150 Error in converting Julian date.
151 An unsupported request operation is specified.
152 One-time activations are not supported.
153 Trusted storage cannot be reset with unsynchronized distribution data present.
154 Served buffer features cannot be returned early.
212
Troubleshooting

155 Client cannot switch from use of served buffer to trusted storage and vice versa.
156 Overage detected on server. Update from back office could not be processed because the
outstanding license count is greater than the updated count.
157 Internal license server error.
158 Request has invalid content.
159 Invalid desired-feature count specified.
160 Server is currently running in environment tolerance interval.
161 Server environment tolerance interval has expired.
162 Server is busy (such as updating license rights from the back office or processing reservations).
163 Client is not registered on the license server.
213
The following tables summarize the RFID reader intended operating environment and technical hardware
specifications.
Table 19 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
214
Table 19 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
215
Table 19 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: 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 154 Ethernet Connections
216
USB Client Connector

The USB Client port is supplied on a USB Type B connector.
Figure 155 USB Client Connector
Pin 2 Pin 1
Pin 3 Pin 4
Table 20 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 156 USB Host Connector (J22)
Pin 4
Pin 1
Table 21 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
217
FX7500 GPIO Port Connections

The FX7500 GPIO connector pinouts include the following:
Figure 157 FX7500 RFID Reader GPIO Connection
Pin 1 Pin 8
Table 22 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
5 GND - Ground connection
6 GP input #1 I Signal for GP input #1
FX9600 GPIO Connections

The FX9600 GPIO connector pinouts include the following:
Figure 158 FX9600 RFID Reader GPIO Connection
Pin 1 Pin 12
Table 23 FX9600 GPIO Pinouts

1 +24V DC Power O Supplies +24VDC At up to 1 Amp
218
Table 23 FX9600 GPIO Pinouts (Continued)

The Figure 159 provides an example of a typical GPIO setup with the power derived from an external power
supply.
Figure 159 FX9600 GPIO Setup Example with Power Derived from External Power Supply
219
The Figure 160 provides an example of a typical GPIO setup with the power derived from GPIO 24V Pin.
Figure 160 FX9600 GPIO Setup Example with Power Derived from GPIO 24V Pin
220
Introduction
This chapter describes three methods to set the static IP address on the FX7500 and FX9600 RFID Readers.
Reader IP Address or Host Name is Known

To set the Static IP on the Web Console when you know the reader IP address or host name:
1. Browse the device using the host name, for example: FX7500CD3B1E.
2. Log in to the device.
Figure 161 Reader Administration Console Login Window
3. Select Communication.
4. Set Obtain IP Address via DHCP to Off and enter all required information.
221
Figure 162 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 completes
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.
222
Reader IP is Not Known (DHCP Network Not Available)

To set the Static IP on the Web Console when you do not have the reader IP address:
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 163 Obtain IP Address
4. When possible, ping the host name of the device.
Figure 164 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.
223
Figure 165 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.
224
Introduction
This section lists the supported air link configurations. The air link configuration is available through the LLRP and
RFID3 API interfaces.
Radio Modes
The supported modes are exposed as a list of individual UHFC1G2RfModeTableEntry parameters in the regulatory
capabilities as shown in Table 24 and Table 25. The Mode Index column refers to the index used to walk the
C1G2UHFRFModeTable. Refer to the EPCglobal Low Level Reader Protocol (LLRP) Standard.
Table 24 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

*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.
225
Table 24 Radio Modes for FCC Readers (Continued)

M Value
EPC HAG
M2=2, Spectral
FM0=1, Mask
M4=4, Indicator**
ance
M8=8

*23 64/3 variable variable PR_ASK variable 6250 25000 variable variable false
36 [ ] 64/3 120000 4 PR_ASK 1500 10400 10400 0 Dense false
226
Table 24 Radio Modes for FCC Readers (Continued)

M Value
EPC HAG
M2=2, Spectral
FM0=1, Mask
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
Table 25 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

227
Table 25 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

*21 64/3 variable variable PR_ASK variable 12500 25000 variable variable false
228
Table 26 Radio Modes for Japan Readers
M Value
EPC HAG
M2=2, Spectral
FM0=1, Mask
M4=4, Indicator**
ance
M8=8

229
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.
230
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 the 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 is 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 Dense Reader Mode (DRM) 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.
231
Index
Numerics C
10/100BaseT Ethernet . . . . . . . . . . . . . 18, 26, 28, 29, 30 cable pinouts
123RFID Desktop ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
USB client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
USB host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
A chapter descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 14
administrator console . . . . . . . . . . . . . . . . . . . . . . . . . 46 commit region change . . . . . . . . . . . . . . . . . . . . . . . . . 22
applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 committing changes . . . . . . . . . . . . . . . . . . . . . . . . . 131
committing changes . . . . . . . . . . . . . . . . . . . . . . 131 communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 27, 30
communication settings . . . . . . . . . . . . . . . . . . . . 78 ethernet, wired . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
configure network services . . . . . . . . . . . . . . . . . . 84 communication settings . . . . . . . . . . . . . . . . . . . . . . . . 78
configure network settings . . . . . . . . . . . . 78, 79, 80 configure
configuring system log . . . . . . . . . . . . . . . . . . . . 137 antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
discarding changes . . . . . . . . . . . . . . . . . . . . . . . 131 LLRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
firmware version . . . . . . . . . . . . . . . . . . . . . 130, 131 read points . . . . . . . . . . . . . . . . . . . . . . . . . . . 63, 64
GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
IPV6 sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 static IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
managing login . . . . . . . . . . . . . . . . . . . . . . . . . . 125 static IP via web console . . . . . . . . . . . . . . 221, 223
reader diagnostics . . . . . . . . . . . . . . . . . . . . . . . . 138 wireless . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
reader profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 configuring network
scan control . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 77 bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
set password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
setting date and time . . . . . . . . . . . . . . . . . . . . . . 122 services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
shutting down . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 wi-fi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 connecting
system log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 to reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
air link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 via bluetooth . . . . . . . . . . . . . . . . . . . . . . . . 148, 149
antennas via host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 via IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 via wi-fi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
ports . . . . . . . . . . . . . . . . . . . . . . . 18, 26, 27, 29, 30 connection
applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
port diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26, 29
bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148, 149 wired ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
connecting . . . . . . . . . . . . . . . . . . . . . . . . . . 148, 149 conventions
232
Index
notational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 G
copying files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151, 230
country list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18, 26, 29
GPIO connections . . . . . . . . . . . . . . . . . . . . . . . .218
pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
D port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27, 30
data protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 GPIO control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 H
discarding changes . . . . . . . . . . . . . . . . . . . . . . . . . . 131
host communication
ethernet, wired . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
E host name connect . . . . . . . . . . . . . . . . . . . . . . . . . . .19
error log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
ethernet I
pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
POE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 information, service . . . . . . . . . . . . . . . . . . . . . . . . . . .16
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28, 30 initiating reads . . . . . . . . . . . . . . . . . . . . . . . . . . . .24, 77
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 38 installation
wired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
event statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 communication connection . . . . . . . . . . . . . . . . . .37
mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
F IP ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
files
copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151, 230 L
firmware
version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130, 131 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28, 31
firmware update . . . . . . . . . . . . . . . . . . . . . 130, 131, 156 LLRP
prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
first time login . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19, 51 radio modes . . . . . . . . . . . . . . . . . . . . . . . . .225, 227
FTP log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
copying files . . . . . . . . . . . . . . . . . . . . . . . . 151, 230 configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
FTPS login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
copying files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
FX Connect managing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
http proxy server . . . . . . . . . . . . . . . . . . . . . . . . . 101
license type M
perpetual license . . . . . . . . . . . . . . . . . . . . . 107
trial license . . . . . . . . . . . . . . . . . . . . . . . . . . 107 mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33, 35
licensing concrete wall mounting . . . . . . . . . . . . . . . . . . . . . 35
acquisition modes . . . . . . . . . . . . . . . . . . . . . 108 drywall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . 35
activation id . . . . . . . . . . . . . . . . . . 106, 109, 112 wood or metal wall mounting . . . . . . . . . . . . . . . . .35
device id . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 mounting plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
download from bin file . . . . . . . . . . . . . . . . . . 111 multiple reader deployments . . . . . . . . . . . . . . . . . . . .47
local license server . . . . . . . . . . . . . . . . . . . . 111
offline . . . . . . . . . . . . . . . . . . . . . . . . . . 111, 112 N
production server . . . . . . . . . . . . . . . . . . . . . 108
UATserver . . . . . . . . . . . . . . . . . . . . . . . . . . 110 NXP
licensing evaluation statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58, 60
enabling license . . . . . . . . . . . . . . . . . . . . . . 107
licensing model . . . . . . . . . . . . . . . . . . . . . . . . . . 106
running inventory . . . . . . . . . . . . . . . . . . . . . . . . . 98
O
USB HID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 obtain reader IP address . . . . . . . . . . . . . . . . . . . . . . .49
using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
233
Index
P wired ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
wired ethernet AC outlet . . . . . . . . . . . . . . . . . . . .37
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . 19, 156, 162 wired ethernet, power-over . . . . . . . . . . . . . . . . . .38
password . . . . . . . . . . . . . . . . . . . . . . . . 19, 51, 156, 162 shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
changing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 SNMP
pinouts configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 software update . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
USB client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 static IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . 221
USB host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 via web console . . . . . . . . . . . . . . . . . . . . . .221, 223
POE . . . . . . . . . . . . . . . . . . . . 18, 26, 28, 29, 30, 38, 216 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26, 29 statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 27, 30 event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 GEN2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18, 26, 29 NXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58, 60
POE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28, 30 system log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
system time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
R
read points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63, 64 T
reader tags
configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43, 77
connecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 technical specifications . . . . . . . . . . . . . . . . . . . . . . .214
GEN2 statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 tool for RFID readers - 123RFID Desktop . . . . . . . . . .44
statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
NXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58, 60
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
reading tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 U
initiating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 77 unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18, 29 updating firmware . . . . . . . . . . . . . . . . . . .130, 131, 156
reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 updating software . . . . . . . . . . . . . . . . . . . . . . . . . . .156
region configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 USB . . . . . . . . . . . . . . . . . . . . . . . . . 18, 26, 29, 145, 157
region control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 client pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
region setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 host pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
region settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 18, 26, 27, 29, 30 user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
RFID user name . . . . . . . . . . . . . . . . . . . . . . . . . .19, 156, 162
FX reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25, 29 user password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
RJ45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28, 30
V
S
version control . . . . . . . . . . . . . . . . . . . . . . . . . .130, 131
SCP vice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
copying files . . . . . . . . . . . . . . . . . . . . . . . . 151, 230
service information . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
set region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22, 52 W
setting date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
wi-fi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
setting time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
connecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
setup
wired ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
234
Index
wireless
configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Z
zero-configuration networking . . . . . . . . . . . . . . . . . . . 50
235
www.zebra.com

Fxseries Ig en

Uploaded by

Copyright:

Available Formats

Fxseries Ig en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fxseries Ig en

Uploaded by

Copyright:

Available Formats

FX SERIES

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

For Australia Only

Change Date Description

-01 Rev A 1/2014 Initial release

-10 Rev A 8/2019 Added:

Updated the Troubleshooting section.

-15EN Rev A 3/2022 Updated:

About This Guide

Installation and Communication

Unpacking the Reader .................................................................................................................... 32

Administrator Console Option Selections ........................................................................................... 53

FX Series Licensing Model ..................................................................................................... 106

Configure and Connect via Wi-Fi and Bluetooth

Cellular Connectivity with Sierra Modem

SOTI MOBI Client

Reader Configuration via USB Thumb Drive

GPS and Triggers for Trucking and Delivery

Moving and Stationary Tags

REST RCI Support

Licensing Error Logs

RF Air Link Configuration

Copying Files To and From the Reader

FTPS ............................................................................................................................................. 230

Related Documents and Software

• Serial number of the unit

Quick Start Demonstration

Figure 1 FX7500 RFID Fixed Reader Rear Panel Connections

Port 1 Port 2 Port 3 Port 4 GPIO 24 VDC

Figure 2 FX9600 RFID Fixed Reader Rear Panel Connections

10/100BaseT Ethernet USB USB

Step 2, Connecting to the Reader

Step 3, First Time or Start-Up Login

Figure 3 User Login Window

Enter your password that should satisfy the following criteria:

Step 4, Set Region

Figure 4 Selecting the Region

Figure 5 Region Configuration, Operation Successful Window

Step 5, Read Tags

Figure 6 Read Tags Window

On the Reader Operation window (see Figure 6):

• EPC Id: Unique tag EPC ID.

Table 1 FX Series RFID Reader Features

Table 1 FX Series RFID Reader Features (Continued)

Port 1 Port 2 Port 3 Port 4 GPIO 24 VDC

Figure 8 FX7500 RFID Reader

FX7500 Rear Panel

Table 2 Rear Panel Descriptions

Table 2 Rear Panel Descriptions

Figure 9 FX7500 RFID Readers LEDs

PWR A C TV STAT APP

Table 3 FX7500 LED Indications

Figure 11 FX9600 RFID Reader

FX9600 Rear Panel

Table 4 Rear Panel Descriptions

Figure 12 FX9600 RFID Readers LEDs

Table 5 FX9600 LED Indications

• Unpacking the Reader on page 32

CAUTION:FX Series RFID readers must be professionally installed.