Wiegand card data formats

0xFFFF · 2013-06-20 22:59:38

A few people here who have been dealing with access control have been posting information on Wiegand data formats. I figure we should put all of the information in the one spot.

If we can try and keep the same formatting, that would be great.

I'll get the ball rolling by putting down a few...

SC = Site Code
CN = Card Number
O = Odd Parity
E = Even Parity

Wiegand 26 bit

SC    2, 3, 4, 5, 6, 7, 8, 9
CN    10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25
E  1  2, 3, 4, 5, 6, 7, 8, 9, 10,11,12,13 
O  26 14,15,16,17,18,19,20,21,22,23,24,25

Indala 26bit

SC    2, 3, 4, 5, 6, 7, 8, 9, 10,11,12,13
CN    14,15,16,17,18,19,20,21,22,23,24,25
E  1  2, 3, 4, 5, 6, 7, 8, 9, 10,11,12,13
O  26 14,15,16,17,18,19,20,21,22,23,24,25

HID 35bit Corporate 1000.

SC    3, 4, 5, 6, 7, 8, 9, 10,11,12,13,14
CN    15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34
E  2  3, 4, 6, 7, 9, 10,12,13,15,16,18,19,21,22,24,25,27,28,30,31,33,34
O  35 2, 3, 5, 6, 8, 9, 11,12,14,15,17,18,20,21,23,24,26,27,29,30,32,33
O  1  2, 3, 4, 5, 6, 7, 8, 9, 10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35

FYI - For anyone who is interested, I have a utility online that allows you to easily translate and interpret data. Contact me if you want access.

marshmellow · 2013-06-21 15:25:50

HID 26 bit follows Wiegand 26 bit exactly - AKA H10301

HID 37 bit standard - AKA H10304

SC    2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,15,16,17
CN   18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36
E  1  2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,15,16,17,18,19
O 37 19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36

HID 37 bit HUGE - AKA H10302

SC  NONE
CN    2-36
E  1  2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,15,16,17,18,19
O 37 19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36

HID Clock & Data - AKA H10320

SC  NONE
CN    1-32  Hex format but does not allow A-F only 0-9 - meaning 100110011001 is actually 999 not 2457
E 33  1, 5, 9,13,17,21,25,29
O 34  2, 6,10,14,18,22,26,30
E 35  3, 7,11,15,19,23,27,31
E 36  4, 8,12,16,20,24,28,32

All these HID formats follow the raw basic format outlined here http://www.proxmark.org/files/Documents … xample.pdf

NOTE: 37 bit formats exclude the 1 start bit that preceeds all other weigand data formats.

That basic raw format is what HID follows for any <= 37bit format
For > 37 bits however the format is slightly different.
As I will outline in next post.

Last edited by marshmellow (2013-06-21 15:42:53)

marshmellow · 2013-06-21 15:40:07

For > 37 bit HID format emulation on a T55x7 configuration goes as follows:

Block 0:
0x001070C0

Meaning it will transmit 192 raw bits - or 8 bit preamble & 92 manchester de-coded bits. Commercial recievers only output weigand data for the data after the first 1 bit.
So instead of the format having up to 44bits (of which 37 can be used in weigand data) it now has 92 (of which i believe 82 bits can be used for weigand data - depending on reader/software capability)

after the 8 bit preamble there is an manchester de-coded 8 bits of Company Code or OEM specific data - example I have is 10011110
the remainder follows the basic format outlined in pdf document referenced above.

marshmellow · 2013-06-21 15:45:56

AWID format specified at this nice link provided by carl55:
http://www.proxclone.com/pdfs/AWID_FSK_Format.pdf

Bugman1400 · 2013-08-23 03:12:55

marshmellow wrote:

AWID format specified at this nice link provided by carl55:
http://www.proxclone.com/pdfs/AWID_FSK_Format.pdf

That PDF has a slight error in that 8 125Khz cycles do not equal 15.625 khz and 10 125Khz cycles do not equal 12.5 khz. Its vice versa.

