EN

EN

Installation and Configuration

AEOS Message Mapper

Version 7 | 23-10-2017
Installation and Configuration | AEOS Message Mapper EN

Date Version Changes

23-10-2017 7 Lay-out
23-08-2017 6 Added section 3.6 - example 6 Datalogic barcode scanner
13-04-2016 5 Typo fix in picture section 4.2, new logo and icons
26-02-2016 4 Example with showing information on Alenco display added
21-04-2009 3 Free CAP fields and Export/Import (and document history) added
…
1 New document

Manual version 7 2/34

Installation and Configuration | AEOS Message Mapper EN

Contents
1. INTRODUCTION 4

2. MESSAGE MAPPER STRUCTURE 6

MESSAGE MAPPER SYNCS (INITIALIZE) 7
MESSAGE MAPPER SENDS COMMANDS TO DEVICE 7
MESSAGE MAPPER RECEIVES COMMANDS FROM DEVICE 9
COMPLETE EXAMPLE USING INTERCOMSERVER MESSAGE MAPPER 10

3. APPLICATION EXAMPLES 12
MESSAGE MAPPER EXAMPLE 1: SENT DATA (AEOS 2.2.1) 12
MESSAGE MAPPER EXAMPLE 2: SENT AND RECEIVE DATA (AEOS 2.2.1) 14
MESSAGE MAPPER EXAMPLE 3: PAGER SERVER (AEOS 2.2.5) 15
3.3.1. AEBC PROPERTIES: 17
MESSAGE MAPPER EXAMPLE 4: PAGER SERVER (AEOS 2.3.2) 19
MESSAGE MAPPER EXAMPLE 5: ALENCO DISPLAY 21
3.5.1. CONFIGURATION 21
3.5.2. SET DATA AT THE CORRECT LOCATION ON THE DISPLAY 23
MESSAGEMAPPER EXAMPLE 6: DATALOGIC BARCODE SCANNER. 25
3.6.1. SCANNER CONFIGURATION 25
3.6.2. AEPU CONFIGURATION 25
3.6.3. MESSAGE MAPPER 26
3.6.4. GENERAL 30

4. TRICKS AND HINTS 31

HOW POWERFUL IS THE MESSAGE MAPPER 31
ENTER MESSAGE IN IO SERVER 31
SORT ORDER IN MESSAGES IN IO SERVER 32
IMPORT / EXPORT MESSAGE MAPPER DATA (UP FROM AEOS 2.3.2) 32

Manual version 7 3/34

 Installation and Configuration | AEOS Message Mapper EN

1. Introduction
Detailed and latest information about the Message Mapper AEbcs can be found in the document:
AEbc Message Mapper Descriptions.
In this document several examples are given, using different AEOS versions. Pay attention that
the possibilities of the Message Mapper are depending on the used AEOS version.

The Message Mapper is a set of AEbcs:

• That translates labels (actions) to commands and vice versa
• Adds variable data (e.g., badge number, carrier name)
rd
• That can be used to link 3 party equipment to AEOS

Translate and
“Map”

Message
Mapping
AEbcs

The translation and Mapping of commands to actions is done by the Message Mapping AEbcs.
This category AEbcs can be divided into two different parts:
• Message Mapper AEbcs
o Generic Message Mapper (IOServer )
Generic Message Mapper for both Serial and IP commands
o IntercomServer
Message Mapper to communicate with an Intercom Server
o VideoServer
Message Mapper to communicate with a video server
o PagerServer
Message Mapper to communicate with a pager system

With 2.3.2 these AEbc are named Message Mapper

(e.g., Pager Message Mapper)

• Additional AEbcs for making the Message Mapper easier to work:

o InputToLabelValue
o LabelValueDemux
o LabelValueMux
o LabelValueToOutput
o LabelValueToString

• Additional properties in other AEbcs for sending variable data:

o BadgeToString (in which, e.g., carrier data can be transferred to a Message Mapper
String input)

In general the Message Mapper works as follows:

• At a string received a logical output can be activated
• At a logical input activated a string is send to the device

Manual version 7 4/34

Installation and Configuration | AEOS Message Mapper EN

• At the start-up of the AEpu some initial strings can be sent to the connected device
The received strings and data to be sent is all entered at the Properties of these AEbcs. The
Message Mapper AEbcs are capable of both sending and receiving data.

With the Message Mapper AEbcs it is easy possible to interface with other systems, and to inform
those systems about the status of the AEOS components, in which variable data, such as badge
data can be included.
Message Mappers can be deployed on normal (hardware AEpus) and virtual AEpus (on a PC) for
bigger configurations which need more processing power.

Manual version 7 5/34

 Installation and Configuration | AEOS Message Mapper EN

2. Message Mapper Structure

At the Properties of the Message Mapper
AEbc the type of Provider type must be
selected (in this example the connected
Intercom Provider type is the Command
GE Protocol.

At the first part the general settings are

done. These settings are the common
interface settings.

At this part the Messages to the device

are made. At a retrieved label from input
a sequence is sent to device.
In this example as input Activator1
becomes active the string
004000F101F10 etc is sent to the device.

This part determines that at a retrieved

sequence (Messages from device)
004000F101F10 etc a label CallFrom101
is sent to the output, including its state.

This part must be read from

right to left.

The last part is used for the initialization

of the connected device
(Synchronisation). The description is not
used, only for improving the readability.
In this example at the restart of the AEpu
the strings 004000F101F10280 and
004000F101F10280 are sent to the
device.

The Label names are connected to the LabelValueToOutput or InputToLabelValue AEbcs to get the
interface with other AEbcs or hardware.

Manual version 7 6/34

 Installation and Configuration | AEOS Message Mapper EN

Message Mapper Syncs (Initialize)

101

02
2

03
3

Sequence:
01 The AEpu starts
02 The AEbc sends all the Commands to the connected AEpack
03 The Commands are sent to the device using the defined communication protocol

The commands are sent sequential as defined in the AEbc, the command at the top as
first.

Message Mapper sends Commands to device

At the change of an input (can be physical or logical input) a (or more) commands are sent to the
device.
04

03
02

05

Input active: 004000F201F20380 + 00400044440004A3

01 05
Input passive: 004000F201FFFF80 + 00400044440000A3

Manual version 7 7/34

Installation and Configuration | AEOS Message Mapper EN

Sequence:

With this example in steps is shown how the change of an input results in sending a command to
the connected device:

01 An input is changed (in this situation on the AP1001)

02 Via the AEpack this hardware input is linked to the InputToLabelValue AEbc, in which for in1
a label (“string”) is defined (e.g., Start Recording)

03
The labels belonging to the input are at each change of
this input sent to the output of this AEbc (outda1), both
as the input becomes active and passive.
At the Message Mapper AEbc Properties the Outputs
are defined for each change of the received labels and
their state change (as the input becomes active and/or
passive) commands can be defined):
• post1 begin: active Command 004000F201F20380 must be sent
• post1 begin: passive Command 004000F201FFFF80 must be sent
• post1 begin: active Command 00400044440004A3 must be sent
• post1 begin: passive Command 00400044440000A3 must be sent

In this case two commands are sent as the post1 begin becomes active.
The AEbc sends all the Commands to the connected AEpack

As soon as a label with its state change is received, the command(s) belonging to this label
and its state are sent to the output (iser) of this AEbc.

04 The command(s) is sent to the communication channel (serial or TCP/IP)

05 The command(s) is received by the connected device and this device handles this command

• For each label at the Message Mapper AEbc (e.g., IntercomServer) command(s) can be
defined for the input getting active and command(s) for the input getting passive.
• On each change of an input more than one command can be defined.
• If more than one command is defined, the commands are sent in logical sequence as
they have been defined at the AEbc.
• There is ‘no’ limitation for the amount of commands to be sent.

Manual version 7 8/34

Installation and Configuration | AEOS Message Mapper EN

Message Mapper receives Commands from device

At the receipt of a string an output is made active or passive.

04

