HandKey

Technical Handbook

Recognition Systems Inc.

1520 Dell Ave.

Campbell, CA. 95008

WWW.RECOGSYS.COM
The data inside this hand book was written with the goal of helping the factory reps. and
dealers to better understand how the HandKey has evolved. I have also included some
of the do’s and don’ts of operating, installing and troubleshooting our access control
products.

This hand book will never be complete......this means it will always evolve and get
better. As we upgrade or products I will update this document. I also invite constructive
criticism on this document. If you see something that is not correct, please let me know.
If you have suggestions for inclusion it this document, please let me know.

Enjoy!

Scott Hallmark

[email protected]
Evolution of the HandKeys:

Gooseneck
Mod “C”. serial #’s 2000-2999. These units used a white light. There are still quite a few of these out
in the field an working.

The Rev. 1 version. About 50 total built. The Rev 2 communicated via an RS-232 port. It had
an acrylic neck. The I/O card had 2 RJ-11 connectors and 1 terminal strip.

The Rev. 2 version had the capability to communicate via a RS-422 network. The I/O card had
3 terminal strips but no RS-232 communications.

Blue Box
Mod “D”. serial #’s 3000-3999. These units are often referred to as “Blue Box” units. These used
both white light and blue light.

ID3D-R
Short board: These were installed in the 4000 series units.
Long board-E5 (no retaining
screws); These circuit boards
started around the 4400 serial #’s.
Instead of being screwed down to
the chassis, they had plastic
inserts mounted to the side of the
chassis. The circuit board would
then slide up the insert into place.
The other difference was that the
LM340T voltage regulator was
mounted directly to the chassis.
The regulator was then connected
to the circuit board using a ribbon
cable. These units had firmware
version 4.04 - 5.02.

Long board-E5 (retaining screws)

These circuit boards started around the
4800 serial #’s. These circuit boards were
screwed down to the chassis. The difference
between this board and the previous board
was that the LM340T Voltage regulator was
attached directly to the circuit board.
Therefore the circuit board was attached to
the dust shield on the back of the. This was
done so the dust shield could act as a heat
sink. These units had firmware version 5.05
up to 5.12
E6 circuit board
The E6 circuit board was the first
major improvement in 3 years to the
circuit board. All input and outputs on
the circuit board were transient
protected. The power supply circuitry
was streamlined to provide better
efficiency and less current draw. The
jumper W1, 4, 5 and 7 were removed
and replaced with a dip switch bank.
The E6 circuit boards have
firmware versions starting with E6.
Theory of operation:

How the HandKey views a hand then stores it (laymen terms):

The HandPunch uses an infra red light source, much the same as the light used in a typical
television remote control, along with a camera chip. When you place your hand in the HandPunch on
a reflective surface that is called the “Platen”. The “Platen” has five finger pins to guide your hand
for correct positioning onto the Platen. The hand is positioned correctly when the finger pin lights on
the top panel of the HandPunch extinguish. The HandPunch determines the correct hand position by
looking a certain pixels on the platen. When these pixels no longer reflect the light associated with
that pixel is turned off.

Mirror

Side view

Camera/IR Lights

Reflector

When the hand is positioned correctly, the camera records an image of the hand. The drawing below
demonstrates, in a simplified way, what the camera sees. As you notice the hand image appears as
a black shadow. As you can see we can easily distinguish the length, width, surface area and with
the side mirror (not shown) height of hand.
The hand template data is then converted into a nine byte template. This template is then stored in
the transaction buffer as an enrollment message also in the static memory (stand alone system). In
the case of a HandKey that is connected to a host computer this message is then retrieved when the
HandKey is polled by the host software and brought up to the host computer. Once the hand
template data is brought back to the host computer, the ID number associated with the enrollment
message is compared against the user database in HandNet /HandNet Plus. If a matching ID is
found, the hand template data is re-written back to the originating HandKey and stored in the “Things
to do” or “TTD” file and distributed to the remainder of the HandKey network.

How the hand template is distributed

