FloBLE EMV User Manual

[RafaelParticipant]

Question: Is there a setup or user manual for this device? If so, please provide a link to it. We purchased the device but can’t get it connected to a phone and aren’t sure if it is connecting to the NFC device either (a blue LED seems to light when in proximity to an NFC device).

[RichardKeymaster]

Hi Rafael, our reference documentation site is here: http://docs.flomio.com . If you have specific questions or are encountering a particular issue, let us know and we can help. The Forums search feature is also a useful tool to get problems resolved quickly.

best,
Richard

[RafaelParticipant]

Hi Richard,

My engineers received some FloBLE Plus devices and were able to read some devices using the NFC_Action iOS app. However, they have been struggling to get the same app to work with the FloBLE EMV device that we purchased as well. So, either the FloBLE EMV device is defective or the NFC_Action iOS app doesn’t support the FloBLE EMV device. Can you confirm that the NFC_Action iOS app does indeed support the FloBLE EMV?

[RafaelParticipant]

Richard,

We have a skeleton app running through which we can read the HME raw data with FloBLE plus.
However when I try to connect to EMV I get the following debug messages:

2017-05-10 00:44:31.703176+0300 flomio[3267:1124311] Init FloBLE EMV
2017-05-10 00:44:40.879841+0300 flomio[3267:1124311] [App] if we're in the real pre-commit handler we can't actually add any new fences due to CA restriction
2017-05-10 00:44:40.879960+0300 flomio[3267:1124311] [App] if we're in the real pre-commit handler we can't actually add any new fences due to CA restriction
2017-05-10 00:44:45.907699+0300 flomio[3267:1124386] findPeripheralReader FT_00A050021031
2017-05-10 00:44:47.011365+0300 flomio[3267:1124386] Have Response, unregistered
2017-05-10 00:44:47.011547+0300 flomio[3267:1124386] The device is not licensed. http://flomio.com/flojack/#getting_device_id

It looks like the device is not registered/licensed (whatever that means)…
There is not visible serial number on the device other than the number 98000 embossed in plastic, but it doesn’t look like a s/n. (The FloBLE plus has a sticker with a lot of numbers,also s/n, among other data).
Can you help us please?

[RichardKeymaster]

Hi Rafael, I’ve added your device to the license server and this should address the issue with the FloBLE EMV. Apologies for the problem, it’s something that should have been done prior to fulfilling your order.

best,
Richard

[RafaelParticipant]

Hi Richard,

Writing to our device via NFC is very important in our application and we were disappointed to see that it isn’t supported yet by Flomio. We saw from another thread (ACR35-A1 iOS Read/Write Sample) that you mention SDK v2.3 and something about support for view synchronous ADPUs. When can we expect information on the upcoming writing function? When will it be supported? I believe that we would have to have a mechanism to specify a memory address and the amount of data we want to write. Also is there a protocol that involves monitoring of some flags on the NFC tag which tells us when we’re available to write?

Thanks,
Rafael

[ScottKeymaster]

Hey Rafael,

You will be able to write to tags using the EMV using v2.3. I have something working here but I will test it and send it to you by tomorrow.
Do you know what tag types you will be using?
Are you familiar with APDUs? And do you know the APDUs used to Read / Write to this tag?
Also, are you using Swift or Objective-C?
No worries if you don’t know the above info, I can help you with them.

Kind Regards,
Scott

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

[RafaelParticipant]

HI Scott,

Our programmers are using Swift but we are not familiar with APDUs. We are using the NXP NT3H2211.

Rafael

[RichardKeymaster]

Hi Rafael, APDU stands for Application Packet Data Unit and it’s an interface defined by the ISO7816-4 specification. It’s something that you and your developers need to be familiar with in order to properly read/write to the NXP NT3H2211 chip. It’s not specific to the FloBLE EMV but to all our NFC readers.

We can bring you and your developers along here in this Forum but it may take some time to ramp up. If your go to market timeline is compressed then you may consider purchasing our premium Flomio Service support. This way we can assign an engineer to carry out your integration needs.

best,
Richard

[RafaelParticipant]

Hi Richard,

Thanks for the ISO link. That will help.

Here’s another question: We have noticed a reading difference between the FloBLE Plus and the FloBLE EMV when reading three different devices: 1.) the NXP device that we are developing, 2.) an NFC Smartcard and 3.) the NFC development board.

On the Plus we have been able to read some raw data, around 255 bytes although there should be about 800 bytes available to be read.

On the EMV whenever we approach any NFC device, we only get an “UUID” (a kind of unique identifier) but no payload/memory data.