03

02

01

receive: 005B002222FFFF41 Out1 active:

01 05
receive: 005B002222FFFF40 Out1 passive:

Sequence:

01 A command string is received from the connected device at the AEpack

02 The AEpack sends this command to the Message Mapper AEbc (in this case the IntercomServer).
At the Message Mapper AEbc for each command that can be received from the external device
a label and a state is to be defined. At receiving a command, the AEbc is checking the defined
commands, at the associated command the label and state belonging to this command is sent
to the output (outda1)

03 At the Properties of this AEbc at the Inputs (Messages from

device) the command to be received is stated at the right part
of the screen. The corresponding actions (both Label name and
State) are defined at the left and middle part:
• Command 005B002222FFFF41 received: the label manual-UL-start becomes
active
• Command 005B002222FFFF40 received: the label manual-UL-start becomes
passive
The here defined Label name together with the belonging state is sent to the
LabelValueToOutput AEbc (in this example: manual-UL-start and depending on the received
string active or passive)

04 At the Properties of this LabelValuetoOutput AEbc, enter a value for each logical output of this
AEbc (Output 1 label ... Output 8 label). For Output 1 label in this example: manual-UL-start.
At the LabelValueToOutput the received labels are compared against the here defined
values. If they match the corresponding output will be changed, according to the state of the
label that is received.

Manual version 7 9/34

Installation and Configuration | AEOS Message Mapper EN

05 The state of the output is linked to another AEbc or as in this example directly to a physical
output
The correct state of the output is sent in this example to the AP1001
• Command 005B002222FFFF41 received: the label manual-UL-start becomes
active
Results that Out 1 becomes active
• Command 005B002222FFFF40 received: the label manual-UL-start becomes
passive
Results that Out 1 becomes passive
With AEOS version 2.3.2 a time can be stated in the properties for automatically make the
output passive after the stated time (Output x activation time).

1. The commands are read sequential as defined in the Message Mapper AEbc, this can
result that more than one action can be performed upon one received command.
2. For the Message Mapper AEbc you both have to define if an output becomes active
and passive, otherwise the output will never return to default. (With version 2.3.2 an
output activation time can be stated.)

Complete example using IntercomServer Message Mapper

At the example below the Message Mapper IntercomServer is used to activate the Intercom if an
Unauthorized badge is detected. Using the intercom the door is opened.

1. Both noa (No Authorised) outputs are OR-ed to the in1 of the InputLabelToValue.
2. This succeeds in the label post1 begin is sent to the IntercomServer.
3. The Intercom for the antenna where the unauthorized badge is been offered is activated
by the command received from the IntercomServer.
4. After the conversation between the person of the unauthorized badge and the guard or
receptionist the ‘Open button’ on the Intercom system is activated.
5. The IntercomServer receives the command belonging to the activation of the ‘Open
button’. (Also a command is received as soon as the button is released)
6. Using the LabelValueToOutput the maul (manual unlock) of the AccessPoint is activated
and the door is opened.

Manual version 7 10/34

Installation and Configuration | AEOS Message Mapper EN

1. The Intercom Message Mapper is specially developed for the Commend GE intercom
systems (Commend International GmbH).
2. When composing a Commend message, the string is automatically added with correct
checksum. See example beside.

Manual version 7 11/34

 Installation and Configuration | AEOS Message Mapper EN

3. Application examples
Below only a view examples are given. Many other applications can be build; e.g., sending
variable data to a serial port on the AEpack including Badgenumber or Not Authorised reasons.
Even a link made to the Socket Interface on the AEpu (version 2.3) is possible to check certain
data, optionally combined with substitution options. In case of request or more information
contact Nedap.

Message Mapper example 1: Sent data (AEOS 2.2.1)

In this example you can send commands with telnet to the AEpu to (de)activate RY1, RY2 and the
UL output. The result will be shown on the RS232 output.

The TCP settings are made at IOServer.1 and LabelValueToOutput.1 (see Properties below):
Following commands are programmed:
• a: RY1 is activated
• A: RY1 passive
• b: RY2 is activated
• B: RY2 passive
• on: UL is activated
• off: UL passive

