Reader Configuration

- TCP port: An external program can be connected to the TCP port 3177 of the reader and parse the reads and events. We have examples in Java and C# that do this. You can find them on REST API development page.
- CSV: The reader can be configured to store the reads and events in an internal CSV file, and can be retrieved via an HTTP call.

CSV files are intended for backup purposes only.

CSV file format may change after an upgrade without further notice.

- SQL: The reader can be configured to store the reads and events in a SQL database, either remote or internal. For example for MySQL.

We recommend using either the HTTP service or the TCP port as it is much faster than the CSV and SQL export.

Access to device serial number

Any device contains a unique serial number. The serial number can be accessed with

- HTTP GET request at: http://{device_ip}/devices/AdvanSafe-m-100-eu/serial
- Change AdvanSafe-m-100-eu by the ID of your device.

Serial number is found inside the tag <result>
Currently, this device serial number is based on the device MAC address.

Available starting with firmware version 2.1.0-rc2.

The device serial number available in this version does not match with the serial number printed on the device label!

Access CSV log

CSV files are intended for backup purposes only.

CSV file format may change after an upgrade without further notice.

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

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

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

- Retrieve all CSV log directory accessing the URL (HTTP GET request)

http://{device_ip}/system/fs/retrieveFile/AdvanNetCSVSDir

Alternatively, use the download link in the system tab:

In case the Export CSV logs is not available, please use the direct URL

http://{device_ip}/system/fs/retrieveFile/AdvanNetCSVSDir

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

Available starting at firmware version 2.1.0-rc2

The size of the log file could grow up to a few hundred MBytes. It is very important to clear it out from time to time to avoid long download times.

All the CSV files may contain more than 1 million lines. Depending on the CSV logrotate configuration the CSV files may contain more than 15 million lines.

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}/system/fs/removeFile/AdvanNetCSVS

To clear all the CSV log Directory:

http://{device_ip}/system/fs/removeFile/AdvanNetCSVSDir

Configure CSV columns

CSV files are intended for backup purposes only.

CSV file format may change after an upgrade without further notice.

Defining a custom CSV column may not prevent file format changes

Each row of the CSV represents an event, possible events are: read events, alarm events, etc.

It is possible to change the CSV columns.

- Request the ssh access to suport@keonn.com

- Locate the file ~/kernel/module/app.AdvanNet/META-INF/connectors.xml
- Edit the file locally or copy it into a host PC
- Locate the <CSV> configuration block and modify the <columns> line

Minimal configuration

The following are the default columns that will always be present in the CSV file

<columns>EVENT_TYPE,EVENT_DETAILS,HEX_EPC,TIME_STAMP</columns>

Possible columns are:

ID: unique ID
EVENT_TYPE: the type of the entry
EVENT_DETAILS: the sub-type of the entry
HEX_EPC: the read epc in hexadecimal format
DECODED_EPC: the decoded epc (if possible)
DEVICE_ID: the ID of the device that generated the event
- DEVICE_IP: the IP address of the device that generated the event
ANTENNA_PORT: antenna port of the read epc, if available.
- MUX_PORT: first level mux port of the read epc, if available.
- MUX_PORT2: second level antenna port of the read epc, if available.
LOCATION_X: x coordinate of the location of the read tag, if available.
- LOCATION_Y: y coordinate of the location of the read tag, if available.
- LOCATION_Z: z coordinate of the location of the read tag, if available.
- LOCATION_ID: ID coordinate of the location of the read tag, if available.
OPERATION_MODE: active operation mode of the event
RSSI: RSSI value of the read epc, if available.
- RF_PHASE: PHASE value of the read epc, if available.
- FREQ: carrier frequency value of the read epc, if available.
- READ_COUNT: read count value of the read epc, if available.
TIME_STAMP: timestamp of the event.

ID is available starting at version 2.3.14

Reduce the CSV rows

It is possible to reduce the number of CSV rows by reducing the events that are exported to CSV.

