Using 26-Bit Wiegand Format on Different Hardware Types

Using 26-Bit Wiegand Format on Different Hardware Types

1.0 Introduction

When using NXT or NXT-MSC controllers, the 26-bit card data is processed using the same 26-bit Wiegand format (which is added to the Doors.NET system, by default). 

If you have Credential Types enabled on your Doors.NET system, the default 26-bit format is the one highlighted.

However, there are other supported hardware types that will require an additional credential format to be added - for the card data (card number, imprint and facility code) to be processed and displayed exactly the same in Doors.NET. These other hardware types include the following:
  1. Wiegand readers connected to 'Real Mercury' hardware, such as EP and LP series controllers
  2. AD-400 readers connected to a PIM400-485 that's wired directly into the NXT-MSC controller
This document explains how to add a second 26-bit Wiegand format to Doors.NET so that the credential imprint, facility code and card number are displayed the same in Doors.NET (regardless of the reader hardware in use on the system).

2.0 Licensing Requirements

Adding additional Wiegand formats requires you to have 'Credential Formats' enabled on your Doors.NET license.

3.0 Adding the Additional 26-bit Wiegand Format

  1. From within Doors.NET, go to Setup >> Credential Types.

  2. Click the ADD ACTIVE FORMAT button.
  3. Select the new format entry and the properties will appear on the right.
  4. From the format drop-down list, select the '26-bit with 24-bit cardnumber' format.
  5. Click the save icon to save the new format.

  1. The NXT-MSC controllers and RIMs will use the Wiegand 26-bit (Full Pattern NXT format)
  2. The AD400 readers connected to a PIM400-485 (that's wired directly into the NXT-MSC controller) or readers wired directly to 'Real Mercury' hardware will use the '26-bit with 24 bit cardnumber' format.

4.0 Assigning the New Format to a Reader

The next step is to enable the new format - for readers that are not connected to NXT-MSC controllers via a RIM (reader interface module). Any readers that are wired into a RIM will continue to use the default 26-bit format (and do not require the format to be manually assigned).
  1. Go to Setup >> Hardware Setup >> All.
  2. The hardware tree will display.
  3. Navigate to (and select) a reader that will be using the new Wiegand format.
  4. The reader properties will appear on the right.
  5. Ensure Advanced View is enabled for the reader properties.
  6. Locate the Card Formats section. By default, the reader will be configured for all formats.
  7. Set all formats to No and then enable the new format (as highlighted).

  8. Save the reader settings.

5.0 Verify the Credential Data in Live Events

The final step is to present the credential at different readers and ensure the programmed card data displays correctly in live events.

6.0 Adding NXT-MSC Controllers to an Existing 'Real Mercury' System

If you have an existing system that consists of 'Real Mercury' EP or LP Series controllers then the readers will be using the 'H10301' format (displayed in Credential Types as 'Standard 26-bit HID H10301') - this format allows new credentials to be enrolled by only entering the imprint (the number physically printed on the credential) and the facility code is stored in the format settings.

When NXT-MSC controllers are connected to Wiegand readers via a RIM you will need to add a new format that will also allow you to only enter the imprint when enrolling credentials. You will need to add the '26 bit Keri NXT format' and then assign that to the readers on the NXT-MSC controller(s).

  1. The Real Mercury (EP/LP) controllers will use the 'Standard 26-bit HID H10301' format
  2. The NXT-MSC controllers with RIMs will use the 26-bit (Keri NXT) format
Once the additional format has been added, you will need to assign the new format to the NXT-MSC readers (see section 4.0 for credential format assignment to a reader).

    • Related Articles

    • Using Multiple Hardware Types in Doors.NET

      Doors.NET is capable of running multiple concurrent hardware platforms. The ability to support multiple concurrent hardware platforms was introduced in Doors.NET v3.5.1.19. Support for the Entraguard, the PXL-G and the PXL-LC was introduced in ...
    • Setup Credential Types

      1.0 Introduction A card format is a set of instructions for the reader to use when decoding a card that a user has presented for identification. There are a number of different reader technologies on the market today. Most of the reader technologies ...
    • Enrolling a 32-bit MIFARE Credential in Doors.NET

      1.0 Introduction This section explains how you can add the 32-bit Mifare CSN (Card Serial Number) and as active card format. Once added, when the reader recognises the credential type, it will pass all 32-bits of the card number to the controller. ...
    • Global Unlock - Hardware

      1.0 Introduction Included in Doors.NET is the ability to perform a Global Unlock of all doors on the system from an input on the system, designated as a Global Unlock input. This input cannot be programmed for any door function; such as ...
    • Setup a Hardware Gateway Using the Gateway Wizard

      Effective from version of Doors.NET a gateway is typically setup using the License Manager. However, there are situations where the hardware gateway needs to be installed on a remote workstation. The Gateway Wizard allows you to add a remote ...