The commands are given at TCP protocol with server event port 4001. The outgoing protocol is
disabled the message mapper is only listening to commands, no commands are sent.
For TCP connection: Open a dosbox and enter telnet <aepuname> 4001:

The serial settings are made at IOServer.2 (see Properties below). It receives its data direct from
LabelValueDemux (all data received by this AEbcs input is transmitted to all outputs)

On RS232 connection with HyperTerminal 9600,8,n,1: following text will show regarding the
action given at the TCP protocol:
• RY1 on: after sending the a and RY1 becomes active
• RY1 off: after sending the A and RY1 becomes passive
• RY2 on: after sending the b and RY2 becomes active
• RY2 off: after sending the B and RY2 becomes passive
• INIT …. after deploy/ start AEpu
The RS232 line (iser) is connected to the AEpack AP1001’s serial channel.

IOServer.1 (using IP) IOServer.2 (using serial)

Manual version 7 12/34

Installation and Configuration | AEOS Message Mapper EN

IOServer.1 (using IP) IOServer.2 (using serial)

Dataflow:
• On TCP terminal command is entered: e.g. b
• b is received at IO.Server.1 and looked up in the Inputs (Messages from device) part.
• if b is received, label out2 with state active must be sent to output (outda1) of this AEbc.
• The AEbc LabelValueDemux sents all received input to all outputs (outda1 ... outda4)
o At LabelValueToOuput the received string is checked against its Properties:
out2 is filled in at Output 2 label, so out2 of this AEbc is changed to the received
state (active), resulting that RY2 of the AP1002 becomes active.
o At IO.Server.2 a string out2 with its state is received (something is to be sent to
the external device) and looked up in the Outputs (Messages to device) part.
Behind the out2 – active the command RY2 on is found, and this command (text)
is sent to the output.
• At starting up (or reboot) the AEpu the Commands in the Syncs part are sent to the serial
port.

Manual version 7 13/34

Installation and Configuration | AEOS Message Mapper EN

Message Mapper example 2: Sent and receive data (AEOS 2.2.1)

In this example the text (Not) Authorised Badge, Direct Door Alarm, Door Open To Long and Door
Locked is send to the serial port and send by TCP to 10.4.108.53 port 8000. These texts
represent their equivalent action at logical outputs of the AEbc Standard Door.

HyperTerminal is connected to the serial RS232 port of the AP1001, as settings are used:
9600,n,8,1.
TCP connection: Open HyperTerminal on the receiving PC: Connect To: Host address
<aepuname> or <address>, Portnr: <remote event port>, connect using: TCP/IP (Winsock). After
OK: a message can come Unable to connect to <name> port <remote event port>, go to top menu:
Call and activate Wait for a call. Now HyperTerminal is ready to receive the data.

Remote event host name: PC receiving the commands.

Manual version 7 14/34

Installation and Configuration | AEOS Message Mapper EN

Dataflow:
• Due to an action on the Access Point one (or more) of the logical outputs are activated.
(For example the unl output, for unlocking the door.)
• At the InputToLabelValue the in1 is connected to the unl output of the StandardDoor.1. At
the Properties of the InputToLabelValue for the Input 1 Label the string unl is
programmed.
• Unl of the StandardDoor.1 becomes active, in1 of the InputToLabelValue becomes active.
The string entered in the properties of the InputToLabelValue and its state (unl – active) is
sent to outda1 of this AEbc.
• On this outda1 two IOservers (inda1) are connected:
o IOserver.1 is used for the serial communication
o IOserver.2 is used for the TCP communication
At the part Outputs (Messages to device) the received string and its state are looked up,
and the string behind the match(es) will be sent (Authorised Badge).

1. In this example only messages are generated if the output of the StandardDoor
becomes active.
2. With this example you can easily make different messages for the Serial and the TCP
connection (because they are different IO severs).
3. At the Generic TCP Protocol the Keep outgoing socket alive is activated otherwise
after each message send the connection is closed.

