Wiegand card data formats

warriors · 2015-09-16 18:24:55

Hello,

I have a 40 bit format from HID could anyone please decipher it.

1) 10010001001011010010100100100100000000101000000 (01124 11101355531-1)
2) 111001000000100000101101011010111010010 (01123 11101355531-1)
3) 111001000000100000101111001010111110011 (01122 11101355531-1)

Thanks,
Warriors

iceman · 2015-09-16 18:39:32

Your first row seems different from the other two. Are you sure you wrote it correct?

warriors · 2015-09-16 18:46:36

Sorry my mistake

1) 111001000000100000101110111110111001100 (01124 11101355531-1)
2) 111001000000100000101101011010111010010 (01123 11101355531-1)
3) 111001000000100000101111001010111110011 (01122 11101355531-1)

Thanks Iceman

warriors · 2015-09-16 21:58:20

Please Ignore this data.
Thanks

warriors wrote:

Sorry my mistake

1) 111001000000100000101110111110111001100 (01124 11101355531-1)
2) 111001000000100000101101011010111010010 (01123 11101355531-1)
3) 111001000000100000101111001010111110011 (01122 11101355531-1)

Thanks Iceman

lockakey · 2015-10-10 19:41:53

Hey there, I was trying to experiment with writing a utility, when I noticed I might be reinventing the wheel. Any chance yours still works?

0xFFFF wrote:

asper wrote:
Thank you 0xFFFF. Can you add an ID HEX example (if you can also with decoded values) ?
I have almost completed an excel tool to automatically decode a generic 11value HEX ID that can be useful in almost any situation (longer HEX IDs are filled with 0es).
Glad I could help.
If you're looking at decoding PACS data I'd suggest using the web app I developed. restricted.b1rkweb.com.1u/c1rdinfo/index.php
Replace the 1's with a's in the URL provided.
Comments, bug reports etc... are welcome.
Sample data:
SC 23
CN 123
001111111000001000000100010

0xFFFF · 2015-10-11 03:58:37

The utility still exists. I took it offline because of a lack of interest and feedback.

I'm happy to make it accessible again. What specifically were you expecting to get out of the utility?

almondxx · 2015-10-27 07:11:23

0xFFFF wrote:

The utility still exists. I took it offline because of a lack of interest and feedback.
I'm happy to make it accessible again. What specifically were you expecting to get out of the utility?

Hi, can u please send me an email, as I can't see ur email, and there is no pm in the fourm, I got some question. Thanks. ---------------------

radkins · 2015-10-29 20:28:22

Ok, quick question if anyone can help me out. I have a card and when I read it i get the following hex 0000076E93555D. Per the user manual that came with the reader, the first two numbers are used by the manufacturer or something and the last two are added for a checksum. If I remove those I get 00076E9355. Also in the User manual the values are allowed to be in the range 0000000000-1FFFFFFFFF. That would make the card 37-bits. Now when I try to use 37-bit wiegand to get the card number and site code it doesn't work. However, if I convert to the 00076E9355 to binary and only use the last 26 bits I can get the card number and site code correctly using a 26-bit weigand format. Anyone know what kind of format this is? Thanks for the answers.

iceman · 2015-10-29 21:13:12

If you enter your number in this calculator, you can test different bitlength formats..

http://www.brivo.com/support/card-calculator/

radkins · 2015-10-30 13:50:27

iceman wrote:

If you enter your number in this calculator, you can test different bitlength formats..

Yeah, that's how I figured out that the 26 bit would find the right card number. Just didn't make sense that they would give me 37 bits and then only use the last 26...? Oh well.

pieterg · 2015-11-24 15:43:47

marshmellow wrote:

@0xFFFF are you certain on the simplex parity break down? I've seen some samples that appear to follow that but others that don't, but I think the ones that don't are imitations.

I do have 3 transponders which have the same site code (0xD9) as these samples, but only one matches the parity scheme:

111011001111101000001110001001000111
011011001101101001111111010011101001
011011001011101000001110001001000101

Looking at the site code and id, these must be the same format, probably the parity calculation is not quite right yet.

marshmellow · 2015-11-25 02:28:28