Carl's pictorials are very informative but, look polished. I've taken several samples of my LF HID tag with my PM3 and it is hard to discern between an FSK Logic 1 and a Logic 0. At least I was able to learn that the waveform I am looking at is, in fact, not amplitude modulated which it initially appears to be to the layman. Perhaps these waveforms from Carl55 are groomed a bit for illustration. However, what I may be looking at is the trash in the beginning before the transmission sequence.

If using the PM3 to read an LF HID tag, how many Raw Data Samples should I capture? What are the next commands I should use to figure out Blocks 0, 1, 2, & 3? If I use the DATA DEMODULATE FSK command, Promark Client displays the correct bits and Hex number but, I want to figure it out manually for the exercise.

Has anybody tried this manually?

SM · 2013-09-18 16:30:52

Hello

I’m trying to read a 125Khz proximity card with the HID Miniprox 5365.

I have a wiegand – RS232 converter connected to the reader and to a serial port of a PC.

When I pass a HID 37 cart in the reader, I read this in the serial port: FFFFFFBBF7DF7FEFBEFBFF76.

Could I help me to get the card id from this number?
Many Thanks.

0xFFFF · 2013-09-19 01:30:33

What is the converter? I think you need to provide more details. Just at a glance it looks like there is one of two things wrong here:

The D1 / D0 lines are back to front.
The converter is massaging the data (pretty common) and you'll need to refer to the documentation for it.

Data retrieved from a HID reader with an RS232 module attached should look something like...
00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 4E 05 BF
...so I'm guessing the converter is from a 3rd party?

SM · 2013-09-19 13:26:04

That’s true, the converter is a 3rd party equipment, I will contact the supplier to ask help for the problem.

Thank you very mush.
SM

marshmellow · 2013-10-14 14:48:40

Bugman1400 wrote:

If using the PM3 to read an LF HID tag, how many Raw Data Samples should I capture? What are the next commands I should use to figure out Blocks 0, 1, 2, & 3? If I use the DATA DEMODULATE FSK command, Promark Client displays the correct bits and Hex number but, I want to figure it out manually for the exercise.
Has anybody tried this manually?

Typically 16000 is plenty of samples to clearly see the repeating pattern. Block 0 is not transmitted, just blocks 1-3 on a normal HID tag.
Manually decoding usually goes like this for FSK. 5 or 6 long waves = 1 5 or 6 short waves =0 (discard extra waves), after getting the binary for HID look for 00011101 that is your preamble byte and it is the only non-Manchester encoded byte. Then follow the HID guide (link posted earlier in this thread) to decode the Manchester / prox format.

this probably isn't 100% correct but it works.

yarhut · 2014-01-06 21:22:59

i am new to all this I've never posted on a forum before. So excuse me if I'm not doing it right. I am reading HID 26 and 35 bit cards using a HID corporation RS232 reader to obtain the data from an HID card. If I scan a typical 26 bit card with the card number 218-03920 I read the following 000007B41E9871. If I read a typical 35 bit card with a card number of 39764 21120199-1 I read the following 0008682136A970 . I need to translate the Hex number back to the card number I see you have a utility for translating and interpreting the card data. I think this will do what I need to do. Could I please have a copy.

Thanks Ray

marshmellow · 2014-01-20 05:23:24

.

Last edited by marshmellow (2014-01-20 05:39:09)

0xFFFF · 2014-03-05 00:14:58

Tecom 27 bit

SC 16,20,25,24,23,19,7, 11,15,4, 3
CN 1, 2, 14,13,10,27,21,17,18,22,26,8, 9, 12,5, 6

asper · 2014-03-05 08:41:39

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).

0xFFFF · 2014-03-05 09:36:33

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

asper · 2014-03-05 19:35:27

So hex uid transmitted by the tag is: 01FC1022 ?

0xFFFF · 2014-03-05 21:28:09

TS870 readers have two interfaces Wiegand and RS485 (proprietary bus).
So I suppose the answer is - The data is never transmitted that way.
'001111111000001000000100010' will be sent as part of a packet over RS485 that includes other information to do with the reader.
If you want I can provide you with the same message formatted as a packet?

asper · 2014-03-05 22:57:19

