flexx16

Wiring & Installation

Instructions
V22/08/06
 proxSafe flexx16

© Copyright 2006 by deister electronic GmbH

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system,
or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording,
or otherwise, without prior written permission of deister electronic GmbH.

deister electronic GmbH reserves the right to make changes to any and all parts of this
documentation without obligation to notify any person or entity of such changes.

May 2006 JR/BF

deister electronic GmbH

Hermann-Bahlsen Str. 11
30890 Barsinghausen
Germany
Phone: +49 (0) 51 05 - 51 61 11
Fax: +49 (0) 51 05 - 51 62 17
E-Mail: [email protected]
Web: www.deister.com

2 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

Contents
1. Technical data ..................................................... 5
1.1 Electrical characteristics.............................................................................. 5
1.2 Customer interfaces ................................................................................... 5
1.2.1 Communication and Power ........................................................................ 5
1.2.2 Motor module ........................................................................................... 6
1.2.3 Emergency unlock ..................................................................................... 6
1.3 proxCylinder selection ................................................................................ 6

2. Wiring diagram ................................................... 7

2.1 Configuration............................................................................................ 7
2.2 Air interface .............................................................................................. 7

3. General ............................................................... 8

4. Operating hints ................................................... 9

4.1 keyTag release .......................................................................................... 9
4.2 keyTag return ............................................................................................ 9

5. Implementing of deBus ....................................... 9

5.1 General.................................................................................................... 9
5.2 Routing..................................................................................................... 9
5.3 Polling .................................................................................................... 10
5.3.1 Polling Request........................................................................................ 10
5.3.2 Answer no data ....................................................................................... 11
5.3.3 Answer Transponder data ......................................................................... 11
5.3.4 Answer Transponder left proxCylinder ........................................................ 12
5.4 Set Outputs............................................................................................. 12
5.4.1 Organisation of output area ..................................................................... 12
5.4.2 Set LED1................................................................................................. 13
5.4.3 Set Rel16 ................................................................................................ 13
5.4.4 Answer proxSafe ...................................................................................... 13
5.5 Get Status............................................................................................... 13
5.5.1 Errorcode................................................................................................ 13
5.5.2 Status ..................................................................................................... 13
5.5.3 Status of end switch for keyTag ................................................................. 13
5.6 Status of proxCylinders ............................................................................. 14
5.6.1 Example: Low voltage and keyTag in proxCylinder 6 ................................... 14
5.6.2 Example: ProxCylinder 15 and proxCylinder 16 not active ........................... 14
5.7 Device specific commands........................................................................ 14
5.7.1 Get Image .............................................................................................. 14
5.7.2 Get Transponder from proxCylinder .......................................................... 15
5.8 Message prefixing.................................................................................... 15

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 3

 proxSafe flexx16

5.8.1 Prefix: Pfx_CmdCount .............................................................................. 15

6. Emergency unlock ............................................. 17

7. Regulatory Notices ............................................ 18

4 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

1. Technical data
1.1 Electrical characteristics
UB: 13,8V
In: 50mA
Imax: 700mA (if one of the proxCylinders is activated)

1.2 Customer interfaces

Figure 1: interfaces

1.2.1 Communication and Power

TTL deBus, 9600 Baud, 1 Startbit, no parity, 1 Stopbit
RJ45 Connector
MUX IN: Data and power line from flexxBackplane.

Pin Description
1 nc
2 nc
3 GND
4 GND
5 +UB (13,8V)
6 +UB (13,8V)
7 TxD
8 RxD

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 5

 proxSafe flexx16

1.2.2 Motor module

MOTOR: Data and power line to optional motor module.

Pin Description
1 nc
2 nc
3 GND
4 GND
5 +UB (13,8V)
6 +UB (13,8V)
7 RxD
8 TxD

1.2.3 Emergency unlock

8-Position Field Wiring Connector, green RM3.5
(see Figure 1)

Pin Description
1 GND proxCylinder 5-8
2 +UB (13,8V)
3 GND proxCylinder 1-4
4 +UB (13,8V)
5 GND proxCylinder 13-16
6 +UB (13,8V)
7 GND proxCylinder 9-12
8 +UB (13,8V)

This feature could only be used in combination with proxCylinders which supports
emergency unlock via RJ45.

1.3 proxCylinder selection

There are several types of proxCylinders.
Some of them (hardware version 060504 and higher) supports emergency unlock via
RJ45.
For those type of proxCylinder the jumpers of the proxCylinder have to be set as follows:

