[Easygoband uso hernandez]

Hi,
first of all thank you for your prompt reply.

Let me better explain the context of the issue we’re facing. We are trying to integrate with some hotel door lock solutions which are only compatible with SL1 (aka Mifare Classic). So what we would like to achieve is configuring the Mifare Plus EV1 so that some sectors operate in mixed mode and others only in SL3.

The actual issue we have is that in order for us to operate with the SL3 commands we need to set the SAK so that it the chip identifies itself as IsoDep card and not MifareClassic. If we set the SAK to be SL1 then the door locks does recognise it and works correctly but then we cannot use the Android IsoDep channel. If we set the SAK to identify as IsoDep then we can use SL3 with android but then the door locks do not work with it.

The question is: Is there a way to set the SAK to be SL1 and use the Mifare Plus EV1 (some sectors are mixed mode and others only SL3) with SL3 mode from Android? Or is this impossible?

---

+ 0  |  - 0

[Easygoband uso hernandez]

Thanks again for the answer!

Let me one last question

How is the correct usage of the TapLinx library to perform a SectorSwitchToSl1SL3Mix with the PlusEV1SL1 object?
The method is in the interface and it throws an authentication failure, but the given keys are correct (I set everything to FFs on SL0)


I attach the image of the code I use for the sector switch, hope you can help me

---

+ 0  |  - 0

[Easygoband uso hernandez]

Hello, thanks for the answer

As you said we want to operate with Sl1Sl3MixMode but the problem we are having is activating the 14443-4 protocol on the reader when the card is detected as MifareClassic

In other words, the SAK of the card is 0x08, but we want Android to open the IsoDep channel with it. How can we perform this operations with TapLinx lib?

The operation for PlusEV1SL1 of "SectorSwitchToSl1SL3Mix" on TapLinx is not working(More info in the first question).
How should it be done?

---

+ 0  |  - 0

[Easygoband uso hernandez]

Hello, thanks for the answer!

We need for our application to perform 14443-3 and 14443-4 operations on the same chip.

The chip should be recognised as mifare classic for the legacy systems, thats why we use 0x08 SAK
But for the new system we would like to operate on IsoDep 14443-4 operations, with SL3 sectors and so on.

So we need to be able to change from 14443-3 to 14443-4 on the same tap of the tag.
Is this behaviour possible?
Also, you said "if you made it correct" can you explain which operations of the taplinx sdk do you refer? can you give an example please?

Thanks for your answer.

---

+ 0  |  - 0

[Author]

Posts