EN

EN

Installation and Configuration

AEOS Locker Management

AP1013 and LoXS terminals
Version 15 | 09-01-2018
Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Date Version Changes

09-01-2018 15 'Clean locker' replaced by 'release locker'

21-04-2017 14 Lay-out
12-05-2016 13 Added section 4.4.1 third party readers
15-09-2015 12 Replace AEpu and move terminals
02-04-2015 11 Cleanup and continuation time, removing LoXS terminals
29-10-2014 10 Updated license requirements and new logo
01-08-2014 9 Version information added
11-06-2014 8 Print screens updated and locker unit Smart added
3rd party readers for LoXS terminal and clean up timer
15-08-2013 7
functionality
11-10-2012 6 Update: Include Mifare Flush and new article numbers
General revision of document. Extra explanation of LoXS
components. Introduction of new names and definitions. Use of
12-10-2011 5
permanent lockers via AP1013 via locker management server
option is cancelled
Amount LoXS terminals pro AEpu + Master LoXS key detailed
18-10-2010 4
info added
Overview lockers menu, check AEpu on LoXS terminal added,
05-10-2010 3
small changes
25-08-2010 2 AP1013 added, more info added
04-06-2010 1 Initial setup

Manual version 15 2/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Contents
1. GENERAL 4

2. LOCKS 5
CABLING 7
PROGRAMMING THE LOCKERBUS ADDRESS OF THE RF LOCK USING THE BINDER UNIT 8
ADDRESSING THE LOCKER UNIT SMART 9
PROGRAMMING MIFARE CARD SETTINGS INTO THE MIFARE LOCK 10

3. LOCKS CONNECTED TO AP1013 11

REQUIREMENTS 11
SYSTEM SET-UP 12
HOW TO USE LOCKS CONNECTED TO AP1013 IN AEOS 12
3.3.1. LOXS INTEGRATOR AND CABINET ACCESSPOINTS 14
3.3.2. LOXS INTEGRATOR AND NORMAL ACCESSPOINTS 15
AEOS USER INTERFACE 15

4. LOCKERS CONNECTED TO LOXS TERMINALS 16

REQUIREMENTS 18
4.1.1. AEOS REQUIREMENTS 18
4.1.2. LOXS TERMINAL REQUIREMENTS 18
4.1.3. LOCK REQUIREMENTS 18
SYSTEM SET-UP 19
LOXS TERMINALS 20
AEMON SOFTWARE 21
4.4.1. THIRD PARTY READERS 22
AEOS USER INTERFACE 23
4.5.1. SET MAXIMUM AMOUNT OF IDENTIFIER TO 1 23
4.5.2. CONFIRM ADDED LOXS TERMINAL 24
4.5.3. DEFINE LOXS TERMINAL TEMPLATES 24
4.5.4. CREATE FREE FIELD TO SELECT WHO IS ALLOWED TO HAVE A LOXS MASTER KEY 25
4.5.5. ASSIGNING LOXS MASTER KEYS 26
4.5.6. ASSIGNING LOCKERS TO CARRIERS 27
4.5.7. LOCKERS STATUS OVERVIEW AND UNLOCK, BLOCK AND DEBLOCK 28
4.5.8. RELOAD LOXS TERMINAL 29
4.5.9. REMOVE LOXS TERMINALS 29
4.5.10. REPLACE AN AEPU 30
4.5.11. MOVE TERMINALS 30

Manual version 15 3/32

 Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

1. General
AEOS allows you to authorize persons for (online and offline) doors, key cabinets, intrusion, etc.
AEOS Locker Management takes access control to the next level, by applying the same principles
of the access control policy to all lockable compartments. AEOS Locker Management allows
carriers to use their current access card to access their lockers, (filing) cabinets or post boxes in a
safe and convenient way. It eliminates key management and enables AEOS customers to not only
manage who is allowed to access which buildings or areas, but also which compartments within
those areas may be used or accessed. All access rights are managed within their trusted security
platform AEOS.
AEOS Locker Management can roughly be divided into the following three applications:

 Cabinet access control

This application is used for all compartments that need authorizations similar to an
Entrance, such as filing cabinets or post boxes. A cabinet can be assigned to multiple
persons (whereas a locker can be assigned to one person).

 Short-term lockers1
Lockers are used dynamically, which implies that fewer lockers are required by making
sure that they are used at maximum efficiency. In AEOS, persons are authorized to claim
any available short-term locker in a selected area. Persons can claim an available locker by
simply presenting their badge, but will not be assigned to this locker permanently. The
locker will become available for other persons after the locker is unlocked (this voids the
assignment) or after an optional daily release time is reached, for instance at night (to
avoid users from occupying lockers unnecessarily). AEOS user interface is used to
authorize persons to claim short-term lockers (and to limit the maximum number of
lockers that can be used at the same time).

 Permanent lockers2
A specific locker is assigned to one person for a longer period of time (until authorization
is cleared in AEOS). Short-term and permanent lockers can never be assigned to more than
one person, however, a person may be assigned to multiple lockers. Assignment of lockers
is done in the AEOS user interface.

Cabinet access control has already been introduced in AEOS 2.2 in combination with the AP1013
AEpack (see chapter 3 for further details). Permanent and short-term lockers require a LoXS
terminal, for which the interface is added in AEOS 2.4 (see chapter 4 for further details). These
three applications can be mixed to build the most efficient and profitable solution for each
customer.

1
Short term lockers are called day lockers in AEOS versions older than 2.4.4.
2
Permanent lockers are called rental or year lockers in AEOS versions older than 2.4.4.

Manual version 15 4/32

 Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