Before removing CSV events please make sure they are not meaningful events for your application.

To remove events exported in the CSV.

- Request the ssh access to suport@keonn.com

- Locate the file ~/kernel/module/app.AdvanNet/META-INF/connectors.xml
- Edit the file locally or copy it into a host PC
- Locate the <CSV> configuration block and modify the <blockedMessages> line

Default value is

<blockedMessages>DEVICE_ERROR,GPI,SENSOR,ADVANNET_INFO,ADVANNET_DEVICE_CONNECTED,TAG_DIRECTION,TAG_READ,TAG_READ_ANTENNA_1,TAG_READ_ANTENNA_2,TAG_READ_ANTENNA_3,TAG_READ_ANTENNA_4</blockedMessages>

Possibles events to be included:

- TAG_ALARM: if your application does not use this event
- TAG_ALARM_ANTENNA_1: if your application does not use this event
- TAG_ALARM_ANTENNA_2: if your application does not use this event
- TAG_ALARM_ANTENNA_3: if your application does not use this event
- TAG_ALARM_ANTENNA_4: if your application does not use this event

It also possible to remove the TAG_READ events by adding a new property to the <CSV> configuration block.

<CSV>

...

</CSV>

Editing CSV cache

Read Editing CSV cache page.

Access common log files

The system generates log files than can be accessed through the REST interface

http://{device_ip}/system/fs/retrieveFile/AdvanNetLogDir

Or at the system tab

On older AdvanNet versions the logs were access from the System tab

In case the Export system logs are not available, please use the direct URL

http://{device_ip}/system/fs/retrieveFile/AdvanNetLogDir

Access SCloud log files

The system generates log files than can be accessed through the REST interface

http://{device_ip}/system/fs/retrieveFile/SCloudLogDir

Events and Actions

GPO and Speaker action configuration

Read GPO and Speaker action configuration page.

Configuration

Configure the Power and Sensitivity

Read Configure the Power and Sensitivity page.

AdvanCloud connection

Read AdvanCloud connection page.

Start Reading on Boot

Any Keonn System can be configured to start reading on boot. Go to Read modes tab on AdvanNet and check the parameter to start on boot. After applying the configuration, persist the settings with the save button on top.

Persist settings

Any change done in AdvanNet manager is applied temporarily. The current configuration set can be persisted to save the current settings in order to use the same settings across reboots.

To persist settings use the "Save" button located top right on the screen.

As one of the settings that will be persisted is the operation mode (e.g. EPC_EAS_ALARM), make sure it is correctly selected when persisting the configuration.

Change Time settings

Read Change Time settings page.

Configure AdvanReader for alarm operation

AdvanReader devices use by default AUTONOMOUS read operation.

To use AdvanReader devices as an alarm device, the following changes must be made.

1. Configure the device to start RF operation at boot time

2. Switch the Device to Alarm mode

3. Choose Read mode, for example EPC_EAS_ALARM

4. Adjust settings as desired

5. Persist new settings with the save button on the top right

Remove PC after configuring device

To configure the device, please check Persist settings chapter.

Once the device is configured:

- Go to monitor page and press start. Verify the Status is in running state.

- Close the browser page or tab without doing any other action.

Exporting the system LED status (beat) to an external GPO line

This requires access to the main configuration file /home/keonn/kernel/module/app.AdvanNet/META-INF/connectors.xml.

Please check the embedded device development page to log into the system and modify connectors.xml file.

When you have access to that file:

- Locate the configuration block

<ADVANNET_STATUS>

<class>COMPOUND_STATUS_DIAGNOSTIC</class>

<entry>

<class>LED_STATUS_DIAGNOSTIC</class>

</entry>

<entry>

<class>BUZZER_STATUS_DIAGNOSTIC</class>

</entry>

</entries>

</diagnostics>

</ADVANNET_STATUS>

Replace it for

<ADVANNET_STATUS>

<class>COMPOUND_STATUS_DIAGNOSTIC</class>

