AdvanSafe-100

Introduction

AdvanSafe is an 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 AdvanSafe detects the tagged items that pass below the antenna, verify if those items have been paid, and sounds an alarm if an item has not been paid.

AdvanSafe comprises a primary unit and several secondary units:

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

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

By using AdvanSafe 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

Download AdvanSafe datasheet

Download User Guide from the Download files chapter.

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.Alarm test with default EPC Alarm configuration

The default configuration of AdvanSafe is to trigger a visual and audio alarm whenever the AdvanSafe reads an EPC that starts with 0x3008. Pass the tag provided by Keonn under the AdvanSafe. A triple-beep will be heard and a light will flash.

3.Configuration

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

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 in 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 <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. Login with the following credentials:

• User: admin

• Password: admin

Read Modes

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

The AdvanSafe Configuration has the following configurations: EPC_EAS_ALARM, HTTP_EAS_ALARM and SQL_EAS_ALARM.

The purpose of each Read Modes is the following:

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

  • HTTP_EAS: EAS mode that uses an http server.

  • SQL_EAS: EAS mode that uses an SQL database. 

Apply EPC Alarm Configuration

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:

Persist Configuration

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

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

• In this case, the AdvanSafe will start with EPC_EAS_ALARM configuration.

Alarm test with new EPC Alarm configuration

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

Advanced configuration

Power and Sensitivity

The power and sensitivity of the AdvanSafe 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.

AdvanCloud Service

Check the configuration in here.

Events & Actions

You can configure which actions will be the trigger for 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.

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:

Change device IP

To change the IP visit  Change device IP.

AdvanSafe Secondary/s

It is possible to increase the reading area of AdvanSafe by attaching AdvanSafe Secondary to an AdvanSafe Primary:

• AdvanSafe Primary consists of an RFID reader, one antenna, a speaker and one LED.

• AdvanSafe Secondary consists of one antenna and one LED.

Physical Connection

• • RF connection: Connect an RF cable from the AdvanSafe Primary to the AdvanSafe Secondary.

  • LED connection: Connect the brown cable with the black and white cable and the blue cable with the completely black cable.

AdvanNet Configuration

Go to the RF & Antenna Options tab of AdvanSafe Primary and configure a new antenna on the port where the Secondary is connected.

Go to the Events & Actions tab and configure an event to light up the LED (GPO_ACTION) of the Secondary when there is an alarm detected by the Secondary. If the Secondary is connected to the data cable number 2, the Line has to be 2.

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

Discover devices

Please see the discover devices for the 150 Series devices: Discover-devices

System features

Please see the system features of AdvanSafe in the 150 Series devices wiki: System-features

Access real-time data

All system activity can be accessed in 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.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>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-100-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-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

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 one or more Secondary units, 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-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.

System configuration

Please see the discover devices for the 150 Series devices: series150_Configuration

Allow access to non-alarmed tags while in EAS operation

Sometime it may be convenient to gain read access to any tag, although the system is running on EAS modes. This is implemented in the EAS-EPC mode:

• • Go to RF tab

  • Enable the SW filter only (This may lead to a degraded performance in read intensive applications.)

When enabled, any tag in the field will be read:

• • Alarmed tags will generate the standard signals.

  • Non-alarmed tags will also be available in the CSV log or in real-time through 3177 socket.

Use GPO lines

AdvanSafe supports up to 3 Secondary antennas, each of the Secondary antennas feature a LED light controlled through a GPO line from the Primary unit.

On those installations where we do not need the Secondary LED lights or not all of the Secondary are used, it is possible to use the spare GPO lines.

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#4 (Secondary #3 uses GPO#4 line).

    • Go to Events & Actions tab

    • Click on new

  • Adjust new event settings as follows

    • TAG_ALARM: is the event that will trigger the action.

    • GPO_ACTION: The action that performs the GPO line change

    • Line: must be 4 to use to Secondary #3 cables

    • 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: 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 loudspeaker. Follow instructions here.

