P81 InstallGuide E

P81 firmware
Installation Guide
2007-10-19 Part.no. 5268419
This information is furnished for guidance, and with no guarantee as to its accuracy or completeness; its publication conveys
no license under any patent or other right, nor does the publisher assume liability for any consequence of its use; specifica-
tions and availability of goods mentioned in it are subject to change without notice; it is not to be reproduced in any way, in
whole or in part, without the written consent of the publisher.
© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 1 of 40

P81 firmware
CONTENTS
1 INTRODUCTION ................................................................................................................................................................................. 4
2 GETTING STARTED ............................................................................................................................................................................ 5
2.1 STEP 1 – HARDWARE CONFIGURATION .......................................................................................................................... 5
2.1.1 DIP SWITCH SETTINGS ............................................................................................................................................. 5
2.1.2 FREQUENCY SETTING............................................................................................................................................... 5
2.2 STEP 2 – HARDWARE INSTALLATION ............................................................................................................................... 6
2.2.1 POWER SUPPLY.......................................................................................................................................................... 6
2.2.2 WIEGAND, MAGSTRIPE, BARCODE COMMUNICATION................................................................................. 6
2.2.3 RS-232 COMMUNICATION...................................................................................................................................... 6
2.3 STEP 3 – SOFTWARE CONFIGURATION............................................................................................................................ 7
2.3.1 P81TEST ........................................................................................................................................................................ 7
2.3.2 SETUP MENU............................................................................................................................................................... 7
3 DIP SWITCH SETTINGS..................................................................................................................................................................... 8
4 IDENTIFICATION ................................................................................................................................................................................ 9
4.1 LONG RANGE VEHICLE BASED IDENTIFICATION .......................................................................................................... 9
4.2 LONG RANGE DRIVER BASED IDENTIFICATION ............................................................................................................ 9
4.3 PROXIMITY IDENTIFICATION............................................................................................................................................... 9
4.4 IDENTIFICATION PROBLEMS ............................................................................................................................................... 9
5 COMMUNICATION PROTOCOLS ................................................................................................................................................10
5.1 RS-232 PROTOCOL (CR/LF) ................................................................................................................................................10
5.1.1 DATA FORMAT .........................................................................................................................................................10
5.1.2 MESSAGE FORMAT .................................................................................................................................................10
5.1.3 EVENT MESSAGES....................................................................................................................................................10
5.1.4 COMMAND MESSAGES .........................................................................................................................................17
5.2 WIEGAND 26/32/37 BIT PROTOCOL ...............................................................................................................................22
5.2.1 CONNECTIONS .........................................................................................................................................................22
5.2.2 MESSAGE FORMAT .................................................................................................................................................22
5.2.3 PROTOCOL TIMING.................................................................................................................................................22
5.2.4 WIEGAND 26 (H10301) ..........................................................................................................................................23
5.2.5 WIEGAND 32 .............................................................................................................................................................24
5.2.6 WIEGAND 37 .............................................................................................................................................................25
5.3 HID CORPORATE 1000 PROTOCOL .................................................................................................................................26
5.3.1 CONNECTIONS .........................................................................................................................................................26
5.3.2 MESSAGE FORMAT .................................................................................................................................................26
5.3.3 PROTOCOL TIMING.................................................................................................................................................26
5.4 MAGSTRIPE ISO 7811/2.......................................................................................................................................................27
5.4.1 CONNECTIONS .........................................................................................................................................................27
5.4.2 MESSAGE FORMAT .................................................................................................................................................27
5.4.3 EXAMPLES..................................................................................................................................................................28
5.4.4 LRC CALCULATION .................................................................................................................................................28
5.4.5 PROTOCOL TIMING.................................................................................................................................................29
5.4.6 CHARACTER SET.......................................................................................................................................................29
5.5 BARCODE CODE39 PROTOCOL........................................................................................................................................30
5.5.1 CONNECTIONS .........................................................................................................................................................30
5.5.2 MESSAGE FORMAT .................................................................................................................................................30
5.5.3 EXAMPLES..................................................................................................................................................................31
5.5.4 PROTOCOL TIMING.................................................................................................................................................31
5.5.5 CHARACTER SET.......................................................................................................................................................31
5.6 FF-56 BIT PROTOCOL ...........................................................................................................................................................32

P81 firmware
5.6.1 CONNECTIONS .........................................................................................................................................................32

5.6.2 MESSAGE FORMAT .................................................................................................................................................32
5.6.3 PROTOCOL TIMING.................................................................................................................................................32
5.7 TEST PROTOCOL....................................................................................................................................................................33
6 SETUP MENU.....................................................................................................................................................................................34
6.1.1 ENTER SETUP MENU ...............................................................................................................................................34
6.1.2 VIEW/EDIT SETTINGS..............................................................................................................................................34
6.1.3 FACTORY DEFAULTS ..............................................................................................................................................34
6.1.4 EXIT SETUP MENU ...................................................................................................................................................34
7 FIRMWARE UPGRADING ...............................................................................................................................................................35
8 FIRMWARE REVISION HISTORY...................................................................................................................................................36
A HARDWARE .......................................................................................................................................................................................37
A.1 TRANSIT PS270 ......................................................................................................................................................................37
A.2 TRANSIT ENTRY......................................................................................................................................................................38
B ASCII TABLE.......................................................................................................................................................................................39
C CARD TYPE IDENTIFIERS ...............................................................................................................................................................40

P81 firmware
1 INTRODUCTION
The P81 firmware is standard TRANSIT reader firmware with various non-proprietary communication protocols.
It can directly be used to replace a wiegand or magstripe readers in an existing access control system. The
TRANSIT is a long range RFID reader that allows identification of transponders at a distance up to 10 meters,
even at high speeding passage.
The P81 firmware supports a wide range of transponders for various vehicle identification applications. All
vehicle based-, and driver based identification transponders are supported.
The following communication interface protocols are supported:

• Wiegand 26 bit (H10301)
• Wiegand 32 bit
• Wiegand 37 bit (H10302 / H10304)
• Magstripe (ISO 7811/2)
• Barcode Code39
• FF 56 bit
• HID Corporate 1000
An easy-to-use RS-232 protocol (CR/LF) can be used to monitor, debug and setup the reader.

P81 firmware
2 GETTING STARTED
This chapter provides simple instructions (only 3 steps) to get the user up and running quickly.
2.1 STEP 1 – HARDWARE CONFIGURATION
The first step is to configure your hardware.
2.1.1 DIP SWITCH SETTINGS

Make sure the DIP-switches are set correctly. The DIP-switches are described in detail in chapter 3.
Below some recommended DIP-switch settings for a few typical applications:
Typical Booster HID application (default setting) ON
Applicable transponders: All long-range (incl. Booster HID)

1 2 3 4 5 6 7 8
Communication protocol: Wiegand 26 (+ RS232 CR/LF 9600 7E1)
General purpose ON
Applicable transponders: All (also on the proximity antenna)

1 2 3 4 5 6 7 8
Communication protocol: Wiegand 37 (+ RS232 CR/LF 9600 7E1)
Optimized for fast identification ON
Applicable transponders: Only Nedap transponders (Window-button, etc).

1 2 3 4 5 6 7 8
Communication protocol: RS232 CR/LF 38400 8N1 (+ Magstripe)
2.1.2 FREQUENCY SETTING

Frequency needs to be offset when the RX-LEVEL led bar is indicating radio interference. This may be caused by
one of the following conditions:
• Multiple readers in the vicinity of each other (distance less than 10 meters [=30 feet]).
• Other devices, such as wireless network presenting radio interference.
The Nedap transponders operate on all selectable frequencies. The transponders do not need to be modified
when the frequency of a TRANSIT reader is changed. The transponders reflect the frequency they receive and
modulate their id-number upon that frequency. This works for all frequencies including the lowest and highest
selectable frequency.
The frequency setting is described in detail in the hardware installation guide.

P81 firmware
2.2 STEP 2 – HARDWARE INSTALLATION

The second step is to connect the wires.
2.2.1 POWER SUPPLY

Connect power supply. Refer to appendix A when locating the power supply connections.
2.2.2 WIEGAND, MAGSTRIPE, BARCODE COMMUNICATION

The wiring depends upon the selected communication protocol. In the previous step the communication
protocol is selected with the DIP-switches. The table below shows the the wiring for the wiegand protocol. Refer
to appendix A when locating the connections.
DESCRIPTION WIRE COLOR CONNECTION NAME

