Home › Forums › Ask the Flomies › Issue reading DESFire EV2 tags with ACR1255U
Tagged: ACR1255U-J1, DESFire EV2, FloBLE Plus
-
AuthorPosts
-
January 17, 2017 at 4:01 pm #58197
Hi,
I’ve been trying to read a DESFire EV2 tag using the ACR1255U on iOS. For the most part the tag can be read but a lot of the times I’m experiencing what appears to be the FW hanging in the middle of a read operation. The app reads other tags fine. My only guess as to what is happening is a fringe/tearing issue which is causing the FW to hang. Only way to get the reader to communicate again is by turning off the reader and turning it back on. We have about 50 readers and they don’t all exhibit this behavior. I’m using an iPhone 6 running iOS 10.2 and the reading is running FW 1.16.03.
January 17, 2017 at 4:21 pm #58198Hi Brian,
Thanks for sending this issue our way. We haven’t done much with DESFire EV2 tags, despite have some samples in stock. In order to help troubleshoot your issue, we will first need to reproduce it. Can you provide an APDU sequence that causes the issue on troubled units? Once we can reproduce the issue internally we can begin to test it across our engineering team. We’ll also coordinate with ACS to reach a resolution you can work with.
Kind Regards,
ScottJanuary 17, 2017 at 4:23 pm #58199More info: After the reader hangs, if I try scanForPeripheralsWithSErvices I get a callback from the Central Manager didDiscoverPeripheral but the cbPeripheral name is null and the state is disconnected.
Running BT Demo at this point shows an empty table when trying to select a reader. If I turn off the reader and turn it back on the reader appears (oddly) in row 2.
January 17, 2017 at 5:51 pm #58201Hi Scott,
Please provide me an address and I will have some tags sent to you. The tags are identical to the tag Richard was using at CES17. You can also download the app on iOS and I can provide you with an activation code.
Here are the commands and apdus the app sends to the ACS Bluetooth SDK:
The format is:
"APP Method" or "ACS API Callback" - "ACS API Method" : "APDU"
<TURN ON READER> didDetectReader - attachPeripheral didAttachPeripheral - authenticateWithMasterKey : XX ... XX didAuthenticate - transmitEscapeCommand : E0 00 00 21 01 00 enablePolling - transmitEscapeCommand : E0 00 00 40 01 didReturnEscapeResponse - transmitEscapeCommand : E0 00 00 29 01 01 <READ TAG> didRxCardStatus(ABTBluetoothReaderCardStatusPresent) getATS - transmitApdu : FF CA 01 00 00 getUID - transmitApdu : FF CA 00 00 00 sendAPDU - transmitApdu : 90 5A 00 00 03 01 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 00 00 00 02 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 02 00 00 32 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 34 00 00 32 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 66 00 00 32 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 98 00 00 32 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 CA 00 00 32 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 FC 00 00 32 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 2E 01 00 32 00 00 00 sendAPDU - transmitApdu : 90 BD 00 00 07 02 60 01 00 32 00 00 00 disablePolling - transmitEscapeCommand : E0 00 00 40 00 didReturnEscapeResponse - transmitEscapeCommand : E0 00 00 29 01 0x00 <DISPLAY DATA>
January 18, 2017 at 4:58 am #58217Hi Brian,
Thank you for that information. I will begin trouble shooting, I think I may have seen this issue before with the ACR1255U-J1. I will email my address to you via the email address associated with your account @itnint.com to get a sample tag sent to me. I am based in Ireland.
Kind Regards,
Scott -
AuthorPosts
You must be logged in to reply to this topic.