Figure 2: jumper settings for proxCylinder with emergency unlock via RJ45

6 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

For the other type of proxCylinder the jumpers of the proxCylinder have to be set as
follows:

Figure 3: jumper settings for proxCylinder without emergency unlock via RJ45

2. Wiring diagram
The deBus supports a maximum of 32 devices. The amount of necessary power supplies is
depending on the application (e.g. if shutters are used or not). In this example an SNG3
adapter is used to connect the data line to the HOST.

2.1 Configuration
Only device address is configurable.
The device address is depending on the used jack of the flexxBackplane where the flexx16 module is
connected to.
Possible device addresses: 0x25,0x26,0x27...0x2C

2.2 Air interface

Frequency: 125KHz
Bitrate: 4Kbit

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 7

 proxSafe flexx16

3. General
proxSafe flexx16, flexx8, flexxMot and flexxBackplane are part of a keyTag management
system.
flexx16, flexx8 and flexxMot modules could only be used in combination with a
flexxBackplane.
For controlling a shutter an optional flexxMotor module is available. The flexxMotor
module could be connected to the flexxBackplane, to the flexx16 or to the flexx8.
Up to eight modules could be connected to one flexxBackplane.
With a proxSafe flexx16 module up to 16 proxCylinders could be handled.
With a proxSafe flexx8 module up to 8 proxCylinders could be handled.
Connection of the proxCylinders is done by RJ45 connectors.
Each proxCylinder contains of the following devices:

• Relay for keyTag release

• Coil for keyTag identification
• Red LED for optical signalisation
• End switch for detecting, if the proxCylinder is occupied

UB: 13,8V

proxSafe flexxBackplane has a serial interface for communication:

RS485, 9600 Baud, no parity, one stop bit

Protocol: deBus

The following parts of the proxSafe flexx16 can be controlled by the host:

• Red LEDs proxCylinders

• Relay proxCylinders

Following states are controlled by the flexx16 module:

• Low voltage
• Voltage on antenna of the proxCylinders (only after reset or after command “Get
Image”)

8 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

4. Operating hints
4.1 keyTag release
A keyTag has been taken, if the corresponding end switch is open. For take-out of
keyTags, the relay of the corresponding proxCylinder must be activated. It's useful to
activate the corresponding red LED at the same time. After the keyTag has been taken, the
corresponding red LED and relay are deactivated automatically by the proxSafe. After a
polling request, a zero transponder will be sent for this location.

4.2 keyTag return

A keyTag has been returned, if the transponder could be read and the corresponding end
switch is closed. In this case the corresponding red LED is activated automatically by the
proxSafe for a short time. After a polling request, the transponder number will be send for
this location. If a transponder could be read but the corresponding end switch is still
open, the response depends on the status of the cabinet. If the cabinet is open, there is no
response. If the cabinet is closed, the transponder number will be sent after a polling
request. In this case the first bit of the reader status is set.

5. Implementing of deBus
5.1 General
In order to communicate with the flexx16 module, the routing mechanism has to be used,
because the flexx16 module is not connected directly to the host.
The address of the flexx16 module is variable. The device address is depending on the
used jack of the flexxBackplane where the flexx16 module is connected to.
Possible device addresses: 0x25,0x26,0x27...0x2C.
5.2 Routing
Assuming device address of flexxBackplane, were requested flexx16 module is connected
to, is 0x21and the flexx16 module is connected to jack Flexx1 of the flexxBackplane, that
means device address of flexx16 module is 0x25.
A polling request should be send to the flexx16 module.
If the flexx16 module is connected directly to the host, the message looks like follows:

SOC DST SRC MSG CRCL CRCH STOP

FD 25 11 0B B8 F4 FE

In this case the flexx16 module is connected to the flexxBackplane and the flexxBackplane
is connected to the host. For this reason the message have to be modified:
The destination address (DST) has to be replaced by the address of the device which is
directly connected to the host (in this example 0x21, which is the device address of the
flexxBackplane).

SOC DST SRC MSG

FD 21 11 0B

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 9

 proxSafe flexx16

Two additional parameters have to be inserted before field MSG.

First parameter is PFX_Route (0x32) which shows the device, that the following message
has to be routed to another device.
Second parameter is the address of the device where the message has to be routed to (in
this example 0x25, which is the device address of the flexx16 module).
The modified part of the message looks like follows:

DST SRC PFX_Route ADR MSG

21 11 32 25 0B