WIEGAND DATA-0 (ZEROS) GREEN O-2
WIEGAND DATA-1 (ONES) WHITE O-3
GROUND BLACK GND
Table 1: Wiegand wiring
For more details about the communication protocols see the references below.
• Wiegand See chapter 5.2.1 on page 22.
• HID Corporate 1000 See chapter 5.3.1 on page 26.
• Magstripe (ISO 7811/2) See chapter 5.4.1 on page 27.
• Barcode Code39 See chapter 5.5.1 on page 30.
• FF 56 bit See chapter 5.6.1 on page 32.
2.2.3 RS-232 COMMUNICATION

The RS-232 interface is required to complete the software configuration described in chapter 2.3.
The cable must be a null-modem cable. The hardware handshake lines are unused. See the cable specifications
below.
TRANSIT SIDE PC SIDE

25-pin SUB-D Connection Name 9-pin SUB-D Connection Name
2 TXD 2 RXD
3 RXD 3 TXD
7 GND 5 GND
Table 2: RS-232 wiring

P81 firmware
2.3 STEP 3 – SOFTWARE CONFIGURATION

The third step is setting up the software configuration options. This step is optional unless your application
requires to deviate from the default settings.
2.3.1 P81TEST
The easiest way to configure the software options is by means of the P81Ttest software application, which can
be downloaded from http://www.nedapavi.com. This user-friendly application is developed to easily configure,
debug and monitor your TRANSIT reader.
Figure 1: P81TEST software
2.3.2 SETUP MENU

An alternative way to setup the software configuration is described in chapter 6. SETUP MENU.

P81 firmware
3 DIP SWITCH SETTINGS

The TRANSIT reader has 8 DIP-switches, which are used by the P81 firmware as described below. Refer to
appendix A when locating the DIP-switches. The TRANSIT Entry has 4 extra DIP-switches which are described in
the hardware manual.
COMMUNICATION PROTOCOL 1 2 3 4 5 6 7 8
CR/LF 7E1, Barcode Code39 ON ON ON x x x x x
CR/LF 8N1, Magstripe ISO 7811/2 OFF ON ON x x x x x
CR/LF 7E1, Wiegand 26 (H10301) ON OFF ON x x x x x
CR/LF 8N1, Wiegand 32 OFF OFF ON x x x x x
CR/LF 7E1, Wiegand 37 (H10302 / H10304) ON ON OFF x x x x x
CR/LF 8N1, FF-56 OFF ON OFF x x x x x
CR/LF 7E1, HID Corporate 1000 ON OFF OFF x x x x x
CR/LF 8N1, Test protocol. See page 33. OFF OFF OFF x x x x x
The selected communication protocol is only changed after a restart.

DIP-switch 1 selects the data format for the CR/LF protocol on the RS-232 interface. Where 7E1 means 7
data bits, even parity and 1 stop bit and 8N1 means 8 data bits, no parity and 1 stop bit.
For Wiegand 32 use command message SVF to select whether parity is used or not (see page 20). For
Wiegand 37 use command message SVF to select whether the facility code is used or not (see page 20).
BAUDRATE 1 2 3 4 5 6 7 8
Baudrate 9600 x x x ON ON x x x
Baudrate 1200 x x x OFF ON x x x
Baudrate 19200 x x x ON OFF x x x
Baudrate 38400 x x x OFF OFF x x x
The baudrate DIP-switches select the RS-232 communication speed (only changed after a restart).
NON-NEDAP DECODING 1 2 3 4 5 6 7 8
Only Nedap transponders enabled x x x x x ON x x
Nedap and non-Nedap transponders enabled x x x x x OFF x x
Non-Nedap decoding enables the TRANSIT to identify non-Nedap transponders such as EM unique
transponders and HID prox cards.
FRAMELENGTH 1 2 3 4 5 6 7 8
Framelength 64/128/192 bit (auto switch) x x x x x x ON x
Framelength 64 bit x x x x x x OFF x
Set DIP-switch 7 to OFF when fast identification is very important. Note that Combi-Booster and Nedap
RW80 transponders cannot be identified in this case.
ANTENNA SOURCE 1 2 3 4 5 6 7 8
Use default antenna (long range) x x x x x x x ON
Long range and proximity antenna (also MTR) x x x x x x x OFF
Set DIP-switch 8 only to OFF when using a TRANSIT reader with an proximity antenna. The firmware
then tries to identify transponders on both antennas (long range and proximity). When one antenna
identifies a valid transponder it sticks to that antenna source and does not check the other antenna. So,
when a vehicle is identified at the long range antenna and this vehicle stays in front of the TRANSIT,
nobody is identified at the proximity antenna.
Table 3: DIP switch settings

P81 firmware
4 IDENTIFICATION
The TRANSIT allows identification of transponders at a distance up to 10 meters, even at high speeding passage.
The P81 firmware combines long range identification with proximity identification.
If a transponder is identified the TRANSIT will automatically generate an event message on the communication
interface. See page 11.
4.1 LONG RANGE VEHICLE BASED IDENTIFICATION

NEDAP has developed a wide range of transponders for various vehicle identification applications. For example
the window-button is a transponder that is easily mounted behind the windshield of a vehicle. The heavy-duty
tag can be mounted outside on a truck or trailer.
4.2 LONG RANGE DRIVER BASED IDENTIFICATION

The Booster is an in-vehicle card reader mounted behind the windshield. The Booster amplifies the reading
range of the inserted access badge at ranges up to 10 meters. The Booster will act as the lock and the personal
identification card as the key. Removal of the card is ensured as it is required to access the building. Once the
driver leaves his vehicle, only the Booster remains in the vehicle, which in itself can not activate a barrier or open
a gate.
Several Boosters are available for various card technologies. The Boosters can also be featured with an
embedded vehicle-id, which will allow the back end to immediately match the right driver with the right vehicle.
This is called a dual-id transponder.
Boosters for HID prox cards require the presence of the HID interface board in the TRANSIT.
4.3 PROXIMITY IDENTIFICATION

Nedap and EM unique (or compatible) transponders can be identified by the TRANSIT directly on the proximity
antenna. These transponders can be placed in a Booster to achieve long range identification. HID Prox cannot be
identified on the proximity antenna.
4.4 IDENTIFICATION PROBLEMS

If your transponder is not identified check the following possible causes:
• For NEDAP transponders verify that the customer code of the transponder corresponds with the customer
code in the reader.
• For non-nedap transponders (such as EM and HID) ensure that DIP-switch 6 is OFF.
• For HID Prox ensure that an HID interface board is installed in the reader. Remember that HID prox cards
cannot be identified directly on the proximity antenna.
• Ensure that DIP-switch 7 is ON when trying to identify a dual-id transponder.
• Check if reading is not disabled with the read disable input (RDIS). This input may be connected to an
inductive ground-loop, only enabling the TRANSIT to identify when a vehicle is present. See hardware
installation guide for more details.
• Ensure that DIP-switch 8 is OFF when trying to identify a transponder on the proximity antenna.

P81 firmware
5 COMMUNICATION PROTOCOLS
The P81 firmware supports various non-proprietary communication protocols.
5.1 RS-232 PROTOCOL (CR/LF)

The RS-232 CR/LF protocol is a simple ASCII based communications protocol. No software handshaking is
required. Retries or retransmissions are not supported. The RS-232 CR/LF protocol is used in combination with
any of the other selected communication protocols, such as wiegand and magstripe. This chapter describes the
RS-232 protocol as it is implemented in the P81 firmware.
5.1.1 DATA FORMAT

Baudrate: 9600(default), 1200, 19200 or 38400. Setup with DIP-switches (see chapter 3).
Data bits: 7(default) or 8. Setup with DIP-switches (see chapter 3).
Parity: even (default) or none. Setup with DIP-switches (see chapter 3).
Stop bits: 1.
5.1.2 MESSAGE FORMAT

The CR/LF protocol supports 7-bit ASCII data communication. The ASCII control characters are reserved for
message handling. The remaining characters (in the range from 20 hex to 7F hex) are valid characters for the
data.
Every CR/LF message is terminated with a carriage-return and linefeed character:

<data> CR LF
Where: <data> Any readable ASCII character (in the range from hex 0x20 – 0x7F).
CR Carriage return character (hex 0x0D).
LF Linefeed character (hex 0x0A).
5.1.3 EVENT MESSAGES

The reader may send the following event messages. Spaces are only added for readability.
Events always start with an alphabetic character (upper or lower case) and may be followed by hexadecimal data
bytes.
The length of the events messages are fixed but may be enlarged in future revisions to contain additional data.
Also new event types may be added in a future revision.
5.1.3.1 Reader Status Events

Reader restarted ('O')
Description: The reader sends this event message as soon as the reader is powered-up to indicate
that the system is active. Application settings stored in EEPROM were not lost.
Syntax: O CRLF
Reader reset ('P')

