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.
I was hoping to follow https://code.google.com/p/proxmark3/wiki/TagOps or rather https://github.com/Proxmark/proxmark3/wiki/lf%20tag%20operations and eventually use proxmark3.exe with data acquired with an oscilloscope. However, I find that the version "pm3-bin-756 (cdc+lua)" from https://code.google.com/p/proxmark3/downloads/list does not accept a "load" command without a serial port specified (and, I assume, the hardware connected..).
Never mind:
https://github.com/Proxmark/proxmark3/wiki/commands seems to say that "load" is actually an argument to "data". Trying this:
P:\pm3-bin-756 (cdc+lua)\pm3-bin-756 - lua branch\win32 (client+GUI)>proxmark3 data load EM4102-1.pm3
ERROR: invalid serial port
proxmark3> data load EM4102-1.pm3
loaded 16000 samples
proxmark3> data plot
proxmark3> Plot Window Keystrokes:
Key Action
DOWN Zoom in
G Toggle grid display
H Show help
L Toggle lock grid relative to samples
LEFT Move left
<CTL>LEFT Move left 1 sample
<SHIFT>LEFT Page left
LEFT-MOUSE-CLICK Set yellow cursor
Q Hide window
RIGHT Move right
<CTL>RIGHT Move right 1 sample
<SHIFT>RIGHT Page right
RIGHT-MOUSE-CLICK Set purple cursor
UP Zoom out
Use client window 'data help' for more plot commands
proxmark3> data autocorr 2000 g
performing 14000 correlations
proxmark3> data askdemod 1
proxmark3> data plot
proxmark3> data load EM4102-1.pm3
loaded 16000 samples
proxmark3> data askdemod 1
proxmark3> data mandemod 64
Warning: Manchester decode error for pulse width detection.
(too many of those messages mean either the stream is not Manchester encoded, or clock is wrong)
Unsynchronized, resync...
(too many of those messages mean the stream is not Manchester encoded)
Manchester decoded bitstream
0 0 1 0 1 1 1 1 0 1 0 1 1 1 1 0
1 1 1 1 1 1 0 0 0 1 1 1 0 0 1 1
1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1
1 0 0 0 0 0 1 0 0 0 1 0 1 1 1 1
0 0 1 0 1 1 1 1 0 1 0 1 1 1 1 0
1 1 1 1 1 1 0 0 0 1 1 1 0 0 1 1
1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1
1 0 0 0 0 0 1 0 0 0 1 0 1 1 1 1
0 0 1 0 1 1 1 1 0 1 0 1 1 1 1 0
1 1 1 1 1 1 0 0 0 1 1 1 0 0 1 1
1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1
1 0 0 0 0 0 1 0 0 0 1 0 1 1 1 1
0 0 1 0 1 1 1 1 0 1 0 1 1 1 1 0
1 1 1 1 1 1 0 0 0 1 1 1 0 0 1 1
1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1
proxmark3>
P:\pm3-bin-756 (cdc+lua)\pm3-bin-756 - lua branch\win32 (client+GUI)>
Note that I disregarded the comment about the "g" parameter so I had to reload the data, as the autocorrelation replaced the data buffer. Also note that the Wiki instructions have notes for newer commands, which I did not test.
The data output stripped of whitespace and aligned matches the wiki data:
001011110101111011111100011100
1111111110000000011000001000101111001011110101111011111100011100
1111111110000000011000001000101111001011110101111011111100011100
1111111110000000011000001000101111001011110101111011111100011100
111111111000000001
(doesn't this mean there should be 3 or 4 correlation peaks?)
Then I found these instructions (less explanation, but specifies how to load data) :
https://github.com/Proxmark/proxmark3/wiki/EM4102%201.pm3%20Walkthrough
Being able to provide incorrect serial port saves me from looking into the source in order to "hack" this argument out of the client. But it brings up another point: https://github.com/Proxmark/proxmark3/wiki/Windows does not actually specify how to build the client on Windows, if I am not mistaken..
The .pm3 file format is just an ANSI text file with a signed decimal integer sample value on each line, ended with Unix newline / line-end (lf aka '\n').
Here are the first lines from EM4102-1.pm3 (16000 samples -> 16001 lines)
85
85
78
68
59
54
56
51
44
35
35
37
33
25
-39
-96
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-128
-105
-112
-112
-101
-92
-94
-86
-76
-79
-73
-63
-67
13
127
127
...
To use my oscilloscopes data I will have to reduce the sampling rate to the 125 kHz somehow, ideally in sync ..
BTW: this version of proxmark3.exe' console even supports filename completion using TAB - but it crashes on "quit".. :-)
Offline
how about you download the latest source from GitHub and compile it. Run that client instead.
If you can't compile yourself, try downloading one of Aspers pre-compiled binary releases in the sticky thread http://www.proxmark.org/forum/viewtopic.php?id=1562
Offline
Thanks, I might give it a try once I have converted my oscilloscope capture to a compatible .pm3 trace.
Offline