Message Mapper example 3: Pager Server (AEOS 2.2.5)

The Pager Server is used to send messages to a Pager system. In this example a message is sent
to the Pager system, in which the person’s name is included in the message to the Pager. So when
an alarm occurs on the Pager directly is visible who has been generating the alarm and at which
door.
For other situations the Pager can be used to send a message to a Pager if a door stays open too
long, etc., etc. It is just how creative you are with using the AEbcs.

In this example following starting points are used:

• Door open, authorized badge is detected.
• Any authorized badge will activate the corresponding relay. This will lock the door.
• If door is closed, no alarm is generated, even if an authorized badge is detected.
• Badge number and Door name is included into the message.
• More than one AccessPoint can be connected to one Pager Server.

Manual version 7 15/34

 Installation and Configuration | AEOS Message Mapper EN

Just as the other examples, below just one possibility is given. It is to the user what information
and flow is used, it is just a matter a being creative with the available AEbcs and their properties.

Resets data on the

String Inputs

Serial channel
where Pager is
connected

Message is only sent if: Badge data output of all AccessPoints Pager Server is connected
- Door is Open is combined in the BadgeMux. At the by the Serial port of one
AND BadgeToString is determined what of the AEpacks to the
- Authorized badge is detected part and how the badge data must be communication port of
OnDelay is needed to be sure that other data included in the string to be sent the Pager Equipment
(badge data) is available at the Pager Server

The BadgeToString (by the BadgeMux) receives the badge data from both AccessPoints, this data
is sent to Strng1 of the Pager Server.
As the door is open and an authorized badge is detected (AND-2 ports), the InputToLabelValue
sends the corresponding data to inda1 of the Pager Server. This triggers the Pager Server to send
the data by iser to the Serial channel of the AEpack (and to the here connected Pager system).

The Reset circuit (NOT.1, NOT.2 and XOR.1) is here used to be sure that old data is been
removed. In cases the AEpu cannot find the correct carrier corresponding data (as been
defined with the BadgeToString) this can be useful. Be sure if you want to use this Reset
circuit.

Manual version 7 16/34

Installation and Configuration | AEOS Message Mapper EN

3.3.1. AEbc Properties:

• For the AccessPoints in this example

following Properties are important:
- Unlock while door is open (output
must be activated at authorized
badge and alarm is given when door
is standing open)
- Read badge while door is open must
be active

Other properties can be changed according to the local situation.

• The labels as defined in the InputToLabelValue are used to determine what must be sent
in the Pager Server (these labels must be identical as in the Pager Server Properties,
Output part, Label name).

Manual version 7 17/34

Installation and Configuration | AEOS Message Mapper EN

• In the BadgeToString is determined what data must be sent. In this example the Carrier
attributes are sent at the txt output. From the Carrier attributes now the carrierName is
selected.

Properties Send badge type with badge data and Convert badge data to text are here not
important (only useful if Badge data is sent to the output).

• String input labels: For the substitution functionality: You can leave the default Label
names, but by changing them the Pager message will be more clearly to read. In this
example we use the client label to insert the Carrier name (of the Carrier attributes of a
badge) into the Pager message.
• At the IO-provider configuration the settings for the Pager unit must be sent.
• The Outputs (Message to device) generates the message, in this example:
o To pager number 12001 the message Door 1 with the client information is sent,
e.g.,

Door1 Peterson

Peterson is the owner of the badge that has been detected, this data is been
retrieved from the Carrier data (as defined in the BadgeToString). Pay attention
for using this substitution you must enter the label name between brackets, such
as: {client}.

Manual version 7 18/34

Installation and Configuration | AEOS Message Mapper EN

Message Mapper example 4: Pager Server (AEOS 2.3.2)

This example is almost identical to the above example (see chapter 3.3), with the difference that
with AEOS 2.3.2 the user can define a free field as CAP data (Carrier Attribute Person data).
For 2.3.2 only one free CAP field named Pager number can be linked in AEOS to one of the free
fields and then selected in AEmon (AEbc BadgeToString). The advantage now is that Carrier
related data, captured in a free field can now be used as variable data in the BadgeToString AEbc.