Yes i am curious to see it! Thank you. My aim is to find what bytes are contained/transmitted inside/by the card.

Last edited by asper (2014-03-05 22:57:44)

0xFFFF · 2014-03-15 03:02:42

Here is an example packet sent from a TS0870 for a card (sc:50, cn:50).

0D 0E 32 00 32 00 00 00 00 00 00 00 00 00 00 00 FC

1 byte - The Tecom Smart Card packet header.
1 byte - The packet length (from after this byte to before the CRC)
2 bytes - The site code.
3 bytes - The card number.
9 bytes - Credit and location data.
1 byte - CRC.

There is a sequential polling arrangement where each module gets its turn to reply but you can throw this packet on the LAN at almost any time and it will work.

asper · 2014-03-15 07:41:24

With "each module" you mean the above described "partial" packet bytes ? If so we can think that the card has 15/16 bytes stored inside... (I think crc is not stored inside while the header can be); anyway if there are other commands and different received bytes from the card i am wrong...

Last edited by asper (2014-03-15 07:42:18)

0xFFFF · 2014-05-12 05:34:38

wojo wrote:

Would love to test this. Sent a request for access. I'm working on a standalone decoder for various Wiegand formats.

Password sent. If something does not work or is missing, please let me know. There is a new version available but I have not made it live yet.

blark · 2014-06-16 23:07:53

Hey I hope you don't mind, I'm doing some work with HID readers too and would love access to the site. I'm building a long range skimmer for work, and just generally having some fun hacking them.

0xFFFF · 2014-06-17 03:06:25

Not at all. I've given you access to it (you should have a password in your email).

The interface has been updated, so any feedback is welcome.
If a feature is not there, please let me know.

0xFFFF · 2014-08-13 02:03:21

joesnipes wrote:

OxFFFF, I would love to get access to this as well. I am working to develop a java client that allows employees to badge into the application. I can pull the Hex data but need to get it converted.
Thanks,
Barry

I've upgraded the server that this utility is hosted on. Annoyingly there is some deprecated code preventing a few components from working. Automated registration is one of the components affected by this.
A registration email has been sent out to you. Your login name should be your username on this forum. If something does not work, please let me know.
As always, any feed back is welcome.

marshmellow · 2014-09-13 13:00:02