Description: The reader sends this event message as soon as the reader is powered-up to indicate
that the system is active. Application settings stored in EEPROM were reset to their
factory defaults. EEPROM settings are not lost when the reader is switched off. The
EEPROM settings may be lost when the firmware is changed.
Syntax: P CRLF
Notes: In case the P-event is sent the O-event is omitted.

P81 firmware
5.1.3.2 Identification Events

When a transponder is identified the TRANSIT reader generates an identification event. The identification event
is sent only once upon identification of the transponder. See the timing diagram below.
Detection
Event message
Figure 2: Timing diagram identification event
Optionally the identification event may be repeated periodically. The repeat timer is setup with command
message SC4.
Detection
Holdtime
T-Repeat T-Repeat
Event message
Figure 3: Timing diagram repeat time
Depending on the transponder type the event may have a different format.
Window Button / Compact Tag / Heavy Duty Tag
By default these transponders are programmed with a customer code and a identification number. The TRANSIT
reader checks if the customer code is correct. This ensures that only your own transponders are read. The event
reports the identification number according to the following format.
Syntax: N nnnnnn [ct] CRLF
Where: N Event type 'N' or 'n'. The event type is a lowercase 'n' when a
transponder with battery-low has been detected.
nnnnnn Transponder number in range from 000001 to 999999.
[ct] Optional card-type identifier. See appendix C.
Alternatively they can be programmed with a RW80 code. In this case there is no customer code. The RW80
identification event has the following format.
Syntax: U xxxxxxxxxxxxxxxxxxxx [ct] CRLF
Where: U Event type 'U' or 'u'. The event type is a lowercase 'u' when a
transponder with battery-low has been detected.
xxx...xxx Identification number 20 hex digits (=80 bit).
Notes: RW80 coded transponders cannot be identified if DIP switch 7 is OFF.

P81 firmware
Manchester encoded transponder (EM unique)
The transponder can be identified directly on the proximity antenna (if enabled by DIP-switch 8) or by the long
range antenna when placed in a Booster. Manchester encoded transponders are non-nedap transponders and
must be enabled with DIP-switch 6. Please see chapter 3 on page 8 for more details about DIP-switch settings.
Syntax: U 0000000000xxxxxxxxxx [ct] CRLF
Where: xx..xx Identification number 10 hex digits (=40 bit).

Combi-Booster / Prox-Booster
The Combi-Booster contains a vehicle-id which is combined with a driver-id. The driver-id is read from the
inserted personal identification card. This can be a Nedap transponder card or a Manchester encoded
transponder card based upon a 64-bit read-only chip from EM-Marin. Manchester encoded transponders are
non-nedap transponders and must be enabled with DIP-switch 6 (see chapter 2 on page 5).
The vehicle-id is programmed is programmed into the Combi-Booster device itself including a customer code.
The TRANSIT reader will verify if the customer code is correct. The customer code of an inserted Nedap
transponder card will also be verified. Manchester encoded transponders do not contain a customer code.
Syntax: U 0000aaaaaa bbbbbbbbbb [ct] CRLF
Where: aaaaaa Vehicle identification number in range from 1 to 999999.

bbbbbbbbbb Driver identification number. Can be hexadecimal if a manchester
encoded transponder card is used.
Notes: The vehicle-id or driver-id field may be left blank (filled with zeros) if the
identification is invalid.

P81 firmware
Combi-Booster HID / Prox-Booster
The Combi-Booster HID is a special Combi-Booster that can read HID prox cards. HID prox cards are non-nedap
transponders and must be enabled with DIP-switch 6 (see chapter 3 on page 8).

bbbbbbbbbb Driver identification number from the HID prox card.
The HID prox card data (=driver-id) is sent in hexadecimal notation of fixed length (10 hex digits).
The data includes the card's complete wiegand message (id-number, parity bits, facility code and site code).
In the example below, the HID prox card data is shown for a wiegand 26-bit formatted card. The example card
contains facility code 1 and card number 55555.
0 0 0 0 0 0 0 0 1 1 1 0 1 1 0 0 1 0 0 0 0 0 0 1 1 1
0 0 0 0 0 3 B 2 0 7
bbbbbbbbbb = 000003B207 Facility code ID-number
Parity Unused
Figure 4: Example HID card data
Booster HID / Prox-Booster single-id
The Booster HID is similar to the Combi-Booster HID, except for now there is no vehicle-id. HID prox cards are
non-nedap transponders and must be enabled with DIP-switch 6 (see chapter 3 on page 8). The Booster HID can
only be identified if an HID interface board is installed in the TRANSIT reader.
Syntax: U 0000000000 bbbbbbbbbb [ct] CRLF
Where: bbbbbbbbbb Driver identification number from the HID prox card. See Figure 4
above.

P81 firmware
Combi-Booster LEGIC / Smartcard-Booster LEGIC
The Combi-Booster LEGIC is a special Combi-Booster that can read LEGIC transponder cards. LEGIC cards are
non-nedap transponders and must be enabled with DIP-switch 6 (see chapter 3 on page 8).
What information is read from the LEGIC card is configured into the Combi-Booster LEGIC using configuration
cards. These configuration cards also determine if the vehicle-id is transferred or discarded in which case there
can more data tranferred from the LEGIC card.
Below the format of the identification event for a Combi-Booster LEGIC including vehicle-id.

bbbbbbbbbb Driver identification number from the LEGIC transponder card 10 hex
digits (=5 bytes).
Below the format of the identification event for a Booster LEGIC.

Syntax: U xxxxxxxxxxxxxxxxxxxx [ct] CRLF
Where: xxx..xxx Driver identification number from LEGIC transponder card 20 digits (=10
bytes).
Tacho-Booster
The Tacho-Booster is an extended Combi-Booster version with an embedded pulse counter. When connected to
the pulse generator of the vehicle the actual pulse count will be recorded. The pulse count relates to the
travelled distance of the vehicle. This information together with the vehicle-id and driver-id are sent in the
following event message:
Syntax: X 0000aaaaaa bbbbbbbbbb 80cccccccc [ct] CRLF
Where: aaaaaa Vehicle-id number in range from 1 to 999999.

bbbbbbbbbb Driver-id number.
80 Tacho pulse counter id. Other values are reserved to transfer other
information.
cccccccc Tacho pulse counter (8 hex digits).
The support for the Tacho-Booster is introduced in P81 version 3.21.

P81 firmware
Smartcard-Booster / Transition-Booster
The Transition-Booster can read both low-frequency (120-125kHz) as high-frequency (13MHz) transponders. It is
developped for users who want to migrate from for example HID prox to HID iClass cards. The configuration
settings are loaded into the Transition-Booster by using Mifare configuration cards. The Smartcard-Booster is a
Transition-Booster that only reads high-frequency (13MHz) cards.
Below the format of the identification event for a Transition-Booster including vehicle-id.
Syntax: Y 0000aaaaaa bbbbbbbbbbbbbbbbbbbbbb [ct] CRLF

bb..bb Driver identification number from the transponder card 22 hex digits
(=11 bytes).
Below the format of the identification event for a Transition-Booster with larger driver-id.
Syntax: Z bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb [ct] CRLF
Where: bbb..bbb Driver identification number from the transponder card 32 hex digits
(=16 bytes).
The support for the Transition-Booster is introduced in P81 version 3.22.
Notes: The Smartcard-Booster can be configured to be compatible with the Combi-Booster. In that case refer to the
Combi-Booster description above.
Refer to the Combi-Booster description above in case of a Transition-Booster that identifies a low-frequency card
(such as Nedap, EM or HID prox).

P81 firmware
5.1.3.3 End-of-detection Event

When the transponder cannot be identified anymore the reader will optionally send out an end-of-detection
event message. This event message must be enabled with command message 0267. The event is not sent until
the holdtime has expired.
Please note that not every identification event has to be followed by an end-of-detection event. See the timing
diagram below.
Detection ID-1 ID-2
Holdtime
ID-1 ID-2 End-of-detection

Event message
Figure 5: Timing diagram end-of-detection event
The end-of-detection event uses the same format as an identification event, except for now the identification
number is left blank (filled with zeros).
Syntax: U 00000000000000000000 [00] CRLF
[00] Only sent if card type is enabled with command message SVF.
5.1.3.4 Input Status Changed Event
Syntax: I xx CRLF
Where: xx Bit-coded byte with the current status of the input pins in hexadecimal
notation. Unused bits are reserved for future use.
- - - - - IN3 IN2 IN1

bit 7 bit 2 bit 1 bit 0
bit 2 IN3: Input 3. Only available on TRANSIT Entry.

1 = Input 3 closed to ground.
0 = Input 3 open (pulled-up internally).
bit 0 IN1: Input 1.

P81 firmware
5.1.4 COMMAND MESSAGES

