FloBLE+ reading card data

[AleixParticipant]

Hey flomies,

I’m trying to get my software right for later deploying a mPOS. I’m trying to read card data with the FloBLE but I haven’t been able yet. As I saw from one video of yours the 2PAY APDU command is “00 A4 04 00 0E 32 50 41 59 2E 53 59 53 2E 44 44 46 30 31 00”. But when I tap the card I get an ATR response from it.

I pasted my actual ViewController here:
http://pastebin.com/ZBnayBHJ

Thanks!

[ScottKeymaster]

Hi Aleix,

The ATR and UUID response (didFindATagUuid) automatically happens when a card is tapped in readUuid mode as in your code. You would then send an APDU to the card after the ATR is returned and you should receive a response in “didRespond(toApduCommand”. Can you try manually sending the APDU using a button or send from didFindATagUuid. Are you receiving any delegate callbacks other than didFindATagUuid after sending the APDU?

Kind Regards,
Scott

[AleixParticipant]

Hi Scott,

The thing is that I receive the ATR when I tap the card to the FloBLE Plus but it’s not calling any delegate method, only didChangeStatus.

Regards,
Aleix

• This reply was modified 8 years, 1 month ago by  Aleix.

[ScottKeymaster]

Hi Aleix,

Ok so I have something for you to move forward with.

Change the code in didChange(_ status to:

func didChange(_ status: CardStatus, fromDevice device: String!) {
        //The card status has entered or left the scan range of the reader
        if (status == CardStatus.present){
            DispatchQueue.main.async {
                let command = "00 A4 04 00 0E 32 50 41 59 2E 53 59 53 2E 44 44 46 30 31 00"
                self.device?.sendApduCommand(command)
            }
        }
        
    }

This will then trigger ‘didFindADataBlock withNdef’, we have not supported reading contactless EMV credit cards with our SDK so bare with us while we try accommodate removing NDEF related stuff that gets in the way. It’s likely that it will be on a later release.

Kind Regards,
Scott

[ScottKeymaster]

Hi Aleix,

Having tested sending the 2PAY apdu: “00 A4 04 00 0E 32 50 41 59 2E 53 59 53 2E 44 44 46 30 31 00” on a contactless EMV card, I have seen that in v2.1 beta, no data will be returned. I will make sure that in v2.2, the SDK will provide raw data ADPU responses.

Kind Regards,
Scott

[AleixParticipant]

Hi Scott,

So how many time is it gonna take to get that raw data using your readers? Could we speak privately somehow?

Thanks for everything,
Aleix

[RichardKeymaster]

Hi Aleix, we only provide free support through the Forums. If you want to speak pricately with our engineering staff to resolve your issues you may consider purchasing Flomio Service hours. We will open a private Slack channel for your issue and allow you to discuss your experiments with us live. This is often well worth it for customers with mission critical needs.

best,
Richard

[ScottKeymaster]

Hi Aleix,

Here is a VERY early beta of Flomio SDK v2.2, there will very likely be bugs. I have updated the Readme (and Swift Readme) with API changes. I have tested a contactless card and it is returning the data from the response. didFindTagWithData returns a NSDictionary with the key “Raw Data”.

Please let me know how you get on and any bugs you find.

Kind Regards,
Scott

[AleixParticipant]

All right! I’ll test it ASAP and I’ll let you know the result!

Thank you very much!!

[AleixParticipant]

I just changed the SDK but now it’s not detecting any smart card at all. It does not even make the sound when a card is tapped. How is this possible? Do I have to upgrade the reader firmware?

Thanks!

[ScottKeymaster]

Could you paste whatever logs you are seeing in Xcode please. You shouldn’t need to update your reader.

Cheers,
Scott

[AleixParticipant]

That’s my log:

2016-11-08 22:39:52.522851 EzyPayments[1067:305038] [MC] Reading from public effective user settings.
2016-11-08 22:40:04.282206 EzyPayments[1067:305038] Init FloBLE Plus
2016-11-08 22:40:04.290436 EzyPayments[1067:305038] serial number not valid
2016-11-08 22:40:04.339084 EzyPayments[1067:305038] [Common] _BSMachError: port 8627; (os/kern) invalid capability (0x14) "Unable to insert COPY_SEND"
2016-11-08 22:40:04.342025 EzyPayments[1067:305038] [Common] _BSMachError: port 8627; (os/kern) invalid name (0xf) "Unable to deallocate send right"
2016-11-08 22:40:04.347362 EzyPayments[1067:305038] ::centralManagerDidUpdateState supports 5
2016-11-08 22:40:04.372314 EzyPayments[1067:305038] ::discovered peripheral ACR1255U-J1-000963 7193609A-8C60-4701-AF5C-3CAE00C86218
2016-11-08 22:40:04.787597 EzyPayments[1067:305038] Peripheral Connected
2016-11-08 22:40:05.203133 EzyPayments[1067:305038] Services Discovered
2016-11-08 22:40:05.212417 EzyPayments[1067:305038] Reader Detected
2016-11-08 22:40:05.893615 EzyPayments[1067:305038] Peripheral Successfully Attached
2016-11-08 22:40:05.952072 EzyPayments[1067:305038] didChangeBatteryLevel 50
2016-11-08 22:40:06.042145 EzyPayments[1067:305038] EscapeResponse <e1000045 002120b6 8bd44b9e 93ac392c 185da339 88>
2016-11-08 22:40:06.102800 EzyPayments[1067:305038] EscapeResponse <e1000046 008e8875 a6663454 6e11700c df336240 ae>
2016-11-08 22:40:06.103019 EzyPayments[1067:305038] Peripheral Successfully Authenticated
2016-11-08 22:40:06.192269 EzyPayments[1067:305038] Firmware: FWV 1.16.00
2016-11-08 22:40:06.251876 EzyPayments[1067:305038] Hardware: HWV 1.03
2016-11-08 22:40:06.312059 EzyPayments[1067:305038] Serial Number: RR330-000963
2016-11-08 22:40:06.389526 EzyPayments[1067:305245] Have Response, registered
2016-11-08 22:40:06.389651 EzyPayments[1067:305245] Verfied Basic license
2016-11-08 22:40:06.658746 EzyPayments[1067:305291] Escape APDU:E0 00 00 48 04

[RichardKeymaster]

Hi Aleix, it seems like we shipped you a unit with outdated firmware by mistake:

2016-11-08 22:40:06.192269 EzyPayments[1067:305038] Firmware: FWV 1.16.00

Please follow these instructions to update your reader firmware.

Apologies for the confusion,
Richard

[AleixParticipant]

I’ll try it ASAP with W7, but with W10 it doesn’t detect the reader.

Thanks,
Aleix

[AleixParticipant]

Hey,

I tried it several times updating, but it gets stuck on the installing driver…

Aleix

[RichardKeymaster]

Make sure you follow the Firmware Upgrade Instructions pdf contained in the Flash tool bundle. Specifically step 6.

Windows is not very cooperative so it may require deleting the default driver on your system and rebooting in order to get the installer to kick on again. It also might be helpful to read this post.

[AleixParticipant]

I installed W7 to do the procedure, I followed everything, but when I get to step 17 it keeps saying Error, I already did the CCIDEnableEscapeCommand and it’s still not working..

[AleixParticipant]

Ok! I finally managed to update the Frimware, it now says 1.16.03.

The thing is that when I tap a Contactless card it says that it should be ISO 14443A. What does that mean? I tried with 3 different cards and I get the same, they are all bank cards that work in shops.

[RichardKeymaster]

Nice! Ok, the error you’re getting is that the Flomio SDK only supports ISO14443A protocol. The payment cards you’re using are probably operating on the ISO14443B protocol so we will need to implement that support for your use case. Is your work mission critical or just an experiment for a potential revenue generating application? I ask because we it will likely take some time for us to implement ISO14443B support. We offer the option to purchase Flomio Service hours to prioritize this work, in case you’re interested.

best,
Richard

[AleixParticipant]

Hi again,

Do you support ISO14443B already?

Regards,
Aleix

[RichardKeymaster]

Hi Aleix, we won’t be getting to implement ISO14443B support until after mid-December, 2017 based on our current workload.

best,
Richard

[AleixParticipant]

Hi Richard,

Before buying the service hours I’d like to get some ETA if I’m finally up for it, just to know how much it will cost me.

Regards,
Aleix

[ScottKeymaster]

Hi Aleix,

To expose 14443B for the FloBLE Plus in a safe and tested manner, we suspect this will take 16 hours of development and testing time which would amount to $2400.

Scott

[tesarParticipant]

Hi Scott,
have implement ISO14443B support for ACR1255U-J1 allready?
Regards Petr

[Author]

Posts