<entry>

<class>LED_STATUS_DIAGNOSTIC</class>

</entry>

<entry>

<class>LED_STATUS_DIAGNOSTIC</class>

</entry>

<entry>

<class>BUZZER_STATUS_DIAGNOSTIC</class>

</entry>

</entries>

</diagnostics>

</ADVANNET_STATUS>

The above code will replicate the LED status to GPO number 1.

Change <ledNo>1</ledNo> to any valid GPO number.

Available filters

AD filter

Also known as False Alarm filter, it is an evolution of the deprecated Time filter. Read AD filter page.

Stray tags remover

Filter designed specifically to reduce the effect of unwanted tags that are consistently read by AdvanSafe during its normal operation.

At system start, a scan is executed of all readable tags and results are stored as stray tags. Any forthcoming operation automatically removes any stray tag. The filter will reset after the Calibrator refresh time, or after the RF is stopped or after the system rebooted.

Use cases

- It's used in stores with products very close to AdvanSafe.
- It should be used whenever products trigger the alarm just after starting the system and consistently.
- It also can be used in parallel with the AD filter (False alarm filter).

Stray tags are left unprotected. Use this filter with caution.

Monitor and diagnosis

Status page

Upon device boot up, the status page will be available. The status page will display any abnormal condition.

http://${device-ip}/status

The contents of the status response are detailed in the REST Reference Guide chapter AdvanNet information.

Possible errors in the status page are:

- Configuration errors.
- Communications errors.
- Run-time errors: problems that happen during operation
  - Too much reflected power
  - Etc.

Access AdvanNet logs

Another feature that may be of interest when tracking down an abnormal operation is the access to the low-level device logs.

Access to the device logs is detailed here: Access common log files

The full understanding of device logs should be left to Keonn Support Team.

support@keonn.com

OS logs

The lowest possible level is the access to the Operating System logs.

Once logged into the Linux board:

keonn@AdvanReader-m2-60:~# dmesg > dmesg.txt

keonn@AdvanReader-m2-60:~# $>sudo tail -f /var/log/syslog -n 2000

The full understanding of OS logs should be left to Keonn Support Team.

support@keonn.com

Remote Monitoring

Check this section on the following page.

Installation requirements

Whenever an installation is to be done, there are some previous steps in order to be ready for any problem:

Hardware:
- - 2 Ethernet Cables.
  - USB cable:
    - USB Type-A a Type-B for enclosed systems (link)
    - USB Type A Male to Mini B (link) for non-enclosed systems.
  - SD Card Class 10 with a new image of the system to install (AdvanEAS, AdvanSafe, ...)
  - Optional hardware
    - Router to provide DHCP server: link
Software:
- - Discovery software:
    - Download and install the software specified in this section.
    - Download and install the AdvancedIPScanner program.
  - USB Ethernet Gadget driver:
    - Download and install the system driver: 64bit - 32bit:
      - Windows Driver Certification warning may pop up two or three times. Click "Ignore", "Install" or "Run"
      - To check if you're running 32 or 64-bit Windows see this: http://support.microsoft.com/kb/827218.
      - On systems without the latest service release, you may get an error (0xc000007b). In that case, please install the following and retry: http://www.microsoft.com/en-us/download/confirmation.aspx?id=13523.
      - You may need to reboot Windows.
  - SSH software
    - Download PuTTy.

If a computer is connected directly to the Keonn system by the USB cable, it is possible that the network it is not configured automatically, do the following:

- Go to the Network Connections and go to the properties to the Linux USB Ethernet... by right-clicking.

- Configure it:

- Open a Web Browser and go to http://192.168.7.2

AdvanNet Updater

Read AdvanNet Updater page.

Other

From EAN to EPC

Introduction

The International Article Number (EAN) (also known as European Article Number, which technically refers to EAN-13) is a 13-digit barcode symbology, which identifies a class of products, and the Electronic Product Code (EPC) is a universal identifier for any physical object. The EPC is built from the EAN code, which allows to build an EPC from an EAN code and extract the EAN code from an EPC.