DST Device address of the device which is directly connected to the host (in
this example flexxBackplane).
SRC Source address.
PFX_Route Information, that the following message have to be routed to the device
with the device address ADR.
ADR Device address of the device where the following message have to be
routed to.
MSG Start of the original message.

The answer of such a message is also modified.

PFX_Route ERRr ADR MSG ERR

32 00 25 0B 00

PFX_Route Information, that the following message is routed from the device with
the device address ADR.
ERRr Error code of the routing process.
ADR Device address of the device where the following answer comes from.
MSG Start of the original answer.

5.3 Polling
5.3.1 Polling Request

SOC DST SRC PFX_Route ADR MSG CRCL CRCH STOP

FD 21 11 32 25 0B 61 22 FE

10 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

5.3.2 Answer no data

This answer will be send if all status changes are transmitted.

SOM DST SRC PFX_Route ERRr ADR MSG ERR

FB 11 21 32 00 25 0B 00
CRCL CRCH STOP
D7 53 FE

5.3.3 Answer Transponder data

This answer will be send if one of the proxCylinders detects a new keyTag.

SOM DST SRC PFX_Route ERRr ADR MSG ERR

FB 11 21 32 00 25 40 00
LOC RST TST LEN D7 D6 D5 D4
28 0C 00 40 40 01 2D FA
D3 D2 D1 D0 CRCL CRCH STOP
00 30 39 D0 ED 8E FE

ADR: 0x25 => Answer comes from flexx16 module with device address 0x25
MSG: 0x40 => TagData
ERR: 0x00 => No alert
LOC: 0x28 => Transponder in proxCylinder 6 of 16
Bit 2...0:
Subsystem Location, in this case 000b
Bit 7...3:
Channel, here proxCylinder number starting with zero => 00101 =>
proxCylinder 6
RST: 0x0C => Valid and new data like V-Protocol
Bit 0 = 1: Transponder was read, but end switch is open and cabinet closed
Bit 0 = 0: Transponder was read and end switch is closed
Bit 2 = 1: Data valid
Bit 3 = 1: New Data
TST: 0x00 => Transponder status always 0x00
LEN: 0x40 => Amount of transmitted bits = 64 => 8 Byte
D7...D0: Transponder data

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 11

 proxSafe flexx16

5.3.4 Answer Transponder left proxCylinder

This answer will be sent, if a keyTag has been taken:

SOM DST SRC PFX_Route ERRr ADR MSG ERR

FB 11 21 32 00 25 40 00
LOC RST TST LEN D7 D6 D5 D4
28 00 00 40 00 00 00 00
D3 D2 D1 D0 CRCL CRCH STOP
00 00 00 00 1E C4 FE

ADR: 0x25 => Answer comes from flexx16 module with device address 0x25
MSG: 0x40 => TagData
ERR: 0x00 => No alert
LOC: 0x28 => Transponder in proxCylinder 6 of 32
Bit 2...0: Subsystem location, here 000b
Bit 7...3: Channel, here proxCylinder number => 00101b => proxCylinder 6
RST: 0x00 => Zero transponder
TST: 0x00 => Transponder status here always 0x00
LEN: 0x40 => Amount of transmitted bits = 64 => 8 Byte
D7...D0: Transponder data, here zero transponder

5.4 Set Outputs

The keylock can be controlled by the command “Set Outputs”. Otherwise the control of
the lock is connected with the control of the motor. This means, that the keylock will be
unlocked automatically before opening of the proxSafe. In order to close the cabinet,
the parameter must be set to FFh. In order to open the cabinet, the parameter must be
set to 00h. The actual status of the motor and the keylock can be requested by the
“Get Status”-command.

5.4.1 Organisation of output area

StdIo:Bit 0: -
Bit 1: -
Bit 2: -
Bit 3: -
Bit 4: -
Bit 5: -
Bit 6: -
Bit 7: -
Rel3…Rel0: Relay proxCylinder 31 … proxCylinder 0 (MSB first)
Led3…Led0: LED proxCylinder 31 … proxCylinder 0 (MSB first)

12 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

5.4.2 Set LED1

SOC DST SRC PFX_Route ADR MSG Status
FD 21 11 32 25 0F FF
StdIo Rel3 Rel2 Rel1 Rel0 Led3 Led2
00 00 00 00 00 00 00
Led1 Led0 CRCL CRCH STOP
00 01 2C 61 FE

5.4.3 Set Rel16

SOC DST SRC PFX_Route ADR MSG Status
FD 21 11 32 25 0F FF
StdIo Rel3 Rel2 Rel1 Rel0 Led3 Led2
00 00 00 80 00 00 00
Led1 Led0 CRCL CRCH STOP
00 00 07 75 FE