Is there a different protocol for each of the different devices? Or different parameters? We know that the EMV is not defective because the LEDs are flashing and we get the UUID promptly when approaching the NFC devices…

[ScottKeymaster]

Hi Rafael,

I am glad to hear that you are having success with the FloBLE Plus. There is no different protocol, but the SDK does not support reading tag data with the EMV on v2.2.

I can send you a beta version of v2.3 which will expose sending APDUs with the EMV, and I can give you a function for you to implement to read the data.
Because tag protocols all vary, we have exposed the SendApdu interface to developers and are moving away from providing support for reading/writing specific tag data.

Here is Flomio MW v2.3 BETA.
There are updated delegate methods, along with one extra step when configuring the Build Settings of your project.
There is also a step to show you how to read data from Type 2 tags, you would need to increase the ’16’ to a higher number to try read more data.

Please let me know how you get on.

Kind Regards,
Scott

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

[RafaelParticipant]

Hi Scott,

We are having some success reading both units but there are still some challenges and it seems like we are having better luck with the Plus than with the EMV.

Specifically, my engineering team is reporting the following:

There are differences between EMV and Plus:
When sending APDU FFB0000F10 I get aabbccdd 11223344 00020000 0000d28c 9000 on EMV.
I get AA BB CC DD 11 22 33 44 00 02 00 00 00 00 D2 8C 90 00 on Plus which is the same data as on EMV even if formatted differently.

However when I send FFB0001010 I get 6a82 on EMV.
On Plus I get 11 22 33 44 00 02 00 00 00 00 D2 8C 1A 00 00 00 90 00 which is correct.

On writing:
Sending APDU FF D6 00 0F 04 AA BB CC DD to Plus I get response 90 00 which is OK and the data is there on subsequent readings.
When sending the same APDU to EMV I get response:

2017-05-23 22:31:30.550712+0300 flomio[8514:3062760] Command APDU:FFD6000F04AABBCCDD
2017-05-23 22:31:30.550829+0300 flomio[8514:3061925] Response Apdu: 6300
2017-05-23 22:31:30.551037+0300 flomio[8514:3061925] handleApduResponse: Operation was unsuccessful.

Please advise on the meaning of the replies on EMV (6a82 means “File or application not found” and 6300 means “No information given”) as isoiec7816-4{ed2.0}en document is not very helpful and also on getting consistent behavior between EMV and Plus.

[RichardKeymaster]

Hi Rafael, the EMV firmware is still coming along so it doesn’t have the same graceful handling than the Plus. I would recommend that you use the shortened commands that are working for now and allow us to investigate and correct the longer commands that are troublesome on the EMV.

best,
Richard

[ScottKeymaster]

Hi Rafael,

Glad to hear we are making a bit of progress. Here is a firmware update for the BR500: firmware update tool

This should help with your commands to write data to tags.

Kind Regards,
Scott

[RafaelParticipant]

Hi Scott,

We couldn’t get the EMV firmware update tool to work. Got a 0x800000d error code, but this error code doesn’t seem to be documented. So we have set the EMV part of the project aside for now.

We’ve turned our focus to get the Plus to be read for now (which as mentioned before requires writing to the device) and we have progressed further. We were able to get the short reads to work. The full size of the memory of our device is 2kB and we have been able to read 1kB of that memory so far. We are working to get it all read.

Cheers,

Rafael

[RafaelParticipant]

Richard/Scott,

We are still stuck with the Plus and unable to get beyond a 1kB read. Can you guide us on how to make a long read beyond address 256?

[RichardKeymaster]

Hi Rafael, we haven’t tested that deep into card memory space. I will log this issue so we can address it once we free up. We’re currently working on a time sensitive release so don’t have bandwidth this week.

stand by,
Richard

[RafaelParticipant]

Hi Richard/Scott,

Please give us an update on your progress concerning reading more than 1kB of memory with the Plus. We are counting on you guys! Thanks.

[RichardKeymaster]

Hey Rafael, we haven’t been able to dedicate any time to this issue yet. Based on our workload it may be 1-2 months before we can get to it. We are committed to this product line and supporting your needs but given that it represents such a small portion of our revenue stream, it’s tough for us to reprioritize staff for this work.

That being said, we offer Flomio Service hours to customers who have a mission critical need. This allows us to hire temporary staff to implement/debug/test the necessary features for your needs.

best,
Richard

[RafaelParticipant]

Richard,

The Flomio Plus I purchased recently doesn’t seem to be able to read NFC tags. Our app picks up the Bluetooth signal but no data is transferred when it is in the vicinity of a tag. My development team in Europe is able to read tags with their Flomio Plus so we believe it might just be a problem with my particular device. What should I do at this point?

[Author]

Posts