Several EPCs can refer to a single EAN code. For example, if in a store there are 10 black sweaters, there will be a unique EAN code to refer to the black sweater type and a unique EPC for each black sweater.

This process is very easily done through the GS1 website:

GS1 Key or other identifiers:

Select the option (section 1) GTIN + serial (AI 01 + AI 21) and introduce the EAN number (section 2), the GTIN has to be 14 digits long, so if the EAN has only 13 digits, add a 0 at the beginning. After this, introduce a serial number (section 3) which will be unique for each product.

GS1 Company Prefix Length:

It depends on the company, the normal length is 7 digits.

RFID Control Information:

There is only two possible tag size: 96 bits and 128 bits, the normal size used is 96 bits. The last part is the filter value, normally set to 1 - POS item.

After this process, there will be as much EPC numbers as different serial numbers were used:

Check hardware and software version

In AdvanNet Manager (Web application), go to Dashboard tab

Using a DHCP device in a non DHCP-enabled network

Series 160 & 60 devices are by default configured with DHCP.

In case the network used to connect your PC to the device is not DHCP-enabled, for example:

- Device wired directly from PC with a cable.
- Device wired through a switch/hub without any present router.

It is possible to provide an IP address to the device by following the simple steps:

- Download into your PC the free utility: DHCP server
- Start utility
- Power on devices: the utility will show an informative balloon with the assigned IP address (this may take around 30 seconds)

Check NTP connection

Keonn Systems get date and time information through a service called NTP (Network Time Protocol), which sometimes it is blocked. If the NTP service is blocked, the Keonn System date will be the date when it was built and will not get updated.

NTP uses UDP protocol at port 123.

Please make sure your network infrastructure does not block such communications.

To check if the NTP service is blocked, follow the next steps using a computer with Windows 7 or older in the same network as the Keonn System.

Requirements

Install the NTP service: https://www.meinbergglobal.com/english/sw/ntp.htm#ntp_stable.
Install the NTP Time Server Monitor: https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm.

Configuration

Execute the NTP Time Server Monitor with Administration rights.
- Go to the tab "NTP Configuration file" and add the following:

# Use specific NTP servers
server 0.debian.pool.ntp.org
server 1.debian.pool.ntp.org
server 2.debian.pool.ntp.org
server 3.debian.pool.ntp.org

- Save the configuration.

Run NTP service

- Go to the tab "NTP Service" and click on the "Start NTP service" button:

NTP Status

If the NTP service is blocked, the NTP status tab will look like the following:

If the NTP service is not blocked, the NTP status tab will look like the following:

SSH Credentials

To acquire the credentials to enter into the Linux Board on the series 160/60 Keonn devices follow these steps:

Device Information

Try to log in the Keonn device by SSH using PuTTy or other and send the information presented to Keonn Support Team (support@keonn.com):

Follow the steps of the discover devices chapter to find the IP address of the device and introduce it, set the port to 22 and click on the Open button.

- Click Yes

- Write keonn and click Enter:

- The following information will be presented to you:

In some systems the information presented may be different from the above.

All readers and systems are changing the static defined passwords by a security infrastructure with unique passwords per device. Passwords are generated automatically and the Password challenge is used to derive the real device password.

Email to Keonn Support

With the information acquired in the last step send an email to Keonn Support Team following this template:

Subject: [Disclaimer Agreement] Keonn Device Information

Dear Keonn Support,

The following is the information presented to me when accessing by SSH:

############################################################################

# KEONN TECHNOLOGIES SL #

# All connections may be monitored and recorded #

# Disconnect IMMEDIATELY if you are not an authorized user! #

############################################################################

Keonn Technologies SL http://www.keonn.com

http://www.keonn.com

Debian GNU/Linux 7.8 (2015-01-27)

Default username and password is [keonn:*****]