I've run across a SETEC format S-10401 originally from AMAG, but on an HID card and it uses HID's Preamble (HID buy them out?).
here is what I know:
37 bit format
max card number is 536870911 (or 29 bits)
Site Code is referred to as FIXED or non-existent but it does exist (I'm guessing the length)
Parities, I'm guessing there are 2, one beginning and one trailing

SC = Site Code
CN = Card Number
P1 = ? Parity
P2 = ? Parity
SC        2, 3, 4, 5, 6, 7  (?)
CN        8 ,9 ,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36
P1(bit1)  ?
P2(bit37) ?

marshmellow · 2014-09-13 13:02:16

Additional lf format information can be found at http://www.proxmark.org/forum/viewtopic.php?id=1767

warriors · 2015-06-23 16:54:45

Hello,

I have a weigand output from 36 bit HID cards.

The output looks like.

011011001100111101000001001010010101 (1002-7997770 printed on the card)
111011001000111101000001001001100101 (1002-7997746 printed on the card)
111011001111001100101100011011011101 (0606-10052462 printed on the card)
111011001001000110000000110001100001 (2304-9176624 printed on the card)

Can you please help me find SC and CC with parity.

warriors · 2015-06-23 16:57:59

Hello,

Can I get access to the online utility. I have few formats to decode if your utility supports it.

Thanks,

0xFFFF wrote:

A few people here who have been dealing with access control have been posting information on Wiegand data formats. I figure we should put all of the information in the one spot.
If we can try and keep the same formatting, that would be great.
I'll get the ball rolling by putting down a few...
SC = Site Code
CN = Card Number
O = Odd Parity
E = Even Parity
Wiegand 26 bit
SC    2, 3, 4, 5, 6, 7, 8, 9
CN    10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25
E  1  2, 3, 4, 5, 6, 7, 8, 9, 10,11,12,13 
O  26 14,15,16,17,18,19,20,21,22,23,24,25
Indala 26bit
SC    2, 3, 4, 5, 6, 7, 8, 9, 10,11,12,13
CN    14,15,16,17,18,19,20,21,22,23,24,25
E  1  2, 3, 4, 5, 6, 7, 8, 9, 10,11,12,13
O  26 14,15,16,17,18,19,20,21,22,23,24,25
HID 35bit Corporate 1000.
SC    3, 4, 5, 6, 7, 8, 9, 10,11,12,13,14
CN    15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34
E  2  3, 4, 6, 7, 9, 10,12,13,15,16,18,19,21,22,24,25,27,28,30,31,33,34
O  35 2, 3, 5, 6, 8, 9, 11,12,14,15,17,18,20,21,23,24,26,27,29,30,32,33
O  1  2, 3, 4, 5, 6, 7, 8, 9, 10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35
FYI - For anyone who is interested, I have a utility online that allows you to easily translate and interpret data. Contact me if you want access.

0xFFFF · 2015-06-24 01:01:15

warriors wrote:

Hello,
I have a weigand output from 36 bit HID cards.
The output looks like.
011011001100111101000001001010010101 (1002-7997770 printed on the card)
111011001000111101000001001001100101 (1002-7997746 printed on the card)
111011001111001100101100011011011101 (0606-10052462 printed on the card)
111011001001000110000000110001100001 (2304-9176624 printed on the card)
Can you please help me find SC and CC with parity.

I have taken the utility offline as it wasn't getting used and people were not giving feedback. I have re-written most of it and added many more features. When it is closer to completion, I'll see if anyone is interested.

PACS format appears to be - HID Simplex 36bit.
All of your cards have the site code - 217 (0xd9)

HID Simplex 36bit.

Card number - 7997770 (0x7a094a)
Issue Level - 2 (0x2)

Card number - 7997746 (0x7a0932)
Issue Level - 0 (0x)

Card number - 10052462 (0x99636e)
Issue Level - 3 (0x3)

Card number - 9176624 (0x8c0630)
Issue Level - 0 (0x)

marshmellow · 2015-06-24 02:08:29

@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.

0xFFFF · 2015-06-24 02:14:50

I'm not absolutely certain. But what I posted is correct based on the information warriors provided.
I think you're right though. I've seen a few variants out there too.

marshmellow · 2015-06-24 03:17:41

Thanks. Someday maybe we should compare notes.

warriors · 2015-06-24 15:23:14

Thanks 0xFFFF

The format matches the binary calculation manually.
I will try on different card.

Thank you for your help,

warriors

0xFFFF wrote:

warriors wrote:
Hello,
I have a weigand output from 36 bit HID cards.
The output looks like.
011011001100111101000001001010010101 (1002-7997770 printed on the card)
111011001000111101000001001001100101 (1002-7997746 printed on the card)
111011001111001100101100011011011101 (0606-10052462 printed on the card)
111011001001000110000000110001100001 (2304-9176624 printed on the card)
Can you please help me find SC and CC with parity.
I have taken the utility offline as it wasn't getting used and people were not giving feedback. I have re-written most of it and added many more features. When it is closer to completion, I'll see if anyone is interested.
PACS format appears to be - HID Simplex 36bit.
All of your cards have the site code - 217 (0xd9)
http://www.proxmark.org/forum/img/3445/1435103680_hid_simplex_36bit.jpg
Card number - 7997770 (0x7a094a)
Issue Level - 2 (0x2)
Card number - 7997746 (0x7a0932)
Issue Level - 0 (0x)
Card number - 10052462 (0x99636e)
Issue Level - 3 (0x3)
Card number - 9176624 (0x8c0630)
Issue Level - 0 (0x)

warriors · 2015-06-25 22:08:09

Hello I tried on different format and it passes.
The bit mapping matches on every card.

I have another format from 36 bit Indala useb by Keyscan.
I am confused with the bit mapping a little bit. Could please decode it.

1) 111100001000010011001100110000100011 (26129 B-038)
2) 111100001000010011001100110000000001 (26112 B-038)
3) 111100001000010011001100110000100000 (26128 B-038)
4) 111100001000010011001100110000011111 (26127 B-038)

