AdvanSafe-300

Introduction

AdvanSafe-300 is the new overhead anti-theft / loss prevention system based on RFID UHF. It comprises an antenna with an embedded reader, controller and alarm combining EAS and RFID functions in one system.

AdvanSafe-300 detects the tagged items that pass below the antenna, verify if those items have been paid, and sounds an alarm if any item has not been paid.

AdvanSafe-300 may comprises up to a primary unit and one secondary unit:

• The primary unit has an integrated reader, a controller, an alarm, a visual alarm indicator and one directive antenna.

• The secondary unit comprises one directive antenna and a visual alarm indicator.

By using AdvanSafe-300 it is no longer necessary to install two technologies for using EAS and RFID functions in one single shop.

Business benefits of AdvanSafe :

• Combination of EAS and RFID in one system, which reduces labeling costs

• Improved store aesthetics, by having an open entrance area in the shop (no antennas on the floor)

• Improved customer experience, since tags are very thin and can be embedded in labels (for apparel). This allows the customer to try on a garment without suffering the annoyance of a traditional EAS mechanisms

• Shrinkage reduction

• Provides data to detect which products suffer more theft attempts, which allows taking corrective actions

• Statistics of EAS alarms

• Plug and play installation

Getting Started

These are the minimum steps to start using AdvanSafe:

1. Power AdvanSafe unit

Connect the AdvanSafe to a power supply (Switch PoE, PoE injector, etc..) through an Ethernet cable and wait until it beeps. It will take between 40 and 50 seconds to boot.

Using a PoE injector

Follow this diagram to connect AdvanSafe through a PoE injector:

2. How it works

AdvanSafe-300 implements beam-switching technology allowing it to have 4 different read beams. Those beams are used to derive whether a tag is going out from the store.

advansafe-300 also implements a mmWave chip that allows to detect when someone is crossing, significantly reducing the false alarms.

3. Alarm test with default EPC Alarm configuration

The default configuration of AdvanSafe is to trigger a visual and audio alarm when the AdvanSafe reads an EPC that starts with 0x3008 and it is read by the 4 read beams in 5 seconds. Pass the tag provided by Keonn under the AdvanSafe path. A triple-beep will be heard and a light will flash.

4. Configuration

Almost in any installation, it is required to adjust AdvanSafe operation.

4.1 Discover Device

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

We need therefore to connect the AdvanSafe 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 AdvanSafe 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.

4.2 Enter AdvanNet Manager

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

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

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

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

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

5. Enter with the following credentials:

• User: admin

• Password: admin

4.3 Read Modes

Go to the RF & Antennas options to see the available AdvanSafe read modes.

The AdvanSafe Configuration has the following configurations: AUTONOMOUS, SEQUENTIAL, EPC_EAS_ALARM, HTTP_EAS_ALARM, SQL_EAS_ALARM, EPC_EAS_ALARM_200, HTTP_EAS_ALARM_200 and SQL_EAS_ALARM_200.

The purpose of each Read Modes is the following:

• • AUTONOMOUS: In this read mode the RF engine schedules the antenna switching automatically amongst the available RF ports.

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

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

  • HTTP_EAS_ALARM: The alarm triggering logic is provided by an HTTP server. 

  • SQL_EAS_ALARM: The alarm triggering logic is provided by an SQL database. 

  • EPC_EAS_ALARM_200: EPC_EAS_ALARM taking benefit of Keonn's beam steering technology. 

  • HTTP_EAS_ALARM_200: HTTP_EAS_ALARM taking benefit of Keonn's beam steering technology. 

  • SQL_EAS_ALARM_200: SQL_EAS_ALARM taking benefit of Keonn's beam steering technology. 

More information about Read Modes can be found here.

4.4 Apply EPC Alarm Configuration

The Autonomous mode can be used to see the tags EPC, it will not trigger an alarm. In the case the EPCs in use followed:

• EPC (SKU) begins with 0x3036.

A configuration to trigger alarms when AdvanSafe reads EPCs that begin with 0x3036 will be:

It is also possible to configure a multiple set of patterns. Visit AdvanNet page for further information

4.5 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 AdvanSafe will start with EPC-EAS-200 configuration.

4.6 Alarm test with new EPC Alarm configuration

With the configuration of the previous chapters, only the EPCs that begins with 0x3036 will trigger alarms:

4.6 Configure AdavnView for presence detection

With the configuration of the RF, now it is only missing to enable the presence detection with the AdvanView Service.

Hardware overview

Please check the Hardware page

Installation

Please check Installation page.

Operation

Overview

Please check Settings overview page.

How to choose tags

The AdvanSafe-300 requires sensitive tags.

• • CheckPoint G6

  • Century CE33081, CE36061

  • Smartrac Web Monza 6

  • Etc.

Adjusting detection / false alarms

Although there is a large set of configuration options, only a few of them are usually needed to adjust the detection/false alarm level of the system.

Power adjust

The most basic thing to change is to adjust the conducted power.

• • Increasing the power will increase detection and will perhaps increase false alarms

  • Decrease the power will certainly decrease detection and also false alarms