@pieterg, are there numbers printed on the tags? also do you have confirmation of the format number?

pieterg · 2015-11-25 10:53:15

The printed numbers are:
111011001111101000001110001001000111 (13660451)
011011001101101001111111010011101001 (13892212)
011011001011101000001110001001000101 (13660450)

There is no information about the format, just that the id matches the HID simplex format, and the site code according to that format is equal to that of the samples in this thread.

marshmellow · 2015-11-26 05:26:25

how about:
p1 = Odd: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19
p2 = always 1

pieterg · 2015-11-26 11:41:22

How certain are we that the issue level bits aren't also parity bits?
The 13660450,13660451 are from the same batch, but have different issue level bits.
That seems a bit strange to me.

marshmellow · 2015-11-26 16:12:02

I agree and I also considered that. But there isn't enough data or samples to know. If someone had a reader we could test against we might be able to figure it out.

warriors · 2016-02-10 20:24:05

Hello I have a 37 bit HID A10202 format
Can anyone decipher it.

1) 1661-31 1010001100111110100000000000000111111
2) 1661-32 1010001100111110100000000000001000001
3) 1661-33 0010001100111110100000000000001000011
4) 1661-34 1010001100111110100000000000001000100
5) 1661-35 0010001100111110100000000000001000110
6) 1661-36 0010001100111110100000000000001001000
7) 1661-37 1010001100111110100000000000001001010
8) 1661-38 0010001100111110100000000000001001101
9) 1661-39 1010001100111110100000000000001001111
10) 1661-40 0010001100111110100000000000001010001

Thank you,
waariors

Last edited by warriors (2016-02-10 20:24:38)

iceman · 2016-02-10 21:01:37

Facility Code = 1661
Card Number = 31

o oo oo oo oo oo oo oo oo oo oo oo o
0123456789012345678901234567890123456
PSSSSFFFFFFFFFFF              CCCCCCP
1010001100111110100000000000000111111                                                                  
  010011001111101              11111
   0x4   (0x67D = 1661)      ( 0x1F = 31)

I'm quite sure you can figure this out...

[edit] added HPK's ODD parity
x(2) & x(3) & x(5) & x(6) & x(8) & x(9) & x(11) & x(12) & x(14) & x(15) & x(17) & x(18) & x(20) & x(21) & x(23) & x(24) & x(26) & x(27) & x(29) & x(30) & x(32) & x(33) & x(35)

Last edited by iceman (2016-02-10 21:02:20)

warriors · 2016-02-10 21:42:48

iceman wrote:

Facility Code = 1661
Card Number = 31