warriors

warriors · 2015-06-29 18:51:42

Hello I tried on different format and it passes.
The bit mapping matches on every card.
I have another format from 36 bit Indala used by Keyscan.
I am confused with the bit mapping a little bit. Could please decode it.

1) 111100001000010011001100110000100011 (26129 B-038)
2) 111100001000010011001100110000000001 (26112 B-038)
3) 111100001000010011001100110000100000 (26128 B-038)
4) 111100001000010011001100110000011111 (26127 B-038)
5) 011100001000010001001100010100011111 (25231 B-034)
6) 011100001000001100100111001111101100
7) 011100001000001010011000011110110111

warriors

0xFFFF wrote:

I'm not absolutely certain. But what I posted is correct based on the information warriors provided.
I think you're right though. I've seen a few variants out there too.

0xFFFF · 2015-06-29 23:17:18

warriors wrote:

1) 111100001000010011001100110000100011 (26129 B-038)
2) 111100001000010011001100110000000001 (26112 B-038)
3) 111100001000010011001100110000100000 (26128 B-038)
4) 111100001000010011001100110000011111 (26127 B-038)
5) 011100001000010001001100010100011111 (25231 B-034)
6) 011100001000001100100111001111101100
7) 011100001000001010011000011110110111

I don't have enough information to work with. In this case the data appears to match 3 formats in my database.

The number 26129, 26112, 26128,... appears to be a card number (bits 20 - 35).

What else can you tell me about these cards?

marshmellow · 2015-06-29 23:19:43

It does match the keyscan c15001 fmt. The b-038 is the facility code.

0xFFFF · 2015-06-29 23:33:09

marshmellow wrote:

It does match the keyscan c15001 fmt. The b-038 is the facility code.

Can you describe the keyscan c15001 format please?

marshmellow · 2015-06-30 03:35:58

C15001 AKA keyscan (in my experience anyway...)

FF     2, 3, 4, 5, 6, 7, 8, 9,10,11
SC    12,13,14,15,16,17,18,19
CN    20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35
E 1    2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,15,16,17,18 
O 36  19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35

FF = Fixed Field
SC = Site Code
CN = Card Number

Last edited by marshmellow (2015-06-30 03:37:39)

marshmellow · 2015-06-30 03:48:30

so for warriors tags:

1) 1 1110000100 00100110 0110011000010001 1 (CN:26129 SC:038 FF:900)
2) 1 1110000100 00100110 0110011000000000 1 (CN:26112 SC:038 FF:900)
3) 1 1110000100 00100110 0110011000010000 0 (CN:26128 SC:038 FF:900)
4) 1 1110000100 00100110 0110011000001111 1 (CN:26127 SC:038 FF:900)
5) 0 1110000100 00100010 0110001010001111 1 (CN:25231 SC:034 FF:900)
6) 0 1110000100 00011001 0011100111110110 0 (CN:14838 SC:025 FF:900)
7) 0 1110000100 00010100 1100001111011011 1 (CN:50139 SC:020 FF:900)

Last edited by marshmellow (2015-06-30 03:49:35)

0xFFFF · 2015-06-30 03:58:34

Is the Fixed Field always 900?
Or does this vary depending on the customer / site / ...?

marshmellow · 2015-06-30 04:04:39

i've seen it vary but i'm not sure the definition (probably either customer or distributor)

0xFFFF · 2015-06-30 05:23:38

Interesting. Thanks marshmellow.

marshmellow · 2015-06-30 05:31:27

no problem

warriors · 2015-06-30 14:37:27

Thanks,

It does matches.
The cards are collected from different sites so the SC is different but the cards are manufactured for Keyscan by Indala.
I will get more cards from the sites to verify it.

warriors.

warriors · 2015-07-15 15:34:18

marshmellow wrote:

no problem

Hello,

Do you have card format for 37 bit Cansec

Thanks,
warriors.

marshmellow · 2015-07-15 18:46:32

I haven't heard of that one. Any examples? It may match another 37 bit format.

warriors · 2015-07-15 21:20:42

