Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
I am "manchester demodulating" some simple tags with some HEX code written on it.
First one "0302584" gives :
0011 0000 0010 0101 0101 1000 0100
= 302584+
Second one "000191" :
0000 0000 0001 1001 0100 1001 0001
= 000191+
What are those 4 more "characters" ? And is there any way to calculate them ?
I don't any other examples so it is a bit hard to understand...
Let's say I have another tag "0782D2", what will be result ?
I am guessing something like "782D2"...
Last edited by app_o1 (2015-06-06 10:14:26)
Offline
Looks like this script is to determine the last byte value... So this is not what I need (?)
Last edited by app_o1 (2015-06-06 10:14:43)
Offline
Well, that looks much better :
Thanks to henryk !
Offline
You then get 32 bits of ID followed by some kind of checksum or parity as a stop sentinel
So what is it exactly ? Checksum, parity, ... ?
Last edited by app_o1 (2015-06-06 10:15:08)
Offline
What is "transit.exe" ? Anyway it doesn't seems to be a parity check, it is probably a CRC but I don't know of which type (CRC-8 with specific polynomial value?).
Last edited by asper (2013-07-07 14:15:14)
Offline
Pages: 1