In order for users to be able to use multiple hand readers within a HandKey system the hand
templates must be distributed. Once the hand template data is brought back to the host computer it is
stored in the HandNet/HandNet Plus database. If HandNet/HandNet Plus determines that the hand
template data needs to be distributed to any other sites, the hand template data is placed in the
“Things to do” file or “TTD”. The “TTD” file is basically a storage area for actions that are to be
carried out when a particular site is polled that wasn’t previously connected to. Once the site is
connected to, HandNet/HandNet Plus checks the “TTD” file to see if any actions need to be carried
out while connected to that particular site. If an enrollment template needs to be downloaded, then
the hand template data is downloaded to the correct hand readers connected to that site. Now the
enrolled user can verify at any hand reader at that site.

How an ID is verified at the HandKey

When a user verifies their ID, the HandKey compares their stored template with their current hand
placement. When this comparison is made the difference between the two templates is noted. The
difference between the two templates is expressed in the form of a “score”. The lower a score is, the
closer the two templates are matching favorably. When an ID is verified the HandKey LCD will
display.................
When the “Score” is lower than the
“User reject” or the “System reject” if the “User reject” is not defined. Then the person’s identification
is verified. Think of the “reject threshold” as a limbo bar. If you lower the limbo bar, it is harder to be
verified. If the limbo bar is raised, it becomes easier to be verified.

Common applications:

Stand Alone:
A Stand Alone configuration, is a HandKey that is not connected to either a host computer nor
another HandKey. This means that the BackHand software should be used with this type of
installation. The reason for this is that if the reader fails you will need some form back up of the
hand template data. Otherwise the customer will have to re-enroll all of the users.
Master/Remote Network:
This is a network of two or more HandKey’s connected via an RS-485 or RS-422 network. The
maximum length of either the RS-485 or 422 network is 4000’. In this type of configuration, users
must be enrolled and removed from the master unit. It is also a good idea to use the BackHand
software to back up the hand template data.

Master/Remote
RS-485 Network

Master/Remote
RS-422 Network
Remote in Host PC network:
In this type of system all of the HandKey’s will be designated as “Remotes”. In this type of
configuration, users can be enrolled from any HandKey within the system because of how templates
are distributed by the host computer. Removals on the other hand should be done from the host
computer so the user is removed globally. If a user is just removed from the HandKey, the hand
template will still exist at the host computer. Therefore the user can still be downloaded from the host
computer to the HandKey inadvertently.

E5 Circuit board to DC-101

connection and jumper settings
for an RS-485 network.

E5 Circuit board to DC-101

connection and jumper settings
for an RS-422 network.
E6 Circuit board to DC-101 connection and
dip switch settings for an RS-485 network.

E6 Circuit board to DC-101 connection and

dip switch settings for an RS-422 network.
HandKey communicate to host PC via printer port (CH1)

This is a rarely used connection. The most common industry to use this type of configuration is the
health club/fitness industry. The host computer is connected to the HandKey via the channel 1
(printer port) this port is uni-directional. Meaning that data is transmitted from the HandKey out of
channel 1. There is no communications from the device to the HandKey. Therefore there is no
capability to retrieve the data once it has been transmitted out of channel 1. What usually happens
in this scenario is that the host computer has a program that monitors the inbound data from the
HandKey. When the software sees the data string it is looking for it reacts to the string a completes
action based on how the software is written. Normally this would be to record the ID number and
record the time and date that the user verified their ID at the HandKey.
HandKey as lock controlling unit:
This is the primary use of the HandKey and it shows in the design. The HandKey has a lock output
that will provide a “Wet Contact” type of relay closure. This circuit will provide a 12 volt DC output at
100 milli-amps of current. When an external locking device is connected to the HandKey, an
isolation relay should always be used. See the drawing below:

On an E5 circuit board the “Output mode” must be

set to Lock & Aux” via the “Set output mode”
command. Also the W4 jumper must et for “Lock &
Aux” output.

If an E6 circuit board is being used, only the “Output

mode” need be set for “Lock & Aux” output. The W4
jumper was not replaced by the dip switch bank n the
E6 circuit board.

If a door strike is used as a locking device, a 12 VDC

normally open relay should be used. If a Mag lock is
used as a locking device a 12VDC normally closed
relay

HandKey interface with card reader system:

If a HandKey is to be interfaced with a card reader system the output of the HandKey should be
wired as shown below.
The standard firmware for the HandKey will accommodate a 26 bit Wiegand format. If Magnetic
stripe computability is required, the HandKey must be ordered with the “Mag Stripe” firmware
installed. There are two different version of magnetic stripe firmware. Both are ABA/ANSI track 2
compatible. One version, the most common, is configured so that when the data is equal to 1 or high
the voltage is 5VDC. The other and less common method is data is equal to 1 or high, the voltage is
0VDC. The latter is common to American Magnetics equipment.

On an E5 circuit board the “Output mode” must be set to Car rdr out” via the “Set output mode”
command. Also the W4 jumper must et for “Lock & Aux” output.

If an E6 circuit board is being used, only the “Output mode” need be set for “Lock & Aux” output. The
W4 jumper was not replaced by the dip switch bank on the E6 circuit board.

Things to look out for when using the HandKey in card reader emulation mode are………………..

1. Most Wiegand formats require a “Site” or “Facility” code. The “Site” or “Facility” code is a set of
digits that identifies a certain customer or location. These are used to ensure that two matching
ID numbers can’t gain access to two different facilities/companies. Example: Joe, at ABC Co. has
an ID number of 1234 and John has an ID number 1234 at XYZ Co. Theoretically Joe could use
his card to access XYZ Co. and John could use his badge to access ABC Co. The use of ‘Site”
or “Facility” codes ensures that only badges from a certain location are allowed access within that
particular facility. Therefore the “Site” or “Facility” code needs to be programmed into the
HandKey. The HandKey would then output the correct “Site” or “Facility “ code with the ID
number to the card reader panel or head end.

2. It is not recommended to use the “ID Length” feature on the HandKey when used in conjunction
with a Card Access system. There is a risk of truncating the ID number that is output to the card
reader panel or “Head end”. This raises the possibility of the correct person not being granted
access by the Card Access system.

3. A 26 bit Wiegand format is broken down to include 8 bits for the facility code and 18 bits for the
ID field/number. This means the highest ID that can be assigned in a 26 bit Wiegand system is
25,536. No ID number may be assigned that is larger than 25,536. If ID numbers larger than
25,536 are needed, a different Wiegand format is required.
Options:

Wall mounting kits:

There are 4 different ways a HandKey can be mounted………………………………………………….

Table top: The HandKey comes standard, with the ability to be mounted to a table top. There are four
8/32 inch treaded stand-offs located on the bottom of each unit. These allow units to be mounted a
desk, counter or similar type of surface. When using the table top mount, it recommended that a
back door also be ordered with the unit. The back door covers the back of the HandKey. The back
door is not only aesthetically , better looking. It also guarantees tamper proof use of the HandKey by
securing all electrical connections.

Recessed Wall Mount (WM-

200): This type of wall mount
recesses the HandKey
approx. 3 inches into the wall.
This is a common use where
sheetrock is used on the wall
surface. The WM-200 uses a
lock to secure the HandKey to
the wall mount.
Surface Wall mount (WM-201): This
type of wall mount allows the HandKey
to be mounted flush with the wall
surface. The WM-201 is commonly
used on concrete or brick (hard surface)
walls. The WM-201 also uses a lock to
secure the HandKey to the wall mount.
 ID3D-RW (Outdoor reader): The ID3D-RW or “Outdoor”
reader comes with a wall mounting kit that is specific to
the “Outdoor” HandKey.

The ID3D-RW can be mounted to a pedestal as shown

or a more common method would be to flush mount the
ID3D-RW to a wall. There are no knockouts or mounting
holes pre-drilled in the ID3D-RW wall mount kit.

The wall mount for the ID3D-RW does not need be

ordered. It is included with the ID3D-RW.

Internal modem (MD-200)

The MD-200 or internal modem is used when the distance form the HandKey to the host computer
will exceed the 4000 ‘ limitations of the RS-422 or RS-485 specifications. The MD-200 is a 2400
baud dial up modem. This a no frills variety of modem. Therefore special modem initialization strings
are required. A list of known compatible modems and their associated modem strings are maintained
by RSI’s technical support. Please contact RSI’s technical support department and request the
modem string document before ordering a MD-200.
Power supply:
The IS-400 power supply is a “Float” type
charger. It can be used alone or in
conjunction with the BB-200 battery back up.
The IS-400 is a regulated 12 volt supply
rated at 500 milli amps of output. Since the
HandKey draws around 300 milli amps of
current, each HandKey will require it’s own
IS-400.
- +

Battery back-up:
BB-200: The BB-200 is a
12 battery that is rated @
2Ah. This battery was
designed to be used with
the IS-400 power supply.
The BB-200 will provide
about 2 hours of use when
connected to an E5 circuit
board and approx. 3 to 3 ½
hours of power to an E6
circuit board.

The BB-200 should be wired directly into pins 1 and

2 of the HandKey along with the IS-400 power
supply. The IS-400 and the BB-200 were
engineered to work together. Consult factory before
using another power supply with the BB-200.
Extended memory:

The HandKey comes with a standard memory configuration to accommodate 256 users. If extra user
memory is required the HandKey can either be ordered from the factory with extended memory
installed or the memory can be field installed. Below are the memory levels for both the E5 and the
E6 circuit boards.

E5 Circuit board
PART NO. STANDARD EM-200 EM-202 EM-204
CAPACITY 256 2304 8448 20736

E6 Circuit board
PART NO. STANDARD EM-600 EM-602 EM-604
CAPACITY 256 3,328 9,728 27,904

Outdoor reader:

The ID3D-RW or “Outdoor” reader is used when the HandKey is to be mounted externally on a
building. And ID3D-RW is built by mounting a regular HandKey chassis inside an outdoor enclosure.
The ID3D-RW is substantially larger than a standard HandKey. Therefore attention to mounting
locations may be required. Also ID3D-RW’s should not be mounted in such a way to allow the sun to
shine directly on the platen. Doing so runs the potential of adversely affecting the HandKeys ability
to correctly read hands. The ID3D-RW should also be mounted so that exposure to the elements be
limited. Failure to do so will increase the amount of preventative maintenance needed to maintain the
integrity of the HandKey.
Platen heater:
The Platen heater is used only on the ID3D-RW. The heaters purpose is to make the reader more
comfortable for users when the unit is subjected to unusually cold weather. The heater also has a
secondary purpose. That is to provide a more electronically friendly environment to the HandKey.
The addition of the heater in humid areas will cut down on condensation. Condensation can also be
a factor in cold environments.

The Platen heater will keep temperature of the HandKey at 70 +or - 5 degrees F. This is done
through the use of a bi-metal thermostat that is mounted on the side of the HandKey chassis. This
thermostat is wired in series with the heater(s).

There have been two different styles of the Platen heaters over the years. The first being a 110 VAC
version. As of July 1997 we switched over to a 12VAC version of the heater. The 12VAC version will
have bright yellow label attached to the leads of the heater. This label will have “24VAC” printed on it
to indicate that it should only be connected to a 12 VAC source.

LCD heater:
The LCD heater’s purpose is to prolong the life of the LCD in very cold weather. In freezing or near
freezing temperatures, the LCD will malfunction. The LCD heater should be installed with the Platen
heater
Special firmware:
Special firmware is a necessary evil in the access control world. Here are just a small portion of the
reasons special firmware is made.
• To convert the text from the standard English prompts to another language (Spanish, Japanese,
etc.)
• To provide a Wiegand output format other than a 26 bit format.
• To remove menus or add special function menus
• To change default setting such as baud rate or reader mode etc.

Wiegand keypad (KP-101):

In applications where a single ID3D-R HandKey is needed to control two doors, a Request To Enter
Keypad should be used. The KP-101 controls access at the first door by requiring the user to enter
their ID number. If the ID number resides in the HandKey, the user will be allowed to open the first
door. The second door is controlled solely by the KP-101. The user follows the normal HandKey
procedure to enter this door. A two color LED is used to prevent the users from using the Request to
Enter Keypad when the HandKey is in use. The LED on the keypad will be green when it is OK to
use the keypad and red when the HandKey is in use. This type of application would be particularly
useful in a “man trap”.

When the KP-101 is used the auxiliary output can not be used for anything other than the KP-101.
The figure below shows how the KP-101 is to be wired to the HandKey.

KP-101 Terminals HandKey Terminals Signal

1 18 +5 VDC
2 21 Data 1
3 10 LED
4 19 Data 0
5 22 Ground
Keypad Harness (KP-104):
The KP-104 is used in conjunction with the KP-103. The KP-104 is an internal harness that allows
the KP-103 to be connected to the HandKey circuit board.

Request to exit keypad (KP-103)

The KP-103 keypad assembly and interior harness (KP-104) are used to provide “Request to Exit “
capability for the ID3D-R HandKey. This configuration requires the user to enter their ID number to
exit the secure area. If the ID number has been previously enrolled and is currently stored in the
HandKey memory, the HandKey will unlock the controlled door, shunt the alarm and datalog this
event.

The figure above shows what the actual keypad will look like. Behind the keypad plate is a RJ-11
jack where the cable for the KP-103 will plug. The RJ-11 jack has a red lead attached to the bottom
of the RJ-11 jack. This red lead can be moved between the two positions noted on the drawing
below. The drawing on the left shows where the red lead should be if the keypad is to act as a
“Remote” keypad. The
drawing on the right shows
where the red lead should
be if the keypad is to act as a
“Request to exit” keypad.
Remote keypad (KP-103)
The ID3D-R HandKey ships from the factory configured with a keypad mounted to the face plate for
ID number entry. For applications where the capability to enter ID numbers remotely in addition to
the attached keypad, order the KP-103 and KP-104 at the same time the HandKey is ordered.

For applications where the ID number will only be entered by other means (i.e.: card reader input)
and removing the attached keypad would be appropriate for the application, order the KP-103 and
KP-104 at the same time the ID3D-R HandKey (specify no attached keypad) is ordered.

The figure above shows what the actual keypad will look like. Behind the keypad plate is a RJ-11
jack where the cable for the KP-103 will plug. The RJ-11 jack has a red lead attached to the bottom
of the RJ-11 jack. This red lead can be moved between the two positions noted on the drawing
below. The drawing on the left shows where the red lead should be if the keypad is to act as a
“Remote” keypad. The drawing on the right shows where the red lead should be if the keypad is to
act as a “Request to exit” keypad.
Keypad cover (KP-105):
The KP-105 is used when no keypad is mounted to the top panel of the HandKey. The KP-105 is
normally used in conjunction with the KP-103 Remote keypad. But only when “no attached keypad” is
specified on the order.

Red/Green light:
The Red/Green light option gives a visual representation of a users verification. A small LED is
mounted above the keypad on the HandKey. When a person’s ID is verified the LED will light in a
green color. If a person attempts to verify their ID but they are rejected by the HandKey the LED will
light up in a green color. This type of application is particularly useful when a language barrier is
present between the user and the HandKey prompts displayed on the LCD.

Card reader:
There are several types of card readers than can be used with the HandKey. Some of which will
require non-standard firmware to be installed in the HandKey. Below is some of the specific types of
card readers, how they can be mounted and the do’s and don’ts.

• Magnetic stripe; The magnetic stripe (Mag) is the most commonly used of all the card readers.
The Mag stripe card reader that RSI uses will read a ABA/ANSI track 2 formatted card and input
the card number into the HandKey for processing. If the application requires that the HandKey
output a magnetic stripe formatted ID number, mag stripe compatible firmware will need to be
installed in the HandKey. The mag stripe card reader can either be top mounted or side mounted
or no mounted to the HandKey at all. The top or side mounted application can not be used in
conjunction with a WM-200 wall mount. It is also not advisable to use a card reader with the
ID3D-RW (Outdoor reader). None of the card readers RSI uses are suitable for outdoor use in
adverse weather.

• Wiegand; RSI does not currently stock Wiegand card readers. None the less these can easily be
used as an ID input device to the HandKey. Remember that the HandKey comes with standard
firmware that will accommodate a Wiegand 26 bit format. If the end users application calls for a
format other than a 26 bit Wiegand, special firmware will be required.

• Bar code; RSI currently uses a swipe style bar code reader. This reader will accommodate
several types of bar code format the most common of which is 3 of 9 or 2 of 5 interleaved. This
may once again require special firmware. This reader is not mountable to the HandKey chassis
due to it’s size.

Software:

HandNet:
HandNet was RSI’s first generation of access control software. HandNet is DOS based software. It
will accommodate up to 32 HandKey ‘s connected to Comm 1 of an IBM compatible computer.
HandNet used Checksum and CRC for error checking of data transmission between the HandKey
and HandNet. Therefore early versions of the firmware 5.01 and up will work with HandNet.
HandNet Large:
HandNet large was a modified version of HandNet. The difference between HandNet and HandNet
Large was that HandNet Large could accommodate up to 120 readers. Reader addresses were
assigned to each Comm port and could not be changed. For example readers 0 through 31 were
assigned to Comm 1, 32 - 63 were assigned to Comm 2, 64-96 to Comm 3 and 97 - 120 were
assigned to Comm 4. The main two reason’s HandNet Large existed was the fact that the distance
of some networks may exceed 4000’ and several sites had more than 32 HandKeys installed.
HandNet Large used Checksum and CRC for error checking of data transmission between the
HandKey and HandNet Large. Therefore early versions of the firmware 5.01 and up will work with
HandNet Large.

HandNet Plus:
As the HandKey became more widely accepted in the access control world, larger networks were
needed. Thus HandNet Plus came into existence. Along with the need for multiple Comm ports and
120 HandKeys, many refinements were added to HandNet Plus. Reader could be assigned to any of
the 4 Comm ports. Status labels were added to each HandKey plus many other features. HandNet
plus only uses CRC for error checking therefore only firmware versions 5.06 and up will work with
HandNet Plus.

BackHand:
BackHand is hand template back up software. RSI used to a Tandy disk drive unit to make template
back-ups. The disk drive unit was used with version 5.06 of the HandKey firmware or earlier
versions. Tandy quit manufacturing the disk drive unit so RSI had to find another way of doing
template back-ups.

MT:
MT or the software development disk as it is often referred to, is free software RSI will distribute
when the need arises. The MT disk has the low level comm drivers that allow software programmers
to write custom applications that work with the HandKey. A copy of the software manual is usually
sent out with the MT disk. The MT disk is not Windows compatible.

DLL’s
The Window’s DLL’s are basically the equivalent to the MT disk. The main difference is that these
allow Windows programmers to write applications for the HandKey that are Windows 16 & 32 bit
compatible.
Repair Procedures

The following are the repair procedures used by Recognition Systems Inc. Failure to
follow these procedures may delay the repairs of HandKeys and HandPunches.

1. When experiencing technical difficulties with a HandKey or its associated software, call
the dealer who installed the system first. The installing dealer is to be the front line of
support for technical problems.

2. If the dealer is not able to correct the problem, the dealer will then contact the technical
support department of Recognition Systems via the telephone or fax to rectify the
problem.

3. If the Recognition Systems technical support department determines that the problem
can not be corrected via the telephone or fax, the unit will need to be sent back to the
factory for repairs.

4. The technical support department will need the following data before any repairs will be
attempted on a hand reader:

• End User’s Name

• Shipping Address
• Serial Number of unit
• Billing Address
• Technical Point of Contact Name and Phone number
• Billing Point of Contact Name and Phone number
• Method of shipment
• Purchase Order Number
• Symptoms defective unit is displaying

Once the above data is received by the Technical Support Department, a RMA number will
be issued. Units received by Recognition Systems without the above data will not be
repaired until a RMA number is issued.