5.4.4 Answer proxSafe

SOM DST SRC PFX_Route ERRr ADR MSG ERR
FB 11 21 32 00 25 0F 00
CRCL CRCH STOP
D7 53 FE

5.5 Get Status

SOC DST SRC PFX_Route ADR MSG CRCL CRCH STOP
FD 21 11 32 25 0D CB F4 FE

5.5.1 Errorcode
Bit 0: 1 => Low voltage
Bit 4: 1 => Power supply error

Note:
The low voltage flag is set and reset automatically by the multiplexer. If the voltage is less
than 11V, the low voltage flag is set, otherwise the low voltage flag is reset.

5.5.2 Status
Status is fixed to 0x02 (device is open).

5.5.3 Status of end switch for keyTag

The status of the end switches for the keyTags will be transmitted in KeyTag3...keyTag0
with MSB first. If the end switch is closed (keyTag inside),a zero bit is transmitted,
otherwise a one bit is transmitted. Example: If proxCylinder 16 is occupied, bit 7 of
KeyTag1 is 0.

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 13

 proxSafe flexx16

5.6 Status of proxCylinders

The status of the proxCylinder will be transmitted in proxCylinder3...proxCylinder0 with
MSB first. If the bit is set (=”1”), the corresponding proxCylinder is active. If the bit is not
set(=”0”), the corresponding proxCylinder is defect or not present.

5.6.1 Example: Low voltage and keyTag in proxCylinder 6

SOM DST SRC PFX_Route ERRr ADR MSG ERR
FB 11 21 32 00 25 0D 01
Status keyTag3 keyTag2 keyTag1 key prox prox prox
Tag0 Cylinder3 Cylinder2 Cylinder1
02 FF FF FF DF 00 00 FF
prox CRCL CRCH STOP
Cylinder0
FF E4 26 FE

In this example bit 1 of error are set => Supply voltage is too low. Bit 5 in byte keyTag0
is zero => the end switch in proxCylinder 6 is closed.

5.6.2 Example: ProxCylinder 15 and proxCylinder 16 not active

SOM DST SRC PFX_Route ERRr ADR MSG ERR
FB 11 21 32 00 25 0D 01
Status keyTag3 keyTag2 keyTag1 key prox prox prox
Tag0 Cylinder3 Cylinder2 Cylinder1
02 FF FF FF FF 00 00 CF
prox CRCL CRCH STOP
Cylinder0
FF D7 F0 FE

In this example bit 6 and bit 7 of proxCylinder1 are not set => proxCylinder 15 and
proxCylinder 16 are not active.

5.7 Device specific commands

5.7.1 Get Image
An internal device check of the proxCylinders is only done after reset of the proxSafe. To
enforce a check of the proxCylinders after reset, the “Get Image”-command must be sent.

SOC DST SRC PFX_Route ADR MSG CRCL CRCH STOP

FD 21 11 32 25 84 02 ED FE

14 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

5.7.2 Get Transponder from proxCylinder

This message can be used to obtain the ID of the keyTag in the requested proxCylinder (if
it is occupied):

SOC DST SRC PFX_Route ADR MSG prox CRCL CRCH STOP
Cylinder
FD 21 11 32 25 8C 00 3F ED FE

MSG: 0x8C => Get data from proxCylinder

proxCylinder: proxCylinder number (0…31) in this example 0

The transmitted data are the same as on polling request.

This answer will be sent, if a keyTag is inside the requested proxCylinder:

SOM DST SRC PFX_Route ERRr ADR MSG ERR

FB 11 21 32 00 25 8C 00
LOC RST TST LEN D7 D6 D5 D4
28 0C 00 40 40 01 2D FA
D3 D2 D1 D0 CRCL CRCH STOP
00 30 39 D0 86 57 FE

See chapter 5.3 for further details.

5.8 Message prefixing

Any regular message / command can be modified by putting a prefix in front of the
message. The prefix ID and the prefix data are inserted behind the SRC address byte and
before the CMD of the basic message (see debus protocol description for further details).
This can be used for example to handle lost messages.

5.8.1 Prefix: Pfx_CmdCount

SOC DST SRC PFX_Route ADR Pfx Counter MSG …

FD 21 11 32 25 31 1 0B …

Pfx: 0x31 => Pfx_CmdCount

Counter: 0x01 => Command counter in this example 1
MSG: 0x0B => Message ID of the basic message (in this example polling request)

