AdvanReader-150

Introduction

AdvanReader-150.03 is a 2-port or 4-port, high power, high-performance UHF reader specially designed for embedded applications.

AdvanReader-150 features:

• • on-board Linux computer: you can program your own software routines, saving the need and cost of an external computer

  • works with batteries, for stand-alone applications: includes a mode of minimum consumption (sleep mode), increasing battery life. It monitors the battery level.

  • 4-port or 2-port

  • high power, high sensitivity

  • controls up to 1024 antennas, with Keonn multiplexers

  • controls electronically the beam orientation of directive antennas, with AdvanPhaser

  • direct connection to an external loudspeaker for alarm applications

  • 2 digital/analog inputs

  • 8 digital outputs

  • Powers up external devices: non-isolated power output: 5 V, 200 mA (DC)

  • Powered through PoE, power supply of 12 V (DC), or batteries

  • Communications interface: Ethernet, optional WiFi

  • software drivers with advanced functions for monitoring and control

AdvanReader-150 benefits:

• • saves the cost of an external computer

  • fully open Linux operating system

  • ideal for stand-alone systems

  • high-performance: high output power and high sensitivity

  • reduces time and cost of developing RFID systems. Ideal for embedding it inside RFID systems

  • can become your own reader, if you put your company logo on the enclosure.

Getting Started

Helpful downloads:

• Download Datasheet (see download files section)

• Download User Manual (see download files section)

Steps

These are the minimum steps to start using AdvanReader-150:

Connect antenna

Connect an antenna to AdvanReader port 1 with an RF Cable.

Power AdvanReader unit

Using a PoE injector

Follow this diagram to connect AdvanReader-150 through a PoE injector, Switch PoE, PoE injector, +24 V supply, etc. and wait until it beeps. It will take between 40 and 50 seconds to boot.

Configuration

Almost on any installation, it is required to adjust AdvanReader operation.

Discover Device

Configuration requires Ethernet access to the unit, as it uses a web application.

We need therefore to connect the AdvanReader unit to an Ethernet network and execute an IP discovery process. After the configuration process is finished, the Ethernet cable can be removed.

To be able to discover the AdvanReader IP address, use a PC on the same network as the computer.

Please see the discover devices for the 150/60 Series devices: series150/60-Discover-devices.

Enter AdvanNet Manager

The previous step will result in the IP that is assigned to the device. Let's named it <AdvanReader-IP-address>

1. Use a computer in the same network as the AdvanReader.

2. Open a Web Browser (Chrome or Firefox are required).

3. Go to the page: http://<AdvanReader-IP-address>:3161

4. Replace the <AdvanReader-IP-address> for the IP found in the discover devices.

5. Enter with the following credentials:

• User: admin

• Password: admin

Read modes

AdvanReader has 3 different Configurations: Autonomous, Sequential, and Alarm mode.

A configuration can have different read modes:

• 1. Autonomous configuration:

     1. AUTONOMOUS: In this read mode the RF engine schedules the antenna switching automatically amongst the available RF ports (1, 2, 3 or 4).

  2. Sequential configuration:

• • 1. SEQUENTIAL: In this read mode the RF engine waits for read commands.

    2. DYNAMIC_INVENTORY: See Dynamic Inventory Wiki page

• 3. Alarm mode configuration:

• • 1. EPC_EAS_ALARM: The alarm recognizes EPC patterns to trigger appropriate events. This is the default read mode.

    2. EPC_EAS_DISABLE: Disables the alarm pattern on each found tag.

    3. EPC_EAS_ENABLE: Enables the alarm pattern on each found tag.

    4. NXP_EAS_ALARM: The alarm recognizes the NXP EAS bit to trigger appropriate events.

    5. NXP_EAS_DISABLE: Disables the NXP EAS bit on any found tag.

    6. NXP_EAS_ENABLE: Enables the NXP EAS bit on any found tag.

    7. SQL_EAS_ALARM: EAS mode that uses an SQL database.

    8. EPCBULK_EAS_ALARM: EAS mode that triggers the alarms when several tags are read at the same time.

Persist Configuration

Using the apply button only changes the runtime settings, in order to make those changes persistent follow the steps below:

• Remember to apply the configuration.

• Click the persist button (surrounded in red) to persist the configuration.

• In this case, the AdvanReader will start with AUTONOMOUS configuration.

Monitor tab

Go to the monitor tab and press the start button. The result will be like the following:

Advanced Configuration

Power and Sensitivity

The power and sensitivity of the AdvanReader its already being set for the best performance but in the RF & Antenna Options tab can be configured for a more suitable performance. For more information about it look at this post What-is-the-difference-between-Power-and-Sensitivity.

Antenna Configuration

Each antenna has its own configuration:

• • Reader port: The port where the antenna is connected. This is the only required parameter.

  • Mux1 port: The multiplexor port where the antenna is connected. Set it to 0 if there is not mux at level 1

  • Mux2 port: The multiplexor port where the antenna is connected. Set it to 0 if there is not mux at level 1

  • Position: Static position for the antenna (x, y, z). Can be left with default values.

  • Location: String definition for the antenna. Can be left with default values.

  • Power: The power for the antenna (If empty it will use the Read Power in the general RF settings chapter (Power and Sensitivity)).

  • Sensitivity: The sensitivity for the antenna (If empty it will use the Sensitivity in the general RF settings chapter (Power and Sensitivity)).

Events & Actions

You can configure which actions will be trigger in the available events. For example, the most used event is:

• TAG_READ: This event is created when AdvanReader reads an EPC and, in this case, it will trigger an Speaker action.

• • TAG_READ_ANTENNA_1: This event is created when the antenna 1 of AdvanReader reads an EPC and, in this case, it will trigger a GPO action.

Change device IP

To change the IP visit Change device IP.

Features

Common Series 150 and 60 Series

Check out Series 160 and 70 page

REST API development

See REST API development page.

Access CSV log

All system activity is logged into a CSV file. This file can be accessed at any time:

• • Retrieve CSV log file accessing the URL (HTTP GET request)

http://{device_ip}:3161/system/fs/retrieveFile/AdvanNetCSVS

• • The CSV file is retrieved as an uncompress file named advansafe-100-tags.csv

• • The CSV file structure is self-explanatory. it contains events of the following type

  • TAG_READ: a read event of a tag

  • TAG_ALARM: an alarm has been detected. The ALARM event also specifies the type of alarm:

    • NXP_EAS: alarm due to NXP EAS bit.

    • EPC_EAS: alarm due to EPC pattern.

    • EPCBULK:_EAS: alarm due to bulk EPC read.

    • TAG_ALARM_ANTENNA_1

    • TAG_ALARM_ANTENNA_2

    • TAG_ALARM_ANTENNA_3

    • TAG_ALARM_ANTENNA_4

Clear CSV log

To clear the internal CSV log file, access the URL (HTTP GET request)

http://{device_ip}:3161/system/fs/removeFile/AdvanNetCSVS

Access real-time data

All system activity can be accessed at real-time by listening at TCP socket port 3177.

The protocol used is very similar to HTTP and the message format is xml. The following is a sample of message:

ADVANNET/1.0

Content-Length:488

Content-Type:text/xml

<?xml version="1.0" encoding="UTF-8"?>

<deviceEventMessage>

<type>deviceEventMessage</type>

<ts>1398285581922</ts>

<status>OK</status>

<event>

<class>com.keonn.device.impl.DefaultTagAlarmEvent</class>

<type>TAG_ALARM</type>

<typeclass>com.keonn.spec.event.DeviceEvent$EventType</typeclass>

<deviceId>AdvanSafe-m-100-eu</deviceId>

<epcs>3008029b5379cb0000000021</epcs>

<alarmType>EPC_EAS</alarmType>

</event>

<deviceId>AdvanSafe-m-100-eu</deviceId>

</deviceEventMessage>

Important characteristics:

• Header always contains

  • ADVANNET/1.0: protocol version

  • Content-Length: length of the message

  • Content-Type: type of the message

• There is an empty line between the headers and the start of the message.

• Line separators are CRLF characters: this applies to header lines and the empty line between headers and content. The content itself (in case of txt or xml type) may contain any form of line separator.

TAG messages

