Installers and integrators · Free converter

Driver-ID Card & Key Number Converter

The number on a card is rarely the number your platform stores. Enter it in any form. Get hex, decimal, reversed bytes, facility and card number, and the parity or CRC check. Calculations run in your browser. Inputs are sent only if you ask for the emailed report.

  • Runs in your browser
  • Parity and CRC checked
  • EM4100, Wiegand 26, iButton
You have the number as

Spaces and colons are fine. The sample is the published example: version 06, data 001259E3. Replace it with your own card.

Digits only, up to 4294967295. This is the 10-digit number many cards print. It does not contain the version byte, so set it below.

One or two hex digits. Use 00 if you do not know it. 06 matches the sample.

Whole number from 0 to 255. Example value.

Whole number from 0 to 65535. Example value.

Up to 4 hex digits. Use 0000 if you do not know them. 0600 matches the sample.

64 characters, only 0 and 1. Spaces are ignored. Paste a raw capture to check its parity.

How the 64-bit frame is built
Frame = 9 ones + 10 x (4 data bits + 1 even parity bit) + 4 column parity bits + stop bit 0 ID (40 bits) = version byte + 32-bit data = 10 hex digits Example 06 00 12 59 E3: last 4 bytes 001259E3 = 1202659 ; byte 3 = 12 = 18 ; bytes 4-5 = 59E3 = 23011

Source: the published EM4100 protocol description (public text). No standards body publishes this format, so it could not be checked in an official text. Last checked 2026-11-03.

Card ID in every formParity checked

Keep a record of the IDs you converted

A report with every form, the parity or CRC result and the list.

Driver-ID report

Get the converted IDs and their checks in one report

  • Every written form of the card or key
  • Parity and CRC results
  • The full converted list for enrolment
  • Repeated and misread lines marked
  • Method and sources

Why is the number on the card not the number in the platform?

A card stores one code. The printed number, the reader output and the platform field each show it in a different way: hex or decimal, whole or in part, first byte first or last byte first. When two of them disagree, the driver is not recognized and nobody knows why.

Three kinds of driver ID
MediumHow it is readBuilt-in checkForms you meet
125 kHz card (EM4100)Held near the reader, no contactRow and column parity10 hex digits, decimal of the last 4 bytes, facility and number
Wiegand 26 reader outputThe reader sends 26 bits to the controllerTwo parity bitsFacility and card, 24-bit hex, 26 bits
iButton key (1-Wire)Touched to a contactCRC-816 hex digits, 12-digit serial on the key, 64-bit decimal

This converter takes the number in the form you have and shows every other form of the same code. It also checks the bits that guard against a misread: parity for the two card types and a CRC byte for the key.

How is an EM4100 card built?

The card repeats a 64-bit frame. Forty of those bits are the ID: one version or customer byte and a 32-bit data value. The rest are the header, parity and stop bit.

The EM4100 frame
PartBitsWhat it holds
Header9Nine ones. They mark the start of a frame.
Ten rows50Each row is 4 data bits and 1 even parity bit.
Column parity4One even parity bit for each data column.
Stop bit1Always 0.
ID 06 00 12 59 E3 Last 4 bytes 00 12 59 E3 = 1202659 Byte 3 = 12 hex = 18 ; bytes 4 and 5 = 59E3 hex = 23011 Facility,number = 018,23011 Reversed bytes = E3 59 12 00 06

The worked example is the one published with the protocol description: version 06, data 001259E3. Readers often print the last 4 bytes as a 10-digit decimal.

Facility and number are a habit, not a rule

Many readers send an EM card to a Wiegand 26 controller by taking byte 3 as the facility code and bytes 4 and 5 as the card number. EM4100 itself does not define this split. Test one card on your reader before you rely on it.

How does Wiegand 26 work?

A Wiegand reader sends the card data to the controller as 26 bits: a parity bit, an 8-bit facility code, a 16-bit card number and a second parity bit. Each parity bit guards half of the 24 data bits.

The Wiegand 26 frame
BitMeaningRange
1Leading parity, even, over bits 2 to 130 / 1
2-9Facility code0 - 255
10-25Card number0 - 65535
26Trailing parity, odd, over bits 14 to 250 / 1
Facility 101 = 01100101 ; card 4095 = 0000111111111111 Bits 2-13 = 011001010000 has four ones -> even parity bit 0 Bits 14-25 = twelve ones -> odd parity needs a 1 Frame = 0 01100101 0000111111111111 1

