Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.
Home › Forums › Ask the Flomies › Ensure BZR is Registered and SDK Access
Tagged: Flomio SDK, NFC write
Hi,
Looking at the git link on the website and then perusing the posts here, it isn’t clear to me what the current stable iOS SDK version is for my device (Flojack BZR) – and where I might find it. Also, want to make sure I’ve properly registered for SDK access, I purchased the device a few months ago. Here is the device ID:
C16C80B8010004D4
Lastly – I am definitely interested in a device that gives ability to write data to tags. I’ve read on the forum here that the BZR might not be the ideal device for writing, only reading. The current tag we are using for our Android implementation, with device hardware, is this:
https://www.atlasrfidstore.com/smartrac-bullseye-nfc-white-wet-inlay-nxp-ntag213-roll-of-4-000/
Is there a device that Flomio offers that would be better suited to reading and writing with iOS?
Thanks!
Bobby
Robert,
Here is the link to the latest Flomio 2.0 SDK: https://www.dropbox.com/s/7moz4izr8hjf3yq/FlomioSDK.zip?dl=1
If you are interested, you can check out the Flomio SDK 2.1 that is on Beta: https://www.dropbox.com/s/vskvgtdo57ymb3p/FlomioSDKv2.1_beta.zip?dl=1
The best device to write NFC tags is the FloBLE Plus (https://flomio.com/shop/readers/floble-plus-nfc-reader-for-mobile/)
At this time, the SDK does not support writing a tag, but it is on the roadmap.
Thanks,
Daniel
Hey Bobby, the device id you sent is indeed registered for Flomio SDK use. The NTAG213 tag you are using should be readable by all of the readers we sell. That being said, the latest release of the SDK does not support writing to tags for any of our readers. This has been a common request from customers but due to our size, a very time consuming effort. If you’d like to speed the process up, you might consider sponsoring some Flomio Service hours to prioritize the task.
best,
Richard
You must be logged in to reply to this topic.