September 21, 2016 at 1:32 pm #56502
I am trying to use Flomio Basic SDK and ACR1255U-J1.
It does not appear to connect to my running on iphone5
It also doesn’t appear to connect to TestFlight app.
I purchased the ACR1255 from someone else.
Is this supposed to work?
Do i need to modify something on the ACR1255 to make it work with Flomio SDK?September 21, 2016 at 1:49 pm #56503
hmmm… seems to be working now…September 21, 2016 at 2:18 pm #56504
Glad to hear that.. some details that might help others:
I’ve sent you the Flomio Test app via TestFlight. Instructions:
1) Install the Test app.
2) Launch the app.
3) Confirm Bluetooth4.0 is enabled on your device
4) Choose FloBLE Plus from the menu.
5) Turn on the FloBLE Plus reader by moving switch to “B” position. Should hear beep and blinking blue LED
6) You should be prompted for Bluetooth Pairing code. Enter: 000000
7) Click Close. And repeat steps 3-6
8) The FloBLE Plus reader (ACR1255U-J1) should be detected and listed in top portion of the app (this is your device ID)
9) Place an ISO14443A NFC Forum Type 2 tag on the surface of the FloBLE Plus (over the Flomio Spark logo)
You should witness scan entries posted on the screen and hear an audible sound.
Send us your device ID for your ACR1255U-J1 so we can enable your Basic SDK license on our back end. You can download the latest Flomio SDK from here.
RichardSeptember 21, 2016 at 7:19 pm #56510
how do i read data with the 2.0 sdk? is there more documentation somewhere?September 22, 2016 at 12:40 am #56513
The only documentation we’ve released at this point in the README.md file inside the Flomio SDK bundle. We know this is less than ideal and we’re working to make things better for customers to operate independently. That said, we are aggressively committed to answering questions posted on these Forums in under 24 hours if not immediately.
What’s your use case? What type of NFC tags are you using? What data are you interested in reading?September 23, 2016 at 1:58 pm #56523
i have a bus and i want riders to tag-in with nfc cards. nfc card is written with ndef data containing card id that i want to read. other posts say ndef may or may not work? or only partially?September 23, 2016 at 3:13 pm #56525
NDEF reading works in the latest Flomio SDK (v2.1) but only for the FloBLE Plus and FloJack MSR. Also, we only support NFC Forum Type 2 tags for NDEF reading and only Type 4 tags from HID (Trusted Tags).September 26, 2016 at 4:06 pm #56540
i am using Type 2 tags. can i get Flomio SDK v2.1? Is there sample code?September 26, 2016 at 4:28 pm #56542
Yeah, NDEF worked on our latest released Flomio SDK bundle (v2.0) including Sample code is downloadable here:
v2.1 is still in Beta and not ready for release since it can brick your device if not used properly.
RichardSeptember 28, 2016 at 3:17 pm #56574
i’m having some trouble with the acr155u-j1 stopping responding after a time. all leds off. perhaps it is going to sleep? pressing the button on the side makes it reconnect and everything is fine. is there something i can do to avoid this? it will always be plugged in, so battery life is not an issue.September 29, 2016 at 8:17 am #56583
This is a feature in the latest beta release of the SDK, v2.1 beta. If your FloBLE Plus (acr155u-j1) is using the latest firmware, 1.16.03, the device is configured to never sleep.
Here is the SDK v2.1 beta. Refer to the README as there are tweaks to the SDK delegate methods.
Please let me know if there are any issues and I can assist you.
ScottOctober 2, 2016 at 11:33 am #56619
So I recently got the SDK Basic to use with an ACR1255u unit I received elsewhere, not a FloBLE device. From what I’m reading above, is it true that I can only read NDEF data if I have. FloBLE device? Because all I can seem to get is a 16 byte chunk of the text I’ve written to my tags. Or is there a way to get the NDEF data that I am overlooking?October 3, 2016 at 6:24 am #56624
You will need to order the Basic Flomio SDK to get your device licensed. You can do so here: https://flomio.com/shop/apps/flomio-sdk-basic-turnkey-oem-support/
Reading NDEF data requires manually sending APDUs to read each 16 byte chunk of your NDEF formatted data and then parsing it to get the payload.
Our NDEF parser currently only supports URL types. If you will be using the SDK for reading other data types, we can add it to our pipeline.
Let me know if you have any issues setting up the SDK or reading NDEF data.
You must be logged in to reply to this topic.