I was testing the newest master build and iceman build
iceman runs v.1.1.0-2001-g966c111 (os and boot)
master runs v.2.2.0-348-g02069db
following results on iceman build with lf em em410xsim <myid>:
3 different readers
1. Gantner Terminal 1015
2. Axess TMC
3. Door Access / Lock on Knob (dont know vendor or brand)
1st - never working, was working on older builds (~okt/sept16?)
2nd - sometimes with pressure and good luck working, wasnt working in older builds
3rd - never worked, even doesnt show any reaction
example of 2nd and 3rd running sim on iceman build
following results on master build with lf em em410xsim <myid>:
1st - not working all the time, similar to what I see in icemanbuild with 2nd device
2nd - works like a charm - even better than the original badge / token
3rd - same for this
example of 2nd and 3rd
I noticed following:
when on iceman build I see 2 leds glowing on my elechouse easy as soon as I am in sim mode
when on master build I only see 1 led glowing while on sim mode
I dont have an idea if this does mean anyhting, just wanted to mention it too
as the distances between the reader and the proxmark feel to be different I did a hw tune to check for output power, but they are more or less the same (0.20v lower for iceman - but I guess thats not consistent)
Last edited by HighPressure (2017-03-20 11:08:03)
I might think this has something todo with some experiments I did, in lfops.c method: SimulateTagLowFrequency
The FpgaWriteConfWord command herehttps://github.com/iceman1001/proxmark3 … ops.c#L403
PM3 master uses
Would you mind testing it out?
just tested it the reverse style first (mistakenly - edited the master lol)
I added your line into the master - now the master doesnt work any longer
I then tried the same with iceman build and the described fix.
1st device - no reaction
2nd device - no reaction
3rd device - blinks read (means wrong id / badge)
at the same time I see that my proxmark does - while it gets in comunication - a lot of differnet blinking codes with the onboard leds?
during one of the tests it also got stuck (client on linux and proxmark himself)
Last edited by HighPressure (2017-03-20 12:07:20)
My line is the one that needs to be changed since PM3 Master works.
You can also comment out this one in my fork, that same method.
yep, I understood. it was just mistakenly and then showed that changing this line in the master has the same effect, that it afterwards doest work.
ok, I´ll check this later this evening again