For achieving this:

• State if a free field can be used for CAP data:
Definition of the Free fields (Maintenance – Free fields – Free fields) the option Is CAP field
must be activated.

• Link one of the free fields to (only with Is CAP field active) to CAP field Pager number
(Maintenance – Free fields – Free fields CAP assignments).
For now only one CAP free field is available that can be sent to the AEpu.

• At AEmon, with the AEbc BadgeToString at the Properties in the Carrier attribute type the
PagerNumber can be selected.
The data field as linked to the Pager number CAP field will now be used.

Manual version 7 19/34

Installation and Configuration | AEOS Message Mapper EN

• At the Pager Message Mapper, the Pager number can now be selected with Use substitution.
In the example below this string is received at strng2 (Label2).

• At the announce screens the Free field data (as normally can be added). In this example the
field Call number is used as CAP data and is sent to the AEpu. With the BadgeToString this
data is as {Label2} integrated to the ESPA 444 Pager as the Pager number.

Usage of CAP data consumes AEpu memory and capacity. Be careful with CAP data for
larger systems. (Otherwise contact Nedap in case of any doubt.)

Manual version 7 20/34

Installation and Configuration | AEOS Message Mapper EN

Message Mapper example 5: Alenco display

In this example the Message Mapper is configured to control an Alenco
display (, e.g., of type: Multi Line Series).
The display can be used to show text and values from AEOS like for
instance the number of free parking spaces.
The basic for this example is a Counter, the Message Mapper and some
conversion AEbcs. (The Counter can easily be replaced by a CountManager for example).
Every change at the Counter will sent a value as text to the Message Mapper, this value will be
displayed at the Alenco display on the location that is programmed.

3.5.1. Configuration
In AEmon the configuration as below can be used to get the correct information on the Alenco
display.

• The NumberToString AEbc converts the data from the Counter AEbc to a string.
• The StringFormatter AEbc is used to set the number of digits always to a fixed length of 2,
e.g.:
01, 07, 15, 99, etc...
This is set by the Properties: Maximum length = 2 and Prefix = 0.

• At the Message Mapper AEbc set the following Properties:

o Set the Number of string inputs to 1 (this will add the label1 input to the AEbc).
o Change the String input labels from [label1] to [cnt] (select the edit box).
The name of this label [cnt] can be used in the Message Mapper to show its value,
changing it is optional, but advised for better readability.

Manual version 7 21/34

Installation and Configuration | AEOS Message Mapper EN

o By activating “Send message on string change” every new value on strng 1 is

processed by the Message Mapper.

The String input ‘Strng 1’transports the data string from the StringFormatter to
the Message Mapper.

o Select as IO Server type: Alenco (IP) Multi Line Serie so this AEbc uses the correct
protocol to connect to the Alenco display.
o Enter IP-address at the Remote event host name and port number at Remote event
port.

The general settings to connect to the Alenco display are made now. Next step is to embed the
data string (as generated by the Counter AEbc) in the commands needed to place the data on the
Alenco display. This is explained below.

Manual version 7 22/34

Installation and Configuration | AEOS Message Mapper EN

3.5.2. Set data at the correct location on the display

The string as received at input strng 1 can be placed on any location on the display, according to
the commands that are available by this display. For a complete set of commands and details we
refer to the Alenco product documents.

Setting the data on the display is controlled by the Parser control panel at the Message Mapper
Properties, when selecting the IO server type.
In this example we need to send data to the display, so the part for Outputs (Message to device)
must be filled.

• Use the Add button to an output message:

• By activating the select box behind Example text the Generic Message editor opens.

