Home › Forums › Ask the Flomies › FloJack BZR Reader Issues
Tagged: BZR, iOS, Tag may not be within range
-
AuthorPosts
-
April 13, 2017 at 6:05 pm #59308
I currently followed the tutorial here without any issues installing it:
http://docs.flomio.com/#configure-project-settingshowever, when launching and running my app from an iPad with iOS 9.3 installed, after i plug in the reader, every 6 seconds, I get a callback to the didReceiveReaderError with the error: ‘Reader Error’. looking at it more it is Error Domain=FlomioSDK Code=-17 “Reader Error.” UserInfo={NSLocalizedRecoverySuggestion=Tag may not be within range.
I haven’t even tried scanning a card, just with the reader sitting with the app open it is having this error every 6 seconds… Is this the normal behavior?
Here’s the print out of the logs
No tag found Apr 13 17:00:52 Error Domain=FlomioSDK Code=-17 "Reader Error." UserInfo={NSLocalizedRecoverySuggestion=Tag may not be within range., NSLocalizedDescription=Reader Error., NSLocalizedFailureReason=Could not establish communication with tag} Apr 13 17:00:52 Warning: Attempt to present <UIAlertController: 0x1247937e0> on <ViewController: 0x12461eca0> which is already presenting <UIAlertController: 0x12464a500> Apr 13 17:00:53 timer running on <NSThread: 0x12453ede0>{number = 93, name = (null)} thread Apr 13 17:00:53 sourceTimer Fired Apr 13 17:00:53 communication:1 CommCounter: 0 Apr 13 17:00:53 Polling for tags Apr 13 17:00:53 in checkForTags Apr 13 17:00:54 timer running on <NSThread: 0x12453ede0>{number = 93, name = (null)} thread Apr 13 17:00:54 sourceTimer Fired Apr 13 17:00:54 communication:1 CommCounter: 1 Apr 13 17:00:54 Polling for tags Apr 13 17:00:54 in checkForTags Apr 13 17:00:55 timer running on <NSThread: 0x12456b770>{number = 31, name = (null)} thread Apr 13 17:00:55 sourceTimer Fired Apr 13 17:00:55 communication:1 CommCounter: 2 Apr 13 17:00:55 Polling for tags Apr 13 17:00:55 in checkForTags Apr 13 17:00:56 flomio detected Apr 13 17:00:56 timer running on <NSThread: 0x12453ede0>{number = 93, name = (null)} thread Apr 13 17:00:56 sourceTimer Fired Apr 13 17:00:56 communication:1 CommCounter: 3 Apr 13 17:00:56 Polling for tags Apr 13 17:00:56 in checkForTags Apr 13 17:00:57 timer running on <NSThread: 0x12456b770>{number = 31, name = (null)} thread Apr 13 17:00:57 sourceTimer Fired Apr 13 17:00:57 communication:1 CommCounter: 1 Apr 13 17:00:57 Polling for tags Apr 13 17:00:57 in checkForTags Apr 13 17:00:58 timer running on <NSThread: 0x12453ede0>{number = 93, name = (null)} thread Apr 13 17:00:58 sourceTimer Fired Apr 13 17:00:58 communication:1 CommCounter: 2 Apr 13 17:00:58 Polling for tags Apr 13 17:00:58 in checkForTags Apr 13 17:00:59 timer running on <NSThread: 0x12456b770>{number = 31, name = (null)} thread Apr 13 17:00:59 sourceTimer Fired Apr 13 17:00:59 communication:1 CommCounter: 3 Apr 13 17:00:59 Polling for tags Apr 13 17:00:59 in checkForTags Apr 13 17:00:59 in FTNFCDidComplete Apr 13 17:00:59 Stat Response time = 0.062339 Apr 13 17:00:59 in FT_FUNCTION_NUM_OPEN_CARD Apr 13 17:00:59 in getConnectResult Apr 13 17:00:59 No tag found Apr 13 17:00:59 Error Domain=FlomioSDK Code=-17 "Reader Error." UserInfo={NSLocalizedRecoverySuggestion=Tag may not be within range., NSLocalizedDescription=Reader Error., NSLocalizedFailureReason=Could not establish communication with tag} Apr 13 17:00:59 Warning: Attempt to present <UIAlertController: 0x124586d10> on <ViewController: 0x12461eca0> which is already presenting <UIAlertController: 0x12464a500> Apr 13 17:01:00 timer running on <NSThread: 0x12453ede0>{number = 93, name = (null)} thread Apr 13 17:01:00 sourceTimer Fired
- This topic was modified 7 years, 8 months ago by Richard.
April 14, 2017 at 9:31 am #59315I guess to add to this, I just want to make sure this is working correct. What I had assumed was, I put an alert when an error was sent to the didReceiveReaderError method to show the user, but i’m thinking that I shouldn’t do that, and it’s simply displaying every 6 seconds that a card couldn’t be found?
April 14, 2017 at 10:10 am #59316Hi Jeff,
You’re right, that’s more for debugging purposes rather than showing users. That error occurs specifically from the BZR and it’s to do with the fact that we constantly poll for tags.Kind regards,
ScottApril 14, 2017 at 10:15 am #59317Thank you, I’m currently trying to get the battery level, however the BZR constantly remains in a scanning state? I figured it would be connected since it’s plugged into the audio jack. Any thoughts why it’s not changing statuses?
- (void)didUpdateConnectedDevices:(NSArray *)connectedDevices { NSLog(@"flomio status changed"); for (FmDevice *device in connectedDevices) { switch (device.communicationStatus) { case kScanning: NSLog(@"Scanning"); break; case kConnected: NSLog(@"Connected"); NSLog(@"Battery Level: %lu", (unsigned long)device.batteryLevel); break; case kDisconnected: NSLog(@"Disconnected"); break; default: break; } }
April 15, 2017 at 6:00 am #59335Hi Jeff,
Unfortunately there is no battery level reading on the BZR.
Scott
April 15, 2017 at 6:02 am #59336The scanning state will just show a change when the reader is disconnected. It is scanning for tags, or disconnected.
Scott
-
AuthorPosts
You must be logged in to reply to this topic.