Since last week I am also the happy owner of a Mifare DesFire EV2 8k Flex implant.
So far I have been able to integrate it into my applications without any problems.
However, our access control system (Mifare Desfire EV1, EV2 and EV3 cards are used here) is having problems recognizing the implant.
The card readers are Honeywell LuminAXS readers (027913.10). These only evaluate the UID for us. On my management PC, I can read the implant with a Honeywell Admitto (Mifare Classic / Mifare DESFire EV1 Art.026487-10) reader without any problems and the UID is also written to the software as with the other cards.
However, when I hold my hand to the reader on the door, nothing happens, neither positive nor negative acknowledgement.
I then read the implant once with my Flipper Zero, saved it and if I emulate it now, I can use it to open the door.
What I noticed, however, is that the Flipper Zero first recognizes the implant as a multichip (Mifare DesFire and EMV) and I am asked which data set of both I want to read.
I then have to confirm DESFire and can read and save the chip.
Could this be the problem?
Is it possible to deactivate the EMV function so that it is recognized as a pure Mifare Desfire chip?
If I understand correctly, EMV is intended as a payment option, which does not work here in Germany with this type of chip anyway ?
I hope I was able to describe my problem reasonably well
Ah ok… TagInfo doesn’t indicate any EMV applet AIDs at all… I bet it’s a Flipper “bug” where it detects APDU support and assumes it’s an EMV capable card… even if there are no EMV applets (see EMV2.png)
Yes, I did some reading yesterday and also saw that the support for ISO/IEC 7816-4 in particular could give the impression of an “EMV card” (as used for payment cards).
Do you have any idea what the problem might be with the Honeywell readers?
I have 2 other physical cards here in the appendix which can be read in the system without any problems. These are EV1 and EV3. Unfortunately I have not found an identical EV2 at the moment, but I have ordered one for testing.
I can’t tell from the ZIP files you sent what the system might be tripping up on. Can you confirm the reader is actually reading the flexDF2? Are there errors in the system logs for failed reads?
I tested a little further and could briefly read the implant on the outer edge.
I have now tested it with the 20mm repeater stickers and I can read the implant reliably.
I saw in the documents that there was an update at the end of 2023 that was supposed to improve the reading for DF EV2. I will have this carried out and test it further.
