The fixes for Serial over FPC and latest battery / BL addon is more or less done.
Watch a video here, https://twitter.com/i/status/1117294810124161024
The future is mobile. I have been looking forward to this day since back in 2013 when I started to platy with proxmark3.
]]>In order for PM3 RDV20, PM3 RDV30 etc to be flashed with RRG Repo , you need to read and follow the instructions found here
https://github.com/RfidResearchGroup/pr … r-non-rdv4
I just got a Proxmark rdv 4.0 and am having some issues with it that I want to know where the best place to discuss them is. Is this the preferred place or is there one I have yet to find?
Specifically I am playing with it using some a 1K card that I have and it seems to be unreliable reading it as compared to the RDV 2.0 card that I have been using. I am using the RDV 4.0 as it came out of the box and the RDV 2.0 is using code from the iceman repo.
The couple of things that I have tried is to use hf search to identify the card. The 2.0 works all of the time and the 4.0 identifies the card less than 50% of the time.
Then I try reading sector 0 with the known A key, "a0a1a2a3a4a5", and the 2.0 reads it every time and the 4.0 again less than half the time.
Frankly, this is not what I expected, so I am looking for where best to seek out answers concerning this disparity and I haven't yet found an active discussion of rdv 4.0 issues, function or much of anything else.
Potentially you have the card too close to the reader. try putting a spacer of about 1 - 1.5cm between the top of plastic casing and the card.
]]>i do agree that for the smartcard add-on the case should have had a small slot for the ribbon cable to come out (i just pinched it - we'll see how long before it breaks).
Actually better than a slot, I would have preferred a connector so that you can easily add or remove it when you don't need it without opening the case every time.
But, as I think I forgot to mention it in my original message, considering that the case was not originally part of the Kickstarter, I do appreciate we have one It was a neat addition so hats off.
Which OS?
hw version
hw status
hw tune
I will repeat what has been said many times before on this forum,
When it comes to repos, don't mix firmware/client.
See first post in this thread for RDV40 repo, HF is quite stable on it. Otherwise try the official pm3 repo.
When it comes to mifare/14a, take notice about distance/positioning with tag and antenna. Find the sweet spot.
]]>Specifically I am playing with it using some a 1K card that I have and it seems to be unreliable reading it as compared to the RDV 2.0 card that I have been using. I am using the RDV 4.0 as it came out of the box and the RDV 2.0 is using code from the iceman repo.
The couple of things that I have tried is to use hf search to identify the card. The 2.0 works all of the time and the 4.0 identifies the card less than 50% of the time.
Then I try reading sector 0 with the known A key, "a0a1a2a3a4a5", and the 2.0 reads it every time and the 4.0 again less than half the time.
Frankly, this is not what I expected, so I am looking for where best to seek out answers concerning this disparity and I haven't yet found an active discussion of rdv 4.0 issues, function or much of anything else.
]]>the rest requires someone to port the code, test, and make it useful. (while allowing it to be defaulted to not be included in the default compile but instead be switched on at will)
i do agree that for the smartcard add-on the case should have had a small slot for the ribbon cable to come out (i just pinched it - we'll see how long before it breaks).
]]>Really great and compact proxmark
I like the ABS case that is provided
Love the antennas
I would have loved to have the JTAG connector/cable provided. Even if normally you never need it, things can go wrong and with such fine pitch, not everyone will be able to recover the pm3
I would have preferred to see a USB-C connector because it's more sturdy (I have so many cases where the micro-USB port started to move because of mechanical stress over time) and in addition to that you can drive more power from the port which could have helped for the antennas too
I would have appreciated if the plastic case would have provided better access to the smartcard connector and the JTAG pins through cutouts instead of having to open the case every time you need it. I'm considering using my Dremel now to do the cutouts myself, especially now that I soldered a connector on the JTAG pins to get easier access which prevents me from closing the case.
Documentation about what can be done through the FPC?
Even though iceman explained the rationale, I would have preferred to see the rdv40 mods (smartcard, FPC, external flash) merged into the main repository. The fork brings more risk about seeing the 2 repositories going out of sync at some point.
1. Currently none, but the team is making a Bluetooth/battery addon as we speak.
2. You will need to ask the distributing webshops what they will offer. We have no saying in it.
Results:
after a few minutes FPGA and the coil drivers (IC9 and IC10) become the warmest parts of the PM3
Maximum measured IC9 temperature during 23hours: 34 degrees Celsius (93 degress Fahrenheit) at the maximum ambient air temperature of 28 degrees Celsius (82 degrees Fahrenheit)
The IC temperature follows the ambient air temperature with a constant difference
Conclusion: There is no overheating risk at all with Orignal and Elechouse RDV2 boards (well, as long as you don't operate them in an oven). The statement above therefore must have been a misunderstanding?
]]>Simple software test would be, like I mentioned a couple of months back on GitHub to take and run iso15 commands, or any command doesn't turn of antenna afterwards, and let the device be for 24+ hours...
https://github.com/Proxmark/proxmark3/issues/499