2. Locks
The electronic locks used for AEOS Locker Management are developed and produced by Nedap
and can easily be mounted into any kind of compartment, such as lockers, filing cabinets, laptop
lockers or post boxes. These locks have an integrated reader for the most important RFID cards,
including all MIFARE and Nedap types, HID iClass and Legic Advant. Our locks can communicate
with an AP1013 or LoXS Terminal MIFARE with COM unit 2G.

Nedap offers the following four types of locks:

 Mifare lock (article no: 9871500 for light grey and

9961968 for charcoal)
This lock has an integrated Mifare reader that can read
all Mifare types. Additionally, the lock can read the
card serial number of 13.56 MHz HID iClass en Legic
Advant and ICODE. It is composed of a lock that is build
into the compartment, and a handle that is mounted in
the door of the compartment. Please note that the
handle is included with the Mifare lock. The Mifare lock
can be used for compartments made of any material,
including compartments with metal doors (whereas the Mifare lock
(article no: 9871500 for light grey
RF reading of the Locker unit IV is highly affected by
and 9961968 for charcoal)
metal doors). Please consult the Mifare lock
installation sheet LoXS_LockerUnit_Mif_Installsheet_EN Including : Handle
for specifications and installation instructions.

 Mifare Flush lock (article no: 9207937)

This lock has an integrated Mifare reader that can read
all Mifare types. Additionally, the lock can read the
card serial number of 13.56 MHz HID iClass en Legic
Advant and ICODE. This set is composed of the lock
that is built into the compartment, the flush mount,
that operates as a RF frequency enhancer and a pin set
long or a pin set short depending on thickness of the
door. The pin set is to be mounted in the door. A pin
set short is required for doors with 8 – 15 mm
thickness. A pin set long for doors with 13 – 20 mm
thickness. Please indicate on the moment of ordering
which pin set is required The RF reading of the Mifare Mifare Flush lock
(Article no: 9207937)
Flush lock is highly negatively affected by metal doors.
Please consult the Mifare Flush installation sheet Including: Flush mount and pin set
LoXS_LockerUnit_MIF FLUSH MOUNT_InstallSheet_E_v1 long or pin set short
for specifications and installation instructions.

Manual version 15 5/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

 Locker unit IV (article no: 9207929)

This lock has an integrated reader for all Nedap XS ISO
badges (older Nedap AM cards - C, D, G code - cannot be
read by the Locker unit IV). Additionally, the lock can
read EM Marin 125 kHz badges. For each lock, a pin set
short or pin set long is required depending on the
thickness of the door. The pin set is to be mounted in the
door. A pin set short is required for doors with 8 – 15 mm
thickness. A pin set long for doors with 13 – 20 mm
thickness. Please indicate on the moment of ordering
which pin set is required. The RF reading of the Locker Locker unit IV
unit IV is highly negatively affected by metal doors. (article no: 9207929)
Please consult the Locker unit IV installation sheet
LoXS_LockerUnit_InstallSheet_EN for specifications and Including: pin set long or pin set short
installation instructions.

The previous version of the Locker unit, the

Locker unit III, may still be in operation, but
differs slightly in terms of functionality (e.g.
blinking red LED instead of red/green LED and
no buzzer). The Locker unit IV is used as
standard in this document, unless stated
otherwise.

 Locker unit Smart (article no: 9981942)

This lock is without an integrated reader. For each lock, a
pin set short or pin set long is required depending on the
thickness of the door. The pin set is to be mounted in the
door. A pin set short is required for doors with 8 – 15 mm
thickness. A pin set long for doors with 13 – 20 mm
thickness. Please indicate on the moment of ordering
which pin set is required. Please consult the Locker unit Locker unit Smart
Smart installation sheet (article no: 9981942)
LoXS_LockerUnit_SMART_InstallSheet_EN for
specifications and installation instructions. Including: pin set long or pin set short

The locker unit Smart will not work in

combination with the AP1013.

In brief following actions must be performed to install a lock, but please refer to the
abovementioned installation sheets for all installation instructions:
1. Make correct cabling and mount the locks.
2. Program all locks with their unique lockerbus address.
3. (Optional) Upload the Mifare configuration.

The settings of the LED indicator of the lock can be modified in AEmon (when using an AP1013;
see chapter 3.3.1) or in the LoXS terminal (see chapter 4.3). Please note that this also depends on
the type of lock; Locker III (only red blinking LED) or Locker IV, Mifare lock, Mifare Flush lock and
locker unit Smart (red and green LED). Please note that Locker unit III and IV may be mixed on the
same lockerbus, but may not be used in a lockerbus with both types of Mifare locks.

Manual version 15 6/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Cabling
All locks are in a bus structure connected to the AP1013 or Com Unit 2G with an RJ10 flat cable
and RJ10 connector. An AP1013 or COM unit 2G can be connected to maximally 62 locks,
distributed over 6 output connectors. Up to 15 locks may be connected per output connector, but
we strongly advise to distribute all locks evenly over all available outputs (e.g., if 6 locks are
used, connect 1 lock to each output).
Please note that Locker unit III and IV may be mixed on the same lockerbus, but may not be used
in a lockerbus with both types of Mifare locks.

For detailed information see:

 For the AP1013, the AP1013 Installation Sheet
 For the LoXS terminal with COM unit 2G LoXS III user manual_EN.

To AP1013 output 2, 4, 6
or
COM unit 2G

To AP1013 output 1, 3, 5
or
COM unit 2G Cable: flat cable RJ10
Max locks: 15

10m 3,5m

Total max cable length lockerbus: 59m