Possible TAG events that will be received are:

• INVENTORY

<?xml version="1.0" encoding="UTF-8"?>

<inventory>

<type>inventory</type>

<ts>1424762478000</ts>

<status>OK</status>

<msg-version>2.1.0beta</msg-version>

<op>inventory</op>

<data>

<advanNetId>AdvanNet-instance-d0:5f:b8:ff:0b:c9--1</advanNetId>

<deviceId>AdvanReader-m4-150</deviceId>

<inventory>

<class>INVENTORY</class>

<deviceId>AdvanReader-m4-150</deviceId>

<size>1</size>

<items>

<item>

<class>READ_EVENT</class>

<epc>3030029b5379cb0000000126</epc>

<ts>1424762477480</ts>

<deviceId>AdvanReader-m4-150</deviceId>

<data>

<class>TAG_DATA</class>

<hexepc>3030029b5379cb0000000126</hexepc>

<tid>2000348f7c14</tid>

<props>

<props>

<prop>TIME_STAMP:1490526372216</prop>

<prop>RSSI:-32</prop>

<prop>RF_PHASE:87</prop>

<prop>ANTENNA_PORT:1</prop>

<prop>MUX1:0</prop>

<prop>MUX2:0</prop>

<prop>FREQ:866829</prop>

<prop>GPI:[1,0,1,1]</prop>

</props>

</data>

<locationData>

<class>LOCATED_TAG_DATA</class>

<epc>3030029b5379cb0000000126</epc>

<antenna>

<class>ANTENNA_DEFINITION</class>

<def>AdvanReader-m4-150,1,0,0,0,antenna1,1,0,0</def>

</antenna>

<location>

<class>LOCATION_DEFINITION</class>

<loc>antenna1,1,0,0</loc>

</location>

</locationData>

</item>

...

</items>

</inventory>

</data>

</inventory>

<locationData> is optional and will only appear under certain system configuration

• TAG_ALARM

<?xml version="1.0" encoding="UTF-8"?>

<deviceEventMessage>

<type>deviceEventMessage</type>

<ts>1398285445702</ts>

<status>OK</status>

<event>

<class>com.keonn.device.impl.DefaultTagAlarmEvent</class>

<type>TAG_ALARM</type>

<typeclass>com.keonn.spec.event.DeviceEvent$EventType</typeclass>

<deviceId>AdvanSafe-m-100-eu</deviceId>

<epcs>3008029b5379cb0000000021</epcs>

<alarmType>EPC_EAS</alarmType>

</event>

<deviceId>AdvanSafe-m-100-eu</deviceId>

</deviceEventMessage>

• TAG_ALARM_ANTENNA_1

<?xml version="1.0" encoding="UTF-8"?>

<deviceEventMessage>

<type>deviceEventMessage</type>

<ts>1398285445702</ts>

<status>OK</status>

<event>

<class>com.keonn.device.impl.DefaultTagAlarmEvent</class>

<type>TAG_ALARM_ANTENNA_1</type>

<typeclass>com.keonn.spec.event.DeviceEvent$EventType</typeclass>

<deviceId>AdvanSafe-m-100-eu</deviceId>

<epcs>3008029b5379cb0000000021</epcs>

<alarmType>EPC_EAS</alarmType>

</event>

<deviceId>AdvanSafe-m-100-eu</deviceId>

</deviceEventMessage>

• TAG_ALARM_ANTENNA_2

See TAG_ALARM_ANTENNA_1

• TAG_ALARM_ANTENNA_3

See TAG_ALARM_ANTENNA_1

• TAG_ALARM_ANTENNA_4

See TAG_ALARM_ANTENNA_1

• TAG_ALARM_DISABLED

<?xml version="1.0" encoding="UTF-8"?>

<deviceEventMessage>

<type>deviceEventMessage</type>

<ts>1424762478112</ts>

<status>OK</status>

<event>

<class>com.keonn.device.impl.DefaultTagAlarmEvent</class>

<type>TAG_ALARM_DISABLED</type>

<typeclass>com.keonn.spec.event.DeviceEvent$EventType</typeclass>

<deviceId>AdvanReader-m4-150</deviceId>

