Forum / MIFARE general topics and applications / MiFare UID Number
So I am using an older Wiegand panel to read a Mifare card, I have read it as a decimal card number and then converted this to Hex, this works fine after I realized the differenct between Big Endian and Small Endian. So most UID's are in Small Endian.
I used Mifare Classic on my phone to read and check the cards that I have been using. I have another Chinese handheld reader that reads the Mifare Cards to a decimal value, so I know that my card numbers have been read correctly, Mifare classic seems to read the cards but seems to add some extra characters, any ideas why this is.... I have some examples below of 3 cards that i have tested...
Decimal value as read by the handheld scanner 0003353930
Hex Vale Unit 32 Big Endian 00 33 2D 4A
Hex Value Unit 32 Little Endian 4A 2D 33 00
UID as read by the Mifare Classic App on phone 4A 2D 33 32
Seem to have 32 added to the last byte by the Mifare Classic App reading in Little Endian.
Park Avenue Card
Decimal Value as read by the handheld scanner 0008790548
Hex Value Unit32 Big Endian 00 86 22 14
Hex Value Unit32 Little Endian 14 22 86 00
UID as read by the Mifare Classic App on phone 14 22 86 1E
Seem to have 1E added to the last byte by the Mifare Classic App reading in Little Endian
Ebay Mifare Card
Decimal Value as read by the handheld scanner 0014810478
Hex Value Unit32 Big Endian 00 E1 FD 6E
Hex Value Unit32 Little Endian 6E FD E1 00
UID as read by the Mifare Classic App on phone 6E FD E1 6E
Seem to have 6E added to the last byte by the Mifare Classic App reading in Little Endian
+ 0 | - 0
awesome thuis post. i like this post
free gift card code generator and free gift card code generator and free gift card code generator and dailymotion video downloader
+ 0 | - 0
Kronospoker Situs Judi Online, IDN Poker, IDN Poker Mobile, Agen Poker Terpercaya Indonesia untuk permainan Poker Online, Domino Qiu Qiu, Cemeqq, Capsa Susun dan Super 10
+ 0 | - 0
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.