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

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

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

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

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