SQL EAS ALARM

For more information look into the following link.

Filters to minimize False Alarms

Filters information can be found on the Series 50 page

Installation

Installation disclaimer

Keonn Technologies S.L. does not accept any responsibility for injuries to installers, store personnel or store visitors, or damage to the existing infrastructure resulting from or associated with the installation of AdvanSafe units.

Keonn Technologies S.L. does not accept any responsibility for improper handling of AdvanSafe units that may result in system damage and/or failure, including but not limited to:

• Improper adjustment of RF cables that may result in damage to RF connectors and/or transitions.

• Improper handling of RF cables and Secondary antennas that may result in RF module damage due to ESD conditions.

Keonn Technologies S.L shall not be held responsible for installation actions taken or not taken.

AdvanSafe is not waterproof. Install AdvanSafe units in a dry location away from excessive heat, humidity and any components likely to damage the system.

It is the installer’s and/or project owner responsibility to ensure that: 

• The method of installation does not damage or interfere with the existing infrastructure.

• The system and its installation are properly maintained to ensure its effective operation and safety.

• The RF cables are properly tightened with a torque wrench

• Proper ESD measures are taken not to damage AdvanSafe units

AdvanSafe orientation

The following diagrams show correct and wrong AdvanSafe orientations

Which tags should I use?

RFID EAS require in general powerful tags:

• • Smartrack WEB like

  • Hard tags: avoid using the smallest options.

How many Primary and Secondary units should I use?

There are two recommendations:

• A separation between AdvanSafe (Primary or salves) units of about 1.5 m - 2.0 m.

• To achieve maximum read rate: the AdvanSafe unit placed on the further left, and the AdvanSafe unit placed on the further right, shouldn't be separated from the edge of the entrance by more than 0.5 m.

Therefore, we recommend the following configuration depending on the width of the entrance to protect:

• • 2 m - 3.5 m: 1 Primary + 1 Secondary

  • 3.5 m - 5 m : 1 Primary + 2 Secondary units

  • 5 - 6.5 m: 1 Primary + 3 Secondary units

  • 6.5 - 8 m: 2 Primary + 3 Secondary units

Which is the maximum recommended distance between Primary and Secondary?

We do not recommend using cables larger than 5 meters.

What is the maximum height AdvanSafe will work?

There is no single answer to that question, several factors must be taken into account:

• • RFID tag in use: more sensitive and powerful tags will perform better and would allow a higher installation.

  • Material to be tagged: some products may detune RFID tags and therefore decrease the overall system sensitivity. Those would be more affected by height.

  • Particular application: also the use case may affect the maximum height.

However, there are some simple recommendations:

• This is a system designed to work with medium and high power tags: it won't work with jewelry tags or similar.

• In general, the best height would be 2.5 meters: minimum height for people moving comfortably.

• Above 3 meters it is important to: use powerful tags and verify the system performance.

Which materials and/or conditions may interfere AdvanSafe operation?

Generally speaking, AdvanSafe is quite robust against external interference. Some of the known sources of interference are:

• • Other RFID systems: having other RFID systems working very close to AdvanSafe-100 may produce uncontrolled effects: reduce system performance or in some cases increase the read range.

  • Large metallic pieces close to AdvanSafe: this is a condition that will certainly cause an unpredictable deformation of the beam shape.

  • Material to be tagged: some products may detune RFID tags and therefore decrease the overall system sensitivity. Some of the products well known for detuning RFID are:

    • Metal

    • Products containing water or liquids

  • Human body: the human body may act shielding RFID operation.

Which are the security margins for AdvanSafe?

As any EAS technology, RFID also requires security margins. Exact margins depend on many factors: installation high, tag model, environment, RF power, etc.

Additionally, RFID may suffer from constructive and destructive reflections that may change the theoretical footprint.

A typical footprint for AdvanSafe is as follows:

Other

Check NTP connection

Please see the Check NTP connection for the 150/60 Series devices: Check-NTP-connection

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.