Read data from a TI RF430CL330H

[FlorianParticipant]

Hello,

we are currently trying to implement a product for an industrial client using one of your NFC readers but we cannot continue because we have a problem.

We bought a FloJack MSR, downloaded the Basic SDK version 2.2beta from Dropbox, followed the instructions using Swift and it is running on our phones. Our NFC tags type 2 are detected by the FloJack and didFindTag gets called with the UUID of the tag.

We are now trying to detect and read a sensor with a RF430CL330H chip from Texas Instruments conforming to the ISO-14443B protocol. The problem is that the sensor is not detected by the Flomio SDK. We also tried sending different APDUs especially REQB (with and without checksum) which is given as the first command in the detection procedure by TI, but did not get any response. When we use the method sendApduCommand in the Flomio SDK to send the REQB, the App always crashes and we don’t know why, because reading the UUID of the type 2 tags with 0xFFCA000000 is working without problems.

Will the Pro SDK help? Our client has already ordered it and we are waiting to get the download link.
Hopefully you can help us to get the communication with the sensor to work. Thanks in advance!

Florian

[ScottKeymaster]

Hi Florian,

The Flojack MSR currently only supports reading ISO-14443A tags. The SDK should not crash when the sendApduCommand method is sent, I will look in to that and get back to you. Unfortunately, the Pro SDK will not make a difference. Our team is currently very busy attending CES so delays may be unavoidable.

Kind Regards,
Scott

• This reply was modified 7 years, 10 months ago by  Scott.

[FlorianParticipant]

Hi Scott,

thank you for your quick reply. Does the FloBLE support reading ISO-14443B tags?
Am I right, that the FloJack MSR technically supports reading ISO-14443B tags, but the SDK does not? So we could also implement it on our own?

We tried to send 0x05000071FF (REQB with checksum) and 0x050000 (REQB without checksum) by the way.

Kind regards,
Florian

[FlorianParticipant]

Hi Scott,

We now noticed that the BLE-reader does not support ISO-14443B-tags, too, since the SDK does not (see https://flomio.com/forums/topic/floble-reading-card-data/).

We’re currently building a high-revenue application for a big company in europe, which is relying on NFC and your reader. Since your website states it supports the required ISO-standard, we thought our project is feasible, but now with that SDK it’s not.

We’re now wondering why the specification (https://flomio.com/shop/readers/flojack-msr-nfc-reader-for-ios-android/) states that you support a protocol which is not yet implemented. We don’t see why we should buy the flomio service for the protocol to be implemented faster because frankly, you’re already claiming that this is reality and we trusted the specification to be truthful. Can you please give us a reliable projection on how long it will take to implement the functionality? With the system in place, our client would use the reader for approx. 200 of their employees.

Thanks!

Best

Florian

[ScottKeymaster]

Hi Florian,

We are a very small team and are evolving the SDK as demand dictates. In this case, ISO-14443b tags should communicate with the reader and be exposed with the SDK but the SDK does not read data. This is obviously not the case because you are experiencing a crash when any APDUs are being sent so you can’t read data yourself. Thank you for bringing it to our attention and I will work to get it resolved. Would you be able to send a sample RF430CL330H tag so I can begin working to fix the SDK to allow communication? I am based in Ireland.

Kind Regards,
Scott

[FlorianParticipant]

Hi Scott,

we are able to send you a sample RF430CL330H tag. Can you please give me an email address so we can contact you to clarify things like your address.

The following is the last part of the log when try to send the REQB before the App crashes:

2017-01-09 18:48:43.805801 FlomioTest[2387:646178] Command Apdu sent: 05 00 00 71 FF
2017-01-09 18:48:43.919973 FlomioTest[2387:646274] in didSendStatus
2017-01-09 18:48:43.920975 FlomioTest[2387:646274] Stat Response time = 0.125205
2017-01-09 18:48:43.921064 FlomioTest[2387:646274] Stat Sleep Setting = 30
2017-01-09 18:48:43.921129 FlomioTest[2387:646274] Battery Level:100
2017-01-09 18:48:44.082483 FlomioTest[2387:646274] in didSendPiccAtr
2017-01-09 18:48:44.082616 FlomioTest[2387:646274] locked responseCondition
2017-01-09 18:48:44.083715 FlomioTest[2387:646274] unlocked responseCondition
2017-01-09 18:48:44.134703 FlomioTest[2387:646178] in didSendPiccResponseApdu
2017-01-09 18:48:44.134962 FlomioTest[2387:646178] Response Apdu: 63 00
2017-01-09 18:48:44.137918 FlomioTest[2387:646178] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]'
*** First throw call stack:
(0x183ad11b8 0x18250855c 0x1839b4eac 0x1839b4d1c 0x1000b437c 0x1000b7df0 0x1000d8188 0x1000d7f08 0x100d19258 0x100d19218 0x100d29080 0x100d28b78 0x182b632a0 0x182b62d8c)
libc++abi.dylib: terminating with uncaught exception of type NSException

Thank you for your support.

Kind regards,
Florian

[ScottKeymaster]

Hi Florian,

Very good! My email is scott@flomio.com
I will use the email associated with your forum account here @tum.de to send my address.

Are you just looking to get the tag UUID of the RF430CL330H using the MSR? If so, I am confident I will be able to resolve this issue in less than two weeks.

Thank you for sending the log of the error, it has helped me find the issue.
Kind Regards,
Scott

[FlorianParticipant]

Hi Scott,

we got the email with your address and will send it out as soon as possible.

Getting the UUID of the tag would be a great step for us because that would mean that the tag is actually detected by the SDK.
We could then continue by trying to read the data.

Kind regards,
Florian

[FlorianParticipant]

Hi Scott,

we shipped the tag earlier this week and it will hopefully arrive soon. Looking forward to hearing from you with good news.

Kind regards,
Florian

[FlorianParticipant]

Hello Scott,

have you already received the tag? If not, then it would be great if you could just write a short message when it arrives.
We can currently not continue to implement our system because the next major step is to read the data from the tag.
Thank you!

Kind regards,
Florian

[ScottKeymaster]

Hi Florian,

I will contact you when it arrives.

Kind Regards,
Scott

[ScottKeymaster]

Hi Florian,

Your device has arrived. I will be testing this with our readers over today and tomorrow and will have a response to you early next week.

Kind Regard,
Scott

[ScottKeymaster]

Hi Florian,

I have not been able to read your tag using the Flojack MSR unfortunately even after trying to reconfigure it. I have however been able to interact with it using 2 other readers we provide, namely the FloBLE EMV and the Flojack BZR.

Please let me know what APDU sequence you will be using (or whatever you know so far) so I can better inform you on the best reader for your use case. My initial recommendation would be the FloBLE EMV. The Flojack BZR has a lower data throughput than bluetooth readers due to the limitations of the audiojack.

Kind Regards,
Scott

[FlorianParticipant]

Hi Scott,

we have already ordered the FloBLE and hope to get it soon. We are running out of time to be honest, so once the FloBLE arrives, what do we have to do? Do we have to change more than the device-type in the SDK? What were your steps to interact with the sensor?

We tried to follow the steps on page 7 of the following file: RF430CL330H User’s Guide.
So the APDUs we tried are 05 00 00 71 FF (REQB with checksum) and 05 00 00 (REQB without checksum).

Kind regards,
Florian

[ScottKeymaster]

Hi Florian,

Can you confirm your order number via email to scott@flomio.com.
If you have ordered a FloBLE Plus, I will recommend you change to a FloBLE EMV.

Kind Regards,
Scott

[Author]

Posts