The following command messages may be sent to the reader. Protocol dependent characters are not shown
here.
5.1.4.1 General Command Messages
QVE Request firmware version

Description: Request reader’s firmware version.
Syntax: QVE
Reply: QVEpppvvv
Where: ppp Firmware name (P81).
vvv Firmware Version (300 = version 3.00).
QID Request identification

Description: Request current identification.
Syntax: QID
Reply: Identification event. See chapter 5.1.3.2 on page 11.
CLS Reset Reader (to factory defaults)

Description: Restart the reader and reset all EEPROM settings to their factory defaults. The reader
will generate a P-event (reader reset).
Syntax: CLS
Reply: CLS
SFC Set Facility Code

Description: The reader’s facility code. For transponders that do not contain a facility code, the
facility code setup with this command message is used instead.
Syntax: SFCffff
Reply: SFCffff
Where: ffff Facility code in the range from hex 0000 to hex FFFF. Most significant
byte first.
Notes: The valid range depends upon the selected communication protocol.
Protocol Valid range facility code

Wiegand 26 (H10301) 0000 – 00FF
Wiegand 32 0000 – FFFF
Wiegand 32 with parity 0000 – 3FFF
Wiegand 37 (H10302) n.a.
Wiegand 37 with facility code (H10304) 0000 – FFFF
FF-56 0000 – 00FF
HID Corporate 1000 0000 – 0FFF
QFC Request Facility Code

Description: Request the reader's facility code. See command message SFC above.
Syntax: QFC
Reply: QFCffff
Where: ffff Facility code in the range from hex 0000 to hex FFFF. Most significant
byte first.

P81 firmware
5.1.4.2 Timing command messages
SC1 Set Timer 1 (relay hold time)

Description: The relay hold time (also referred to as the unlock-time) is default 5 seconds. It causes
the unlock relay to stay activated for the specified time after the transponder could
not be identified anymore. See timing diagram in Figure 6. When during the relay
hold time the same transponder is identified again the reader will not generate a
new identification event. Changed timer values are stored in EEPROM and are only lost
when the ‘reset reader’ command is performed.
Syntax: SC1xx
Reply: SC1xx
Where: xx Relay hold time in the range from 1 to 255 tenths of a second. Specify
timer value hexadecimal. E.g. 1 second is hex 0A.
Example: SC11E Set the relay hold time to 3 seconds.
Detection
Holdtime
Relay
Figure 6: Timing diagram relay-hold-time
QC1 Request Timer 1 (relay hold time)

Description: Request timer 1. See command message SC1 above.
Syntax: QC1
Reply: QC1xx
Where: xx Relay hold time in the range from 1 to 255 tenths of a second.
SC4 Set Timer 4 (repeat-time)

Description: The repeat time is default 0 seconds, which means that the identification event is
only sent once. The repeat time causes the reader to transmit a identification event
every ‘repeat time’ seconds for as long as the transponder is present. See timing
diagram in Figure 3 on page 11. Changed timer values are stored in EEPROM and are
only lost when the ‘reset reader’ command is performed.
The repeat timer works for every communication protocol.
Syntax: SC4xx
Reply: SC4xx
Where: xx Repeat time in the range from 0 to 255 tenths of a second. Specify
timer value hexadecimal. E.g. 1 second is hex 0A.
Example: SC400 Disable the repeat timer option.
QC4 Request Timer 4 (repeat-time)

Syntax: QC4
Reply: QC4xx
Where: xx Repeat time in the range from 0 to 255 tenths of a second.

P81 firmware
5.1.4.3 Dual-ID Control command messages
SC5 Set Timer 5 (Combi-Booster inter id delay)

Description: Dual-id transponders combine a vehicle-id with a driver-id. Both id-numbers may be
sent in a separate event message to the host computer. Two event messages are
only sent for the Wiegand, Corporate 1000 and Magstripe communication protocols.
The delay between the two messages can be setup with this timer. First is always the
vehicle-id transmitted. The second event message contains the driver-id. Either event
can be disabled. The vehicle-id message is disabled if the timer is set to 255 (hex FF).
The driver-id message is disabled if the timer is set to zero.
Changed timer values are stored in EEPROM and are only lost when the ‘reset reader’
command is performed.
Syntax: SC5xx
Reply: SC5xx
Where: xx Combi-Booster inter-id delay in the range from 0 to 255 hundredths of
a second. Specify timer value hexadecimal. E.g. 100 msec is hex 0A.
Notes: This timer is not applicable for the RS232 and Barcode protocol because these
protocols send the vehicle-id and driver-id in a single event message. The FF-56 bit
protocol only supports the vehicle-id for dual-id transponders.
When to the total amount of time required to sent both id numbers is greater than
the repeat time, see command message SC4, then the second message containing
the vehicle-id follows directly after the first message with the driver-id. See also
‘Events D’ in Figure 7. This may result in bad identification handling on the host side.
Example: SC500 Disable the driver-id. See ‘Events A’ in Figure 7.
Example: SC50A First send the vehicle-id, wait for 100 msec and secondly send the
driver-id. See ‘Events B’ in Figure 7.
Example: SC5FF Disable the vehicle-id. See ‘Events C’ in Figure 7.
Detection
T-IID = 0
Events A T-Repeat = 0
T-IID = 100 ms (0A)

Events B T-Repeat = 0
T-IID
T-IID = FF
Events C T-Repeat = 0
T-Repeat
T-IID = 100 ms (0A)
Events D T-Repeat > T-IID
T-IID T-IID
vehicle-id
T-Repeat T-Repeat
T-IID = 250 ms (19) driver-id
Events E T-IID T-IID T-Repeat < T-IID
Figure 7: Timing diagram Combi-Booster inter id delay (T-IID)
QC5 Request Timer 5 (Combi-Booster inter id delay)

Syntax: QC5
Reply: QC5xx
Where: xx Combi-Booster inter-id delay in the range from 0 to 255 hundredths of
a second (0=disable driver-id, FF=disable vehicle-id)

P81 firmware
SVF Set Various Flags

Description: Set various flags. Default all flags are off (=0).
Flag to select alternative wiegand format (valid for wiegand 32 and wiegand 37).
Flag to select automatic or manual relay activation.
Flag to enable card-type in identification events.
Flag to enable end-of-detection events.
Flag to inhibit identification events.
Changed settings are stored in EEPROM and are only lost when the ‘reset reader’
command is invoked.
Syntax: SVFxx
Reply: SVFxx
Where: xx Bit-coded byte in hexadecimal notation with the various flags.
Example: SVF02 Select manual relay activation (other options unused).
- - - IDE EODE CTE RAM AWF

bit 7 bit 4 bit 3 bit 2 bit 1 bit 0
bit 4 IDE: Inhibit identification events.

0 = Identification events are automatically sent upon identification.
1 = Identification events are inhibited. Identification status can by requested with
command message QID.
bit 3 EODE: End-of-detection event enable.
0 = End-of-detection event disabled.
1 = End-of-detection event enabled.
bit 2 CTE: Card type enable.
0 = Card type not transmitted.
1 = Card type transmitted in identification events.
bit 1 RAM: Relay Activation Mode.
0 = Automatic relay activation. Relay activated when a transponder is identified.
1 = Manual relay activation. Relay only controlled by command messages SR1, SR0
and SRT
bit 0 AWF: Alternative Wiegand Format (valid for wiegand 32 and wiegand 37).
Description for wiegand 32:
0 = Wiegand 32 without parity
1 = Wiegand 32 with parity
Description for wiegand 37:
0 = Wiegand 37 without facility code (H10302)
1 = Wiegand 37 with facility code (H10304)
QVF Request Various Flags

Description: Request various flags. See command message SVF above.
Syntax: QVF
Reply: QVFxx
Where: xx Bit-coded byte in hexadecimal notation.

P81 firmware
5.1.4.4 Digital I/O command messages

The following command messages are introduced in firmware version P81 v3.08.
SR1 Set Relay: Activate

Description: Activate Relay RY1
Syntax: SR1
Reply: SR1
Notes: The relay is activated and will not be de-activated until command message SR0 is
received. When relay activation mode is automatic (default setting) the relay is
activated when either this command is sent or a transponder is identified. When this
command is sent the relay stays activated, also when there is no more detection. See
command SVF for details about how to change the relay activation mode.
SR0 Set Relay: Deactivate

Description: Deactivate relay RY1.
Syntax: SR0
Reply: SR0
Notes: When relay activation mode is automatic the relay may be activated if a transponder
is identified. If this is the case, this command will not deactivate the relay until end-
of-detection. See command SVF for details about how to change the relay activation
mode.
SRT Set Relay: Timed

