UPASS ACCESS | INSTALLATION GUIDE
Introduction
3/23
1
INTRODUCTION
The uPASS Access includes a RS485 interface, a Wiegand/magstripe and a RF-
modulation interface. The uPASS Access can also be connected to NEDAP AEOS
access control hardware such as the AP1001, using the RF-modulation interface. The
uPASS Access does not offer the TRANSIT compatibility features. The uPASS Access is
equipped with a fixed shielded cable pigtail, 12 x 0.14 mm
2
, length 5 meter (15
feet). The cable shield shall be connected to the metal case of the external device or
external devices. In the case of extending this pigtail cable, ONLY shielded cables
shall be used and all shields shall be connected to the metal case of the external
device(s).
1.1
SUPPORTED TAGS
Any EPC Class 1 Gen 2 tag is supported by the uPASS Access.
NEDAP formatted UHF tags can have the following formats:
•
NEDAP UHF Wiegand tags
These tags will contain all Wiegand information including facility code and
parity bits. All Wiegand formats can be supported. The reader transparently
sends this information via the Wiegand outputs. There is no need to change
any DIP-switches or configuration settings. See chapter 3.2.3 for wiring
details.
•
NEDAP UHF magstripe tags
These tags will contain all magstripe information. The reader transparently
sends this information onto the magstripe interface. There is no need to
change any DIP-switches or configuration settings. See chapter 3.2.3 for
wiring details.
•
NEDAP UHF XS tag
These tags are especially programmed in the same format as our 2.45GHz
AVI tags (Compact-Tag, Window-Button and Heavy-Duty-Tag). The tags will
also have a customer-code and id-number. The reader will modulate the
tag-info onto the Nedap antenna interface output, which can be connected
to NEDAP AEOS access control hardware such as the AP1001.
1.2
TAG SECURITY
EPC (Electronic Product Code) tags were introduced as a possible successor to the
barcode with added functionalities. The tag emits its EPC in plain text. This makes
the tags vulnerable to cloning and counterfeiting attacks. Unlike many 13MHz
smartcards, EPC tags do not support any DES, 3DES or AES encryption.
EPC tags contain a data field known as the Tag Identifier (TID). At the discretion of
the EPC manufacturer, the value may be factory programmed and locked, ensuring
that tags have a unique identity and (theoretically) cannot be cross-copied. This TID
based anti-cloning mechanism is not considered to be a strong protection.
NEDAP UHF tags support a locked serialized TID and the uPASS Access reader can be
configured to read the TID data field.
In addition NEDAP has also implemented an advanced anti-cloning and anti-
Note
The Wiegand output format
is determined by the tag
and not by the reader.
Note
The magstripe output
format is determined by the
tag and not by the reader.
Note
See also the 'decode Nedap
xs' feature as described in
chapter 5.2.2.