Other Wiegand formats, such as 34 or 37 bits, use other layouts. This tool covers the 26-bit format. The parity convention is a choice because readers differ.

What is inside an iButton key?

A 1-Wire key sends 8 bytes when you touch it: a family code, a 48-bit serial number and a CRC-8 byte. The key sends the least significant byte first, so the family code comes first and the CRC last.

The 1-Wire ROM
ByteMeaning
1Family code. Many driver keys use 01.
2-748-bit serial number, least significant byte first
8CRC-8 of the first 7 bytes
Family 02 ; serial 00000001B81C Read order: 02 1C B8 01 00 00 00 + CRC A2 CRC over all 8 bytes = 00 CRC byte first: A2 00 00 00 01 B8 1C 02

Some tools print the 64-bit number the other way round, CRC byte first. If the CRC check fails, try the other byte order before you decide that the key is bad.

How do you enrol many drivers without a mismatch?

  1. Read one card. Use the reader you will install. Note the form it shows: hex, decimal or facility and number.
  2. Find the form your platform wants. Check the device manual or the platform help for the driver-ID field. Do not guess the byte order.
  3. Convert the whole list. Use the list tab. Fix the lines marked as wrong and remove repeats.
  4. Test with one real card. Enter one driver, swipe the card, and confirm that the right name appears.
  5. Keep the list. Save the converted list with the installation record, so the next technician can trace any card.

Assumptions and limits

  • The tool converts numbers. It does not read cards and it does not know which form your device or platform expects.
  • Parity and CRC show that a read was clean. They do not show that a card belongs to a driver or that it is allowed to open anything.
  • The facility and number split of an EM card is a common convention. Your reader may use another one.
  • The Wiegand parity convention is a setting. The common one is leading even, trailing odd. Check your reader documentation.
  • Long numbers are converted with exact digit arithmetic, so a 64-bit value is never rounded.
  • The calculations run in your browser. Pasted lists and inputs are sent to our server, and kept for up to 45 days, only if you ask for the emailed report. A share link that you copy yourself also carries a list when it is short.
Related Tracom solution

Get the card number right before you drive off

Tracom hardware supports driver identification. Which cards or keys, and which number form, your device and the SCMS portal expect depends on the model and the firmware. Ask Tracom before you order cards.

  • Driver ID links a trip to the person who drove it.
  • SCMS portal holds device settings and configuration files in one place.
  • Real-time SMS adjustments change a setting without a site visit.
  • Over-the-air updates bring new firmware to devices in the field.
Questions

Questions about driver-ID numbers

Building a driver list for a project? Contact Tracom.

Why does the number printed on my card not match the platform?

The printed number is one written form of the code. The reader and the platform may use another form: hex instead of decimal, the last 4 bytes only, or reversed bytes. Convert the number here and enter the form your platform asks for.

What is the difference between an EM4100 card and an iButton key?

An EM4100 card is read by radio at 125 kHz when you hold it near the reader. An iButton key is read by touch on a contact. The card has parity bits in its frame. The key has a CRC-8 byte.

Which byte order does my tracker or platform expect?

This tool cannot know. Check the device manual and the platform help. Then test one real card. The tool shows both orders, so you can enter whichever one works.

Do I need the CRC byte of an iButton key?

Yes, as a check. A key ID with a correct CRC was read cleanly. If you only have the 14 digits without it, the tool calculates the CRC and gives you the full 16-digit ID.

Are the numbers I enter stored anywhere?

Only if you ask for the emailed report. The conversion happens in your browser. If you ask for the report or the CSV by email, your name, your email and your inputs, including any pasted list, are sent to our server and kept for up to 45 days.

Does this tell me which card types a Tracom device reads?

No. It converts numbers for any reader. Which cards and number forms a Tracom device accepts depends on the model and firmware. Ask Tracom before you buy cards.

Related tools and templates

Keep going with the installation

Get the report

Enter your details and we will email you the file.

Use your real name so the file arrives addressed to you. Don't worry, we won't flood you with emails or calls.

Scroll to Top