<epcs>3030029b5379cb0000000126</epcs>

<alarmType>EPC_EAS</alarmType>

</event>

<deviceId>AdvanReader-m4-150</deviceId>

</deviceEventMessage>

• TAG_ALARM_ENABLED

<?xml version="1.0" encoding="UTF-8"?>

<deviceEventMessage>

<type>deviceEventMessage</type>

<ts>1424762478112</ts>

<status>OK</status>

<event>

<class>com.keonn.device.impl.DefaultTagAlarmEvent</class>

<type>TAG_ALARM_ENABLED</type>

<typeclass>com.keonn.spec.event.DeviceEvent$EventType</typeclass>

<deviceId>AdvanReader-m4-150</deviceId>

<epcs>3030029b5379cb0000000126</epcs>

<alarmType>EPC_EAS</alarmType>

</event>

<deviceId>AdvanReader-m4-150</deviceId>

</deviceEventMessage>

• GPI

<?xml version="1.0" encoding="UTF-8"?>

<deviceEventMessage>

<type>deviceEventMessage</type>

<ts>1490526372159</ts>

<status>OK</status>

<deviceId>AdvanReader-m4-150</deviceId>

<event>

<type>GPI</type>

<deviceId>AdvanReader-m4-150</deviceId>

<line>1</line>

<lowToHigh>true</lowToHigh>

</event>

</deviceEventMessage>

SYSTEM messages

Possible SYSTEM events that will be received are:

• • ADVANNET_INFO

<?xml version="1.0" encoding="UTF-8"?>

<eventMessage>

<type>eventMessage</type>

<ts>1409827170979</ts>

<status>OK</status>

<event>

<class>com.keonn.advannet.impl.event.DefaultAdvanNetEvent</class>

<type>ADVANNET_INFO</type>

<typeclass>com.keonn.spec.event.AdvanNetEvent$AdvanNetEventType</typeclass>

<advanNetId>AdvanNet-instance-00:1e:8c:25:0c:43--1</advanNetId>

<deviceId>adrd-m4-100</deviceId>

<msg>Device[adrd-m4-100] started in mode: EPC_EAS_ALARM</msg>

</event>

</eventMessage>

• • ADVANNET_DEVICE_CONNECTED

<?xml version="1.0" encoding="UTF-8"?>

<eventMessage>

<type>eventMessage</type>

<ts>1398285635331</ts>

<status>OK</status>

<event>

<class>com.keonn.advannet.impl.event.DefaultAdvanNetEvent</class>

<type>ADVANNET_DEVICE_CONNECTED</type>

<typeclass>com.keonn.spec.event.AdvanNetEvent$AdvanNetEventType</typeclass>

<advanNetId>AdvanNet-instance-7c:66:9d:55:60:df--1</advanNetId>

<deviceId>AdvanSafe-m-100-eu</deviceId>

</event>

</eventMessage>

• • ADVANNET_DEVICE_DISCONNECTED

<?xml version="1.0" encoding="UTF-8"?>

<eventMessage>

<type>eventMessage</type>

<ts>1398285635331</ts>

<status>OK</status>

<event>

<class>com.keonn.advannet.impl.event.DefaultAdvanNetEvent</class>

<type>ADVANNET_DEVICE_DISCONNECTED</type>

<typeclass>com.keonn.spec.event.AdvanNetEvent$AdvanNetEventType</typeclass>

<advanNetId>AdvanNet-instance-7c:66:9d:55:60:df--1</advanNetId>

<deviceId>AdvanSafe-m-100-eu</deviceId>

</event>

</eventMessage>

• • Also several error messages can be received.

Battery operation

AdvanReader-m-150.03 can be operated with a battery in the range of 12 to 24 V.

Battery voltage level can be checked at AdvanNet Manager

Battery voltage level can also be queried by using the REST API

Battery level or remaining charge

From battery voltage it is possible to derive the battery level or remaining battery charge.

Every battery has a characteristic discharge curve that can be used to derive such value.

For example, the following is the curve for one NiCd cell

Battery deep discharge

Some battery may suffer damage from deep discharges, battery life may be reduced or battery may become completely unusable.

Customization

AdvanNet Manager

