FloBle + Swift + SDK 2.2beta : no delegate callbacks

[NicolasParticipant]

Hi,

I just got a FloBle device.
I’m trying to use it on an iPhone App developed in Swift.

Unfortunately I’m not able to detect any NFC tag.
I’ve followed all the steps in the README_Swift.md:
– included the framework 2.2 beta
– added the link flags, bitcode=no and added the MediaPlayer.framework
– copied the code into my ViewController class

When I launch the app, the FloBle is detected and everything seems fine.
I’ve got the following console logs:

2016-12-07 16:25:00.911445 V[570:86397] ::discovered peripheral ACR1255U-J1-001067 B5D444A3-FA21-4E18-BFAB-AB5CA2718003
2016-12-07 16:25:01.130194 VProject[570:86397] Peripheral Connected
2016-12-07 16:25:01.674094 VProject[570:86397] Services Discovered
2016-12-07 16:25:01.684099 VProject[570:86397] Reader Detected
2016-12-07 16:25:02.961761 VProject[570:86397] Peripheral Successfully Attached
2016-12-07 16:25:03.023633 VProject[570:86397] didChangeBatteryLevel 50
2016-12-07 16:25:03.083657 VProject[570:86397] EscapeResponse <e1000045 00b55287 6606fdef cd280ad1 d6f7a0d9 c9>
2016-12-07 16:25:03.351979 VProject[570:86397] EscapeResponse <e1000046 00521ac7 bcc1f382 947f1d9f 4a82602b 77>
2016-12-07 16:25:03.352261 VProject[570:86397] Peripheral Successfully Authenticated
2016-12-07 16:25:03.532244 VProject[570:86397] Firmware: FWV 1.16.03
2016-12-07 16:25:03.622307 VProject[570:86397] Hardware: HWV 1.03
2016-12-07 16:25:03.682719 VProject[570:86397] Serial Number: RR330-001067
2016-12-07 16:25:04.516155 VProject[570:86460] Have Response, registered
2016-12-07 16:25:04.516348 VProject[570:86460] Verfied Basic license
2016-12-07 16:25:04.784958 VProject[570:86550] Escape APDU:E0 00 00 48 04
2016-12-07 16:25:04.854212 VProject[570:86397] EscapeResponse <e1000000 0104>
2016-12-07 16:25:05.118735 VProject[570:86545] Escape APDU:E0 00 00 20 01 01
2016-12-07 16:25:05.183401 VProject[570:86397] EscapeResponse <e1000000 0101>
2016-12-07 16:25:05.440691 VProject[570:86514] Escape APDU:E0 00 00 40 01
2016-12-07 16:25:05.663244 VProject[570:86397] EscapeResponse <e1000040 01>
2016-12-07 16:25:05.665834 VProject[570:86397] Change Status:Absent

Unfortunatly when I try to detect a NFC tag nothing happens. No bip, no callback, nothing.

I tried the previous framework (v2.1) : the tag was detected (didChange delegate method was called with status : “present”), but nothing else (no didFindTag).

– Am I missing anything?
– How can I get the data stored into the tag? (I’m just trying to read it)
– Is there any documentation (other than the Readme file)
– I found the URL of the SDK on this forum. Is there an “official” place where I can download it.

Thanks for your reply.

[RichardKeymaster]

Hi Nicholas, this is an issue we’ve seen before and thought we had resolved. Let’s try a few things. First, I’ve sent you the Test App via TestFlight to make sure your hardware is working. We don’t have documentation beyond the Readme file so you need to depend on the Forum as a source of information. We’re working to improve on this soon.

Check out this thread where Scott seems to have addressed this issue.

best,
Richard

[ScottKeymaster]

Hi Nicholas,

Once you confirm using the Test App via TestFlight that your hardware works with your tags, I would ask that you add
"Transmit Power" : TransmitPower.highPower.rawValue,
into the configuration dictionary so it looks like this:

  let configurationDictionary : [String : Any] =
            ["Scan Sound" : 1,
             "Scan Period" : 1000,
             "Reader State" : ReaderStateType.readData.rawValue, 
             "Power Operation" : PowerOperation.autoPollingControl.rawValue, 
             "Transmit Power" : TransmitPower.highPower.rawValue,
             "Allow Multiconnect" : false]
        
        readerManager.setConfiguration(configurationDictionary)