P P
1 0100 0110 0111 1101 000 0000 0000 0001 1111 1
110 0111 1101 (0x67D = 1661)
1 1111 ( 0x1F = 31)
0100 (0x4
I'm quite sure you can figure this out...

I figured that out the only confusing thing is Parity.
I have tried different combination but none seem to worked.

warriors

ntk · 2016-03-28 22:37:27

edit

You have 37bit H10202

strange ...

37 Bit Wiegand HID H10304 Card Format
34 Bit Wiegand HID N1002 Card Format
35 Bit Wiegand HID Corporate 1000 Card Format
36 Bit Wiegand HID Simplex Card Format
26 Bit Wiegand HID H10301 Card Format
33 Bit Wiegand HID (D10202) Card Format
37 Bit Wiegand HID H10302 Card Format
32 Bit Wiegand HID Check Point Card Format
37 Bit Wiegand HID H10302 ASSA ABLOY IP Lockset Card Format
32 Bit Wiegand Kastle Systems Card Format

Last edited by ntk (2016-03-28 22:48:04)

marshmellow · 2016-12-19 16:42:00

has anyone seen an AWID 37 bit, possibly a PCSC P10004 format?
https://helpdesk.rs2tech.com/kb/article … ard-format

C0d3M0nk · 2017-08-11 19:17:58

I apologize if I am activating an older post. I found this page on google looking for formats of HID Cards. I was hoping to get in contact with 0xFFFF and check out that format script. Do you have 32-Bit formats inside your script?

Also ntk, I see you posted a couple 32-Bit formats, do you know how I can decypher the 32-Bit formats or is there a program/site I can use with a Omnikey 5427CK reader?

Thanks,
Brad

ntk · 2017-08-12 11:46:33

I have only 26bit and 35bit standard, but OxFFFF does have 32bit in his tool. I would recommend to go here:

Very well done Wiegand card format info/tool

and no I am not genius, send thanks to iceman and 0xFFFF

I ran only on theory, never have any real reader to play with, not even 26bits, so I could not confirm if it works in reality. But interesting to see the different concepts available HID, intelli etc. 0xFFFF built in and so on.

Hope it helps

PS:
Perhaps it is sensible that you keep this thread from OxFFFF clean, open a new thread, keep this magnificent HID tool link, and a lot more RFID tools treasure at the top, and so you can spread the words to all future researchers, in the way you would keep this knpwledge alive.

Also post what bother you or what you find with your reader there too

Last edited by ntk (2017-08-13 08:44:33)

DBDNY · 2017-10-28 20:16:48

I am hoping that someone can fill in the blanks for this card. I have an 34 Bit Wiegand HID N10002.
I am looking for the number of bits for even and odd parity and the address to start from for both.
I am also looking for the number of issue level bits and the address to start from.
Any help would be much appreciated. Thank you

hkplus · 2017-10-30 22:59:30

warriors wrote:

iceman wrote:
Facility Code = 1661
Card Number = 31

P P
1 0100 0110 0111 1101 000 0000 0000 0001 1111 1
110 0111 1101 (0x67D = 1661)
1 1111 ( 0x1F = 31)
0100 (0x4
I'm quite sure you can figure this out...

I figured that out the only confusing thing is Parity.
I have tried different combination but none seem to worked.
warriors

On format A10202 - Upper parity bit is ODD and is computed with the following formula:

x(2) & x(3) & x(5) & x(6) & x(8) & x(9) & x(11) & x(12) & x(14) & x(15) & x(17) & x(18) & x(20) & x(21) & x(23) & x(24) & x(26) & x(27) & x(29) & x(30) & x(32) & x(33) & x(35)

Where X is a bit in the stream. Bit stream in my example starts at POSITION ZERO (Upper Parity Bit in Position Zero)

I am trying myself to figure out how to compute the lower parity. If anyone knows that would be helpful thanks.

Proxmark3 community

Announcement

#51 2015-09-16 18:24:55

Re: Wiegand card data formats

#52 2015-09-16 18:39:32

Re: Wiegand card data formats

#53 2015-09-16 18:46:36

Re: Wiegand card data formats

#54 2015-09-16 21:58:20

Re: Wiegand card data formats

#55 2015-10-10 19:41:53

Re: Wiegand card data formats

#56 2015-10-11 03:58:37

Re: Wiegand card data formats

#57 2015-10-27 07:11:23

Re: Wiegand card data formats

#58 2015-10-29 20:28:22

Re: Wiegand card data formats

#59 2015-10-29 21:13:12

Re: Wiegand card data formats

#60 2015-10-30 13:50:27

Re: Wiegand card data formats

#61 2015-11-24 15:43:47

Re: Wiegand card data formats

#62 2015-11-25 02:28:28

Re: Wiegand card data formats

#63 2015-11-25 10:53:15

Re: Wiegand card data formats

#64 2015-11-26 05:26:25

Re: Wiegand card data formats

#65 2015-11-26 11:41:22

Re: Wiegand card data formats

#66 2015-11-26 16:12:02

Re: Wiegand card data formats

#67 2016-02-10 20:24:05

Re: Wiegand card data formats

#68 2016-02-10 21:01:37

Re: Wiegand card data formats

#69 2016-02-10 21:42:48

Re: Wiegand card data formats

#70 2016-03-28 22:37:27

Re: Wiegand card data formats

#71 2016-12-19 16:42:00

Re: Wiegand card data formats

#72 2017-08-11 19:17:58

Re: Wiegand card data formats

#73 2017-08-12 11:46:33

Re: Wiegand card data formats

#74 2017-10-28 20:16:48

Re: Wiegand card data formats

#75 2017-10-30 22:59:30

Re: Wiegand card data formats

Board footer