User guide
Table Of Contents
- 1. Introduction
- 2. Specifications and Requirements
- 3. Installation
- 4. System Overview
- 5. How to Set Up a Site
- 5.1 Adding Time Zones
- 5.2 Adding Holidays
- 5.3 Adding a Network
- 5.4 Adding Access Control Panels
- 5.5 Configuring the Doors
- 5.6 Configuring the Readers
- 5.7 Configuring the Inputs
- 5.8 Adding a Camera
- 5.9 Adding Panel Links
- 5.10 Creating Groups
- 5.11 Adding Users and Cards
- 5.12 Adding Departments, Users, and Visitors
- 5.13 Adding Access Areas
- 5.14 Adding Global Antipassback Rules
- 5.15 Car Parking
- 5.16 Adding Operators
- 5.17 Creating Elevator Control
- 5.18 Creating Status Maps
- 6. ViTrax™ Video Integration
- 7. Manual Operation
- 8. AxTraxNG™ Reports
- 9. Administrator Operations
- A. Firewall Configuration
- B. SQL Service Settings
- C. Network Configuration
- D. Restoring Factory Default Settings
- E. Configuring User Counters
- F. Cross Platform Camera Setup
- G. Enrolling Cards using MD-08 Desktop Reader
- H. SQL Server Installation Troubleshoot
- I. AxTrax.NET Watchdog
- J. Adding Custom Wiegand Formats
Adding Custom Wiegand Formats
134 AxTraxNG™ Software Installation and User Manual
J. Adding Custom Wiegand Formats
The Wiegand protocol it the most common protocol between readers and
controllers. This protocol is actually a collection of bits that represents the
number of the user card ID.
There are many types of Wiegand protocols. Protocols differ from one another
depending on the following three factors:
The number of bits sent per card
The most common format is 26-bit, but there are many more types such
as 30-, 32-, 35- , and 36-bit.
The representation of the user number
In each card, there is a number that defines the user, but the
representation of this number inside the Wiegand protocol can be
changed. In addition, there is a Facility code in most protocols, which is
not part of the number but is common to all users in this particular area.
There are cards with additional codes such as Site code, but AxTraxNG™
recognizes them as a Facility code only. This means that if a card has both
a Site code and a Facility code, AxTraxNG™ recognizes the first Facility
code and the second Facility code is ignored.
The authentication mechanism and its type inside the bit stream
In most protocols, there is a certain type of authentication of the data
transferred from the reader to the controller.
Once the user knows the format of the card, meaning how many bits there are
per card, the user can use the other two factors to create new rules, which can
then be enrolled into the software to teach the controller to understand the
new format.
J.1 Representation
The following options are available when discussing the number
representation:
Card number is represented in a binary or hexadecimal code
All the bits in the protocol are represented with ‘D’, which stands for data.
Card number is represented in the protocol as a “reverse bytes”. For
example, if the number (hexadecimal) is 34 65 89 32, then it is
represented as: 32 89 65 34.
All the bits in the protocol are represented with ‘R’.
Card number is represented in the protocol as a “reverse bits”. For
example, if the number (hexadecimal) is 34 65 89 32, which is
represented in binary code as:
00110100 01100101 10001001 00110010