In order to request the keonn user password, please provide the MAC address

and password challenge to support@keonn.com

MAC address

7c:66:9d:55:92:14

Password challenge

BezA2BtFI+tS0qgyueYwwvbgHsEQDBbQ2i7VZcvQOtr8uNU9MujSwkYj1AiSSXLQDondD/biMVZ4

JSnniI/OoTIZK6F69SOgSctMxu6rrsK7ZiFHCeyDmWA94M5kmjJpr6W61gwpPhNM1b9mEMC1zPnd

sPXaOBbWzFCk+Bb6NWfTGl7yIr2R5g1kpMjqBeoEkmXRK3MxS1MkyPUAAwrrsFLdyIvcoQmfQWAV

wE3d9JTtUfe/wvpJaLzkk0W3neM5Pb5BUd9KUzAZSf4OIyC6DyU7upPe2HR4koQ2gg7hpA4GA3vW

R/p1ZrhM+S9huQdRxH3b+xOxs2NWLE3hZo13s/NJqF3C/+Ls2CU+21pW7k02zSWZVJK8CWB2v4Dy

7csVcLGCRcU1Dm9ji9uEbGd3zpkDt2r6dqYRSFdKDbE8GhhFeWuU2h+Y9ONDFYSfja5Kf5Z7RH8l

4xsepjysmI7+E8MMi5wjxvADQ3CWbUdLPFbb+rvrxoM7PBnvLFDUM471sUAvih2qdXk2Lfyv41+P

Sf82XubkD09qKmS+1U5dxnoamEA+XVb7XTHBsOrYWLl6K0l4B7ohu3jTWWUySxTo6zlEQC2/8syf

nAmTZnzhbuPr4+cvWOxtNTVNzLteFl/+X6e0XSESLSW15OIip4VLEEMvzSqo2FDa7A0ffU5pqCEG

UV+5Gko7nNP8yUUbq4IOkstno6S+STV2Hhutie1Fq453IZoAWADJ93FArDsSwCgzm5ovED9sczeb

jzk/PNnmte+uhyfmH4BgFVkNTdazl85BSxDfyDQSKqCs4WWjKd7iLGNk02JdQKX81+9W4xxKdWFj

ZxnWfEt431dwQC7n08Ww+wVlltbG6bA67OjqO/UatxcEWpzXSHxCO0m0VbwUjSdQEAe1MITPpuSW

CriZkl5gnNuvvWsxWQNtpyMkCN0oh0pLAcJP/aLcA/4ZTcOx5o6o7Lxy7DyVPj7iyMkMNtz8kC6O

ovnBuYTKoQm+LL4Hrjpc8/th5H0fDRj+LEeLML9++KUc4CLAXViB+9P2nulFOTjdikjPDJxXEUyJ

3tsJXg3g7/hz8u802ajLb6P5e6ai1Yvl2zgUsWvLglmtohmRFS9rSqqY7PR2ZSa9LWgEh+ML9WyA

nR6tHyKnMCgK0GiglcxSxZ9Nq+Zfk+L7pPGk60+MVHc0ay+JEuVd+GrLmmBnWRHD51q9JUOln2/+

KhxX9Qk+0X3YU4Rvzn6wShdqNC71RinAXtbzJb31d0hvVCm7X7KzTp5robQm8se9jC1x9MX8OrcM

97zlGCpvfjKa65fLyfHcZi4acx4EtGqsuMF/hwbEYUaw1P9a6MmuugxWLfJNupjZ39ptiY3n4Xc=

If keonn user password is lost, it can be cleared by login into the system as

the user reset (password reset)

Keonn Technologies SL http://www.keonn.com

http://www.keonn.com

keonn@192.168.1.161's password:

Regards,

Client.

Our support team will get back with the credentials to enter as Keonn user.

Send the Password challenge in text format.

In case putty is used:

- Select text
- Right-click to copy
- Paste text into email or text file

Download Files

Page updated

Report abuse