Description: Activate relay RY1 for a period of relay-hold time and automatically deactivate
afterwards. The relay-hold time is setup with command message SC1 (refer to page
18 for more details).
Syntax: SRT
Reply: SRT
Remark: When relay activation mode is automatic, the relay may also be activated upon
identification of a transponder. See also command messages SR1, SR0 and SVF.
QIN Request Input status

Description: Request input status.
Syntax: QIN
Reply: QINxx
Where: xx Bit-coded byte with the current status of the input pins in hexadecimal
notation. Unused bits are reserved for future use.
- - - - - IN3 IN2 IN1

bit 7 bit 2 bit 1 bit 0

bit 0 IN1: Input 1.

P81 firmware
5.2 WIEGAND 26/32/37 BIT PROTOCOL

The Wiegand protocol is based upon the Wiegand-effect card readers widely used in access control applications.
Wiegand cards incorporate two rows of tiny wire particles representing binary zeros and ones. The Wiegand
interface uses two TTL-level outputs that correspond to these zeros and ones.
5.2.1 CONNECTIONS
The following TTL-level outputs are used. Refer to appendix A when locating these connections.
• Data-0 Zeros (active low) O-2 (Green)
• Data-1 Ones (active low) O-3 (White)
• GND Signal ground GND (Black)

When a transponder is identified, the TRANSIT reader generates an identification event. The identification event
is sent only once upon identification of the transponder. See the timing diagram in Figure 2 on page 11.
Optionally the identification event may be repeated periodically. The repeat timer is setup with command
message SC4 (see page 18).
Dual-id transponders
When using a dual-id transponder two wiegand event messages are generated. The first for the vehicle-id and
the second with the driver-id. One of these event messages may be disabled with command message SC5. This
command message also controls the delay between the two events (see page 19).
The Tacho-Booster is handled as a dual-id transponder; the tacho pulse counter is ignored.
Facility code
NEDAP cards do not contain a facility code. The P81 firmware will add the facility code to the Wiegand
messages. Setup this facility code with command message SFC (see page 17). The same applies to other cards
without facility code, such as EM and Mifare.
HID prox cards

The message format for HID prox cards is preserved including the HID prox card’s facility code. This means that
the Wiegand event message, with the HID prox card data, may be transmitted in a different format than selected
by the DIP switches. Even OEM proprietary formats can be expected. The maximum length for these HID prox
cards is 40 bits. For longer formats only the least significant 40 bits are transmitted.
Other cards (e.g. EM4102 and Mifare)

Many third party transponders contains more data than fits in the Wiegand message format. Only the least
significant bits will be used.
5.2.3 PROTOCOL TIMING

In the figure below the Wiegand protocol timing is specified.
Tpw
5V
DATA-1 0V
Tpw
5V
DATA-0 0V Timing constants:
Tpi Pulse interval time 1msec
Tpi Tpi Tpw Pulse width time 50μsec
Figure 8: Wiegand protocol timing

P81 firmware
5.2.4 WIEGAND 26 (H10301)

Wiegand 26 is the industry standard format. It consists of a leading parity bit, 8 facility code bits, 16 bits
identification number and a trailing parity bit. The facility code and id-number are transmitted with the most
significant bit first. The total number of bits is 1+8+16+1 = 26.
The leading parity bit is even calculated over the succeeding 12 bits. The trailing parity bit is odd calculated over
preceding 12 bits.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
P F F F F F F F F X X X X X X X X X X X X X X X X P
facility code identification number
even parity over bits 2 - 13 odd parity over bits 14 - 25
Notes: The id-number for Nedap CF, DF or GF-coded (6 digit) transponders is converted to a binary value. The message
will only contain the 16 least significant bits. E.g. maximum id-number is 65535.
For cards that contain more data than fits in the Wiegand 26 bit message (e.g. EM4102 and Mifare), the data will
be truncated. Only the 16 least significant bits are transferred.
The message format for HID prox cards is preserved including the HID prox card’s facility code.
Example
Wiegand 26: Window-Button (reader’s facility code 10, id-number 123).
5V
DATA-1 0V
5V
DATA-0 0V
facility code id-number
Wiegand 26: Prox-Booster (reader’s facility code 10, vehicle-id 16959, no driver-id).
5V
DATA-1 0V
5V
DATA-0 0V
vehicle-id driver-id
Wiegand 26: Prox-Booster (reader’s facility code 10, vehicle-id 16959, driver-id 1365).
5V
DATA-1 0V
5V
DATA-0 0V
Wiegand 26: Prox-Booster (reader’s facility code 10, vehicle-id 16959, hid prox card driver-id).
5V
DATA-1 0V
5V
DATA-0 0V

P81 firmware
5.2.5 WIEGAND 32
Two separate wiegand 32 bit formats variant are supported. Select the appropriate format with the alternative
wiegand format (AWF) bit with command message SVF (see page 20).
5.2.5.1 WIEGAND 32 (AWF = 0; no parity)

The Wiegand 32 bit format consists of 16 bits facility code, followed by 16 bits identification number. The facility
code and id-number are transmitted with the most significant bit first. The total number of bits is 32. There are
no parity bits.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
F F F F F F F F F F F F F F F F X X X X X X X X X X X X X X X X
facility code identification number
Example
Wiegand 32: Window-Button (reader’s facility code 10, id-number 12345).
5V
DATA-1 0V
5V
DATA-0 0V
5.2.5.2 WIEGAND 32 (AWF = 1; with parity)

Wiegand 32 bit with parity differs only from Wiegand 32 in that the facility code is 2 bits smaller and that it has a
leading and trailing parity bit. The leading parity bit is even calculated over bits 2 - 17. The trailing parity bit is
odd calculated over bits 16 - 31. Bits 16 and 17 are used in calculating both parity bits.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
P F F F F F F F F F F F F F F X X X X X X X X X X X X X X X X P
even parity over bits 2 - 17 facility code identification number odd parity over bits 16 - 31
Example
Wiegand 32 with parity: Window-Button (reader’s facility code 10, id-number 12345).
5V
DATA-1 0V
5V
DATA-0 0V

P81 firmware
5.2.6 WIEGAND 37
Two separate wiegand 37 bit formats variant are supported. Select the appropriate format with the alternative
wiegand format (AWF) bit with command message SVF (see page 20).
5.2.6.1 WIEGAND 37 (AWF = 0; H10302)

Wiegand 37 was developed to provide the industry with an open standard format that supports large id-
numbers. The Wiegand 37 bit format consists of a leading parity bit, followed by 35 bits identification number
and a trailing parity bit. The id-number is transmitted with the most significant bit first. The total number of bits
is 1+35+1 = 37.
The leading parity bit is even calculated over the succeeding 18 bits. The trailing parity bit is odd calculated over
preceding 18 bits. Bit 19 is used in calculating both parity bits.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
P X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X P
even parity over bits 2 - 19 identification number odd parity over bits 19 - 36
Note: For cards that contain more data than fits in the Wiegand 37 bit message (e.g. EM4102 and iCLASS CSN), the data
will be truncated. Only the 35 least significant bits are transferred.
The message format for HID prox cards is preserved.
Example
Wiegand 37: Smartcard-Booster (vehicle-id 1, driver-id Mifare CSN hex 14DE7A46).
5V
DATA-1 0V
5V
DATA-0 0V
Wiegand 37: Smartcard-Booster (vehicle-id 1, driver-id iCLASS CSN hex E012FFF5000188FF).

5V
DATA-1 0V
5V
DATA-0 0V
5.2.6.2 WIEGAND 37 (AWF = 1; H10304)

Wiegand 37 with facility code differs only from Wiegand 37 in that it has a facility code. The Wiegand 37 bit with
facility code format contains 16 facility code bits and 19 bits identification number.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
P F F F F F F F F F F F F F F F F X X X X X X X X X X X X X X X X X X X P
even parity over bits 2 - 19 facility code identification number odd parity over bits 19 - 36
Note: For cards that contain more data than fits in the Wiegand 37 bit message (e.g. EM4102 and Mifare), the data will
Example
Wiegand 37 with facility code: Window-Button (reader’s facility code 10, id-number 300).
5V
DATA-1 0V
5V
DATA-0 0V

P81 firmware
5.3 HID CORPORATE 1000 PROTOCOL

The HID Corporate 1000 format is a 35 bit wiegand format with a unique Company ID Code and over 1,000,000
card numbers available for use.
5.3.1 CONNECTIONS
The connections are described in chapter 5.2.1.

HID can provide you with a document that details the generic Corporate 1000 Format. HID's Technical Support
can also answer specific questions that you may have about the Corporate 1000 program.
The reader will send a message when a transponder is identified. Note that HID prox cards cannot be identified
directly on the proximity antenna, but have to be placed in a Booster.
Optionally the message may be repeated if the transponder stays within the reading range. Setup the repeat
interval with command message SC4 on the RS-232 interface (see page 18).
Dual-id transponders
When using a dual-id transponder two wiegand event messages are generated. The first for the vehicle-id and
the second with the driver-id. One of these event messages may be disabled with command message SC5. This
command message also controls the delay between the two events (see for more details page 19).
Facility code
NEDAP cards do not contain a facility code. The P81 firmware will add the facility code to the Corporate 1000
messages. Setup this facility code with command message SFC (see page 17). The same applies to other cards
without facility code, such as EM and Mifare.
HID prox cards

The message format for HID prox cards is preserved including the HID prox card’s facility code. This means that
the Wiegand event message, with the HID prox card data, may be transmitted in a different format than selected
by the DIP switches. Even OEM proprietary formats can be expected. The maximum length for these HID prox
cards is 40 bits. For longer formats only the least significant 40 bits are transmitted.
Other cards (e.g. EM4102 and Mifare)

Many third party transponders contains more data than fits in the Corporate 1000 message format. Only the 20
least significant bits are used.

The protocol timing is described in chapter 5.2.3.

P81 firmware
5.4 MAGSTRIPE ISO 7811/2

The Magstripe ISO 7811/2 protocol is implemented according to the standard ISO 7811/2 track 2 with ABA
format, which is often used in magnetic stripe readers.
The data information of the message is included between start-sentinel and end-sentinel. After the end-sentinel
the LRC is sent (Longitudinal Redundancy Check) to check the received data. The contained data is in BCD
notation.
5.4.1 CONNECTIONS
The following TTL-level outputs, which are active low, are used. Refer to appendix A when locating these
connections.
• /CLS Card Loaded Signal O-1
• /RCP Reader Clock Signal O-2
• /RDP Reader Data Signal O-3
• GND Signal ground GND

The reader sends a message when a transponder is identified. Optionally the message is repeated if the
transponder stays within the reading range. Setup the repeat interval with command message SC4 on the RS-
232 interface (see page 18).
For every transmitted character in the event message an odd parity bit is calculated. Therefore each character
contains 5 bits. The least significant bit is transmitted first, finally the parity bit is transmitted. After the end-
sentinel the LRC is transmitted.
Magstripe ISO 7811/2 message format (spaces are only added for readability).
Syntax: <ssen> ccc ssss nnnnnn <esen> <lrc>
Where: <ssen> Start sentinel (hex B).

ccc Customer code (fixed 000).
ssss Status code (fixed 0000).
nnnnnn Identification number in the range from 000001 to 999999.
<esen> End sentinel (hex F).
<lrc> Longitudinal redundancy check.
When using a dual-id transponder two event messages are sent. The first event contains the vehicle-id and the
second the driver-id. The delay between the events can be setup with command message SC5 (see page 19).
Notes: For cards that contain more data than fits in the message format (e.g. EM4102 and Mifare), the data will be
truncated. Only the 16 least significant bits are used. This 16 bit binary value is converted to a BCD value in the
range from 0 to 65535. This BCD number is transmitted in the Magstripe ISO 7811/2 message.
HID prox cards are not supported in this protocol. The id-message will be filled with zeros.

P81 firmware
5.4.3 EXAMPLES
Window-Button identified (id no. 666666).
B0000000666666F4
Prox-Booster (id no. 123456) identified without a card.
B0000000123456F3 First message contains vehicle-id.
B0000000000000F4 Second message with empty driver-id.
Prox-Booster (id no. 123456) identified with a NEDAP XS-card (id no. 004444).
B0000000004444F4 Second message with driver-id.
Prox-Booster (id no. 123456) identified with a HID prox card.

B0000000000000F4 Second message with empty driver-id.
A Nedap RW80 formatted Window-Button identified (id no. 0000019AAD000123FC92). Hex FC92 = 64658.
B0000000064658FD
5.4.4 LRC CALCULATION

The LRC is the vertical even parity over all data bits including start-, and end-sentinel. In the example below the
LRC is calculated on a data message 0000000123456:
HEX PAR BIN Description
B 0 1011 start-sentinel
0 1 0000 data \
0 1 0000 data > customer code (always 000)
0 1 0000 data /
0 1 0000 data \
0 1 0000 data \ status code (always 0000)
0 1 0000 data /
0 1 0000 data /
1 0 0001 data \
2 0 0010 data \
3 1 0011 data \ id-number
4 0 0100 data / (123456)
5 1 0101 data /
6 1 0110 data /
F 1 1111 end-sentinel
3 1 0011 lrc
LRC = (B ⊕ 0 ⊕ 0 ⊕ 0 ⊕ 0 ⊕ 0 ⊕ 0 ⊕ 0 ⊕ 1 ⊕ 2 ⊕ 3 ⊕ 4 ⊕ 5 ⊕ 6 ⊕ F) = 3.

P81 firmware

In the figure below the timing for one character is specified. Each bit consists out of one period low (220μsec)
and two periods high (440μsec). The bit times have an accuracy of 10 percent. The data-signal RDP is valid and
stable on the falling edge of the clock-signal RCP.
3300µsec
660µsec 220µsec
5V
RCP 0V Timing constants:
Card present period 74msec
Clock period 660μsec
RDP 5V Clock high 440μsec
0V
Clock low 220μsec
lsb msb odd parity Data preamble 11msec
0 1 1 0 1 Data postamble 11msec
Figure 9: Magstripe ISO 7811/2 protocol timing one character
The card present signal will be active (=low) for about 74 milliseconds. Before and after the data 16 clock pulses
are generated, resulting in 2 ×16 × 660μsec ≈ 22 msec delay.
74.4msec
CLS 5V
0V
RCP 5V
0V
RDP 5V
0V 11msec 11msec
Figure 10: Magstripe ISO 7811/2 protocol timing complete message
5.4.6 CHARACTER SET

HEX BIN Description
0 0000 0
1 0001 1
2 0010 2
3 0011 3
4 0100 4
5 0101 5
6 0110 6
7 0111 7
8 1000 8
9 1001 9
A 1010 Reserved for hardware control purposes
B 1011 Start-sentinel
C 1100 Reserved
D 1101 Separator
E 1110 Reserved for hardware control purposes
F 1111 End-sentinel
Table 4: Magstripe ISO 7811 track 2 character set

P81 firmware
5.5 BARCODE CODE39 PROTOCOL

Code39 is commonly used for various bar-coding labels such as name badges, inventory and industrial
applications. The Code39 barcode is the easiest to use of alphanumeric barcodes and is designed for character
self-checking, eliminating the requirement for check character calculations. The 3 of 9 Code and Code 3 of 9 are
just other names for the same symbology.
Each character consists of 9 elements, 5 bars and 4 spaces. Three elements are wide and six elements are small.
The ratio between wide and small are 3:1. A bar corresponds with a high level (5V) on the TTL-output, a space
with a low-level (0V) on the TTL-output.
The messages contain a start and stop character. The characters are separated by an inter character gap. The
inter character gap is a small space.
5.5.1 CONNECTIONS
• BC39 Code39 data O-3

The reader sends a message when a transponder is identified.
Message format for Nedap CF, DF or GF-coded (6 digit) transponders.

Syntax: *NNNNNN*
Where: * Start character.
NNNNNN Identification number in the range from 000001 to 999999.
* Stop character.
Message format for dual-id transponders, Nedap RW80 transponders and non-Nedap transponders.
Syntax: *XXXXXXXXXXXXXXXXXXXX*
XXX...XXX Identification number 20 hex digits.
* Stop character.
Message format for Tacho-Booster

Syntax: *0000AAAAAABBBBBBBBBB80CCCCCCCC*
AAAAAA Vehicle-id number in the range from 000001 to 999999.
BBBBBBBBBB Driver-id number.
80 Tacho pulse counter id. Other values are reserved to transfer different
information.
cccccccc Tacho pulse counter (8 hex digits).
* Stop character.
Optionally this message may be repeated if the transponder stays within the reading range. Setup the repeat
interval with command message SC4 on the RS-232 interface (see page 18).

P81 firmware
5.5.3 EXAMPLES
Window-Button identified (id no. 666666).
*666666*
Prox-Booster (id no. 123456) identified without a card.

*00001234560000000000*
Prox-Booster (id no. 123456) identified with an EM unique card (id no. 01F7A9C2E5).
*000012345601F7A9C2E5*
Prox-Booster (id no. 123456) identified with a HID prox card (H10301 format).
*0000123456000003B207*
A Nedap RW80 formatted Window-Button identified (id no. 0000019AAD000123FC92).

*0000019AAD000123FC92*

In the figure below the timing for two characters is specified including the inter character gap.
(intercharacter gap) 1msec
15msec 15msec
3msec 1msec 1msec 3msec

BC39
5V Timing constants:
0V
Small element 1msec
Wide element 3msec
START/STOP
* 5 Inter character gap 1msec
Figure 11: Code39 protocol timing
5.5.5 CHARACTER SET

The symbology of the Code 39 character set consists of bar code symbols representing characters 0-9, A-Z, the
space character and the following symbols: - , . , $ , / , + , %. For transmitting id-numbers only the characters 0-9
and A-F are used.
Description Code39 Description Code39
0 1
2 3
4 5
6 7
8 9
A B
C D
E F
* START/
STOP
Table 5: Code39 character subset

P81 firmware
5.6 FF-56 BIT PROTOCOL

The FF56 protocol is a clock and data protocol, which is used in Effeff access control systems. The data is valid
and stable on the rising edge of the clock signal.
5.6.1 CONNECTIONS
• FF56C Clock (active high) O-2
• /FF56D Data (active low) O-3

The reader sends a message when a transponder is identified. Optionally this message may be repeated if the
transponder stays within the reading range. Setup the repeat interval with command message SC4 on the RS-
232 interface (see page 18).
Setup the facility code with command message SFC on the RS-232 interface.
FF-56 bit message format
Syntax: FFFFFFFFSSSSPSSSSPSSSSPSSSSPNNNNPNNNNPNNNNPNNNNPVVVVPDDD
Where: F Reader facility code (8 bit binary value, most significant bit first).
S System number (fixed BCD 0000).
N Identification number in the range from 0001 to 9999.
V Version (fixed BCD 0).
P Odd parity over preceding 4 bits.
D Dummy bits (3 bits binary, fixed bin 001).
Notes: For dual-id transponders only the vehicle-id is used.

If the id-number exceeds the range from 0001 to 9999 then there is no FF-56 bit message sent.
When an Nedap RW80 formatted transponder, HID Prox or Manchester encoded transponder is identified there
will be no FF-56 bit message.

In the figure below the FF-56 bit protocol timing for one BCD digit including parity bit is shown.
5msec
1msec 350µsec
5V
FF56C 0V
FF56D 5V Timing constants:

0V
Clock period 1msec
msb lsb odd parity Clock high 350μsec
0 1 1 0 1 Clock low 650μsec
Figure 12: FF-56 bit protocol timing

P81 firmware
5.7 TEST PROTOCOL

When ‘Test mode’ is selected with the DIP-switches, the output O-1, O-2 and O-3 continuously output a special
test pattern. This is useful to test the Wiegand, Barcode and Magstripe connections.
Connect O-1, O-2 and O-3 successively to the input 1 and watch the input 1 status LED.
O-1 is activated once per second.
O-2 is activated twice per second.
O-3 is activated three times per second.
The test protocol is introduced in P81 v3.09.

P81 firmware
6 SETUP MENU
The complete software configuration of the TRANSIT can be changed by means of the setup menu.
6.1.1 ENTER SETUP MENU

To reach the setup-menu through the serial connection follow these steps:
1. Connect a console terminal or PC running a terminal emulation program to the reader's serial port. The
port settings are 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control (the port settings are not
changed by the DIP-switches).
2. Power off the reader.
3. Hold down the x key on the terminal (or emulation), because after power-up three lowercase x
characters (xxx) must be seen within 1 second to enter the setup-menu.
4. Power up the reader and wait (while still holding the x key) for the message
Firmware version: NEDAP P81xxx
Press Enter to go into Setup Mode
to appear on your terminal.
5. To enter the setup-menu, you must press Enter within 5 seconds. The setup-menu will appear.
Setup Menu:
1. View/Edit settings
7. Factory defaults
8. Exit without save
9. Save & exit setup
Your choice ?
Note: While you're in the setup menu the TRANSIT does not read any transponders. The status LED
periodically flashes twice to indicate that the setup menu is still active.
6.1.2 VIEW/EDIT SETTINGS

Select '1. View/Edit settings' and go through all available settings. To enter a value for a setting, type the value
and press Enter, or to leave the current value unchanged, just press Enter.
Relay hold time (0A hex) ?

Relay hold time in tenths of a second. 0A hex = 10*0.1sec = 1sec. See SC1 on page 18.
Repeat time (00 hex) ?

Repeat time in tenths of a second. 00 hex = do not repeat (Send once). See SC4 on page 18.
Combi-booster inter-id delay (32 hex) ?

Delay on the wiegand interface between the two Combi-Booster events. Also used to disable one of them.
Time in hundredths of a second. 32 hex = 50*0.01sec = 0.5sec. See SC5 on page 19.
Facility code (000A hex) ?

The reader's facility code. Used for cards that do not contain a facility code (such as Nedap cards). Enter in
hexadecimal notation. See SFC on page 17.
Various flags (00 hex) ?

Bit-coded byte with various flags. 00 hex = no flags enabled. See for details SVF on page 20.
6.1.3 FACTORY DEFAULTS

Select '7. Factory defaults' to reset all settings to their factory defaults.
6.1.4 EXIT SETUP MENU

When you are finished make sure to exit the setup menu.
Select '8. Exit without save' to exit the setup menu without saving any changes you have made.
Select ‘9. Save & exit setup’ to exit the setup menu and save any changes you have made.

P81 firmware
7 FIRMWARE UPGRADING
The firmware in the reader can be upgraded through the RS-232 interface. Upgrading is performed by a
freeware application named “PIC downloader” which downloads the firmware file into the reader. The upgrade
procedure is described below.
1. Start the ‘PIC downloader’ application.

2. Select the serial port to which the reader is connected.
3. Select the firmware file (*.hex, *.ehx).
4. Disable ‘download customer codes’ to prevent your customer codes inside the reader to be overwritten.
Enable ‘download customer codes’ when you want to load the customer codes from the hex-file into the
reader. Hex-files on www.nedapavi.com contain DEMO customer codes.
5. Click ‘Download’ to start downloading the firmware.
6. Once the downloading has completed ‘PIC downloader’ displays the message ‘Download successfully
completed’ and the reader starts the upgraded firmware.
Figure 13: PIC downloader
Notes: Aborted downloads may cause the TRANSIT to stop functioning. In such cases repeat the upgrade procedure until
it succeeds.
If the message ‘Searching for bootloader’ does not disappear check the cables and the com-port settings.
Sometimes it may be required to restart the TRANSIT before the bootloader can be found. Before restarting the
TRANSIT make sure that the message ‘Searching for bootloader’ is still shown in the statusbar.

P81 firmware
8 FIRMWARE REVISION HISTORY

Below the P81 firmware modifications are listed. For information on how to obtain the latest release of the P81
firmware contact Nedap.
Version Date Description of change

v3.29 2007-07-19 • Improved handling for uid88 and uid128 on wiegand and magstripe interfaces.
v3.28 2007-07-02 • Bug fixed: initialize MTR Rf-disable.
v3.27 2007-06-26 • Added support for TRANSIT Entry new features.
• Bug fixed: same hid prox card could fail.
v3.26 2007-02-15 • Em-card identification: check 2 times (except when dip7 off).
• Bug fixed: Y-event could appear when identifying em-card.
v3.25 2007-01-26 • Bug fixed: wieg32 together with hid prox didn't work good.
v3.24 2007-01-16 • Removed: herk_bpem (identify biphase em-cards).
v3.23 2006-12-15 • Bug fixed: when test protocol selected ghost numbers and other unpredictable side
effects may appear due to incorrect interrupt routine.
v3.22 2006-11-29 • Added support for HID prox on prox-booster. Requires HIB v2.
v3.21 2006-07-05 • Added Flexible Frame Format support.
v3.20 2006-03-06 • Initialize SDA pin as output (otherwise hang on i2c communication).
v3.19 2006-02-06 • Bug fixed: incorrect end-of-detection for hid boosters. introduced in v3.15.
v3.18 2005-12-23 • Added Wiegand 32 bit with parity format. select with command SVF.
v3.17 2005-12-16 • Added identification of biphase EM400x tags.
• Added bNoIDEvents to disable identifications events.
• Bug fixed: initialize i2c pins as input. i2c module override not good enough.
v3.16 2005-11-11 • Bug fixed: for EM-cards it was possible that incorrectly a battery-low event was generated.
• Bug fixed: search header for em-tags incorrect. did not check the last bit. wrongly aligned.
bug occurs with tags that start with first data bit 1.
v3.15 2005-10-19 • Bug fixed: communication with HID interface board could cause a reader restart.
v3.14 2005-05-11 • Added battery-low support.
v3.13 2004-10-22 • Added HID Booster support.
v3.12 2004-08-30 • Bug fixed: serial communication could hang up under extreme conditions.
v3.11 2004-07-08 • New feature: double data rate recognition (auto switch).
v3.10 2004-06-08 • Bug fixed: could not identify a Combi-Booster with an invalid customer code, but with a
valid EM card.
v3.09 2004-03-12 • Added: select test protocol when DIP1,2 and 3 are OFF.
• Added: generate end-of-detection event if enabled.
• Added: append tag-type to identification event if enabled.
v3.08 2004-01-13 • Added the command messages SR1, SR0, SRT and QIN.
• Changed command message SVF (added relay activation mode).
v3.07 2003-12-10 • Bug fixed: if interrupt latency too long it was possible that a wiegand pulse width became
900 usec wide.
• Bug fixed: setup menu save settings resulted in P-event (instead of O).
v3.06 2003-11-13 • Wiegand pulse width now 50μsec (was 100μsec before).
• Bug fixed which was introduced in v3.05.
v3.05 2003-10-28 • Added setup menu.
• Default value for inter-id delay now 0.5 sec (instead of 0 = only vehicle-id).
v3.04 2003-07-08 • Bug fixed: full duplex RS-232 communication could cause failures.
• I2C acknowledges now properly handled.
v3.03 2003-04-24 • Added Combi-Booster HID support.
• Added Corporate 1000 protocol.
• Added commands SVF/QVF to select Wiegand 37 with facility code.
• Disable vehicle-id when inter id delay is set to hex FF.
v3.02 2003-03-03 • Send ? CRLF instead of NAK when unknown messages are received.
v3.01 2003-01-17 • Bug fixed for wiegand 26-bit. odd parity over last 12 bits incorrect.
v3.00 2002-10-11 • Initial release.
Table 6: Firmware revision history

P81 firmware
A HARDWARE
A.1 TRANSIT PS270
Below an overview of the TRANSIT PS270 hardware components. For more details about the connections and
electrical specifications refer to the TRANSIT PS-270 hardware installation guide.
Figure 14: Overview TRANSIT PS-270 board

P81 firmware
A.2 TRANSIT ENTRY

Below an overview of the TRANSIT Entry hardware components. For more details about the connections and
electrical specifications refer to the TRANSIT Entry hardware installation guide.
Figure 15: Overview TRANSIT Entry board

P81 firmware
B ASCII TABLE
Dec Hex Char Dec Hex Char Dec Hex Char Dec Hex Char
0 0 NUL 32 20 SP 64 40 @ 96 60 ‘
1 1 SOH 33 21 ! 65 41 A 97 61 a
2 2 STX 34 22 " 66 42 B 98 62 b
3 3 ETX 35 23 # 67 43 C 99 63 c
4 4 EOT 36 24 $ 68 44 D 100 64 d
5 5 ENQ 37 25 % 69 45 E 101 65 e
6 6 ACK 38 26 & 70 46 F 102 66 f
7 7 BEL 39 27 ‘ 71 47 G 103 67 g
8 8 BS 40 28 ( 72 48 H 104 68 h
9 9 HT 41 29 ) 73 49 I 105 69 i
10 A LF 42 2A * 74 4A J 106 6A j
11 B VT 43 2B + 75 4B K 107 6B k
12 C FF 44 2C , 76 4C L 108 6C l
13 D CR 45 2D - 77 4D M 109 6D m
14 E SO 46 2E . 78 4E N 110 6E n
15 F SI 47 2F / 79 4F O 111 6F o
16 10 DLE 48 30 0 80 50 P 112 70 p
17 11 DC1 49 31 1 81 51 Q 113 71 q
18 12 DC2 50 32 2 82 52 R 114 72 r
19 13 DC3 51 33 3 83 53 S 115 73 s
20 14 DC4 52 34 4 84 54 T 116 74 t
21 15 NAK 53 35 5 85 55 U 117 75 u
22 16 SYN 54 36 6 86 56 V 118 76 v
23 17 ETB 55 37 7 87 57 W 119 78 w
24 18 CAN 56 38 8 88 58 X 120 78 x
25 19 EM 57 39 9 89 59 Y 121 79 y
26 1A SUB 58 3A : 90 5A Z 122 7A z
27 1B ESC 59 3B ; 91 5B [ 123 7B {
28 1C FS 60 3C < 92 5C \ 124 7C |
29 1D GS 61 3D = 93 5D ] 125 7D }
30 1E RS 62 3E > 94 5E ^ 126 7E ~
31 1F US 63 3F ? 95 5F _ 127 7F DEL
Table 7: ASCII table

P81 firmware
C CARD TYPE IDENTIFIERS

The card type identifier is a byte that contains the following information.
LFA NN1 NN0 CT4 CT3 CT2 CT1 CT0

bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
bit 7 LFA: Low Frequency Antenna (proximity).

0 = The transponder was identified by the long range antenna.
1 = The transponder was identified by the proximity antenna (120kHz).
bit 6-5 NN1:NN0: Non-Nedap card type.
00 = Nedap card
01 = HID prox card
10 = Manchester encoded transponder (e.g. EM unique)
bit 4-0 CT4:CT0: Nedap card type.
00000 = RW80
00001 = Prox-Booster, Smartcard-Booster, Tacho-Booster etc (with extended frame-length)
00010 = Combi-Booster
00011 = HID Booster
0010x = CF-code
0011x = DF-code
010xx = GF-code
111xx = VCF-code (only agri applications) x = don't care
EXAMPLES
NEDAP GF-coded tag identified: Card type = 08, 09, 0A or 0B
NEDAP GF-coded tag identified at the proximity antenna: Card type = 88, 89, 8A or 8B
Combi-Booster identified with a NEDAP card: Card type = 02
Combi-Booster identified with a HID prox card: Card type = 22
HID Booster identified: Card type = 23
EM unique card identified: Card type = 40
EM unique card identified at the proximity antenna: Card type = C0

P81 InstallGuide E

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

P81 InstallGuide E

Uploaded by

Copyright:

Available Formats

P81 firmware

2007-10-19 Part.no. 5268419

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 1 of 40

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 2 of 40

5.6.1 CONNECTIONS .........................................................................................................................................................32

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 3 of 40

The following communication interface protocols are supported:

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 4 of 40

2.1.1 DIP SWITCH SETTINGS

Typical Booster HID application (default setting) ON

Applicable transponders: All long-range (incl. Booster HID)

Applicable transponders: All (also on the proximity antenna)

Optimized for fast identification ON

Applicable transponders: Only Nedap transponders (Window-button, etc).

2.1.2 FREQUENCY SETTING

The frequency setting is described in detail in the hardware installation guide.

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 5 of 40

2.2 STEP 2 – HARDWARE INSTALLATION

2.2.1 POWER SUPPLY

2.2.2 WIEGAND, MAGSTRIPE, BARCODE COMMUNICATION

DESCRIPTION WIRE COLOR CONNECTION NAME

2.2.3 RS-232 COMMUNICATION

TRANSIT SIDE PC SIDE

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 6 of 40

2.3 STEP 3 – SOFTWARE CONFIGURATION

Figure 1: P81TEST software

2.3.2 SETUP MENU

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 7 of 40

3 DIP SWITCH SETTINGS

The selected communication protocol is only changed after a restart.

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 8 of 40

4.1 LONG RANGE VEHICLE BASED IDENTIFICATION

4.2 LONG RANGE DRIVER BASED IDENTIFICATION

4.3 PROXIMITY IDENTIFICATION

4.4 IDENTIFICATION PROBLEMS

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 9 of 40

5.1 RS-232 PROTOCOL (CR/LF)

5.1.1 DATA FORMAT

5.1.2 MESSAGE FORMAT

Every CR/LF message is terminated with a carriage-return and linefeed character:

5.1.3 EVENT MESSAGES

5.1.3.1 Reader Status Events

Reader reset ('P')

Notes: In case the P-event is sent the O-event is omitted.

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 10 of 40

5.1.3.2 Identification Events

Figure 2: Timing diagram identification event

Figure 3: Timing diagram repeat time

Window Button / Compact Tag / Heavy Duty Tag

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 11 of 40

Manchester encoded transponder (EM unique)

Where: xx..xx Identification number 10 hex digits (=40 bit).

Where: aaaaaa Vehicle identification number in range from 1 to 999999.

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 12 of 40

Combi-Booster HID / Prox-Booster

Where: aaaaaa Vehicle identification number in range from 1 to 999999.

bbbbbbbbbb = 000003B207 Facility code ID-number

Figure 4: Example HID card data

Booster HID / Prox-Booster single-id

© Nedap AVI, P.O. Box 103, NL-7140 AC GROENLO Page 13 of 40

Combi-Booster LEGIC / Smartcard-Booster LEGIC

Where: aaaaaa Vehicle identification number in range from 1 to 999999.