To answer your question above “How can I get the data stored into the tag?”, setting “Reader State” to readData will return the data stored. Using readUuid will return the unique ID of the tag.

I have tested the code in the Readme again and I can’t replicate your issue. Please reply here if the above method didn’t work and I’ll continue to assist you.

Kind Regards,
Scott

[NicolasParticipant]

Hi Richard and Scott,

Thanks for your replies.

I downloaded the Flomio app from TestFlight and the tags are still not detected (I’ve got 4 of them).
I’m sure that they are working properly as I can read and write them from my Android smartphone. They are blank tags bought in this website : http://www.whiztags.com/.
I’m using this app to read and write data: https://play.google.com/store/apps/details?id=com.wakdev.wdnfc&hl=en.

With the TestFlight App, the Flomio is responding exactly the same as in my test app (built wit the code provided in the readme file) : Flomio is detected and is scanning, but no beep nor detection when NFC tag is close to it.

Is there anything special to do to initialize the tags ? (On the ones I’ve got, I’m not sure they have any UUID stored on them).

What makes me think that there may be something with the last SDK (2.2 beta) is that with the previous one (2.1), the Flomio was detecting the tags but no other delegate callback.

One last point, is that I’ve tried to detect the NFC tag that I have in my credit card (it’s a French one, I don’t know if you’ve got that in the US).
With SDK 2.1: tag detected but no data nor UUID
With SDK 2.2: nothing

I’ve tried to add the configuration lines Scott provided me (Transmit Power). There’s no significant change.

Regards,

Nicolas

[RichardKeymaster]

Hi Nicholas, I looked through the whiztags website and noticed that they sell Topaz tags as well as NTAG2xx tags. We do not support Topaz tags in the Flomio SDK and it may be the reason for the issue. Can you confirm you’re not trying to read Topaz tags with the Test app?

thanks,
Richard

[NicolasParticipant]

Hi Scott and Richard,

I confirm you : the NFC tags I’m using are TOPAZ.

I’m a bit disappointed by the Flomio Ble, I thought it would be able to scan every type of NFC tags and not only NTAG2xx.
Can it scan Mifare Tags?

Is it a limitation from the hardware or from the SDK?
Is it the same with the Flomio Jack?

Do you think that in a near future, I will be able to scan all types of NFC tags with my Flomio (with a SDK update) ?

Regards,

Nicolas

[RichardKeymaster]

Hi Nicholas, the limitation is not with hardware but with the Flomio SDK. Adding TOPAZ support is not a trivial undertaking so we are focusing on more accessible features at the moment. Mifare tags are currently supported though.

If TOPAZ support is mission critical for your integration you have two options to proceed:
1) Purchase Flomio Service hours to allow us to prioritize your request.
2) Build your app using the raw driver from the manufacturer. You can find those on GitHub here.

best,
Richard

[NicolasParticipant]

Hi Scott and Richard,

I got the final NFC tags which will be used by my client.
Good news it’s not Topaz, bad news, they are not detected either.

Here are their specs: http://imgur.com/a/DqiYm

Here are the info I got from the NFC Tools Android app: http://imgur.com/a/Kv0Pl

They are ISO 15693.

Regards,

Nicolas

• This reply was modified 7 years, 11 months ago by  Nicolas. Reason: Imgs didn't work

[RichardKeymaster]

Ughhh.. man, that’s a tough one as ISO15693 is a hardware dependent protocol. This means only our FloBLE EMV or FloBLE Mini readers can potentially read it. It will require firmware work as well as mobile SDK effort to get it to work for you. What’s the size of your client opportunity? How many readers do you expect will be purchased? Depending on some variables the cost of implementation can range between $10k and $30k of Flomio Service hours.

best,
Richard

[Author]

Posts