Overview

This guide explains how to use the data extracted from the RF IDeas Configurator Tool to define a Wiegand format in the Oloid system. Accurate format definition enables seamless integration for access control.

Introduction to Wiegand Format Definitions in Oloid

What is Wiegand Format?

The Wiegand format is an access card data encoding system used in access control applications. It allows card readers to transmit encoded data to controllers. Proper configuration ensures compatibility between the reader and access card (badge or NFC).

Key concepts:

Bit length: The number of bits in a badge binary.

Parity bits : A parity bit is used as a very simple quality check for the accuracy of the transmitted binary data.

Facility code: This is a number that represents the facility or building that the card will be used in.

Card number: The unique ID on the RFID card. Typically located on the card's back, it includes a manufacturer number and a unique chip number.

Gathering Required Data from the Configurator Tool

The following data is required from the RF IDeas Configurator Tool to configure Wiegand Format in Oloid Portal:

bit length,
facility code,
card number

Refer to screenshots below to locate the above data

Note : You need to scan the card on the reader and click GetID to see the Data bytes

Facility Code Calculation

To calculate the Facility Code for a 26 bit card, follow the steps below:

Locate the Hex code ( as shown in above screen) from the rf IDEAS configuration utility app.
Convert the Hex Code to Binary.
Convert the obtained Hexadecimal code into its Binary equivalent. You can use any standard Hex-to-Binary conversion tool or perform the conversion manually.
Adjust to 26 Bits
If the Binary number is shorter than 26 bits, add leading zeros to make it a 26-bit Binary number.
Note: This step is necessary because the card format being used is 26 bits.
Break Down the Binary Format
In a 26-bit card, the Binary number is divided into the following segments:
- First digit and last digit: Represent the parity bits.
- Next 8 digits: Represent the Facility Code.
- Last 16 digits (excluding parity bits): Represent the Badge ID or Card Number.
Calculate the Facility Code.
- Extract the 8 Binary digits that represent the Facility Code.
- Convert these Binary digits to their Decimal equivalent.
  The resulting Decimal number is the Facility Code.
Calculate the Card Number.
- Extract the remaining 16 Binary digits (Badge ID).
- Convert these Binary digits to their Decimal equivalent.
  The resulting Decimal number is the Card Number.

Note : For cards other than 26 bits, contact the Oloid Technical Team for assistance.

Accessing the Wiegand Format Definition Section in Oloid

To configure Wiegand formats in the Oloid platform:

Log in to the Oloid Portal.
Navigate to Wiegand Access via the left menu panel on the home page..
Select the desired Wiegand Name to view its details
The Weigand details page is displayed.

Creating a New Wiegand Format

Refer to below guides to Create New Format in Oloid.

Mapping Card Data to Wiegand Fields in Oloid

Map the following data extracted from the Configurator Tool to their respective fields in Oloid: Portal:
• Bit Length: Enter the card’s bit length (e.g., 26-bit, 37-bit).
• Facility Code: Define where the facility code starts and ends, if applicable.
• Card Number: Define the card number segment according to the format.
• Parity Bits: Configure parity bits if the card format includes them.

Saving and Testing the Wiegand Format

Once the Wiegand format is created successfully, ensure the Wiegand format functions correctly with the reader and card.

Follow the below steps to test Wiegand Format:

Login to Oloid Portal.
Go to Directory > Users > User> Credential
Select Badge > Assign Badge.
Enter Badge ID/Secondary ID and select Wiegand Format.
Click Assign to create the Badge Binary and assign to user.
If the format and data entered is correct, you can successfully create the Badge Binary.

For detailed instruction to assign badge, see How to assign Badge ID as credential to users

Troubleshooting Common Issues

Common Problems

Incorrect Bit Lengths: Ensure the bit length matches the card’s specification.
Mismatched Facility Codes: Verify the facility code matches the card and reader setup.
Invalid Card Data: Ensure the card is compatible with the configured reader.