CSL-Intelligent-Fixed-Reader-User-Manual
CSL-Intelligent-Fixed-Reader-User-Manual
1 Release Notes
Cloud server
2 Content
4 INTRODUCTION ....................................................................................... 12
4.1 CSL INTELLIGENT FIXED READER FAMILY ....................................................................... 12
4.2 CS463 4 PORT INTELLIGENT FIXED READER ................................................................... 13
4.3 CS203X INTELLIGENT INTEGRATED READER WITH 1 EXTERNAL PORT .................................... 15
4.4 PRODUCT PACKAGE ................................................................................................. 17
4.4.1 Basic Package Content ..................................................................................................... 17
4.5 PRODUCT SPECIFICATIONS ......................................................................................... 18
4.6 PRODUCT ACCESSORIES ............................................................................................ 20
4.7 HOW TO CONNECT TO AND CONTROL CSL INTELLIGENT FIXED READER.................................. 21
4.8 SOFTWARE DEVELOPMENT KITS .................................................................................. 22
5.9 FILE TRANSFER TO AND FROM CS463 USING USB MEMORY DEVICE .................................... 59
5.10 CONNECTING TO HOST PC USING USB CLIENT PORT ........................................................ 67
5.11 CONNECT FROM USB HOST PORT USING USB COM DRIVER TO A USB CLIENT ....................... 75
5.12 CONNECTING FROM CONTROL SERIAL PORT TO RS232 CLIENT DEVICES ................................ 82
5.13 GPIO PORT AND ACCESSORIES FOR CONNECTION ........................................................... 87
5.14 CONNECTING TO BLUETOOTH DEVICES: E.G. SPEAKER ....................................................... 92
5.15 WIRESHARK LOGGING ON PC SERVER SIDE .................................................................. 108
9 READ TAG USING BROWSER INTERFACE AND EVENT ENGINE ................. 250
9.1 READ TAG USING DEFAULT PROFILE AND DEFAULT EVENT................................................. 250
9.2 READ TAG USING CUSTOM PROFILE AND CUSTOM EVENT ................................................ 254
9.3 EXAMPLE 1: EXAMPLE EVENT SEND TO CSL DEMO CLOUD SERVER .................................... 265
9.4 EXAMPLE 2: TRAFFIC CONTROL – MANAGEMENT OF TRAFFIC AT BUILDING ENTRANCE ............ 275
9.5 EXAMPLE 3: MULTIPLE ANTENNA PORTS WITH DIFFERENT EVENTS FOR EACH PORT ............... 283
9.6 EXAMPLE 4: EXAMPLE EVENT USING DATABASE TAG GROUP AND DATABASE DISPLAY ............. 286
9.7 EXAMPLE 5: READ MAGNUS S3 TAG TEMPERATURE ...................................................... 295
12 READ TAG USING CS461 HIGH LEVEL API (CSL HTTP/XML API) ................ 315
13 READ TAG USING CS461 LOW LEVEL API (MACH1 API) ........................... 316
14 READ TAG USING CS108 BLUETOOTH API ............................................... 321
15 READ TAG USING CUSTOM EMBEDDED RFID.......................................... 329
16 DEMO SOURCE CODES FOR DOWNLOAD ............................................... 331
17 HISTORICAL FIRMWARE VERSIONS ........................................................ 332
APPENDIX A: FEDERAL COMMUNICATIONS COMMISSION COMPLIANCE ..... 335
APPENDIX B: READER MODES (LINK PROFILES) ............................................ 336
APPENDIX C: SESSIONS ................................................................................ 337
APPENDIX D: TAG POPULATION AND Q ........................................................ 338
APPENDIX E: QUERY ALGORITHM ................................................................ 339
APPENDIX F: TARGET .................................................................................... 340
APPENDIX G: RECEIVER AMPLIFIER GAIN VALUES ......................................... 341
APPENDIX H: TAGFOCUS .............................................................................. 342
APPENDIX I: FASTID ...................................................................................... 343
APPENDIX J: SECURITY ................................................................................. 344
APPENDIX K: MODELS & REGULATORY REGION ............................................ 346
APPENDIX L: TECHNICAL SUPPORT ............................................................... 347
3 Regulatory Regions
3.1 Introduction
The CSL Intelligent Fixed Reader family is offered as various regulatory region specific
models, using the format of CSXYZ-N where N is of various values, each covering one
regulatory region. Each regulatory region may apply to one or more countries.
For example, CS463-2 covers the regulatory region of FCC, which includes USA, Canada,
Mexico and other Latin America Countries that use the FCC frequency range.
The following is a model table with N as index, for CSXYZ-N, and the corresponding
frequency band and regulatory regions:
N=1: 865-868 MHz for Europe ETSI, Russia, Mid-East countries, Hong Kong
865-867 MHz for India
N=2: 902-928 MHz, FCC, for USA, Canada and Mexico. Hopping frequencies locked
N=2 AS: 920-926 MHz, Australia. Hopping frequencies locked
N=2 NZ: 921.5-928 MHz, New Zealand. Hopping frequencies locked
N=2 OFCA: 920-925 MHz, Hong Kong. Hopping frequencies locked
N=2 RW: 920-928 MHz, Rest of the World, e.g. Philippines, Brazil, Peru, Uruguay, and
any other countries that use sub or partial sections of the FCC frequency range
N=4: 922-928 MHz, Taiwan
N=6: 917-920.8 MHz, South Korea
N=7: 920-925 MHz, China
N=8: 916.7-920.9 MHz, Japan
N=9: 915-921 MHz, Europe Upper Band
Note that you MUST follow each country’s emission regulation and use the appropriate
regulatory region model. For example, in USA you can only use N = “2”. In Hong
Kong you can only use N = “2 OFCA” or N= “1”. In Australia you can only use N = “2
AS”. etc.
Some regulatory regions require the User Manual to contain some declaration statement. The
following sections are those statements.
1. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions:
(2) This device must accept any interference received, including interference that may cause
undesired operation.
2. Changes or modifications not expressly approved by the party responsible for compliance could
NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device,
pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a residential installation.
This equipment generates uses and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications. However,
there is no guarantee that interference will not occur in a particular installation. If this equipment does
cause harmful interference to radio or television reception, which can be determined by turning the
equipment off and on, the user is encouraged to try to correct the interference by one or more of the
following measures:
-Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
IC STATEMENT
This device complies with industry Canada license-exempt RSS standard(s). Operation is subject to the
(2) This device must accept any interference received, including interference that may cause undesired
This device complies with RSS-247 of industry Canada. Operation is subject to the condition that this
This Class B digital apparatus complies with Canadian ICES-003(Cet appareil numérique de classe B
This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment. This
equipment should be installed and operated with minimum distance of 5mm between the radiator and
your body. This transmitter must not be co-located or operating in conjunction with any other antenna or
transmitter.
3.3 European CE
Hong Kong Government requires the frequency of operation to be limited to within one of the
following 2 frequency bands
1. 920 - 925 MHz, hopping frequency channels, follow USA FCC Part 15 regulation
2. 865 – 868 MHz, fixed frequency channels, follow the European CE RFID regulation in
this band
3.5 Australia AS
Australia Government requires the frequency of operation to be limited to within the frequency
band allocated: 920-926 MHz.
New Zealand Government requires the frequency of operation to be limited to within the
frequency band allocated: 921.5-928 MHz.
4 Introduction
The CSL Intelligent Fixed Reader Family consists of many members, some with Wi Fi and
Bluetooth connectivity, and some without. Some are IP68 and MIL-STD-810F ruggedized,
some are not. The following is a product matrix differentiating them:
1 internal
(embedded)
integrated
antenna,
1 external
antenna port
The CS463 RFID 4-port fixed reader is an intelligent reader designed to work standalone in an
autonomous manner. An intelligent Event Engine is embedded with configurable complex
logic sequence, triggers and resultant actions that are automatically activated on power up.
The settings can be saved and further deployed to as many readers, as many sites as you want,
thus providing easy scalability for the system integrators.
CS463 has the following connectivity: Ethernet, Wi Fi (2.4 GHz b/g/n), Bluetooth 4.0, RS232,
and USB.
The photo below shows a typical connection during operation of CS463 4-port fixed reader
Note: Use only the Power Adaptor Unit included in the package.
External Port
The CS203X RFID Integrated fixed reader is an intelligent reader designed to work standalone
in an autonomous manner. An intelligent Event Engine is embedded with configurable
complex logic sequence, triggers and resultant actions that are automatically activated on
power up. The settings can be saved and further deployed to as many readers, as many sites
as you want, thus providing easy scalability for the system integrators. CS203X integrated
reader has 1 embedded antenna, plus 1 RF port that connects to an external antenna.
The photo below shows a typical connection during operation of CS203X Integrated fixed
reader
Features:
ISO 18000-6C and EPCglobal Class 1 Gen 2 UHF RFID protocol compliant including
dense reader mode
Ultra-long read range – peak at more than 20 meters for Monza R6 Dogbone tag with
CS771S antenna
Sophisticated data handling for efficient management of large streams of tag data.
Highly configurable buffering and tag filtering modes to eliminate the redundant tag data
so as to reduce LAN traffic and server loading
Robust performance in dense-reader environments
Excellent in transmit and receive mode – generates a different combination of unique
reader-to-tag command rate, tag-to-reader backscatter rate, modulation format, and
backscatter type
Configurable parameters offer maximum throughput and optimal performance
Supports all Gen 2 commands, including inventory, read, write, lock and kill
Specifications:
Physical Characteristics: Length: 272 cm; Width: 152 cm; Height: 24 cm;
Weight: 720 grams
*RS232 Debug Serial Port is the standard Linux boot up port, it displays all the Linux
messages, and you can access Linux OS and file system on this port using standard terminal
programs such as HyperTerminal, Putty, etc.
**RS232 Control Serial Port is the serial port that you can use to connect to other devices,
sensors and systems that have RS232 connectivity. This port is meant to be used by software
programs embedded into CS463.
CSL Intelligent Fixed Reader comes with a HD-15 to wiretap terminal adapter accessory.
This enables you to connect wires to the HD-15 GPIO socket conveniently.
Fixed Reader
One can connect to CSL Intelligent Fixed reader via Ethernet, RS232, Wi Fi, USB and GPIO
interface, depending on which particular model.
One can control CSL Intelligent Fixed Reader in the following 7 ways:
1) Use the browser interface and the built-in event engine to configure CS463 to run
autonomously based on certain logic sequence.
2) Use LLRP V1.1 API to control the reader.
3) Use CSL Unified API to control the reader
4) Use CS461 Low Level API (MACH 1 API) to control the reader
5) Use CS461 High Level API (HTTP/XML API) to control the reader
6) Use CS108 Bluetooth API to control the reader
7) Write embedded program in the Linux OS inside directly to control the reader.
To switch among 1) to 7), just go to the browser interface, System/Access Mode page, and then
choose the Access Mode, as shown below:
Software development kits are available for the following on CSL website:
1) LLRP API
2) CSL Unified API
3) CS461 Low Level API (Mach1 API)
4) CS461 High Level API (HTTP/XML API)
5) CS108 Bluetooth API
6) Custom Embedded RFID: sample codes in /opt
5 Reader Basics
The CS463 RFID Reader is an EPCglobal Class 1 Gen 2 4 Port reader product.
Below is the top view of the CS463 4-port reader. There are LEDs to indicate the operating
status
1. Power
2. Activity (programmable LED)
3. Active antenna port currently selected (Port 1, 2, 3,4)
Below is the front side, left side and back side views of the CS463 reader.
Serial RS232 GPIO Port BT Antenna port Four RFID Antenna Ports
Debug Port 15 pin Port 1, 2, 3,4
Wi Fi Antenna port
The CS203X RFID Reader is an EPCglobal Class 1 Gen 2 4 Port reader product.
Below is the front and side view of the CS203X Integrated reader. There are LEDs to indicate
the operating status
1. Power
2. Activity (programmable LED)
3. Active antenna port currently selected (Port 3,4) Port 3 is external antenna port.
Port 4 is internal embedded antenna.
4. Ethernet link and Ethernet data LED
Below is the front, back, bottom and left side views of the CS203X reader .
Internal antenna
in this side
Mounting screws
1) AC Adaptor Unit
CS463 4-port reader can be powered up with the AC adaptor unit included in the package.
Below photo shows the typical connection to use the AC adaptor. The AC adapter
connects to CS463 via a “Locking” plug DC power plug. Please screw tight the lock on
the DC power plug to ensure reliable power connection. That way the DC power plug
would not loosen up over time.
Plug in AC adapter,
2) PoE+
CS463 also supports the use of Power over Ethernet (PoE+) to give it power. Below shows
the typical connection of using PoE+ as the power supply to the CS463 4-port reader.
Note that it must be POE Plus (POE+) for it to give enough power to CS463. Make sure
you use 30 Watt POE+ port to ensure CS463 receive enough power to operate.
Connect RFID antenna with wrench (8mm torque with 100 N-cm) to reader
(CS463 has 4 available RFID antenna ports from Port 1 to Port 4)
WiFi
antenna
BT
antenna
5) Ethernet Cable
1) AC Adaptor Unit
CS203X reader can be powered up with the AC adaptor unit included in the package.
Below photo shows the typical connection to use the AC adaptor. The AC adapter
connects to CS203X via a plug DC power plug. Please screw tight the lock on the DC
power plug to ensure reliable power connection. That way the DC power plug would not
loosen up over time.
Plug in AC adapter,
2) PoE+
CS203X also supports the use of Power over Ethernet (PoE+) to give it power. Below
shows the typical connection of using PoE+ as the power supply to the CS203X reader.
Note that it must be POE Plus (POE+) for it to give enough power to CS203X. Make sure
you use 30 Watt POE+ port to ensure CS203X receive enough power to operate.
There is one internal RFID antenna connected to antenna ports Port 4 internally.
Connect RFID antenna with wrench (8mm torque with 100 N-cm) to reader
(CS203X has one available RFID external antenna ports Port 3)
Reader should be mounted in different ways depending on the surface on which the reader is
installed:
1) Reader is installed on metal surface
2) Reader is installed on non-metal surface
Installation method on non-metal surface, such as wood surface: The reader should be
mounted leaving some space between the bottom of the reader and the surface. This will
allow ventilation of air underneath the reader.
The standard C-Clamp for pole mounting will fit the screw holes at the back of CS203X:
There are 2 Linux OS versions: 3.0.35 or 4.x.x. For units shipped before September 2019, the
OS is Linux 3.0.35. After September 2019, the OS is 4.xx.yy or beyond. Some of the
firmware has different versions per the OS version. Please note this variation.
using Browser
All CSL Intelligent Fixed Readers are set to Ethernet Static IP of 192.168.25.160 ex-factory.
Wi Fi is disabled ex-factory. This is to simplify out-of-box experience.
Set your PC to a static IP of 192.168.25.100 (or any other as long as the subnet is 25)
Connect Ethernet cable from your PC to the reader directly, or via an Ethernet switch.
Key in User Name: root, Password: csl then click Login to login to system
To control CS463 reader now using the browser interface, please go to Chapter 5.
For a Linux device, Debug Serial Port is a popular interface to monitor the boot up and also
type in commands.
On the PC side, one needs to run a terminal application. In this user manual, the application
PuTTY is used to review the CS463 operation in Linux OS level.
You need to connect your PC to the Debug Serial Port. If your PC has serial port, you can
connect directly. If your PC does not have a serial port, you can use a USB to Serial
adapter.
Please use a USB-to-Serial cable to connect the CS463 debug port to the USB port of PC
Laptop/PC
(b) Check the COM port number that corresponds to the USB to Serial Adapter
(c) Setup a Baud Rate = 115,200 connection to the appropriate serial port
1. Select “Serial”
4. Select “Serial”
After clicking “Serial” in step 4 in above diagram, the window will change to as below, please
select “None” for the “Flow control” option. Then click “Open” to confirm the connection
Below diagram shows the display at the end of CS463 Linux boot up and embedded processes
boot up. There is a prompt for login and password.
ifconfig
The purpose of “ifconfig” command is to show the relevant network information
WIFI IP Address
WIFI MAC Address
top
The key purpose of “top” command is to show user how many process being execute and
the occupancy of CPU percentage.
lsmod
The purpose of “lsmod” command is to list out how many modules in operation as shown
below. Note that rtk_btusb is the Bluetooth driver. 8723du is the Wi Fi driver.
lsusb
The purpose of “lsusb” command is to list out how many USB devices are connected to
the system.
via SSH
Another popular way to connect to a Linux device is via SSH.
You can also use the application PuTTY, but choose SSH on the front page:
Start Putty, select SSH on Connection Type and type in IP address of CS463, then click Open
Using the Debug Serial Port or using SSH, one can now develop embedded Linux codes inside
CS463 in the usual Linux development manner.
For popular open source software, one can use the command “dnf” to download popular
precompiled binaries (dnf is similar to apt-get) by following the steps below:
Step 1: type the command “dnf --refresh makecache” (beware of the double dash) to refresh
the directory of available precompiled binaries
Step 2: type the command “dnf list” to list the available precompiled binaries in long name
format.
Step 3: type the command “dnf list | grep <keyword of the application you want>” to narrow
your search to those in long name format.
Step 4: type the command “dnf install <long name of the application as obtained from Step 3>”
Memory Device
First of all, we need to connect to the Linux OS via the Debug Serial Port.
Setup connection
Below show the set up page of the PuTTy .
2. Select “Serial”
4. Select “Serial”
After clicking “Serial” in step 4 in above diagram, the window will change to as below, please
select “None” for the “Flow control” option. Then click “Open” to confirm the connection
After plug in USB memory, “lsusb” command to show one more USB device appearing
At this point, the way to get to the files in the USB memory finger is different for Linux 3.0.35
and Linux 4.xx.yy:
Here, for example, it shows there is a USB with name USB_HKCHAN. To access files inside,
just type “cd USB_HKCHAN” and you will see all the files inside.
First of all, we need to connect to the Linux OS via the debug serial port.
Setup connection
3. Select “Serial”
4. Select “Serial”
After clicking “Serial” in above step the window will change to as below, please select “None”
for the “Flow control” option. Then click “Open” to confirm the connection
Use a mini-USB to USB Type A cable to connect between CS463 USB Console port and the
PC USB port
At this point, to connect to a PC and let the PC “sees” the CS463 as a hard disk is different for
Linux 3.0.35 and Linux 4.xx.yy:
1. cd ..
2. cd opt
3. ./usb_client_store_start
1. cd /opt
2. ./usbcdisk_start
After that you can use the File Explorer on the Windows PC to check if it discovers a new hard
disk.
Laptop
CS463
Fixed IP : LAN cable
192.168.25.102
Default fix IP : 192.168.25.160
USB-to-Serial cable 1
COM4
Arduino
UNO
(i) Setup the Arduino environment. It can download the from below URL
https://www.arduino.cc/en/Main/Software
(ii) After unzip, and then go into the directory to execute the Application (circled
in below figure)
(iv) Connect the Arduino UNO board to your laptop with USB cable
(v) Check the COM port number for the Arduino dongle from device manager
(viii) Download the SerialEchoBack from CSL Web site and Read the Download
program “SerialEchoBack.ino” into Arduino IDE
Main menu: File Open
Program Code :
Step 2: Ensure the hardware setup mentioned in beginning of this section was done
Step 4: Open PuTTy window for debug port according to below settings on Laptop
Step 5: After boot up finished, plug in the Arduino dongle to CS463 host USB port
Step 6: Input below command to check the connectivity of Arduino device on laptop command
prompt for CS463 debug port.
Command: ls /dev/ttyUSB*
Step 7: Open the serial terminal for Arduino with below command
exit “mincom”
Client Devices
Following section show how to send and receive data from CS463 Control Serial port
Set up the connection as below. Connect two USB-to-Serial cables between PC and the CS463.
In below demonstration, the corresponding COM ports shown in device manager are 4 and 6
respectively.
CS463
Debug Port
COM4
USB-to-Serial cable 1
Step 2: Open PuTTy window for debug port according to below settings
Click Open to open the com port 4 which connected with CS463 debug port, below
window will pop up
Step 3 : Open PuTTY window for “Control Serial “ port according to below settings
Click Open to open the com port 6 which connected with CS463 debug port, below
window will pop up
setup”
minicom –D /dev/ttymxc1 -s
Remarks: Black arrow means to add space and then press “ESC” button two
Please aware the use of capital/small characters
time to exit !
exit “mincom”
Below figure shows the pin definition for the GPIO port.
GPI : General Purpose Input
GPO : General Purpose Output
GPO3/GPO4(-)
GPO3(+)
GPO4(+)
GPI3(+)
GPI4(+)
GPO1(+)
GPO2(+)
GPI1(+)
GPI2(+)
+12V
+12VGND
GPI1/GPI3(-)
GPO1(-)
GPO2(-)
GPI2/GPI4(-)
Of the 4 GPOs, two of them are fully isolated with independent (+) and (-) terminals: GPO1
and GPO2. Two of them share a common (-) terminal: GPO3 and GPO4.
Of the 4 GPIs, GPI1 and GPI3 share the same (-) terminal, and GPI2 and GPI4 share the same
(-) terminal.
The 12 Volt output is fully isolated, with terminals +12V and +12VGND.
In summary, the following is the application table for system integrators (common pins are
highlighted in specific colors for reminder):
There are 2 accessories that come with the GPIO port operation:
When using the HD15 to Wiretap Terminal Adapter, the Pin #s are actually printed to the
outside of the terminal, as shown in below photo. Here the functions are labeled for easy
reference.
Black
Red Blue
Pink
Orange
Brown
White
Gray
Brown / White
Green
Violet
Blue / White
Green / White
Yellow / White
Yellow
Following is the application table for system integrators (common pins are highlighted in
specific colors for reminder):
+12V 5 Red
GND 15 Black
GPO_1 (+) 4 Yellow
GPO_1 (-) 14 Yellow/White
GPO_2 (+) 3 Blue
GPO_2 (-) 13 Blue/White
GPO_3 (+) 10 Violet
GPO_3/4 (-) 8 Pink
GPO_4 (+) 9 Orange
GPO_3/4 (-) 8 Pink
Please note the connection method with Linux 3.0.35 is different from Linux 4.x.x.
Debug Port
USB-to-Serial cable
Fig 14
Bluetooth Antenna
Step 2: Using VNC Viewer to connect to CS463 through ethernet as shown below.
Step 3: Within the Ubuntu main menu, click the setup icon to enter “System Settings”
Step 5: After clicking the “Bluetooth” icon, below window will pop up.
Please click the “+” icon.
Step 6: After clicking the “+” icon, below window will pop up. Please press “Continue” to
proceed.
Step 7: After pressing the “Continue” icon, please power up your Bluetooth Speaker device and
force it into “Pairing “ mode. After some time, the Bluetooth Speaker, namely “DOSS
Pie” is shown in below Figure in this example. (Please note that your device should
have different name other than this one).
Normally, the bluetooth
device name is on the chassis
or label
Step 8: Please use the cursor to select (become highlighted after selection). Then press
“Continue” to proceed
Step 9: After pairing the Bluetooth Speaker device, please go back to “System Settings” menu.
Please select the “Sound” icon.
Step 10: After entered the “Sound” menu, please click the alert sound “Bark” twice (or any
other alert sound). You will hear the corresponding sound from the Bluetooth Speaker.
Step 11: After successfully generating the sound from Bluetooth Device. Please go back to the
device menu as shown below. Please select (highlight) the Bluetooth device,
Step 12: Remove the paired device record by clicking the “-“ icon. Then the paired device
record will be empty as shown below.
Empty Bluetooth
device pairing record
as default
Laptop
LAN cable CS463-2 (Finished Good)
Fixed IP :
Default fix IP : 192.168.25.160
192.168.25.100
Debug Port
Fig 14
Run Putty with SSH Bluetooth Antenna
section
Start PuTTY in PC, select SSH on Connection Type and type in IP address of CS463, then
click Open as below
Look for target Bluetooth device in scanning result as shown below, the
Bluetooth speaker device called DOSS Pie was used in this example,
Run the command “scan off” to stop the Bluetooth scanning process
functionality can be checked by playing any wav file. Some wav file
paplay /usr/share/sounds/alsa/Side_Left.wav
below method.
The purpose of Wireshark is to capture the Ethernet protocol handshake package between
reader and the PC and log them for analysis.
In the “Input” tag, please click to select the “Ethernet” for capturing
The CSL Fixed Intelligent Reader Family’s GPIO ports are actually optically isolated switches
only. There are various ways one can connect them up for common peripheral control. The
following sub-chapters describe typical ways to connect up for General Purpose Input and
General Purpose Output operations.
In addition to 4 optically isolated GPO and 4 optically isolated GPI, the CSL fixed intelligent
reader family also supply an isolated 12 Volt DC supply at 2 Watt, i.e., a maximum of 160 mA
current drive output. For low power peripheral devices, including most relays, this 12 Volt
isolated DC power supply can be used to drive them.
For load that requires higher current drive, external power supply is needed, and some of the
examples show how this is done in a safe manner. The important thing to remember is to
handle exception cases when the load encounters a shorting failure, so that unlimited current
can pass through that, and the optical isolated switch can be damaged if a protective resistor
(high power resistor) is not placed in series with the power supply path. As long as a
protective resistor is there, the overall circuit is protected. This is a standard industry practice.
GPI ports contain an optical isolator inside. The input line has a series resistor of 1K Ohm
with 1.5 Watt rating for protection. This will withstand external voltage up to 36 volt as
shown below.
P = V2 / R
P = 362 / 1000 = 1.296 Watt < 1.5 Watt
Therefore the highest voltage the GPI port of CSL Intelligent Fixed reader can “see” is 36
volts.
If one uses the 12 Volt DC output from the CSL Intelligent Fixed Reader in the input sensing
circuit (examples are in next few pages), then that voltage is well below the limit of 36 Volt.
Each GPI pin pair “looks” into an optical isolator with an operational forward voltage of
1.2 Volt, maximum 50 mA current. An internal series 1K Ohm 1.5 Watt resistor is also
present for protection.
Each GPI pin pair “looks” into an optical isolator with an operational forward voltage of
1.2 Volt, maximum 50 mA current. An internal series 1K Ohm 1.5 Watt resistor is also
present for protection.
Inside CS463
GPI_1 (+)
(Pin-2)
GPI_1 Logic become High
Sensor or Push
when the Sensor or Push button
button switch 5V External
switch is turned on (pushed)
Power
(Pin-12)
Supply
GPI_1 (-)
Example 3: (GPI using the Internal Isolated +12V, 2 Watt Power Supply)
Each GPI pin pair “looks” into an optical isolator with an operational forward voltage of
1.2 Volt, maximum 50 mA current. An internal series 1K Ohm 1.5 Watt resistor is also
present for protection.
1K
Inside CS463
GPI_1 (+) (Pin-2)
GPI_1 Logic becomes Low
Sensor or Push
when the sensor or Push
button switch
button switch is turned on
GPI_1 (-) Pin-12)
(pushed)
GND (Pin-15)
When external push
Example 4: (GPI using the Internal Isolated +12V, 2 Watt Power Supply)
Each GPI pin pair “looks” into an optical isolator with an operational forward voltage of
1.2 Volt, maximum 50 mA current. An internal series 1K Ohm 1.5 Watt resistor is also
present for protection.
Sensor or push
button Switch
Inside CS463
GPI_1 (+)
GPI_1 Logic becomes High (Pin-2)
when the Sensor or Push
(pushed)
GPI_1 (-)
GND (Pin-15)
Maximum current that can pass through the GPO optically isolated switches of CSL Intelligent
Fixed Readers is 2 Ampere.
Therefore a protection resistor with very high power rating must be added in series to the
external circuit to limit the current to 2 Ampere. The value of this resistor should be such that
the current cannot exceed 2 A.
In addition, there is actually a resettable fuse internal to the GPO circuit in series with the
circuit that will protect the switch as a last-ditch defense.
Example 1: GPO with +10V External Power Supply for High Load Current
A high wattage external resistor of N Ohm and rated to P Watt must be connected in case the
LOAD shorts out. N and P must satisfy the following equation to limit current to 2 Ampere in
such LOAD shorting situation:
In this example, current in the load (e.g. a buzzer with 1K Ohm internal resistance) is
calculated by the following equation:
10 Ohm 20 Watt
GPO_1 (+) (Pin-4)
Resistor
10V
The Load powers up when I = 9.3 mA @ GPO1=Close
GPO_1 becomes Close
LOAD 1K Ohm
GPO_1 (-) (Pin-14)
This is ground of
external devices
Example 2: GPO using relay for full isolation and high coil current (with External Power
Supply)
10 Ohm 20 Watt
GPO_1 (+) (Pin-4)
Resistor
External Power
Supply 12V
This is ground of
This is ground of
external circuit
Example 3: GPO for Load Current < 160 mA (using +12V, 2 Watt Internal Isolated Power
Supply)
I = 8.9 mA @ GPO_1=Close
+12V(Pin-5)
1.2K
Close
GPO_1 (-) (Pin-14)
GND (Pin-15)
Example 4: GPO for Load Current < 160 mA (with +12V, 2 Watt Internal Power Supply)
+12V(Pin-5)
Inside CS463
GPO_1 (+) (Pin-4)
LED lights up
Example 5: GPO using Relay for Full Isolation and Low Coil Current (using +12V, 2 Watt
Internal Isolated Power Supply)
The example relay below is a 12 Volt relay with 90 Ohms resistance coil, which means current
flowing through the coil is 133 mA.
+12V(Pin-5)
GPO_1(+) (Pin-4)
Inside CS463
The Relay powers up I < 160mA
GPO_1(-) (Pin-14)
when GPO_1 Switch 12V Relay
becomes Close
90 Ohm Device to be
Coil controlled
GND (Pin-15)
7 Quick Start
This chapter describes quick start guidelines for the various readers in the CSL Intelligent
Fixed Reader family.
This chapter explains how to quickly connect up and run CS463 OOB (Out Of Box) to read
RFID tags and display them on a browser.
CS463 comes with a Default Profile and a Default Event. The Default Event is not enabled at
the point of delivery to customer. On receiving the CS463 reader, the customer can then
enable the Default Event and use that to immediately read RFID tags from antenna Port 1 and
observe the tag IDs showing up in the Events/Tag Inventory page.
After login to the reader and ensuring the reader is in HTTP/XML access mode (this should be
the state when delivered from factory) as explained in section 4.3,
Make sure antenna Port 1 is connected to an antenna as stated in Default Profile of
Operation Profile.
Antenna
Connect Port 1 to
the antenna
Go to the Operation Profile in System page and select List Profile to ensure the
Default Profile can be found as shown below
Go to the List Event of Event Management in Event page and click List Event to show
the Default Event
Click “Default
Event” to continue
In Default Event, reading of tag from antenna port 1 can be started after the default event
is enabled (ticking the tick box) and the button “Modify” clicked to confirm the change
Click “Modify” to
confirm the change
Reading of tag from antenna port 1 can be stopped once the default event is disabled by
unchecking the “Enable Event” tick box and clicking the “Modify” button to confirm
the change
Now go to the page Events/Tag Inventory, you should be able to see tags being read:
This chapter explains how to quickly connect up and run CS203X OOB (Out Of Box) to read
RFID tags and display them on a browser.
CS203X comes with a Default Profile and a Default Event. The Default Event is not enabled
at the point of delivery to customer. On receiving the CS203X reader, the customer can then
enable the Default Event and use that to immediately read RFID tags from antenna Port 4
(internal) and observe the tag IDs showing up in the Events/Tag Inventory page.
After login to the reader and ensuring the reader is in HTTP/XML access mode (this should be
the state when delivered from factory) as explained in section 4.3,
External Antenna
port
Go to the Operation Profile in System page and select List Profile to ensure the
Default Profile can be found as shown below
Go to the List Event of Event Management in Event page and click List Event to show
the Default Event
Click “Default
Event” to continue
In Default Event, reading of tag from antenna port 4 (internal) can be started after the
default event is enabled (ticking the tick box) and the button “Modify” clicked to confirm
the change
Click “Modify” to
confirm the change
Reading of tag from antenna port 4 (internal) can be stopped once the default event is
disabled by unchecking the “Enable Event” tick box and clicking the “Modify” button
to confirm the change
Now go to the page Events/Tag Inventory/Capture Tags Raw, you should be able to see tags
being read:
This chapter describes in details the various pages of the web browser interface. With CS463,
this web browser enables full control of the reader, including the event engine.
The home page of the web-based administration interface can be entered by just entering the IP
address of the reader (default IP address is printed on the label) on the web browser.
For example, if the IP address of the reader is 192.168.25.160, you should enter:
http://192.168.25.160
Use default User Name: root and Password: csl and click Login to login to the Reader
8.2 Status
The “Status” page gives a quick overview of the current status of the reader.
The reader basic information such as serial number and access mode can be found on
beginning of status page
If any event was enabled and reading tag, the basic RFID related parameters will show on
status page such as transmitting power, profile and session as below
Network information can be found on status page such as IP and Mac address
The “Users Management” page contains sub-menu for adding, deleting and modifying
password, set auto-logout time and login/logout.
To add user, input the user name, password, authorization level and description. Then click
“Add”.
To delete user, select the user name and then click “Delete”.
To modify password, input the current password, new password and retype new password.
Then click “Modify”.
The “List Users” page lists all the users and his/her authority.
The “Set Auto Logout Time” page allows ones to set the time for automatic logout if the user is
idle.
8.3.6 Login/Logout
The “Login/Logout” page is for users to login or logout the web browser interface.
8.4 System
The “System” page contains many sub-menus to configure the reader for operation. Users are
recommended to access these pages to determine the required settings before any operation.
8.4.1 Reader ID
One can modify the reader ID here. Note that the ID cannot be too long if one plans to use
Bluetooth to control the reader (using the CS108 Bluetooth API access mode) because
Bluetooth standard does not allow too long a device name.
The name of each antenna port is the capture point name (Some readers call it read point name).
This name can be configured. In other words, each antenna port (or capture point, or read point)
can be uniquely identified and accessed or referred to. Note that the word capture and read
are interchangeably used in the context of this reader. A capture point is the same as a read
point.
1. HTTP/XML
2. CSL Unified API/High Level
3. CSL Unified API/Low Level
4. CSL Unified API/High Level via RS232 Control Serial Port
5. CSL Unified API/Low Level via RS232 Control Serial Port
6. CS461 Low Level API (MACH1)
7. LLRP
8. CS108 Bluetooth API (CS463 model only)
9. Custom Embedded RFID HTTP
For configuring the reader to be controlled by LLRP API, please set the Access Mode to LLRP.
For configuring the reader to be controlled by CSL Unified API so that one can use the C#
Demo App to control CS463, please set the Access Mode to CSL Unified API
For customers who have already developed programs using the CS461 high level or low level
API, they can use their existing programs to connect to CS463:
For configuring the reader to be controlled by CS461 High Level API, please remember to set
the Access Mode to “HTTP/XML”
For configuring the reader to be controlled by CS461 Low-Level API (MACH 1 API), please
remember to set the Access Mode to “CS461 Low Level API (MACH1)”.
If you need to configure the reader on the web interface (e.g. Network setting, Time settings,
Event Engine, etc.), you must set the Access Mode to “HTTP/XML”.
If you have already developed codes to control CS108 handheld sled reader, you can set the
Access Mode to “CS108 Bluetooth API“. Once you set that, you can use your iPhone or
Android CS108 App to control this CS463 reader.
Some customers would like to use their own embedded control system. In that case, set the
Access Mode to “Custom Embedded RFID HTTP” and then configure the page “Custom
Embedded RFID Application” so that every time the reader powers up it will run that particular
application.
This page is used to input custom embedded RFID application path and its command. This
command will be run on power on – provided Access Mode has been changed to “Custom
Embedded RFID HTTP”.
If one SSH into the reader, and change directory to /opt, you will indeed see a sub-directory
with that name. If you go into that sub-directory, you will then see the program example.c
and the related makefile and other resources. This example.c code demonstrates how to run
the RFID circuits inside to do inventory. You can modify that code or build your own
company’s code based on that.
The “Frequency Configuration” page allows user to configure the country and frequency to be
used by the reader. Please refer to the regulatory law of your region for the allowed frequency
to be used. Here is the “Frequency Configuration” submenu:
One can set the different “Regulatory Region” for different operation frequency band in
different country in this page for RW model and frequency band is fixed for all other model.
Click “Modify” to confirm the change.
The “Operation Profile” page is extremely important as it sets the basic RFID parameters of the
reader.
Parameter Description
Profile ID Each profile can be saved and recall for use in Event
Engine, or be uploaded and redeployed to other
CS463 readers in the field.
Capture Point Which antenna port to enable (turn power on) and the
output conducted power of each antenna port, in
terms of 10 x Power (dBm)
Dwell time of each antenna port – how long the
reader will stay in that particular antenna port to do
RFID tag inventory in each antenna cycle.
Parameter Description
Reader Mode/Link Profile For CS463 there are different Reader Modes:
0 – Best Multipath Fading Resistance
1 – Longest Read Range, Dense Reader Mode
2 – Read Range and Throughput, Dense Reader
Mode
3 – Maximum Throughput
The “Memory Information” page shows the RAM and Flash memory used and free (available
for use).
It also displays the Clear Cache cycle time. This is the periodic time when the Linux OS
cache is cleared.
Configuration Backup
Configuration Restore
To restore backup configuration, click “Choose File”. Then select the backup configuration file
and click “Open”.
System can send power up notification to server with particular format if it is enabled
8.4.10 Heartbeat
If the HTTP Post type server is selected, corresponding Server and Data Format should be
selected as below. Server and Data Format was defined in Cloud Server page
There is different type of log files which can be enabled as shown below.
All Log files can be download in this page, select Log files type going to download then click
Download to start download
Company label can be shown on web page and was defined in this page
The reader sensitivity can be set on this page by changing below parameters
In “Network Configuration” page, one can configure the network parameters such as the reader
IP address, Subnet mask, Gateway and DNS server.
8.5.2 Wi Fi Configuration
All basic setup for wifi can found in this page, you are able to enable/disable the wifi from here
Trusted server for automatic data submission by the reader using the event engine is set in the
“Cloud Server” page. Here is the “Cloud Server” submenu:
Configuration
One can enable network failure data backlog in the Configuration in Cloud Server page. It
allows the reader to buffer the tags read during network failure in memory. Buffered tags are
sent to trusted server when network is restored.
A further selection is necessary in the way the data is backlogged: Either “Drop the Oldest
reading or Ignore the new reading.
To add a trusted server for receiving tag events, input the web address path then click Add.
To modify cloud server, select the server ID in List Cloud Server submenu, modify any fields
and click “Modify”.
Information of trusted server can be retrieved by the “List Cloud Server” page.
democloud.convergence.com.hk/CSLRFIDCloudServer/
you may encounter a certificate warning, please press “details” and then “proceed to website”
You can find the Reader ID from the entry called Reader Serial # on Status page.
So the password for this reader to log in server web page is 00057B84004100057B870041
If any resultant action Send to cloud is set and was triggered as below
Different fields can be added to the reporting format for Cloud Server as below
If data is going to be sent to CSL provided Cloud Server, the fields RFIDReaderSerialNumber
and RFIDReaderInternalSerialNumber must be added as below otherwise CSL Cloud Server
would ignore the send data.
Once the TagDataList was added, more tag related parameter can be selected to send to cloud
Server
Any available field can be added or remove from reporting format on here
8.6.1 Date/Time
The “Date/Time” page allows the user to set the real time clock inside the reader. Please note
that you have to configure the UTC (GMT) time on the reader. The local time will then be
calculated based on the time zone you set. Note that for some country they also practice
Daylight Savings Time.
Warning: After changing the date and time, the reader may pause reading 30-60 seconds for
re-initiation. It is recommended not to open the “Capture Tags Testing” page in “Tag & Tag
Filter” for viewing tags in this period.
This page allows one to setup the NTP server. The CS463 reader will update its time by
connecting to the NTP server at a preset time and preset mode. Be sure to enter the gateway
and DNS server in the network configuration page in order for the NTP server be reachable by
the reader.
The “Tag & Tag Filter” page allows you to create the Tag group or Tag database which will be
used in Tigger page and define filter to be enabled on operation profile. In actual deployment,
RFID reader is used to do security screening of incoming or outgoing vehicles/personnel/asset
or logistic items. A list of predefined tag IDs can be downloaded to each RFID reader so that
the RFID reader will distinguish whether that tag belongs to that list (tag group or tag database).
Only when a tag belongs to that group would the RFID reader carries out further action as
stipulated by the event – for example open the door.
Tags group can be created and download from CS463 reader as follow
Go to Tag group in Tag & Tag Filter and click Add Tag Group
Input the new tags group name as below
Database can be created in reader for user to link tag with database record include basic
information such as staff name, number and corresponding photo, then show the record on web
page after proper even defined. The detail usage can be found on section 9.6 even Example 4:
Example Event using Database Tag Group and Database Display
The defined database can be shown on page List Database as below
Tag Record on particular database can be added after choosing right database
Tag Record on particular database can be deleted after choosing right database
Tag Record on particular database can be modified on List Tag Record submenu after choosing
right database as below
The content of database on particular record can be modified in this page as below
Each Database can be backup on Database Backup/Restore submenu as below after choosing
target database
Particular database can restore to system from pervious backup file as below
The tag filter was used to find particular tags from large population. There are two type of filter
can be used include pre filter and post filter. If the pre filter is used, tags not matching filter
will not transmit response while post filter reader will filter out all not matching tags after
received all tags response.
All defined filter can be found in page List Filter under Tag & Tag Filter page as below
Once any filter was defined here, such filter can be enabled in operation profile then take effect
as shown below
The “IO Port Testing” page allows users to test functionality of IO port
Below is the “IO Port Testing” page, it allows one to look at sensor input (you MUST press the
“Refresh” button to update the input state), and control the outputs for system testing.
Event is the most important part of the reader configuration. By setting it intelligently, one can
handle many business applications autonomously with no interactive computation requirements
needed from remote server. To create and enable an event, one needs to set up triggers,
resultant actions, and then use that to assemble events. Once an event is created, the reader
would run according to it continuously, and will continue even if the reader is powered down
and up (rebooted). In other words, the reader is running autonomously.
Note that there is ex-factory a “Default Event” running the “Default Profile”. It comes
disabled (in the Enable column, it is False). Once you enable it, it will start reading RFID
tags from Port 1 (assuming an antenna is connected to Port 1 for model CS463/CS468XJ and
there are RFID tags in front of the antenna)
Add Event
One should select the operation profile for the event. This operation profile is defined in the
“System” page “Operation Profile” submenu.
The Inventory Enabling Trigger is the initial trigger that turns on the RF power of the reader to
start doing inventory. This trigger can be set to “Always On” and then the reader will do
inventory the moment the reader is powered on. Note that this trigger has to be defined in the
Trigger page. Note that if one wants the reader to be always on, simply choose “Always On” in
the Inventory Enabling Trigger entry.
The Inventory Enabling Action is the action that accompanies an inventory enabling trigger.
For example, one may want to turn on a signal light when the inventory has started.
Once the inventory enabling cycle is entered, then the event engine would look for actual event
triggers, and these triggers can be Boolean operated together as defined in the entry “Trigger
Logic”. The Trigger Logic is a Boolean combination of triggers that are defined in the “Trigger”
page which will be described later.
When the Trigger Logic is satisfied, the event is established, and the resultant actions are
defined in “Resultant Action” section. Again it can be a combination, sequential (THEN) or
(AND), of actions.
The overall inventory enabling cycle is ended based on the triggers defined in “Inventory
Disabling Trigger” section. Sometimes this can be another Infrared sensor at the exit of the
reader read zone, or it can be defined as a period of time of no tag reads. If the user wants the
reader to be always reading tags, then the selection “Never Stop” should be chosen here.
The Inventory Disabling Action is the action that accompanies the inventory disabling trigger.
For example, one may want to turn off a signal light (that was turned on due to an inventory
enabling action as described before) when the inventory is stopped.
Modify Event
To modify event, go to “List Event” page and select the “Event ID”, modify the event and click
“Modify”.
Enable/Disable Event
To enable/disable event, select/de-select the checkbox “Enable Event” and click “Modify”.
Delete Event
List Event
8.9.2 Trigger
A trigger is a stimulus that causes the reader to recognize it and do something about it.
The trigger is used in Inventory Enabling, Inventory Disabling, and of course inside the actual
Event Triggering Logic section. Below is the “Trigger” submenu:
Add Trigger
Below is the “Add Trigger” page:
1. “Read Any Tags (any ID, 1 trigger per tag)” would look at tags coming in to the four
antenna ports (or capture points), the ones being ticked here would be selected, and will
generate 1 trigger per tag (different ID) notification. By selecting which antenna port one
can then select tags read by specific antennas to trigger an event. Note that in Time
Windowed Mode there is a duplicate elimination action within each time window, and for
the same ID within that window, it will only be recorded once into the buffer – unless the
box called “Antenna Differentiation” in the Event Management page is ticked, in that case
the same tag read by different antennas will generate different triggers. Hence for each
different ID within that duplicate elimination time it will generate an event.
2. “Input Sensor State” would look at the state (high or low) of one of the general purpose IO
input.
3. “No Tag Read in Specified Time Span” would check if for a specified time read, no tag
passes through the reader read zone.
4. “Trigger in Tag Group” would check if any tag is within a pre-defined tag group .
5. “Trigger if RSSI larger than or equal to” would check if read tag Rssi is larger or equal to
defined value
6. Specified Time Span elapsed”.
For “read any tags” trigger, the user also has to specify which antenna port or capture point it is
collecting the tags from. To choose it, just tick the box on the left of each entry.
For “Input Sensor State” trigger, the Port Number 1 shown on below, is mapped to physical
GPI1 port which using pin 2 /pin12 of GPI1 terminal (GPI1 ports details see section 5.8).
Level High was selected on below case so the trigger will be set if there is high voltage applied
on pin2 (GPI1(+)) and pin 12 (GPI1(-)) is properly connected
Modify Trigger
To modify trigger, go to List Trigger and select the “Trigger ID”, modify the trigger and click
“Modify”.
Delete Trigger
List Trigger
The “Resultant Action” pages define the resultant action that will be enforced when an event
logic is established. Below is the “Resultant Action” submenu:
1. Do Nothing (Only Show on Screen) – here nothing is affected, except the tags collected can
be shown on browser screen. Note that there are APIs that can collect the tag IDs or
information on demand from the remote server. So this is actually a polling mode in
terms of collecting tag information.
2. Batch Alert to Server – here the collected tag information are sent to Server at the end of
each duplicate elimination cycle (Time Window)
3. Instant Alert to Server – here the collected tag information are sent to Server immediately
as it is read.
4. Low Latency Alert to Server
5. Output Port – here the General Purpose IO output port would be controlled to have certain
level change or pulse or even pulse train.
6. Save to External USB Memory – here the tag information was sent to external USB flash
memory.
7. Display Tag Database Record
8. Display Tag Group Record
If one selects “Batch Alert to Server”, “Low Latency Alert to Server” or the “Instant Alert to
Server”, then one has to also select the Server ID, which is defined in the Trusted Server page
of the Network page. The user also has to select the Server ID and Data format ID are going
to use.
If one selects “Output Port” then one has to input few more fields. The user has to select the
Port Number, 1 to 4. The Output Logic has to be selected, which can be either Open, Close or
Pulse .
For Pulse, there are more parameters to be configured. The Pulse Logic, which can
Open-Close-Open, or Close-Open-Close, and Pulse Mode, which can be One Shot Pulse or
Pulse Train, the Pulse Width in msec., and for Pulse Train, the duty cycle and Pulse Duration.
These are all self-explanatory.
To modify resultant action, select the “Resultant Action ID” from list table, modify it and then
click “Modify”.
To delete resultant action, select the “Resultant Action ID” and click “Delete”.
When tag record within particular database was read by reader, the database content can be
shown in this page as below
Below is the Event called “Example Tag Database Display” (installed on shipped reader), once
the Event was enabled and right tag was detected, the database content will be shown as
previous diagram
The “Version Management” page allows you to review the version upgrade history (in the
Version Control Submenu), and to do firmware upgrade (in the Firmware Upgrade Submenu).
Version Control
In the “Version Control” sub-menu page, one can see the version number of the software.
This is an important page to check if the versions are correct, especially after a firmware
upgrade. It also shows the upgrade history of the reader.
Firmware Upgrade
In the “Firmware Upgrade” submenu, just press the “Choose File” button and find the upgrade
file (which the user has already downloaded from CSL website before). Then press the
“Firmware Upgrade” button. The upgrade takes a few minutes, depending on the size of that
particular upgrade. Please wait until you see the success message. After that please wait for the
WebApplication to automatically restart to the login page.
There are 2 Linux OS versions: 3.0.35 or 4.x.x. For units shipped before June 2019, the OS is
3.0.35. After July 2019, the OS is 4.x.x. Some of the firmware has different versions per the
OS version. Please note this variation.
Below is the page to upgrade Web application. Linux OS versions: 3.0.35 or 4.x.x use same
Web application
In case of web application version 3.x or later, the upgrading can be done directly using the
zipped file
For existing web application 2.x or earlier, the zipped Web application file needs to be
unzipped first before upgrading. The unzipped file should have the file extension of “war” as
shown below.
Then click Upload after choose the Web application file and upgrading will start
If there is any patch for system, it can be done on this page. Linux OS versions: 3.0.35 or
4.x.x can use same Patch file
One can use a browser to quickly configure the CS463 reader to autonomously read tags based
on certain logic sequence defined in the event engine and operation profile.
Event
CS463 comes with a Default Profile and a Default Event. The Default Event is not enabled
yet. Once the user enable that event, then the user can use that to immediately read RFID tags
from antenna Port 0.
After login to the reader and ensuring the reader is in HTTP/XML access mode as explained in
section 4.3,
Make sure antenna Port 1 is connected to an antenna as stated on Default Profile of
Operation Profile which mentioned on previous session Setup Reader.
Antenna
Port 1 was
connected to the
antenna
Go to the Operation Profile in System page and select List Profile to ensure there is
Default Profile can be found as below
“Default
Profile”
Go to the List Event of Event Management in Event page and click List Event to show
the Default Event
Click “Default
Event” to continue
In Default Event, the reading tag from antenna port 1 can be started after the default event
was enable and click Modify to confirm the change
Click “Enable
Event” to enable
the tag reading
Click “Modify” to
confirm the
changing
reading tag from antenna port 1 can be stopped once the default event was disable by
unchecking Enable Event and click Modify to confirm the change
Event
To define your own profile and event, the following steps are needed:
Add Profile:
Go to the Operation Profile in System page, then click Add Profile as below
Antenna
Port 1 was
connected to the
antenna
Go to List Event in Event Management and click “ Event 1” to modify the Event.
Click “Event 1” to
modify the Event
Select Always
On
Click “Modify” to
apply the change
Please click “Modify” to confirm the change and inventory will start.
Go to Tag inventory to check inventory result.
Click “Tag
Inventory” to check
Inventory result
The Inventory can be stopped by disabling the Event 1 on Event Management as below
Click “Modify” to
apply the change
Below procedure to enable particular group of tag to be detected and used this group as trigger
Add tag group
Go to Tag group in Tag & Tag Filter and click Add Tag Group
Input the new tags group name as below
Prepare tag record file, below is the example file and view by notepad
In the Add trigger of Event menu, new tag group (TagGroup 3) is available as shown below
Cloud server
Step 1: Set up the Cloud Server Path (use CSL Demo Cloud Server in this example)
List the Cloud Server and check CSL Cloud Server path is correct (this server is saved on
reader when shipped)
CSL cloud server path:
https://democloud.convergence.com.hk:29090/WebServiceRESTs/1.0/req/create-up
date-delete/update-entity/tagdata
Select fields to be used as below. Note that in order to send data to CSL Demo Cloud Server,
you MUST include RFIDReaderSerialNumber and RFIDReaderInternalSerialNumber. The
server will check the actual production CS463 units serial number and internal serial number as
well as the MAC addresses to ensure it is a bona fide CSL product.
For your own server you do may not send these data.
Click Add
Step 2: Add Resultant Action that sends data to this Cloud Server
Add Resultant Action with Low Latency Alert Server action mode as below and using the
proper Server ID (the ID “Send to CSL Demo Cloud” is used in this example) and Data Format
ID
Add “Example Event Send to CSL Demo Cloud Server” and using pervious defined Resultant
Action “Send to CSL Demo Cloud”
Enable the event “Example Event Send to CSL Demo Cloud Server” to start Inventory so that
data will be sent to cloud server
Go to Tag Inventory page to check any tags was read from reader as below (show all tags read
mean raw data)
Step 5: Verify tag data is indeed sent to the CSL Demo Cloud Server
To verify the tag data has been sent to the remote server, in this case the CSL Demo Server,
you need to log in to the CSL Demo Cloud Server.
democloud.convergence.com.hk/CSLRFIDCloudServer/
you may encounter a certificate warning, please press “details” and then “proceed to website”
To log in, it asks you for the Reader ID, which is the Reader Serial Number as printed on the
product label. You can also find this on the Status Page Reader Serial # entry.
Get the login password from status page and the password is the concatenation of the Ethernet
MAC address and the Wi Fi MAC address:
Password = “Ethernet MAC Address + Wi Fi MAC Address” (details go to section 8.5.3)
Again, you can find this information either on the product label or on the Status page. Note
that you need to enable the Wi Fi in order to see the Wi Fi MAC address on the Status page.
The CSL web page after login for this Reader will show a table with all the data uploaded:
For incoming personnel case, the Tigger “Infrared Sensor GP1 Port 1 High” is used
to detect incoming personnel then start inventory, this personnel leaving is detected
by “Infrared Sensor GP1 Port 2 High” then stop inventory.
For leaving personnel case, the Tigger “Infrared Sensor GP1 Port 2 High” is used to
detect leaving personnel then start inventory, the personnel going out is detected by
“Infrared Sensor GP1 Port 1 High” then stop inventory.
One Input port is used to monitor the incoming Personnel/truck, If the level of input port
changed from Low to High such as infrared detector, the inventory will be enabled. This trigger
is defined as below
There is another trigger to control the detection of tag group as shown below and trigger mode
is “Tigger in Tag Group”
The Tag Group called Test Group 1 is used in this trigger and this tag group was defined in Tag
group under Tag &Tag filter page as shown below
There are Resultant actions after particular tag was detected within the group and defined as
below
This resultant action will turn on the output port
The inventory will be stopped by trigger called “Infrared Sensor GPI Port 2 High”
Another Input port is used to monitor the incoming Personnel/truck leaving detection zone, If
the state of input port level changed from Low to High such as infrared detector, the inventory
will be stopped. This trigger is defined as below
After the both “Example Event Entrance Boom Barrier Control”/ “Example Event Exit Boom
Barrier Control” event was defined, each event should be enabled by clicking Even Enabled
and click Modify to save the changed
After both events was enabled and Enable field become true as shown below
Please ensure both Antenna Port 1 and Antenna Port 2 was connected with antenna before
enable mentioned Events
The event “Operate on Tags from Antenna 1” is used to handle tags from antenna port 1 while
event “Tags from ant 2” work for tags from antenna port 2. If both even was enabled, different
event can work for each port simultaneously.
The event “Operate on Tags from Antenna 1” details as below. It will turn on GPIO port1 if
tag within tag group defined in Test Group 1, was detected coming from antenna port1.
The event “Tags from ant 2” details as below. It will turn on GPIO port2 if tag within tag group
defined in TagGroup 3, was detected coming from antenna port 2.
After corresponding even was enabled, database content will be shown on below page if the tag
in database was detected and its corresponding record can be found in database
The database is going to use in this event, was choose in Trigger page as shown below
The way showing database content was defined in Display Format, so, you need choose right
display format in Resultant Action page as shown below on Display Tag Database Record
Action Mode
Type of record on particular database can be listed in List Database as shown below.
The content of each record on each database can be changed from List Tag Record as shown
below
click here to
continue
The new record can be added to particular database in Add Record as shown below
click here to
continue
The content of each record on particular database can be added in this page as shown below
After all necessary modification was done, the event can be run again by clicking Even
Enabled as shown below
If you go to Display Tag Group/Database Record, you can see the database record content
linking to the detected tag(The tag with EPC 123456789012345678901234 was used in this
event Example Tag Database Display shipped with reader ).
The event Read Temp is used to read temperature from Magnus S3 tag. This Event was shipped
with latest version of reader.
Once the event was enabled as below and the condition on temperature higher than 10C in
trigger Read Temp tag was fulfilled, reader will send pulse to IO port. You can check the
temperature reading on Display Magnus Tag Data page under Tag Inventory and shown on
coming section
Here is the trigger Read Temp tag used on Read Temp event
Temperature requirement
is set on here
You can find the temperature result on this page Display Magnus Tag Data page under Tag
Inventory
Temperature
read
The returned value of On Chip RSSI S3 tag should be within a range (details can be found on
official Magnus S3 document) otherwise the temperature accuracy will be affected. The target
range of On Chip RSSI can be set on Profile page as shown below. If the received “On Chip
RSSI” from S3 tag out of the defined range, the temperature result will not show on Display
Magnus Tag Data page. Correcting the problem, you need to adjust the reader power or the
distance between reader antenna and S3 tag
Here is the operation profile Read Temp Magnus S3 used on event Read Temp.
The tag model Magus S3 was chosen in this operation profile, correct model of tag must
match the using one otherwise you can’t read the temperature
The CS463 can be controlled via the Ethernet. In this case user needs to connect the PC with
CS463 with a Ethernet cable directly or via a router, or via the Wi Fi network.
Log in to the reader with User name root and password csl
Change the access mode to CSL_API then click Set to apply the change
Click “Set” to
apply the change
At this point, you can logout from reader and start the Demo application
Below is the screen capture of a Demo application, which is also available for download from
Convergence website (www.convergence.com.hk), on PC controlling CS463.
Highlight the CS463 reader which are going to connect then click Connect
Click “Connect” to
connect to the reader
Below shows the main menu of the PC Demo application. User can perform typical basic tag
operations via this PC Demo application as mentioned below.
Inventory
Tag memory bank read and write
GPIO On/Off control
Antenna port settings
Output power settings
Click “Setup” to
change reader
configuration
Go to Setup Page to modify the setting of reader to match hardware connection such as which
ports were connected with antenna
Go to Antenna Port Config to configure which port was connected with antenna
Click corresponding antenna port which was connected with antenna, and change the state to
Active state
Go to Inventory Config page and change all inventory related parameter such as session, target
and algorithm
After the configure the reader, inventory can be started to read tags
Download the LLRP application from CSL website and unzip got follow files
First byte Format: Mode: 0 = Toggle AB (default); 1 = Target A; 2 = Target B (Hex #, 1 bytes)
Second byte Format: inventory algorithm: 0 = fixed Q; 1 = Dynamic Q (default) (Hex #, 1
bytes)
For Example: Set Toggle AB and Dynamic, data should be “0001”
To be added
Unzip package and start the Mach1 PC software by double click the
CS463Mach1Samples
Select “Inventory”
for reading tags
Using Android Phone with Play store and search application with keyword CS108 C# as below
After the CS108 C# Demo application installation successful, the software icon can be found
on phone main page as below
All available reader can be found in this page as below and select the right one to connect
CS108 C# Demo main page is shown as below and detail operation can be found on CS108
operation manual available on CSL Web page
You can select Inventory page to read tags
Remark: Ensure Antenna was connected on Reader before starting to read Tags
Available tags was shown below after you press the Start Inventory
Input the Embedded RFID application path and its command in this page as shown below, the
application will run once the access mode changed to “Custom Embedded RFID”
Web Application:
JNI Library:
Patch:
LLRP Library:
The CS463 model has been tested and found to comply with the limits for a class B digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause harmful interference to radio
communications. However, there is no guarantee that interference will not occur in a particular
installation. If this equipment does cause harmful interference to radio or television reception,
which can be determined by turning the equipment off and on, the user is encouraged to try to
correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna
Increase the separation between the equipment and receiver
Consult the dealer or an qualified radio/TV technician for assistance
FCC NOTICE:
To comply with FCC part 15 rules in the United States, the system must be professionally
installed to ensure compliance with the Part 15 certification. It is the responsibility of the
operator and professional installer to ensure that only certified systems are deployed in the
United States. The use of the system in any other combination (such as co-located antennas
transmitting the same information) is expressly forbidden.
Note:
Changes or modifications not expressly approved by the party responsible for compliance
could void the user’s authority to operate the equipment.
Reader Mode/ 0 1 2 3
Link Profile
Appendix C: Sessions
Session is a concept of the EPC Global Standard to allow a tag to respond to multiple readers
inventorying it at the same time, each using a different session number.
The user however has to be careful because these 4 sessions have different behaviors, notably
how the tag flag “persists” in time. A tag, before being inventoried or when just after being
powered on, has a flag of State A. When it is inventoried, the flag will go to State B. The tag
flag will stay in State B until the tag powers off or the persistence time is up.
A reader can declare it only wants to inventory flag A, so that after a tag is inventoried and its
flag gone to State B, it will no longer respond to further inventory rounds – until the end of the
persistence time.
Now for S0, S1, S2 and S3, the persistence times are DIFFERENT! Because of that, one has to
be very careful in choosing which session to use.
Q is an EPC Global Standard concept related to the way a group of tags is inventoried.
When a reader broadcasts its desire to inventory tags, it sends out a Q value. The tag will,
based on that Q, calculate a certain number and define that as the number of repeated
inventories the reader will do. Basically, the relationship of Inventory Repeats and Q is:
Inventory Repeats = 2Q
The tag will then choose by random a certain number less than this Inventory Repeats. When
the reader starts doing inventory, the tag will then respond at that repeat number.
For example, if there are 8 tags, then in theory the Q can be 3, and if each tag chooses a
number different from that of the other 7 (miraculously, of course), then the 8 tags will be
inventoried in an orderly manner in turn.
Of course this will never happen, as the tags will easily choose a number the same as that of
another one, and a collision will occur.
Therefore, it is a normal practice to have a bigger Q, such as 4 in this case, so that the 8 tags
would have a lower chance of choosing the same number.
Q = INTEGER(LOG2(Tag Population))
For Fixed Q, the Q value does not change. In other words, the expected Tag Population does
not change.
For Dynamic Q, the Q value changes adaptively: when there are a lot of inventory repeats
where no tags respond, the reader will interpret that there are not that many RFID tags in the
front environment, and hence it is more efficient to change the Q to a smaller value. When
there are a lot of inventory repeats where the reader receives data but they do not satisfy
checksum, meaning there is heavy collision, then the reader will interpret that there are too
many RFID tags in the environment and hence it is better to increase the value of Q.
Dynamic Q algorithm is a way to allow the RFID reader to adapt to different amount of RFID
tags being seen by the reader. The idea is that if there are a smaller number of tags in the
environment, then the Q can be reduced and the reader can collect all the tag data faster.
Appendix F: Target
Target refers to the target flag that the reader wants to inventory. There are 2 possible flags of
an RFID tag: State A and State B.
When an RFID tag is first powered up, it has a flag of State A. After it is inventoried, the state
of the flag becomes State B.
The tag will only go back to State A if either it is powered off and powered on again, or if its
persistence time has run up (See Appendix B).
For each round of inventory, the reader sends out a notification to the environment which tag
flag state it wants to inventory. It can inventory State A, or it can inventory State A and State B
alternatively from one round of inventory to the next round of inventory.
In theory, it is a good thing to inventory only State A. The reason being that those tags that
have been inventoried should not respond again, and will hence quickly reduce the amount of
collisions between tags. Generally in practice if you set inventory to State A only, the inventory
of large amount of tags can be faster.
The only catch is that when a tag responds to the reader, it does not know another tag is
colliding with it. It sends out the response and thinks it has done the job, hence transitioning to
flag State B. So in such a case, the tag will not respond to further inventory queries by the
reader, even though its response has been lost due to collisions. Because of that, sometimes the
user will set the inventory to target State A in one inventory round, and then State B in the next
round, and vice versa, and so on. This is called A/B Toggle or A & B Dual Target or simply
Dual Target.
The receive path has many amplifiers and their gain can be configured also.
If one has to read tags that are far away, or tags that are heavily blocked, then increasing the RF
LNA Gain may help.
However, if tags can be very close to the antenna, then one may need to check if the increased
LNA Gain cause saturation of the LNA. To check, just put a tag at a distance that is closest
possible to the antenna during the site’s specific business scenario, and see if that tag can be
read properly.
Appendix H: TagFocus
TagFocus is a special Impinj extension to EPC protocol to enable longer persistence time when
Session is S1, Target is Flag A only (no toggle). This combination setting is traditionally used
to inventory a lot of tags. However, since the normal persistence time of this combination as
defined by EPC is only 2 to 5 seconds, so when this time is up, the tag will still go back to Flag
A. Therefore, depending on how many tags the reader can read during this period of 2 to 5
seconds, the inventory will be very fast up to a certain limit and then will become very slow.
For Impinj IC based tags, this TagFocus property, when invoked, will cause the tag to stay in
Flag B a much longer time, until the end of all inventory rounds. This will enable much faster
read when you need to read more than 1000 tags, for example.
Appendix I: FastID
FastID is a special Impinj extension to EPC protocol. By setting this, an inventory of Bank 1
EPC will have both Bank 1 EPC and Bank 2 TID coming back together in a simple inventory.
The PC value is automatically modified – specifically the first 5 bits that contain the encoded
EPC length. Since the added TID makes the whole return values longer, therefore this first 5
bits of PC is always made larger. The reader always captures the data based on the 5 bits of
PC, so it simply grabs a longer number. The user will then need to separate the EPC and the
TID bits – the length of which is known a priori because the TID Bank 2 length of Impinj tag
IC is known.
Appendix J: Security
There are 4 actions you can apply on the memory inside an RFID tag:
1) Lock
2) Unlock
3) Permanent Lock
4) Permanent Unlock
You can obtain an EPC Global document which can be downloaded from the EPC Global
website that explains this:
https://www.gs1.org/epcrfid/epc-rfid-uhf-air-interface-protocol/2-0-1.
Once there, press the button showing the latest air interface protocol document and click on it
to get the pdf file.
Click the
latest Air
Interface
Protocol
document
For the Access Password and Kill Password the security locking affects both reading and
writing.
For the EPC memory bank and the User memory bank, the security locking affects only
writing.
For the TID memory bank, since we are the user and not the manufacturing vendor, there is no
security action that can be applied. It has been permanently unlocked in the factory and it
cannot be changed.
There are various models, denoted by the alphanumeric key to the right of the dash after the
CSXYZ-N, here denoted by “N”. The applicable regulatory regions for each model are
described below:
N=1: 865-868 MHz for Europe ETSI, Russia, Mid-East countries – 4 channels
865-867 MHz for India – 3 channels
N=2: 902-928 MHz, FCC, for USA, Canada and Mexico. Hopping frequencies locked
N=2 AS: 920-926 MHz, Australia. Hopping frequencies locked
N=2 NZ: 921.5-928 MHz, New Zealand. Hopping frequencies locked
N=2 OFCA: 920-925 MHz, Hong Kong. Hopping frequencies locked
N=2 RW: 920-928 MHz, Rest of the World, e.g. Philippines, Brazil, Peru, Uruguay,
Bangladesh, etc.
N=4: 922-928 MHz, Taiwan
N=6: 917-920.8 MHz, South Korea
N=7: 920-925 MHz, China
N=8: 916.7-920.9 MHz, Japan
N=9: 915-921 MHz, Europe Upper Band