© Nedap N.V.
Nedap Readers Installation Guide
Page 9 of 21
Accessor III /
SimpleXS
AC3/2TR
AB350
AX1011
The data from the cards read at the Convexs/Invexs is transparently sent (‘Direct transmission mode’) to
the AEpack. If both Nedap and Mifare cards must be read, use at the Access Point the Primarly and
Secondarly Identifier type (check your AEOS version if this is available).
At AEreco the output format must be configured as:
Nedap RF data
.
•
Not advisable, but with older firmware at the AEpack the Mifare cards must be converted to XS code,
The maximum label number 999.999 (in combination with a GF code). At the Access Point in AEOS the
XS Identifier is choosen. So now both Mifare (GF) and the Nedap XS cards can be identified.
XS cards will be transparently transmitted.
The chosen XS code may not be used already with existing XS cards.
At AEreco the output format must be configured as:
Nedap RF badge
.
Remark
: This option can at special request only be programmed at Nedap, so not with the standard
AEreco programm.
3.2.2.
RF output to Nedap XS readers for AEOS integration
Same as 3.2.1, but now for Nedap XS readers (AB350 on Accessor,
SimpleXS). Connected using the MD300 to an AX1001 on the AP1003
for integration with AEOS.
This option can be used if e.g. the existing Nedap RF antenna on the XS
reader is replaced with the Convexs/Invexs, thus enabling that both
Nedap and Mifare cards or Mifare cards replacing Nedap cards can be read.
For each XS reader one AB350 (Convexs adapter) must be placed on the XS reader antenna connector, on which
the Convexs/Invexs is connected.
Possibilities and settings are identical as at 3.2.1. Preferable is to use the
Nedap RF data
output.
3.2.3.
RF output to Nedap XS readers at a WinXS system
Same as 3.2.1, but now for Nedap XS readers (AB350 on Accessor,
SimpleXS), to be connected to the WinXS system (using e.g. LanBoXS or
InterVisor, or directly to the WinXS PC) .
This option can be used if e.g. the existing Nedap RF antenna on the XS
reader is replaced with the Convexs/Invexs, thus enabling that both Nedap
and Mifare cards or Mifare cards replacing Nedap cards can be read.
For each XS reader one AB350 (Convexs adapter) must be placed on the XS reader antenna connector, on which
the Convexs/Invexs is connected.
The Mifare cards must be converted to an XS code:
•
The maximum label number is 220.000 (in combination with a GF code) and depending on the amount of
memory in the XS reader.
If beside the Mifare still the Nedap XS cards are used, the Eprom at the XS readers must be capable of
reading both factory codes. The chosen XS code may not be used already with existing XS cards.
At AEreco the output format must be configured as:
Nedap RF badge
.
Remark
: This option can only be programmed at Nedap, so not with the standard AEreco programm.
3.3.
Wiegand
Maximum cable distance is 150 meters, the LED’s on Convexs/Invexs
are controlled by hardware signals on the Convexs/Invexs connector.
Beeper control:
By hardware connection or software (configuration depending)
PIN code:
8 bits message 4 bits PIN + 4 bits complement, (Dorado format)
For the possible Wiegand protocols, see the section below. Depending of the data read (Card type and Customer
code) a different Wiegand code can be transmitted. Also if the selected Wiegand protocol is capable of using
facility codes for each code read a different Wiegand facility code can be transmitted
Attention:
The card number and customer code that is read must fit in the chosen Wiegand protocol.
If
no
*bin Wiegand is used, the data format must be specified (AEreco in the
Block decoder
part).
- Third party systems
- AEOS Wiegand
Accessor III /
SimpleXS
AC3/2TR
AB350
1 2 3
4 5 6
7 8 9
C 0 E
1 2 3
4 5 6
7 8 9
C 0 E
1 2 3
4 5 6
7 8 9
C 0 E