marshmellow wrote:

I haven't heard of that one. Any examples? It may match another 37 bit format.

1) 1010100010100001110100010000010000011 (02589 04161 A C37)
2) 1010100010100001110100001111001100111 (02589 03891 A C37)
3) 0010100010100001110100001011101110110 (02589 03003 A C37)
4) 1010100010100001110100010000011010111 (02589 04203 A C37)
5) 0010100010100001110100001010101111011 (02589 02749 A C37)
6) 0010100010100001110100001011010011100 (02589 02894 A C37)

This is the raw binary data

warriors

marshmellow · 2015-07-15 21:51:49

based on the maximums for FC and Card# from this doc i get this far:

FC:   6, 7, 8, 9,10,11,12,13,14,15,16,17,18,19,20
CN:  21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36
??:   2, 3, 4, 5  - possibly the A in reverse order?
E: ?
O: ?

iceman · 2015-07-16 07:33:28

in that document there was an interesting passage of how the pin was calculated from FC and CN...
you don't have the pin for those cardnumbers?

warriors · 2015-07-16 19:09:18

No I do not have pin

iceman wrote:

in that document there was an interesting passage of how the pin was calculated from FC and CN...
you don't have the pin for those cardnumbers?

Proxmark3 community

Announcement

#1 2013-06-20 22:59:38

Wiegand card data formats

#2 2013-06-21 15:25:50

Re: Wiegand card data formats

#3 2013-06-21 15:40:07

Re: Wiegand card data formats

#4 2013-06-21 15:45:56

Re: Wiegand card data formats

#5 2013-08-23 03:12:55

Re: Wiegand card data formats

#6 2013-09-18 16:30:52

Re: Wiegand card data formats

#7 2013-09-19 01:30:33

Re: Wiegand card data formats

#8 2013-09-19 13:26:04

Re: Wiegand card data formats

#9 2013-10-14 14:48:40

Re: Wiegand card data formats

#10 2014-01-06 21:22:59

Re: Wiegand card data formats

#11 2014-01-20 05:23:24

Re: Wiegand card data formats

#12 2014-03-05 00:14:58

Re: Wiegand card data formats

#13 2014-03-05 08:41:39

Re: Wiegand card data formats

#14 2014-03-05 09:36:33

Re: Wiegand card data formats

#15 2014-03-05 19:35:27

Re: Wiegand card data formats

#16 2014-03-05 21:28:09

Re: Wiegand card data formats

#17 2014-03-05 22:57:19

Re: Wiegand card data formats

#18 2014-03-15 03:02:42

Re: Wiegand card data formats

#19 2014-03-15 07:41:24

Re: Wiegand card data formats

#20 2014-05-12 05:34:38

Re: Wiegand card data formats

#21 2014-06-16 23:07:53

Re: Wiegand card data formats

#22 2014-06-17 03:06:25

Re: Wiegand card data formats

#23 2014-08-13 02:03:21

Re: Wiegand card data formats

#24 2014-09-13 13:00:02

Re: Wiegand card data formats

#25 2014-09-13 13:02:16

Re: Wiegand card data formats

#26 2015-06-23 16:54:45

Re: Wiegand card data formats

#27 2015-06-23 16:57:59

Re: Wiegand card data formats

#28 2015-06-24 01:01:15

Re: Wiegand card data formats

#29 2015-06-24 02:08:29

Re: Wiegand card data formats

#30 2015-06-24 02:14:50

Re: Wiegand card data formats

#31 2015-06-24 03:17:41

Re: Wiegand card data formats

#32 2015-06-24 15:23:14

Re: Wiegand card data formats

#33 2015-06-25 22:08:09

Re: Wiegand card data formats

#34 2015-06-29 18:51:42

Re: Wiegand card data formats

#35 2015-06-29 23:17:18

Re: Wiegand card data formats

#36 2015-06-29 23:19:43

Re: Wiegand card data formats

#37 2015-06-29 23:33:09

Re: Wiegand card data formats

#38 2015-06-30 03:35:58

Re: Wiegand card data formats

#39 2015-06-30 03:48:30

Re: Wiegand card data formats