The counter in the prefix data field is used to send the job number of this message to the
addressed device. The job counter is for handling lost messages in a secure manner. If an
addressed device receives a prefixed message with Pfx_CmdCount, the device stores the
command counter. If the device receives the next prefixed message with Pfx_CmdCount,
the device compares the stored counter value with the newly received counter value. If
both values are equal, the device hereby knows, that the host did not receive the last
answer. In this case the device repeats the last message instead of executing the new
message. If a message is received by the host, the host increments the counter by one.

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 15

 proxSafe flexx16

The recommended start value for the host counter is one. For each device a separate
counter is needed.

Example:

A keyTag is returned. The number of the keyTag and the number of the corresponding
proxCylinder are transmitted only once after Polling Request. If this message is lost, the
host does not register the returned keyTag. To avoid this problem, it is recommendable to
use polling request combined with prefix Pfx_CmdCount.

In this example the polling request message is combined with prefix Pfx_CmdCount.
First polling request is transmitted with counter = 1:

SOC DST SRC PFX_Route ADR Pfx Counter MSG CRCL

FD 21 11 32 25 31 01 0B AF
CRCH STOP
1B FE

The addressed device answers with keyTag data. In this example the host has not
received the answer and repeats the polling request with counter = 1:

SOC DST SRC PFX_Route ADR Pfx Counter MSG CRCL

FD 21 11 32 25 31 01 0B AF
CRCH STOP
1B FE

The addressed device sends the same answer again independently of the transmitted
message. After receiving the answer, the host increments it's command counter and
sends the next request (in this example polling request):

SOC DST SRC PFX_Route ADR Pfx Counter MSG CRCL

FD 21 11 32 25 31 02 0B C7
CRCH STOP
31 FE

The addressed device received the message with the new counter value and executes
the received message.

16 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

6. Emergency unlock

This feature could only be used in combination with proxCylinders which supports
emergency unlock via RJ45 (see chapter 1.3)
If normal operation failed (e.g. processor does not work) to get keys out, an emergency
unlock is integrated.
The emergency unlock for the proxCylinders must now be activated separately as
follows:

To activate this emergency unlock, the jack must be connected to the emergency opening
box with the 8-pole cable (enclosed).
While this jack is connected and the switch of the emergency box is being pressed
constantly, all keys can be taken out.

Picture: emergency opening box with two different cables (one 2-pole-
cable and one 4-pole cable)

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 17

 proxSafe flexx16

7. Regulatory Notices
Europe

Hereby, deister electronic GmbH declares that this equipment - if used according to the
instructions - is in compliance with the essential requirements and other relevant provisions
of the RTTE Directive 1999/5/ EC.

A complete declaration of conformity can be requested at:

[email protected]

Approved for the use in all European countries.

18 deister electronic GmbH 30890 Barsinghausen Germany V22/08/06

proxSafe flexx16

Notes:

V23/03/06 deister electronic GmbH 30890 Barsinghausen Germany 19

 deister worldwide

Germany:
deister electronic GmbH
Hermann-Bahlsen Str. 11
30890 Barsinghausen
Tel.: +49 (0) 51 05 - 51 61 11
Fax: +49 (0) 51 05 - 51 62 17
[email protected]

www.deister.com

Great Britain: Belgium & Luxemburg:

deister electronic (UK) Ltd. deister electronic office
Stapleton Way, Enterprise Park Business Park E 19
Spalding, Battelsesteenweg 455/A
Lincolnshire PE11 3YQ 2800 Mechelen
Tel.: +44 (0) 1775 - 717100 Tel.: +32 (0) 15 - 28 09 68
Fax: +44 (0) 1775 - 717101 Fax: +32 (0) 15 - 28 09 71
[email protected] [email protected]

USA: The Netherlands:

deister electronic USA Inc. deister electronic office
9303 Grant Avenue Tolnasingel 3
Manassas, VA 22110 2411 PV Bodegraven
Tel.: +1 703 - 368 2739 Tel.: +31 (0) 1726 - 32970
Fax: +1 703 - 368 9791 Fax: +31 (0) 1726 - 32971
[email protected] [email protected]

Canada: France:
deister electronic Inc. deister electronic france
1099 Kingston Road, Suite 212 101 rue Pierre Semard
Pickering, ON L1V 1B5 92320 Chatillon
Tel.: +1 905 - 837 5666 Tel.: +33 (0) 1 47 - 35 78 78
Fax: +1 905 - 837 0777 Fax: +33 (0) 1 47 - 35 92 59
[email protected] [email protected]