AdvanGo-100
Introduction
AdvanGo is an RFID-based modular solution that identifies faster and with higher reliability all the products a customer wants to buy.
As a result, the payment process it’s accelerated, reducing queues, which improves the customer shopping experience and increases sales.
This system has a special on-board software for confining the reading area, which avoids reading unwanted RFID tags.
It reads the EPC codes of the products being purchased and filtering the results for easy processing by the POS software.
AdvanGo can be used together with AdvanSafe, AdvanMat or AdvanGate to provide a complete loss prevention system fully based on RFID UHF.
It can be used for different types of self checkout:
Wall mount
Desktop
Bag well
Basket
AdvanGo comprises:
High power RFID reader
Antennas
RF cables
Power supply
Specific on-board software
AdvanCloud platform (optional)
Getting Started
These are the minimum steps to start using AdvanGo:
Power AdvanGo unit
AdvanGo can be powered either by PoE or a 24 V(DC) power supply
AdvanGo connection with a PoE switch
AdvanGo connection with PoE injector
AdvanGo connection using a 24 V(DC) Power Supply
Connecting to AdvanGo
AdvanGo supports three different connection interfaces:
TCP/IP
TCP/IP over USB
Serial over USB
TCP/IP
The Ethernet interface can be set to static or dynamic (DHCP). DHCP is the default option
TCP/IP over USB
Is it possible to create an ad-hoc point-to-point Ethernet network by using the USB-B connection of the ADRD160, or USB-MicroB of ADRD70
This interface only has one static IP: 192.168.7.2
Follow the instructions here to configure the Host PC to use this interface
Serial over USB
In case you need a Serial point-to-point connection please contact support@keonn.com
Configuration
Almost on any installation, it is required to adjust the AdvanGo operation.
Discover Device
TCP/IP
Configuration requires Ethernet access to the unit, as it uses a web application.
We need therefore to connect the AdvanGo 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 AdvanGo IP address, use a PC in the same network as the computer.
Please see the discover devices for the 150/60 Series devices: series150/60-Discover-devices.
TCP/IP over USB
Check the USB connection page
Enter AdvanNet Manager
The previous step will result in the IP that is assigned to the device. Let's named it <AdvanGo-IP-address>
Use a computer in the same network as the AdvanGo.
Open a Web Browser (Chrome or Firefox are required).
Go to the page: http://<AdvanGo-IP-address>
Replace the <AdvanGo-IP-address> for the IP found in the discover devices.
You will see the AdvanNet GUI:
Monitor
An easy way to check if the system is reading is by using the Monitor menu
Be careful as in the monitor page you just see tags read recently.
In AdvanGo operation it is normal to read some percentage of tags only when they are moving in into the well.
Advanced configuration
Power and Sensitivity
The power and sensitivity of the AdvanGo its already being set for the best performance but in the RF & Antenna Options tab the sensitivity can be configured for more suitable performance. For more information about it look at this post: What-is-the-difference-between-Power-and-Sensitivity. Remember that if you're using the AdvanGo API is better to configuring the Power using the API.
System features
USB Keyboard Wedge
AdvanGo can be connected directly to a POS PC and act as a keyboard.
Follow the steps:
Identify in the RFID reader the USB HID connector, it is a USB-B type connector.
Enable and configure the USB-HID-Service
Open a text editor (Notepad, Gedit, ...) in the PC where AdvanGo is connected to:
Make sure AdvanGo operation is started
Put one or more tags into AdvanGo:
The EPC or decoded GTIN will be printed on the active PC window.
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 a compressed file named
AdvanNetCSVS.zip
The CSV file structure is self-explanatory. It contains events of the following type:
TAG_READ: a read event of a tag
TAG_ADDED: a read that has to be considered for a payment operation
TAG_WRITE: a tag write event. Tag write events may be a side-effect of the AdvanGo operation.
The timestamp in the CSV files is expressed in UTC
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 a message:
ADVANNET/1.1
Content-Length:452
Content-Type:text/xml
<?xml version="1.0" encoding="UTF-8"?>
<deviceEventMessage>
<type>deviceEventMessage</type>
<ts>1478216232082</ts>
<status>OK</status>
<event>
<type>TAG_ALARM</type>
<deviceId>AdvanPay-cf-us-120</deviceId>
<alarmType>TAG_ADDED</alarmType>
<epcs>303602c25c09bbe003deb652</epcs>
<sku>08433815099679</sku>
<readerPort>1</readerPort>
<mux1>0</mux1>
<mux2>0</mux2>
</event>
<deviceId>AdvanPay-cf-us-120</deviceId>
</deviceEventMessage>
Important features:
Header always contains
ADVANNET/1.0: protocol version
Content-Length: length of the message
Content-Type: type of 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>1445500793000</ts>
<status>OK</status>
<msg-version>2.3.0</msg-version>
<op>inventory</op>
<data>
<advanNetId>AdvanNet-instance-78:a5:04:ed:a8:f2--1</advanNetId>
<deviceId>AdvanPay-cf-us-120</deviceId>
<inventory>
<class>INVENTORY</class>
<deviceId>AdvanPay-cf-us-120</deviceId>
<size>1</size>
<timeWindow>-1</timeWindow>
<items>
<item>
<class>READ_EVENT</class>
<epc>30360000a1360008889d3604</epc>
<ts>1445500793789</ts>
<deviceId>AdvanPay-cf-us-120</deviceId>
<data>
<class>TAG_DATA</class>
<hexepc>30360000a1360008889d3604</hexepc>
<opMode>AdvanPay-cf-us-120.AdvanPay.ADVANPAY_PAYMENT</opMode>
<props>
<prop>TIME_STAMP:1445500793789</prop>
<prop>RF_PHASE:0</prop>
<prop>FREQ:866829</prop>
<prop>READ_COUNT:1</prop>
<prop>RSSI:-50</prop>
<prop>ANTENNA_PORT:1</prop>
</props>
</data>
<locationData>
<class>LOCATED_TAG_DATA</class>
<epc>30360000a1360008889d3604</epc>
<antenna>
<class>ANTENNA_DEFINITION</class>
<def>AdvanPay-cf-us-120,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>
TAG_ADDED
ADVANNET/1.1
Content-Length:452
Content-Type:text/xml
<?xml version="1.0" encoding="UTF-8"?>
<deviceEventMessage>
<type>deviceEventMessage</type>
<ts>1478216232082</ts>
<status>OK</status>
<event>
<type>TAG_ALARM</type>
<deviceId>AdvanPay-cf-us-120</deviceId>
<alarmType>TAG_ADDED</alarmType>
<epcs>303602c25c09bbe003deb652</epcs>
<sku>08433815099679</sku>
<readerPort>1</readerPort>
<mux1>0</mux1>
<mux2>0</mux2>
</event>
<deviceId>AdvanPay-cf-us-120</deviceId>
</deviceEventMessage>
DEVICE_ERROR
A common error found when the configured password do not match the tag password:
<?xml version="1.0" encoding="UTF-8"?>
<deviceEventMessage>
<type>deviceEventMessage</type>
<ts>1445499839780</ts>
<status>ERROR</status>
<event>
<class>DEV_ERROR_EVENT</class>
<type>DEVICE_ERROR</type>
<typeclass>com.keonn.spec.event.DeviceEvent$EventType</typeclass>
<advanNetId>AdvanNet-instance-78:a5:04:ed:a8:f2--1</advanNetId>
<deviceId>AdvanPay-cf-us-120</deviceId>
<errors>
<error>
<code>25</code>
<humanCode>Error[0000040a] Changing EPC pattern in 30360000a1360033331d3604. Error msg: Password seems wrong.</humanCode>
<ts>1445499839774</ts>
</error>
</errors>
</event>
<deviceId>AdvanPay-cf-us-120</deviceId>
</deviceEventMessage>
A common error found when the write operation fails. Usual conditions are:
The tag does not stay the required time for the write operation
The write power is not high enough
<?xml version="1.0" encoding="UTF-8"?>
<deviceEventMessage>
<type>deviceEventMessage</type>
<ts>1445499840685</ts>
<status>ERROR</status>
<event>
<class>DEV_ERROR_EVENT</class>
<type>DEVICE_ERROR</type>
<typeclass>com.keonn.spec.event.DeviceEvent$EventType</typeclass>
<advanNetId>AdvanNet-instance-78:a5:04:ed:a8:f2--1</advanNetId>
<deviceId>AdvanPay-cf-us-120</deviceId>
<errors>
<error>
<code>25</code>
<humanCode>Error[00000400] Changing EPC pattern in 30360000a1360033331d3604. Error msg: No tags found.</humanCode>
<ts>1445499840683</ts>
</error>
</errors>
</event>
<deviceId>AdvanPay-cf-us-120</deviceId>
</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>AdvanPay-cf-us-120</deviceId>
<msg>Device[AdvanPay-cf-us-120] 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>AdvanPay-cf-us-120</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>AdvanPay-cf-us-120</deviceId>
</event>
</eventMessage>
Also several error messages can be received.
Reset settings to default
It is possible to reset the system to factory defaults. That means:
Any network settings are removed and the system is reverted to use DHCP
Any persisted operation settings (AdvanNet settings) are removed
The procedure is as follows:
Identify the Reset button in the RFID reader
Power the system and waits to hear the start-up beep.
Use a paper clip or similar to press the Reset button for at least 12 seconds.
The reset process will start when the reset button is released.
The system will be restarted.
Wait for the start-up beep.
How to alter the system Hardware
Changing the reader: check out pdf in the Downloads section down below.
Accessing the antennas: Video
Integration
We have a dedicated page on how to integrate our AdvanGo system with your POS system here:
Latest Firmware
You can always download and install the latest Firmware from here
https://wiki.keonn.com/rfid-components/reader-upgrade/update-advannet-procedure
Downloads
Find the User Guide and other downloadable content below: