Issue
- I/NET Seven and Key Card translation
- What is the Key / Card Translation table and how do I use it?
- Can I use the Key / Card Translation table for other card types other than I/DISC?
Product Line
TAC INET
Environment
I/NET all revisions
Cause
Need to understand what is the Key / Card Translation table and how do I use it.
Resolution
As I/NET evolved it first used what might be called a sequential look up table to translate I/DISC keys from number much to big for the DPU / SCU to interpret to one of the 1 to 24,000 (32,000 current) individual numbers permitted in a Tenant. The I/DISCs are shipped in lots from the manufacturer and the container states the starting key number, e.g. 897541, and the number of keys in the container.
I/NET has an editor called Key / Card Translation that allows associating those I/DISCs with an individual. The box labeled Source is used to enter the first key/card in a lot of keys (usually read off the container). The Target box is used to assign the key to an individual in a Tenant. The Count box is used to set how many sequential keys will be associated with individuals.
There are four card types that can be read directly without a translation table, Wiegand 26 and 32 bit and ABA 115 and 85. On the Wiegand cards the Tenant Code must match the site or tenant code on the cards and the card number must be less than 24,000. For all four types of card Switch 7 on the DPU is set to off. Wiegand 66 bit, Custom Wiegand and Custom ABA must be selected to use a translation table, and Switch 7 on the DPU is ignored.
The next evolution involved allowing the “big (large) card number” to be stored with the Individual. This removes the requirement of using the key / card translation editor.
Please see the following document for additional details and examples: Card Numbers.doc