AdvanNet Manager is the web application used to configure and test AdvanReader and AdvanReader derived system.

AdvanNet Manager is a web application written entirely using HTML and Javascript, some parts of it can be customized easily.

Follow the steps above to customize the look & and feel of it:

• • As the customization requires access to the internal Linux machine, please request root password as stated in 150 Series Embedded Development

• • Log into the Linux machine

  • Stop the AdvanNet process: >sudo killall java

  • Locate the web application file:

/home/keonn/kernel/module/app.AdvanNet/lib/AdvanNetRest.war

• • Customize the contents of the application as defined in AdvanNet Manager UI customization. (just follow the steps 2 to 4 -both included-)

  • Remove the web application cache

sudo rm -rf /home/keonn/tmp/*

• Restart AdvanNet Manager

sudo /etc/init.d/keonn-startup.sh start

Embedded development

See the embedded development page.

Frequently asked questions

IP protection

As a general purpose embedded reader, the AdvanReader-150.3 is used in completely different environments: from indoors to harsh environments. That's why the reader does not provide any IP rating and the protection must be implemented for each specific use.

Available SDK

The AdvanReader-150.03 can be used from the following APIs:

• • AdvanNet API: Keonn common product API.

  • Mercury Java API: modified version of the ThingMagic Mercury API. The modifications allow using the IO functionality of the reader.

Date/Time management

The reader 150.03 does not have an internal battery to hold the Date and Time settings across system reboots.

With Internet access

Whenever the reader has Internet access

• It uses NTP to update its internal time after each reboot and periodically.

• The Date/Time can also be changed by using the AdvanNet Manager (Web GUI). Once the Date/Time has been changed the NTP stops updating the system Date/Time.

• The Date/Time can also be updated programmatically using the REST API.

Without Internet access

• • The system Date/Time is reset after a reboot.

  • It is required to use AdvanNet Manager or the API to update the Date/Time.

In order to change the Date and Time settings from the GUI, please follow the steps on the Change Date and Time [...] section

Time zone management

The Time zone is persisted across reboots.

• The TimeZone can be changed by using the AdvanNet Manager (Web GUI)

• The TimeZone can also be updated programmatically using the REST API.

IO features

The AdvanReader-150.03 features the following IO capabilities:

• • 1 x speaker output (2 Watt)

  • 1 x LED on line

  • 1 x Ethernet link line

  • 1 x Ethernet activity line

  • 1 x +5 V OUT line

  • 4 x digital GPO lines: 5 V and 100 mA

  • 4 x digital GPO lines: 5 V and 8 mA

  • 2 x digital/analogue GPI lines:

    • range: 0 V - 3 V

    • range: 0 V - 10 V

What is the maximum sensitivity?

In AdvanReader-m4-150.03 the real maximum sensitivity is around -78 dBm to -80 dBm.

In AdvanReader-m2-150.03 the real maximum sensitivity is around -75 dBm to -77 dBm.

Is AdvanReader-150 reading power limited by POE or power supply?

No, AdvanReader-150 can read up to 31.5 dBm, regardless of whether it is powered by POE or power supply.

Is AdvanReader-150 compatible with a Bluetooth adapter?

Yes, AdvanReader-150 is compatible with Bluetooth adapters for Linux operating systems

What is the maximum SD card size supported by AdvanReader-150?

AdvanReader-150 supports SDXC, so the maximum size will be 2 TB.

Can the reader be connected to a 12 V (DC) battery?

Yes, the reader 24 V IN connector supports from 11 V to 24 V (DC).

When using a battery assisted vehicle, you should ideally:

• • Limit the amount of current: 2 A @ 12 V and 1 A @ 24 V

  • Add an external regulator to remove any voltage peek. This is just 'nice to have' feature, as the reader itself uses a voltage regulator.

What is the maximum speaker cable distance?

AdvanReader uses 8-ohm speaker as they are more robust to cable losses. The speaker will continue working normally with cables up to 20 meters.

Latest Firmware

You can always download and install the latest Firmware from here

https://wiki.keonn.com/rfid-components/reader-upgrade/update-advannet-procedure

Download files

Find the User Guide and other downloadable content below.