AdvanGuard-100

Introduction

AdvanGuard is an RFID UHF alarm unit for loss prevention at retail stores, libraries and other spaces.

It comprises an embedded reader and alarm combining loss prevention and RFID functions in one system. It connects easily to various RFID antennas. It is ideal for combining it with AdvanMat RFID floor mat, for creating a complete loss prevention system.

The use process is as follows:

1. AdvanGuard is connected to chosen RFID antennas or systems

2. AdvanGuard detects the tagged items under the coverage of the antennas

3. AdvanGuard verifies if those items have been paid or fulfill a condition

4. AdvanGuard triggers an acoustic and/or visual alarm if any of the items has not been paid or does not fulfill a condition

Business benefits:

• Theft reduction

• Combination of loss prevention and RFID in one system

• Provides data to detect which product suffer more theft attempts

• Statistics of alarms

• Connects easily to various RFID antennas

• Built-in LEDs indicate which antenna has detected the stolen item

• Plug and play installation

Download Datasheet and User Guide at the Download files chapter.

Getting Started

Helpful downloads:

• Download Datasheet (see download files section)

• Download User Manual (see download files section)

1. Connect the Antennas

Connect the AdvanGuard with 4 Antennas. AdvanMat is the perfect AdvanGuard companion.

2. Power AdvanGuard unit

Connect AdvanGuard to a power supply and wait until it beeps. It will take between 40 and 50 seconds to boot. Optionally, AdvanGuard can be connected to a Router/Switch to be configured, it is explained in the following chapters.

3. Alarm test with default EPC Alarm configuration

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

4. Configuration

Almost in any installation it is required to adjust operation.

4.1 Discover Device

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

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

4.2 Enter AdvanNet Manager

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

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

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

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

4. Replace the <AdvanGuard-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 AdvanGuard read modes.

The AdvanGuard 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 Region Configuration

Set the configuration for your country or region:

4.5 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.

Change the configuration to EPC_EAS and configure it to trigger alarms when AdvanGuard reads EPCs that begin with 0x3036 will be:

4.6 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 AdvanGuard will start with EPC_EAS configuration.

4.7 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 AdvanGuard 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:

• • Port: The port where the antenna is connected.

  • Mux1 port: The first level multiplexor port where the antenna is connected.

  • Mux2 port: The second level multiplexor port where the antenna is connected.

  • Power: The read power for the antenna (If "inherit" is selected it will use the Read Power saw in the previous chapter (Power and Sensitivity)).

  • Sensitivity: The sensitivity for the antenna (If "inherit" is selected it will use the Sensitivity saw in the previous chapter (Power and Sensitivity)).

  • Location: String definition for the antenna + static position for the antenna (definition, x, y, z)

  • Orientation: Logical IN or OUT areas definition used when estimating the direction of the tags (more than one antenna needed).

AdvanCloud

To connect AdvanGuard to the cloud using sCloud please follow these instructions.

Events & Actions

AdvanGuard can be configured which actions will be trigger in the available events. For example, the most used events are:

• • TAG_ALARM: This event is created when AdvanGuard reads an EPC that triggers an alarm.

AdvanGuard can have AdvanGuard Masters and AdvanGuard Slaves, in this case there are the following events:

• • TAG_ALARM_ANTENNA_1: This event is created when AdvanGuard Master reads an EPC that triggers an alarm.

  • TAG_ALARM_ANTENNA_2: This event is created when the AdvanGuard Slave connected to the port 2 of the AdvanGuard Master reads an EPC that triggers an alarm.

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

Change device IP

To change the IP visit  Change device IP.

Discover devices

Please see the discover devices for the 150 Series devices

System features

Please see the system features for AdvanSafe-100.

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:

• 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 releasing the reset button.

• The system will be restarted

• Wait for the start-up beep

System Configuration

Please see the system configuration for AdvanSafe-100.

Available filters

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.

External Connections

Using a Relay

It is possible to connect a relay to a GPO of AdvanGuard as it can be seen in the following picture (the relay used is OMRON G5V-1-5VDC). 

Hardware wiring

There are 3 cables and 6 pins used as it can be seen in the following pictures:

Cable connection:

• • Cable 1 (connected to PIN 5) and Cable 2 (connected to PIN 1 and 2) will be connected to a dry contact connection in your equipment.

  • Cable 3 (pair) (connected to PIN 3 and 4) will be connected to GPO 1, 2, 3, or 4.

Using LEDBAR #1,#2,#3 or #4

LEDBAR output lines provide up to 100 mA at 5 V. They can be used to directly drive a relay.

For example OMRON G5V-1-DC5 (Mouser 653-G5V-1-DC5)

Using OUT #5.. OUT#8

OUT #5 to OUT#8 are limited to 8 mA, it is therefore required a small circuit to drive a relay.

The circuit will use two GPO lines

• • +5 V output: this provides up to 100 mA

  • OUT5: this is used to control the state of the relay

Configure AdvanNet

Once the wiring is done, we need to configure AdvanNet to enable the external relay on any alarm.

If we choose GPO 1, we would need to configure as follows:

• • Go to the Events & Actions tab and configure the following action with the correct GPO number:

    • Trigger: TAG_ALARM

    • Action: GPO_ACTION

    • Line: 1

  • Click on Save Action to persist configuration.

Other

Check NTP connection

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

Troubleshooting

I cannot here the beep on system start up

Make sure this is a persistent error by rebooting (power off and on) the device. 

Please have a look at the status LED. In the chapter Hardware overview there is a detailed explanation of the status LED codes. 

In case the beep cannot be heard, it may mean it is a hardware error. Please contact support@keonn.com.

I do not have a DHCP server

Please check alternatives to connect to device

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.