• Activate Use substitution, so the value of {cnt} (the label name as defined in String input
labels) that is recurrent at input Strng 1will be used in the message. This value is received
from the Counter (and is the string the user is interested in).
• Enter the display control bytes, the message you want to display and label {cnt} to show
the value of cnt.
f1 01 f1 f2 01 f2 f3 01 f3 fb 00 00 24 08 00 fb 4e 52 2e 7b 63 6e 74 76
The data represents:
For getting the info on the upper corner of the display we use following commands:
f1 01 f1 = Methods Control, 01 for direct display the text with no effect.
f2 01 f2 = Font Control, 01 for displaying the text with Font SS7.
f3 01 f3 = Colour Control, 01 for the default colour red.
fb 00 00 24 08 00 fb = This command has got more parameters then the other commands.
Syntax: Xposition YPosition Width Height Align.

Manual version 7 23/34

Installation and Configuration | AEOS Message Mapper EN

The following values can be selected for alignment.

00 - Horizontal=left vertical=top
01 - Horizontal=centre vertical=top
02 - Horizontal=right vertical=top
03 - Horizontal=left vertical=centre
04 - Horizontal=centre vertical=centre (default)
05 - Horizontal=right vertical=centre
06 - Horizontal=left vertical=bottom
07 - Horizontal=centre vertical=bottom
08 - Horizontal=right vertical=bottom

• Top left, is (x=0,y=0)

• Minimum width: 24
• Minimum height: 5
• Xposition, YPosition, Width and Height are noted as a Hexadecimal value.

4e 52 2e 7b 63 6e 74 76 = Text to be display (NR.) and {cnt} where the counter value is

presented.

Manual version 7 24/34

Installation and Configuration | AEOS Message Mapper EN

MessageMapper example 6: Datalogic barcode scanner.

This example describes a solution for entrances where barcode tickets
are used to get access. A guard scans a ticket and will then see either a
green or a red LED light on the scanner, representing the validation
result. Extra information is also displayed. In this example the PM9500
scanner and the BC9180-STAR cradle are used, connected to a LAN
network. The connection from the AEpu to the scanner runs via a socket
where the cradle is a listener. The scanned number passes to an access
point as an identifier. If the carrier the identifier belongs to is
authorised, the green LED will light up and an 'OK' message will be
displayed. If the carrier isn’t authorised, the red LED will light up and a
'Not authorized' message will be displayed.

3.6.1. Scanner configuration

To configure the scanner, use the Datalogic tool Aladdin. With this tool you can change for
example the IP address and the scan format. Another part of the configuration instructions can be
found in the document PowerScan PM9500 Two-Way Communications Tutorial. Follow the
instructions in this document, except the instruction regarding the Radio ID prefix setting
(CBTAS01). On the last pages, the different settings for beeps and leds are listed. Other settings
are documented in the document Powerscan PRG - 820053614 - jan 2017.

3.6.2. AEpu configuration

The main component in this configuration is the MessageMapper, establishing the connection to
the scanner and receiving the scanned barcode numbers from the scanner. Three label names
(UL, NA and INIT) are configured to send different messages, depending on the authorisations of
the presented identifier. A Pulse Generator and three Delays are added to clear the message on
the display after a timeout of 30 seconds. The correct settings for the Pulse Generator and the
Delays can be found in the AEbc descriptions.

The standard Access Point settings are:

• Unlock time= 1000ms
• Minimum Unlock Time=100ms
• Not Authorized time=1000ms

Manual version 7 25/34

Installation and Configuration | AEOS Message Mapper EN

• Set the Input To LabelValue properties as shown in the image below:

3.6.3. Message Mapper

• Set the MessageMapper properties as shown in the image below:

Manual version 7 26/34

Installation and Configuration | AEOS Message Mapper EN

• Select IO Provider Type 'Generic IP protocol'.

• Enter the scanner's IP address and remote event port number.
• Select Outgoing Protocol 'Full TCP' to enable communication in two directions. (The
Datalogic scanner is a listener).

Manual version 7 27/34

Installation and Configuration | AEOS Message Mapper EN

• Add a new line for Outputs.

• Enter the Label name 'INIT'.
• Click the 'Command' section to enter the hex data.

