February 25, 2016 at 2:48 pm #54624
I have received my FloBLE and FloJack. I have also downloaded the SDK from Github.
With both I have had problems to get them working.
The model numbers I have received are:
For the FloBLE. None of my iOS devices can find the bluetooth device. If I go to settings Bluetooth. No new device is found. The android phone can find a device ACR1255U-J1-000147, but cannot connect to it. If I connect it asks for pin, I enter 000000 and then it disconnects. If I enter any other pin, it does not accept it.
For the FloJack, it detects the device fine. But none of the apps will read any Tag.
The NFC Actions app will detect the device, but will not read any Tag.
The ACS Mobile app detects it and also tells me the flash data is corrupted
Firmware ACR35 V1.06
Battery Level 100%
Reader ID (I get hexadecimal string here)
Custom ID (blank)
The Audio Jack Demo app from the SDK detects it too, and gets the same device ID, but when I get the Custom ID it also tells me the flash data is corrupted.
How can I get my FloBLE detected by iOS and my FloJack to read Tags?
ThanksFebruary 25, 2016 at 8:20 pm #54625
Hi Hector, sorry for the confusion. I believe you downloaded the device drivers (which are on GitHub here) rather than the Flomio SDK – Basic (which is on Dropbox here). From our experience building apps with the low cost readers we sell, the drivers are too bare and force developers to write a lot of (often buggy) boilerplate code. The Flomio SDK is meant to add that necessary middleware and we guarantee it will work for your use case. We’ve battle tested and optimized it across several different applications with some unthinkable edge cases and we’re consistently pushing out new releases.
To get the FloJack and FloBLE Plus to start reading tags your have a couple options. First, you can try building an example app by following the steps in the README.md file inside the Flomio SDK bundle. We have a Test App very similar to this one on TestFlight that we can share with you if you just want to do a quick sanity check. Just send an email to info at flomio dot com with your Apple ID and you original order number.
The NFC Actions app only works with the FloJack v1 hardware (from Kickstarter 2012 project). The ACS Mobile app and the Audio Jack Demo are buggy and not very useful for most applications. The FloBLE Plus is not detected on iOS Bluetooth settings because it uses Bluetooth Smart “just works” pairing workflow. This means that unless the pairing request is initiated in code, it isn’t connectable like Bluetooth Classic. Android offers the dialog but errors out because of this. With the Flomio Test App the pairing dialog will appear and “0000” is the proper pairing code (this is persisted in host device so only need to be entered on first connection to reader).
Hope that get you going. If not, let us know where you’re getting hung up.
RichardFebruary 26, 2016 at 2:49 am #54628
Thank you Richard for your reply.
I have completely missed the sdk. You were right, I had downloaded the drivers and the sample apps.
I followed the instructions in the readme.md and tested the demo app. I still cannot make the FloJack read tags and after pairing the FloBLE I get an exception. Maybe are my Tags?? I will buy new ones to check. In the meantime, I have sent you a mail with my apple id, can I get the app to test?. In the console, I get the following
2016-02-26 08:39:16.969 Flomio[504:64262] Init FloBLE Plus
2016-02-26 08:39:17.237 Flomio[504:64262] bundle/var/mobile/Containers/Bundle/Application/96304710-21B9-4379-ACD1-33459BDF2B7B/Flomio.app/ScanSound.caf
2016-02-26 08:39:17.243 Flomio[504:64262] Updated settings for reader 0x15d61160
2016-02-26 08:39:17.253 Flomio[504:64262] App Activated
2016-02-26 08:39:17.254 Flomio[504:64262] Found existing reader 0x15d61160
2016-02-26 08:39:17.267 Flomio[504:64262] ::centralManagerDidUpdateState supports 5
And after I pair the floBLE I get this:
2016-02-26 08:40:05.276 Flomio[504:64262] ::discovered peripheral ACR1255U-J1-000147 <__NSConcreteUUID 0x15d84d10> 63850A4A-64C8-B0F9-1CEF-E94718C0F40A
2016-02-26 08:40:05.278 Flomio[504:64262] ::discovered peripheral ACR1255U-J1-000147 <__NSConcreteUUID 0x15d84d10> 63850A4A-64C8-B0F9-1CEF-E94718C0F40A
2016-02-26 08:40:05.415 Flomio[504:64262] Peripheral Connected
2016-02-26 08:40:05.798 Flomio[504:64262] Services Discovered
2016-02-26 08:40:05.812 Flomio[504:64262] Reader Detected
2016-02-26 08:40:06.669 Flomio[504:64262] Peripheral Successfully Attached
2016-02-26 08:40:06.671 Flomio[504:64262] -[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x15d8a4a0
2016-02-26 08:40:06.673 Flomio[504:64262] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘-[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x15d8a4a0’
*** First throw call stack:
(0x24cb810b 0x2445ee17 0x24cbd925 0x24cbb559 0x24bebc08 0xa830b 0xa6c13 0xa5f43 0x986b5 0xa7cd1 0x2994fd61 0x2994fdfd 0x2994ffd7 0x29955a8f 0x21cc97 0x21cc83 0x22176d 0x24c7b3fd 0x24c798f7 0x24bccbf9 0x24bcc9e5 0x25e18ac9 0x28e5cba1 0x8c859 0x2487b873)
libc++abi.dylib: terminating with uncaught exception of type NSExceptionFebruary 26, 2016 at 4:44 am #54630
Hi Hector, from reviewing the console output you included I don’t believe the issue is with your tags. It seems there’s a configuration problem with the SDK.. can you copy/paste what you put in you
Here’s the example app I built to test out the instructions from the README:
let me know if you see something different from what you have.
RichardFebruary 26, 2016 at 7:58 am #54632
You are right, it was not the TAGs, thanks. The Testflight app works nice I can read the Tag ID with the FloJack and the FloBle.
The sample app you sent me works well with FloJack. But I get an issue with FloBLE. The same unhandled exception.
2016-02-26 13:50:24.780 TestFlomioSDKv1.9[545:102223] Init FloBLE Plus
2016-02-26 13:50:25.077 TestFlomioSDKv1.9[545:102223] bundle/var/mobile/Containers/Bundle/Application/F7BF6617-97E2-4052-BB19-1CD64A1B8A3B/TestFlomioSDKv1.9.app/ScanSound.caf
2016-02-26 13:50:25.080 TestFlomioSDKv1.9[545:102223] Updated settings for reader 0x14e69f10
2016-02-26 13:50:25.094 TestFlomioSDKv1.9[545:102223] App Activated
2016-02-26 13:50:25.094 TestFlomioSDKv1.9[545:102223] Found existing reader 0x14e69f10
2016-02-26 13:50:25.114 TestFlomioSDKv1.9[545:102223] ::centralManagerDidUpdateState supports 5
2016-02-26 13:50:33.161 TestFlomioSDKv1.9[545:102223] ::discovered peripheral ACR1255U-J1-000147 <__NSConcreteUUID 0x14e64630> 63850A4A-64C8-B0F9-1CEF-E94718C0F40A
2016-02-26 13:50:33.167 TestFlomioSDKv1.9[545:102223] ::discovered peripheral ACR1255U-J1-000147 <__NSConcreteUUID 0x14e64630> 63850A4A-64C8-B0F9-1CEF-E94718C0F40A
2016-02-26 13:50:33.526 TestFlomioSDKv1.9[545:102223] Peripheral Connected
2016-02-26 13:50:33.621 TestFlomioSDKv1.9[545:102223] Services Discovered
2016-02-26 13:50:33.629 TestFlomioSDKv1.9[545:102223] Reader Detected
2016-02-26 13:50:33.741 TestFlomioSDKv1.9[545:102223] Peripheral Successfully Attached
2016-02-26 13:50:33.742 TestFlomioSDKv1.9[545:102223] -[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x14e66f70
2016-02-26 13:50:33.743 TestFlomioSDKv1.9[545:102223] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘-[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x14e66f70’
*** First throw call stack:
(0x24cb810b 0x2445ee17 0x24cbd925 0x24cbb559 0x24bebc08 0x8830b 0x86c13 0x85f43 0x786b5 0x87cd1 0x2994fd61 0x2994fdfd 0x2994ffd7 0x29955a8f 0x1fcc97 0x1fcc83 0x20176d 0x24c7b3fd 0x24c798f7 0x24bccbf9 0x24bcc9e5 0x25e18ac9 0x28e5cba1 0x6c855 0x2487b873)
libc++abi.dylib: terminating with uncaught exception of type NSException.
The only difference between the app I had and the example you sent me are>
sharedManager.operationState = kReadUUID; // instead of kReadDataBlocks
and in the readerAlert function, the precence of:
reader.delegate = self; // Set reader delagate once it’s clear reader’s connectFebruary 26, 2016 at 8:22 am #54633
Understood. I can confirm that this is an issue with the SDK v1.9 (build 10). The Test App is based off of SDK v1.9 (build 17). We will update the SDK bundle to latest FloBLE fixes and let you know on this thread once it’s done. Our estimated release date is Monday but latest by Tuesday end of day.
Sorry for the inconvenience.
RichardFebruary 26, 2016 at 8:29 am #54634
good to know that is not something I was doing wrong. I can rest and return to this issue once the new SDK bundle is released 🙂
Thank you very much
HectorMarch 9, 2016 at 7:46 am #54736
Is there any update on the SDK bundle that will work with the test app?
HectorMarch 9, 2016 at 9:35 pm #54742
Hi Hector, sorry for forgetting about you.. the updated the SDK bundle link so you can download the new v1.9 Build 17 version now:
RichardMarch 18, 2016 at 9:17 am #54817
sorry for the late reply. I have substituted the SDK, but I still get the same error with the test app you sent me for FloBLE
2016-03-18 14:15:12.738 TestFlomioSDKv1.9[774:183315] Init FloBLE Plus
2016-03-18 14:15:13.040 TestFlomioSDKv1.9[774:183315] Updated settings for reader 0x16d44eb0
2016-03-18 14:15:13.051 TestFlomioSDKv1.9[774:183315] App Activated
2016-03-18 14:15:13.052 TestFlomioSDKv1.9[774:183315] Found existing reader 0x16d44eb0
2016-03-18 14:15:13.065 TestFlomioSDKv1.9[774:183315] ::centralManagerDidUpdateState supports 5
2016-03-18 14:15:13.185 TestFlomioSDKv1.9[774:183315] ::discovered peripheral ACR1255U-J1-000147 <__NSConcreteUUID 0x16e41f60> 63850A4A-64C8-B0F9-1CEF-E94718C0F40A
2016-03-18 14:15:13.532 TestFlomioSDKv1.9[774:183315] Peripheral Connected
2016-03-18 14:15:13.635 TestFlomioSDKv1.9[774:183315] Services Discovered
2016-03-18 14:15:13.641 TestFlomioSDKv1.9[774:183315] Reader Detected
2016-03-18 14:15:13.754 TestFlomioSDKv1.9[774:183315] Peripheral Successfully Attached
2016-03-18 14:15:13.755 TestFlomioSDKv1.9[774:183315] -[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x16e39640
2016-03-18 14:15:13.756 TestFlomioSDKv1.9[774:183315] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘-[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x16e39640’
*** First throw call stack:
(0x228f810b 0x2209ee17 0x228fd925 0x228fb559 0x2282bc08 0x12432b 0x122c33 0x121f63 0x11459d 0x123cf1 0x2758fd61 0x2758fdfd 0x2758ffd7 0x27595a8f 0x298c97 0x298c83 0x29d76d 0x228bb3fd 0x228b98f7 0x2280cbf9 0x2280c9e5 0x23a58ac9 0x26a9cba1 0x1087bd 0x224bb873)
libc++abi.dylib: terminating with uncaught exception of type NSExceptionMarch 21, 2016 at 11:57 am #54836
Same error here (see separate post of Cordova/FloBLE).March 21, 2016 at 2:18 pm #54841
Still debugging this issue… should have a fix by later today.March 31, 2016 at 11:41 am #54950
Was this issue resolved? I’m currently facing the same problem and any update or information on a fix would be great.
Carl AndersonApril 5, 2016 at 10:20 am #55018
Still no news?April 5, 2016 at 10:36 am #55021
Hey guys, sorry for the delay but there is still no news. We are working to get our SDK2.0 release out to address this issue. Given it’s a major release we didn’t think it made sense to repair the v1.9 bug that is the root cause of the issue listed here. In tandem this is high season for conferences including Launch Festival, SXSW, Payments Summit, and RFID Journal Live, all of which Flomio was asked to attend so it’s presented some management challenges for us.
Of course, you are our priority and we will continue to hustle to get you the working SDK you paid for. I just wanted to provide some context so that you didn’t think we weren’t taking this issue seriously.
RichardApril 7, 2016 at 5:56 am #55043
We finally found that adding the linker flag -ObjC stopped that error from occurring.
Pinnacle Visualisation Ltd.April 7, 2016 at 11:19 am #55047
thank you Carl! that worked
Looking forward for the SDK 2.0 anyway 🙂
/HectorApril 7, 2016 at 2:38 pm #55048
@Carl, thanks for that find. We’ve literally been going nuts trying to find a bug in our threading code or something introduced by the latest iOS or Xcode updates. It’s disappointing we spent so much time on something so trivial but glad it’s resolved now. I have added this detail to the README.md instructions in the Flomio SDK bundle.
You must be logged in to reply to this topic.