The first 10 meters depends on the total length of the cable. If for instance 4 locks are
used, the first lock can be placed on 59 – (4*3,5) = 45 meters from the AP1013 or COM
unit 2G.

Manual version 15 7/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Programming the lockerbus address of the RF lock using the

Binder unit
Each lock must have a unique lockerbus address, as they are placed in a communication loop.
This lockerbus address is wirelessly programmed into the lock using the Binder unit (article no:
9887075). Binder units up from September 2009 can be used for both Mifare locks (13.56 MHz)
and Locker units (120kHz); older versions can only be used for Locker units. The ON LED will only
be active if the Binding unit is held close to a lock and the Program button is pressed.

Version from 9-2009 Version before 9-2009

For Mifare lock and Locker unit IV For Locker unit IV only

ANTENNA
ADDRESS

ANTENNA
0 4 Power LED (green)

0 4 Thumbwheel
PROGRAM
120 kHz
13.56 MHz
Batt
On

Power switch

NEDAP

The programming procedure is as follows (note that the locks need to be powered before
starting the addressing procedure):

Select the lockerbus address with the tumble wheels on the Binder unit (01-62). Make
Step sure that all locks connected to the same AP1013 or COM unit 2G receive a unique
01 address between 1 and 62.
Please note that this address is not the locker number, but a unique lockerbus address.

If programming a Mifare lock with handle or Mifare Flush, make sure that the handle or
Step pin is in the lock. If programming a Locker unit IV, the pin set may be either in or out of
02 the lock. The Binder unit will automatically detect whether a Mifare lock or Locker unit
is in reach of the antenna.

Step Press the power button while keeping the Binder unit close to concerned lock to keep
the signal in reach of the integrated antenna of the lock (please verify the location of
03 the antenna on the Binder unit).

Step The red LED and buzzer of the lock will signal if the address is received and stored
correctly in the none volatile memory of the lock (please note that the buzzer is not
04 available in the Locker unit III).

Manual version 15 8/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Addressing Locker unit Addressing Mifare lock

Programming address 90 will reset the lock back to factory default settings, except for
the unique lockerbus address. This is strongly recommended when using locks that
have previously been used in other settings or installations.

Addressing the locker unit Smart

After the hardware has been added the process of assigning system addresses to the locker unit
Smart can commence. All LEDs are flashing green at a slow pace.

Step Select the shackles icon in the LoXS terminal.

01

Step Select the locker number that needs to have a system address assigned and press
BIND. The green LEDs now start to flash faster.
02

Step Go to the locker with the number indicated by the terminal and execute the next few
steps:
03 1. In case the locker is open, close it first.
2. Open the locker: the green LED goes out; wait for it to start flashing again.
3. Close the locker: the green LED goes out again; wait for it to start flashing again.
4. Open the locker: the LED will now stop flashing and stay on in the colour of the
present status (red or green).

The LEDs of all locks that yet have to receive a system address once again slowly flash green.
When the red LED starts flashing an error has occurred. This happens when the locker door is
opened and closed too quickly. If this happens, retake steps 1 to 4 as described above.

Manual version 15 9/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Step The following screen is shown when the procedure has been completed successfully:
04

Press 'Next' to go to the next locker number, 'Redo' to start over with the same locker
number or 'Stop' to close this screen.
'Stop' can also be used to abort the procedure intermittently.

The execution of these steps, in this order, is necessary to ensure that every Smart lock
receives the appropriate system address and to ensure that the terminal knows when
this has been done and the next locker can be assigned one.

Programming Mifare card settings into the Mifare lock

Mifare cards can be used with the CSN number, but more often data from one of the sectors or
files is used as identifier. If sector or file data is used, the Mifare locks must be programmed with
the correct configuration to read this data. The Mifare configuration file is provided by Nedap on
request and is made with the ‘SCCL’ program. This configuration file contains all necessary
information for reading the correct data on the Mifare card. Please contact Nedap for a Mifare
configuration file request.

Loading the generated file from the SCCL program is done as follows:
 For the Mifare locks connected to an AP1013:
AEmon is used to load the configuration file (identical to loading a configuration to a Convexs
reader).
 For the Mifare locks connected to a LoXS terminal Mifare:
The configuration file must be loaded onto the LoXS terminal Mifare using FTP. The LoXS
terminal Mifare transfers the information of the configuration file to all connected Mifare
locks.

Manual version 15 10/32

 Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

3. Locks connected to AP1013

Locks used for securing cabinets or other compartments that need authorizations similar to an
Entrance need to be connected to an AP1013 AEpack. The AP1013 seamlessly integrates Nedap’s
proven electronic locks into the AEOS Security Management platform. Cabinet access control has
been introduced in AEOS version 2.2. However, AEOS version 2.2 supports Locker units III
functionality only (Locker units IV may also be used, but will only support functionality of Locker
unit III, please refer to chapter 2 for differences; the Mifare locks are not supported). Up from
AEOS version 2.4.1., Locker unit IV and the Mifare Locks are supported in AEmon.

Like all other AEpacks, the AP1013 needs to be connected to an AEpu (in the example below the
AP8001X):

Per AEpu:
Max 124 locks

Per AP1013 (9854150):

Max 62 locks
230VAC Max 6 lockerbuses
LAN/WAN network
Per cabinet:
Web clients
Mifare lock (9871500 for light grey and 9961968 for
charcoal)*
Mifare Flush (9207937)*
or
Locker unit IV (9207929)*

* Locker unit Smart not allowed.

AEOS Server
and license:
Doors Cabinets Cabinet AccessPoint (8015481)
or
Standard AccessPoint (8013527)+ badge reader (8013535)

Requirements
The following is at least required to integrate the locks in AEOS using the AP1013:
 AEOS version 2.2 or higher for Locker unit III (note that a Locker unit IV can be used, but will
behave like a Locker unit III in 2.2.)
 AEOS version 2.4.1 or higher for Locker unit IV, Mifare lock or Mifare Flush Lock (Locker unit
Smart not allowed).
 Correct licenses:
o Cabinet AccessPoint (article no: 8015481) for each compartment. Cabinet
AccessPoints can be generated automatically by the LoXS-Integrator AEbc.
or
o Standard AccessPoints (only if extensive functionality is required).
 One or more AP1013 connected to the AEbus (for connecting to the AEpu).

Please note:
o Up to 62 locks may be connected per AP1013.
o Up to 124 locks may be connected per AEpu.
o Using the AP1013 for Cabinet Access Control can be combined with LoXS terminals for
short-term or permanent lockers (using the LoXS Terminal Manager) in the same AEOS
system.

Manual version 15 11/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

System set-up
Following steps must be performed to use the locks connected to the AP1013:

Step
Mount and connect the locks to the AP1013 as described in chapter 2.
01
Step
Use AEmon to deploy the LoXS-Integrator AEbc to the AP1013.
02
Step
Apply the settings at the LoXS-Integrator AEbc.
03
Step
In the AEOS User Interface, the new deployed cabinet AccessPoints can be linked to
04 Entrances.

Step
Entrances can now be assigned to carriers.
05

How to use locks connected to AP1013 in AEOS

After the locks are correctly addressed (using the Binder unit) and connected to the AP1013, they
can be shown in AEmon. In AEmon (hardware level), the implementation of the locks is selected;
 Cabinet AccessPoint (cabinet functionality)
 Normal AccessPoint (extensive functionality)

Both options are available in the LoXS Integrator AEbc. A cabinet AccessPoint includes the badge
reader and door contact. Per LoXS integrator AEbc, there is a shared output for all connected
locks, which for instance can be used for triggering and alarm or camera. A cabinet AccessPoint
should be sufficient for the far majority of applications.

In the AEOS software, the deployed locks will be shown at Confirm AccessPoints; after
confirmation you need to assign them as an Entrance, similar to the procedure of AccessPoints.
This gives all functionality for an entrance, multiple persons can be assigned to a cabinet.

Lock Cabinet Standard AEOS:

AccessPoint
Lock  Entrance functionality
Entrance  Multiple persons to one cabinet
 Time schedules, etc.
Normal
Lock AccessPoint

AEpu AEOS Server

Manual version 15 12/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Manual version 15 13/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

3.3.1. LoXS Integrator and Cabinet AccessPoints

You need to use the AEbc: LoXS-Integrator. The Lbus (communication bus) of the AP1013 is
connected to the communication input of the AEbc.

At Properties, Lockerbus configuration, enter the lockers

that are connected. In the hardware view of AEmon, you
will only see the locks that are connected to the AP1013.

The available locks can be checked for their hardware

status (in this case at locker 203 the door is open).

The lockers are not placed directly under the

corresponding AP1013.

To use Cabinet AccessPoints, go to Properties and activate Automatic AccessPoint creation (see
illustration of AEOS 2.2 below).

The LoXS-Integrator connects the lockers automatically to the LoXS-Integrator AEbc, with all
necessary bindings. Also one dda (Direct Door Alarm) and one dotl (Door Open Too Long) is added
to this AEbc. Both outputs are for all connected locks, it is not possible to generate a message
about which specific lock is open.

The Locker unit Address offset can be used if more than one AP1013 is connected to the
same AEpu; the offset is added to the unique lockerbus address that is programmed
into the lock with the Binder unit.

The just now generated Cabinet AccessPoints are available in AEOS as AccessPoint-Locker and can
be used as Entrances in AEOS.

Manual version 15 14/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

3.3.2. LoXS Integrator and normal AccessPoints

The first part of the procedure is identical to 3.3.1. Use the LoXS-Integrator and enter the locks
that are connected at Properties, Lockerbus configuration.

After the amount of locks is stated and deployed, you need

to load the deployed configuration from the AEpu to show
the available lockers: Configuration – Open – From AEpu.

The locks are now available to AEmon as hardware object

(Locker). It is for the user free to decide how these can be
used.

In this example, locker 402 is used in combination with a

StandardDoor, locker 401 is connected to a TNK AEbc.

The just now generated AccessPoints are available in AEOS

as AccessPoint and can be used as Entrances in AEOS.

AEOS User Interface

The deployed AccessPoints are shown in the Confirm AccessPoints menu after deploying the
configuration in AEmon. After confirmation, they can be used as AccessPoint.

Follow the ‘normal’ procedure for adding an Entrance in AEOS, which allows you to combine the
entrances in Entrance groups and combine them with Time Schedules.

Manual version 15 15/32

 Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

4. Lockers connected to LoXS terminals

Locks used for either permanent or short-term lockers need to be controlled by a LoXS terminal.
The LoXS terminal can control up to 124 locks. Carriers can present their badge at the LoXS
terminal if they have forgotten their locker number or in case they cannot find an available
locker. There are 2 types of LoXS terminals, which are almost identical, except for the integrated
badge reader:
 LoXS terminal Mifare (article no: 9561862) for controlling Mifare locks.
This terminal has an integrated Mifare reader.
 LoXS terminal (article no: 9561889) for controlling Locker units.
This terminal has an integrated Nedap XS reader.

In this document, we will refer to LoXS terminals in general, unless stated otherwise.

All locks controlled by a LoXS terminal are connected to a COM unit 2G (article no: 9899197), for
power and communication. As from AEOS 2.4, multiple LoXS terminals can be controlled by one
AEpu (e.g., the AP8001, see chapter 4.2 for maximum number per AEpu). The LoXS terminal
communicates with the AEpu over IP and has a fixed IP address (see illustration below).

LAN/WAN network

Per Terminal:
LoXS terminal (9561889)
or
LoXS terminal Mifare (9561862)
Web clients AEOS Server

Max 2 COM units 2G

COM unit 2G Max 124 locks

Per COM unit 2G (9899197):

Max 62 locks

Per locker:
Mifare lock (9871500 for light grey and 9961968 for charcoal)
Mifare Flush (9207937)
or
LoXS terminal Locker unit IV (9207929)
or
3rd party Locker unit Smart (9981942)
reader
and license:
Lockers connected to LoXS terminal (8019690)1

The number of lockers connected to the LoXS terminals is licensed in AEOS. Filters can be applied
to prevent AEOS users from assigning rights to lockers that they are not authorized to assign
(actually to the LoXS terminals these lockers are connected to).

Manual version 15 16/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Permanent locker:
 Assigned in AEOS
 One person per locker
Lock Permanent  Not affected by release time
locker
Lock

Short-term locker:
Short-term  Claimed at terminal
Lock locker  One person per locker
LoXS  Assigned until unlocked
terminal or
COM Unit 2G  Assigned until optional
AEpu AEOS Server
automatic release time

In AEOS, persons may be authorized for using permanent and/or short-term lockers in a selected
area. Also, persons may be authorized in AEOS for using multiple lockers at the same time. Due to
technical constraints, they will not be able to use multiple lockers controlled by the same LoXS
terminal. All lockers connected to a LoXS terminal are considered as short-term lockers, unless
they are assigned to a person as a permanent locker.

Two different modes are available in the LoXS terminal that determine the way persons can
obtain a locker and whether the not assigned lockers are locked or not:

 Toggle mode (recommended): Toggle mode implies that all not assigned lockers are
unlocked.
Implications for short term lockers: Persons authorized to use short-term lockers may lock a
locker by holding their badge close to the lock (this will assign their badge to the locker).
By unlocking the locker, the assignment ends and the locker immediately becomes
available for another person (or the same person may lock the locker again if (s)he needs it
for a longer period). An optional daily release time will void all assignments of short-term
lockers (for instance at night), to ensure that persons do not occupy lockers unnecessarily.
Implications for permanent lockers: Permanent lockers are locked and not affected by the
release time.

Toggle mode is recommended as it has two advantages: persons do not need to use the
LoXS terminal to claim a locker and have the right to choose their locker. Lockers cannot
be locked when not in use. Therefore, Nedap advises to apply locker doors with a self-
closing hinges, to ensure that all doors are closed.

Toggle mode will not work in combination with 3rd party readers.

 Standard mode: Standard mode implies that all lockers are locked, even if they are not
assigned.
Implications for short term lockers: Persons authorized to use short-term lockers can claim
a locker by scanning their badge at the LoXS terminal. The LoXS terminal will assign a
locker (this implies that they cannot choose their own locker). The locker will remain
assigned to the person (even if the person does not use the locker anymore), until the
daily release time voids all assignments.
Implications for permanent lockers: Permanent lockers are locked and not affected by the
release time.

This mode is in practice only used when lockers that are not in use have to be locked and is
recommended for the use of 3rd party readers.

Manual version 15 17/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Requirements
4.1.1. AEOS requirements
The following is required to control lockers in AEOS with the LoXS terminals:
 AEOS version 2.4 or higher
 AEOS version 3.1.1 or higher in case of locker unit Smart or 3rd party reader connected to the
LoXS terminal.
 License: AEOS Blue license: Locker - Licence no. 8030130
AEOS Classic license: Lockers connected to LoXS terminal (license per locker) - Licence
no. 8019690
The total amount of lockers connected to AEOS with LoXS terminals is licensed. If the amount
for this license option is set to 0, the LoXS Integration option is in disabled in AEOS.
 LoXS terminals connected to an AEpu via the IP network: Com Units 2G

Please note:
 Up to 62 locks may be connected per COM unit 2G.
 Up to 2 COM unit 2G may be connected per LoXS terminal, resulting in a maximum of 124
locks per LoXS terminal.
 Communication between terminals is only possible if they are connected to the same AEpu.
LoXS terminals cannot verify whether a person already uses a locker at a different terminal if
they are connected to different AEpus. However, connecting all terminals to a single AEpu
means that your locker system is dependent on the network. Please take this into account
when deciding to which AEpu the LoXS terminals will be connected.
 The LoXS terminals are managed by an AEpu behaviour component called
LoXSTerminalManager. The maximum number of LoXS terminals managed by a
LoXSTerminalManager is not limited. In practice however, the maximum number of LoXS
terminals strongly depends on the AEpu platform capabilities (see also the LoXS Integrator
AEbc description). The figures listed below are advised maxima, but cannot be guaranteed as
they depend on the locker system usage. Furthermore, these figures assume that one
LoXSTerminalManager AEbc and no other components are deployed at this AEpu.

AEpu control board type: Maximum nr of managed LoXS terminals:

Compulab 586 10
Nedap AX8004 (XScale) 50
Nedap AX8008 (Sheeva) 100
Virtual AEpu 2000

 Using LoXS terminals for short-term or permanent lockers can be combined with the AP1013
for cabinet access control (using the LoXS Integrator) in the same AEOS system.

4.1.2. LoXS terminal requirements

LoXS terminal III firmware needs to be version 3.32 or higher.
LoXS terminal IV firmware needs to be version 4.26 or higher.
The LoXS terminal required a fixed IP address.

4.1.3. Lock requirements

The firmware of the lock needs to be:
 Locker unit III: Firmware version 2.26 or higher
 Locker unit IV: Firmware version 3.15 or higher
 Mifare lock: Firmware version 3.36 or higher
 Mifare Flush lock: Firmware version 3.36 or higher
 Locker unit Smart: Firmware version 1.16 or higher

Manual version 15 18/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

System set-up
Carry out the following steps to use the locks connected to LoXS terminals:
Step
Mount and connect the locks as described in chapter 2.
01
Step Configure the LoXS terminals (IP settings, AEOS compatible mode, Third party reader,
02 etc.).

Step Use AEmon to deploy the LoXSTerminalManager (add the LoXS terminals with their
03 correct settings).

Step
Perform actions on AEOS to set up the LoXS terminals.
04
Step
Lockers can now be assigned to carriers.
05

Manual version 15 19/32

 Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

LoXS terminals
Only the most important aspects are discussed in this chapter. For detailed information on how
to configure the LoXS terminal, please see the document LoXS IV User Manual for instructions.
If the terminal is configured for locker unit Smart change the function of the info reader into an
unlock reader by deleting the info reader and adding the unlock reader with the same address.

The LoXS terminal must be configured as ‘AEOS compatible’ using its menu interface. If the LoXS
terminal is of version 3.22 or lower and used in ‘non AEOS compatible’ mode, the customer code
of the badges that have been used at this LoXS terminal will be written in the locks. Please reset
the locks to factory defaults settings before using it in ‘AEOS compatible’ mode (see chapter 2.2).

Administrator menu
LoXS terminals needs at least one manager master key, otherwise the
Administrator menu will be shown. Master keys must be added in AEOS.

In the advanced setup, the following settings are required:

 Enable white list: Yes
 AEOS compatible: Yes
Also, make sure to select the appropriate card type (different types of Nedap
Advanced setup or Mifare cards). A Mifare configuration file needs to be copied to the LoXS
terminal Mifare if Mifare file sector or file data is required (see chapter 2.3).
All other settings are situation specific and may differ per customer or LoXS
terminal. These customer dependent settings are set by the LoXS technician.
If a 3rd party is connected to the LoXS terminal, the following settings are
required:
 Third Party Reader: Other (CR/LF)
 Baudrate: 1200 - 19200
 Databits: 5 - 8
 Parity: none / even / odd
 Stopbits: 1 - 2
 Reader Manufact No: e.g., 7
 Reader Subtype No: e.g., 1

Network setup The AEpu address to which the LoXS terminal is connected can be checked in
the network menu. Each LoXS terminal required a fixed IP address and uses
port number 33 and 34.

Manual version 15 20/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

AEmon software
The LoXS terminals are managed by an AEpu behaviour component called LoXSTerminalManager.
This component must be configured and deployed using the AEmon configuration tool. Each
LoXS terminal defined in the LoXSTerminalManager will appear in AEOS as an AccessPoint. The
name of each AccessPoint will be: [LoXSTerminalManager AEbc name]:[LoXS terminal name as
defined in the LoXSTerminalManager configuration].

Communication between the AEpu and LoXS terminals is over TCP. Each LoXS terminal listens at
fixed port number 34 and the communication is always initiated by the AEpu.

Each LoXS terminal requires a fixed IP address

The Display name is used when information about a LoXS terminal is shown in the LoXS
terminal display. For instance, persons may scan their badge if they have forgotten
their locker number. The LoXS terminal will then use the Display Name to refer the
person to the right LoXS terminal.

Detailed settings for the LoXS Terminal Manager can be found in the AEbc Integrator Descriptions
manual.

After deploying, the LoXS terminals are available in the AEmon – View - Hardware: (in example
below, other LoXS terminals are shown than added above):

A LoXS terminal can only make connection

to one LoXSTerminalManager.

Manual version 15 21/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

4.4.1. Third party readers

For third party readers, you can use the identifier type ‘Generic’ and manage its settings. To do
so, you need to know the badge number formats. Numbers of badges that have been presented
to the third party reader can be retrieved from the AEmon log, for example:

LockerData: badge read at reader= 0a0801000000008bf752aa

0a (numeric: 10) is the length of the byte string.

08 manufacturer code
01 badge sub type
000000008bf752aa badge number

Please note that in this situation the badge manufacturer number and the badge sub type in the
‘Terminal ‘screen must have the default value ‘0’. These parameters are set in the ‘Identifier type’
screen.

Enable the Data type filter box

byte 1 = manufacturer code, e.g., 8
byte 2 = badge sub type, e.g., 1
byte 3 = leave default, 255

Set badge number format, e.g., ‘Binary’.

Set bit position, e.g., ‘0’
Set badge number length, e.g., ‘64 bits’ (length of the byte string minus the first two bytes)

Manual version 15 22/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

AEOS User Interface

In AEOS, the deployed LoXS terminals must be added to LoXS Terminal Groups. These LoXS
Terminal Groups are used in LoXS terminal templates, in which is determined how many short-
term and permanent lockers of this group a person may use.

Locks LT1
Locks
Locks
LT2 LTGroup1
Locks
LT3 LTTemplate1

Locks LTGroup2
Locks LT4

LT5 LTTemplate2

Locks
Locks LT6 LTGroup3
Locks
LT7

Locks connected to LoXS Terminal Groups: a LoXS LoXS terminal Templates, define for
LoXS terminals terminal can be added to one each group how many short-term and
LoXS Terminal Group only permanent lockers a person may use

The following actions must be taken in AEOS and are further explained in the following chapters:
1. Set maximum amount for the identifier type used by LoXS to 1.
2. Confirm added LoXS terminals (identical to adding confirmed AccessPoints).
3. Create LoXS terminal groups.
4. Define LoXS terminal templates, to determine how many short-term and permanent lockers
may be used per person.
5. Create free field to select who is allowed to have a LoXS master key .
6. Define LoXS master keys.

After these steps, the LoXS terminals are ready to be used. This means you can:
 Assign lockers to carriers according LoXS Terminal Templates
 Check which lockers are in use
 Unlock, block or deblock lockers

4.5.1. Set maximum amount of identifier to 1

For using LoXS terminals, the amount of badges allowed for one carrier must be limited to 1 for
the used badge type (Administration – Maintenance – Identifiers – Set maximum identifiers).

Manual version 15 23/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

4.5.2. Confirm added LoXS terminal

The configuration of LoXS terminals is similar to the configuration of AccessPoints:

Step Start by confirming the LoXS terminals (AccessPoints) in Configuration – Maintenance –

Confirm AccessPoints. In this menu, you can see the LoXS terminals configured in the
01 AEpu.

Step After confirming the LoXS terminals, you need to add them to a LoXS terminal group.
This can be done in Configuration – Maintenance – LoXS terminal groups. The handling
02 is similar to handling entrances.

Step
Select Synchronize LoXS lockers to synchronize the data with this LoXS terminal.
03

4.5.3. Define LoXS terminal templates

A LoXS terminal template determines the amount of short-term and permanent lockers a person
may use in the concerning LoXS terminal groups. In Authorisation – LoXS terminal templates you
can add LoXS terminal groups to a template. You need to define the number of short-term and
permanent lockers a person may use per group. The maximum is the number of LoXS terminals
assigned in the group, as each LoXS terminal has a technical restriction that restrains persons
from having more than one locker per LoXS terminal.

It is possible to set a timer for the usage of a locker. You can enter the values in the fields Action
after (hours) and Continuation (hours). When the Action after time has expired, the locker will be
released, or blocked. You can select one of these options in the Action field. The timer starts on
the moment a user is assigned to a locker. With the continuation option, you can extend the
action time, starting at the moment the user opens and locks his locker.

Example: The Action after (hours) is set to 12 hours, the Continuation (hours) is set to 4 hours, and
the Action field is set to Release locker. A user claims a locker at 08.00 hours. With a release time
of 12 hours, he can use his locker until 20.00 hours. At 20.00 hours, if he has not used it, his
locker will be released. However, if he opens his locker less than 4 hours before the release time,
the time will be extended. So, when the user opens his locker at 17.00 hours, he can use it until
21.00. And would he open it again at 20:55 hours, he can use it until 00.55 hours. And so on.

Manual version 15 24/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Please note that the value of the Continuation (hours) field should not exceed the value of the
Action after (hours) field.

Only if the user leaves the building, after emptying his locker, this locker is available for the next
user. The time out for this can be set in the properties of the Terminal manager component with
the setting Key life time.

Select the LoXS terminal groups for which you need to change the number of lockers or the
timers:

4.5.4. Create free field to select who is allowed to have a LoXS master key
Each LoXS terminal requires at least one master key. A user with a master key has additional
rights (depending on the type of master key), but cannot claim or assign a locker with the master
key. Two different types of LoXS master keys can be assigned, which give the following rights for
the LoXS terminals in their group:

1. Master key – Locker

 Opening any locker in this LoXS terminal group (either by holding the master key close to
the lock or via the menu in the LoXS terminal).
 Blocking or unblocking lockers via the menu in the LoXS terminal (we recommend to block
or unblock via AEOS, and not via the LoXS terminal menu. See chapter 4.5.7 for details).

2. Master key - Manager

 Opening any locker in this LoXS terminal group (either by holding the master key close to
the lock or via the menu in the LoXS terminal).
 Blocking or unblocking lockers via the menu in the LoXS terminal.
 Access to all other menus (including technical setup) in the LoXS terminal.

Manual version 15 25/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

A master key can only be assigned to carriers that are marked as ‘master’ (by ticking a checkbox,
defined by a free field) in the announce screen. This free field is a ‘yes/no’ data type and must be
assigned for this function with System Property 25.02.
Please follow these steps to create this free field:

Step Administration – Maintenance - Free fields

Define a free field with Data type Yes/No (Name and Category can be chosen freely).
01

Step Management – System users – Maintain users

Leave the default settings, to ensure that this free field will default be not visible.
02

Step Administration – Maintenance - Settings – System properties

Select the define free field.
03

4.5.5. Assigning LoXS master keys

To assign a LoXS master key to a carrier, go to the LoXS master key menu (Person –
Employee/Visitor/Contractor - Assign LoXS master key) and select the carrier (only the carriers that
have the abovementioned free field activated are shown). Assign the master type and LoXS
terminal groups to this carrier.

Master keys assigned to a LoXS terminal group cannot use a locker at these LoXS
terminals.

Manual version 15 26/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

4.5.6. Assigning lockers to carriers

You can authorize a person for a LoXS terminal template in the announce screen for visitors,
employees and contractors. The template determines at which LoXS terminal groups short-term
lockers may be claimed or permanent lockers may be assigned. If a Template is assigned, the
carrier can claim his own short-term locker at the concerning LoXS terminals during the selected
period of the Template.

The announce screen:

With the more sign (>>), the Template can be changed and permanent lockers can be assigned (in
the Maintain Profile screen).

In the “Maintain Profile” screen, you can issue additional templates and permanent lockers. It is
not possible to have overlapping templates: this means that it is not allowed to have a template
that contains a LoXS terminal that is already in a assigned template. Issuing permanent lockers is
done in this screen. You can only issue permanent lockers of those LoXS terminals that you are
authorized for. The LoXS terminal should be in one of the abovementioned templates.

The “Maintain Profile” screen:

Permanent lockers from this LoXS terminal group can be assigned

with the Add button in the rental lockers menu.

All available LoXS terminals in this profile and the free lockers
connected to the corresponding LoXS terminals are shown at the
bottom part. At the top, the already assigned lockers are shown.

Only those LoXS Templates that are allowed (regarding

the used LoXS Terminal groups) are shown, preventing
inconsequent situations (a LoXS terminal group can be
used in several LoXS Templates).

Manual version 15 27/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

4.5.7. Lockers status overview and unlock, block and deblock

Go to Entrance – LoXS terminal for one of the following menus:
 Overview lockers: retrieve an overview of the lockers.
 Provide access: unlock selected lockers.
 (de)block locker: block or deblock selected lockers.

After selecting one of the abovementioned menus, select the LoXS terminal for which you need
to see the information.

Overview lockers
You can see an overview of all lockers using the columns Name, Carrier blocked, Identifier,
Identifier assigned, Identifier assigned, in which among others the following information is
showed:
 Present: the locker is online if present is ticked.
 Identifier number: if an identifier number is shown, but no Name, then the identifier of this
person been removed, and this locker can be de-blocked manually.
 Blocked: Locker is blocked via AEOS front-end.
 Block status: status according to the LoXS terminal. This status may differ from the ‘blocked’
status, if the locker is blocked via the LoXS terminal. The corresponding locker will be shown
in orange if the status in AEOS (Blocked) is not equal to the status of the LoXS terminal (Block
status).

Manual version 15 28/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Provide access
For unlocking, select the lockers and press the Unlock button. The lockers will be unlocked for the
time set in ‘unlock time long’ in the advanced setup menu in the LoXS terminal.

(De)block locker
Select the lockers and press the block or de-block button. If a locker is blocked, a block reason can
be stated. Block reasons can be defined at Administration – Maintenance – Lock reasons.

4.5.8. Reload LoXS terminal

Go to Entrance – LoXS terminal – Reload LoXS terminals to reload all authorizations to all
terminals in the selected LoXS terminal group.

4.5.9. Remove LoXS terminals

Go to Configuration – AccessPoints if you want to remove one or more LoXS terminals from
AEOS. Select the LoXS terminals you want to delete and click 'Delete selection'.

Manual version 15 29/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

4.5.10. Replace an AEpu

Replacing an AEpu with a new one without losing allocation data can be done as follows:
Step
Place the new AEpu and enter the same AEpu name as the previous one.
01
Step
In AEmon, restore the configuration.
02
Step In AEOS front end, go to Configuration – LoXS terminal group, select a group and
03 synchronize the lockers for this AEpu.

Step
Check the status in Entrance – LoXS terminal – Overview lockers.
04

4.5.11. Move terminals

If you want to move a terminal from one AEpu (A) to another (B) without losing allocation data,
you need to take the following steps:
Step
Make a note of all lockers that are blocked and the associated block reasons. The block
01 reason cannot be moved to the new AEpu

Step
Remove the network cable from the terminal.
02
Step
In AEmon, deploy a new Terminal manager on an AEpu (B).
03
Step Add the terminal with the exact same name and IP address as the previous AEpu (A) and
04 enable.

Step
Confirm this AccessPoint in the AEOS front end.
05
Step
Add this LoXS terminal to the existing locker group.
06
Step
Disconnect AEpu A from power or Ethernet (the AEpu where this terminal came from).
07
Step Remove the old terminal from the locker group, confirm that everything will be erased
08 and click OK.

Step
Remove the old terminal in Configuration – AccessPoints.
09

Manual version 15 30/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Step
Reload the terminal at the new AEpu (B) in Entrance – Reload LoXS terminal.
10
Step
Connect the Terminal to the network.
11
Step
In Configuration – LoXS terminal group, synchronize the LoXS lockers.
12
Step
Check the status in Entrance – LoXS terminal – Overview lockers.
13
Step Go to Entrance –LoXS terminal - (De-)Block or release locker and update the locker state
14 as from point 1.

Step
Re-connect AEpu (A) and use AEmon to remove the old terminal.
15
Step
Test the system for short term locker, permanent locker and Master key.
16

Manual version 15 31/32

Installation and Configuration | AEOS Locker Management AP1013 and LoXS terminals EN

Copyright
Copyright© Nedap 2018 Contents subject to revision without
prior notice.
Nedap AEOS is a registered trademark of N.V. Nederlandsche
Apparatenfabriek ‘’Nedap’’. The information in this document is
subject to change without notice. All other trademarks belong to
their respective owners.

Disclaimer
Nedap has made every effort to ensure the accuracy of the
information contained in this document. However, Nedap makes
no representations or warranties whatsoever whether express or
implied as to the accuracy, correctness, currency, completeness or
fitness or suitability for any purpose of such information and
therefore disclaims to the maximum extent permitted by
applicable law any and all liability for any error, damage, loss,
injury or other consequence which may arise from use in any
manner of any information contained in this document. Nedap
makes no commitment to update or keep current the information
in this document and reserves the right to make improvements to
this document and/or the products described therein at any time
without notice.

Nedap Security Management

P.O. Box 103
NL - 7140 AC Groenlo
+31 (0)544 471 111
[email protected]
www.nedapsecurity.com

Manual version 15 32/32