(12 1b 23 34 1b 5b 32 4a 2a 2a 20 20 20 20 20 20 20 2a 2a 1b 5b 36 71 1b 5b 35 71 1b 5b 37
71 20 0d)
The data starts with a DC2 (12 hex) in order to send messages directly to the scanner, without
scanning a label.

This message will clear the last message. It starts with selecting a large font (Esc#4) and clearing
the screen (Esc[2J). This is followed by turning on the green LED (Esc[6q), waiting for 100mSec
(Esc[5q) and then turning the green LED off again (Esc[7q).

These settings are only an example. They can be changed according to the client's demands.

Make sure that the string of data always ends with a Carriage Return (0d hex).

The next settings are for the 'OK' message and LED control.

(1b 23 34 1b 5b 32 4a 3e 3e 3e 20 4f 4b 20 3c 3c 3c 1b 5b 36 71 1b 5b 35 71 1b 5b 37 71 0d)

Make sure that the string of data always ends with a carriage return (0d hex).

Manual version 7 28/34

Installation and Configuration | AEOS Message Mapper EN

Below you'll find the settings for the 'Not Authorized' message:

(1b 23 34 1b 5b 32 49 6e 76 61 6c 69 64 21 21 21 1b 5b 34 71 1b 5b 38 71 1b 5b 35 71 1b 5b
35 71 1b 5b 35 71 1b 5b 35 71 1b 5b 35 71 1b 5b 35 71 1b 5b 35 71 1b 5b 35 71 1b 5b 35 71
1b 5b 35 71 1b 5b 39 71 0d)

There are several Esc [5q sequences to make the red LED light up a little longer.

Make sure that the string of data always ends with a carriage return (0d hex).

Manual version 7 29/34

Installation and Configuration | AEOS Message Mapper EN

Below you'll find the settings for the incoming data:

(2e 2a 5c 72)

The most important setting is Use message as label. It will send the incoming data to the output of
the message mapper. The ‘.*\r’ data is set to search for a Carriage return in the message as an end
of line. This is a so called regular expression, other parameter can be found on the internet.

• To establish a connection during the initialisation, enter the following data:

(20 0d)

3.6.4. General
To avoid scanning the same label a second time, at the same entrance or another, set Anti Pass
Back and\or blocking time for this access point. This isn’t described in this document and is more
general AEOS.

Manual version 7 30/34

 Installation and Configuration | AEOS Message Mapper EN

4. Tricks and Hints

How powerful is the Message Mapper
The Message Mapper can be a very power full tool to make a connection to other systems. It is
just depending on if there is an interface possibility between the AEbcs and this third party
system (can be IP or serial).
After making these connections, you can interface from all points inside your AEbc configuration
to inform the third party system. From this third party system you can interact with any location
(binding) inside your configuration. How powerful you can make the Message Mapper is just a
case of being creative using the AEbcs.

Enter message in IO Server

Entering data in the IO server fields to be received or send can be done at three different
locations in this field.

01 02

03

04

01 Click on this field and filling data in enables to enter hexadecimal characters (e.g., 0D for
Carriage return, or 03 for ETX)
02 Part two is used for all readable data
03 Part 3 is the same as part two, but can be easy to copy data.

04
With Use substitution the data according to the corresponding input {badge} is substituted
at this location (Property ‘String input labels’)

Manual version 7 31/34

Installation and Configuration | AEOS Message Mapper EN

Sort order in messages in IO Server

By clicking on the column header the data is sorted (Up or Down). So it is easy to sort, e.g., on the
Label name or Command.

Import / Export Message Mapper data (up from AEOS 2.3.2)

For Inputs and Outputs parts of the Message Mapper, data can be exported and imported. With
this option you can, e.g., export data to Excel, add simple and fast many new labels and import
the data again.

Advise: Add one Label name with Command at the normal way, use the Export and copy this line
in, e.g., Excel. This gives an example how the complete line must look.

Manual version 7 32/34

Installation and Configuration | AEOS Message Mapper EN

Manual version 7 33/34

Installation and Configuration | AEOS Message Mapper EN

Copyright
Copyright© Nedap 2017 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 7 34/34