For example the following configuration

Can be increased by 2 dB to:

Or decrease 3 dB to:

Power adjust (advanced)

Increasing the central beams power (1:2 and 1:3) to the same level of the external beams (1:1 and 1:4) has a direct effect on detection.

This can be used in cases where the previous procedure does not work.

When increasing the centrals beams power improves detection but generates too many alarms, the False alarm filter must be used.

False alarm filter

When the required detection can only be achieved in a way that generates too many false alarms, the only solution is to use the False Alarm filter.

Advanced configuration

AdvanCloud

To connect AdvanSafe-300 to the cloud using sCloud please follow these instructions.

Events & Actions

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

• • TAG_ALARM: This event is created when AdvanSafe reads an EPC that triggers an alarm, as was explained in USB-emulation-with-EPC-change-configuration.

AdvanSafe can have AdvanSafe Primary and AdvanSafe Secondary. In this case, there are the following events:

• • TAG_ALARM_ANTENNA_1: This event is created when AdvanSafe Primary reads an EPC that triggers an alarm.

  • TAG_ALARM_ANTENNA_2: This event is created when the AdvanSafe Secondary connected to the port 2 of the AdvanSafe Primary reads an EPC that triggers an alarm.

Normally these events will trigger a Speaker (sound) and a GPO (light) action for each alarm event:

If needed the connection with AdvanCloud, follow the previous chapter on AdvanCloud Service.

Change device IP

To change the IP visit Change device IP.

System features

Please see the discover devices for the 150 Series devices: System-features

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:xml:

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-200-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 the 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>1398285449000</ts>

    <status>OK</status>

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

    <op>inventory</op>

    <data>

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

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

        <inventory>

            <class>INVENTORY</class>

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

            <size>1</size>

            <timeWindow>-1</timeWindow>

            <items>

                <item>

                    <class>READ_EVENT</class>

                    <epc>3008029b5379cb0000000021</epc>

                    <ts>1398285448873</ts>

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

                    <data>

                        <class>TAG_DATA</class>

                        <hexepc>3008029b5379cb0000000021</hexepc>

                        <props>

                            <prop>TIME_STAMP:1398285448873</prop>

                            <prop>RSSI:-62</prop>

                            <prop>READ_COUNT:1</prop>

                            <prop>ANTENNA_PORT:1</prop>

                            <prop>RF_PHASE:47</prop>

                        </props>

                    </data>

                </item>

            </items>

        </inventory>

    </data>

</inventory>

• 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-200-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-200-eu</deviceId>

        <epcs>3008029b5379cb0000000021</epcs>

        <alarmType>EPC_EAS</alarmType>

    </event>

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

</deviceEventMessage>

• TAG_ALARM_ANTENNA_2

Same as TAG_ALARM_ANTENNA_1 with TAG_ALARM_ANTENNA_2

• TAG_ALARM_ANTENNA_3

Same as TAG_ALARM_ANTENNA_1 with TAG_ALARM_ANTENNA_3

• TAG_ALARM_ANTENNA_4

Same as TAG_ALARM_ANTENNA_1 with TAG_ALARM_ANTENNA_4

Whenever a TAG_ALARM is sent, it is also sent the TAG_ALARM_ANTENNA_X counterpart. They are redundant messages.

It also important to understand that AdvanSafe installations with Secondary unit, the antenna that detects a tag is not the antenna which is closer to that tag, is just the first antenna that is able to read a tag.

Use it the antenna value with caution

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-200-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-200-eu</deviceId>

    </event>

</eventMessage>

• • Also several error messages can be received.

Factory reset

It is possible to do a full factory reset.

Whenever the system is fully booted:

• • Press the reset button for 15 seconds. Use a paper clip or similar.

• • The unit will be rebooted with:

    • Default network settings: DHCP

    • Default system settings 

Use GPO/relay lines

AdvanSafe supports Secondary antennas. Each of the Secondary antennas feature a LED light controlled through a GPO line from the Primary unit.

The spare GPO lines can be used to control whatever system we wish.

Let's image we want to use the GPO cable of Secondary #3 to control whatever external device:

• • Configure the system to use the GPO#3

    • Got to Events & Actions tab

    • Click on new

• • • Adjust new event settings as follows

      • TAG_ALARM: is the event that will trigger the GPO line change

      • High: the event will switch the GPO line to high value.

      • On time: amount of time the line will be high

      • Off time: amount of time the line will be low

      • Total time: the total amount of time the GPO event will last.

• • • Persist changes if necessary.

• • Use the GPO line to control an external device. Remember the electronic characteristics are:

    • 5 V

    • 100 mA

Speaker sound level

it is possible to adjust the level of the external loud speaker. Follow instructions here.

Autonomous Mode

The Autonomous Mode configuration allows the user to test the AdvanSafe performance without any alarm configuration. The purpose of this configuration is only for testing, not for real scenarios.

To set this configuration, enter the AdvanNet manager (Web Application) of AdvanSafe, stop the reading and change the configuration to Test Mode: