Device Connection Issues

[SweetParticipant]

Hello. We are currently having issues connecting reliably to our FloBlePlus devices. Once the device is connected we are able to start and stop the reader quite reliably, but we are testing for the situation where the connection is dropped by turning off bluetooth on the device, or the device is turned off and on with the switch, and reconnecting to the device reliably. The test case I’ve used the most is simply turning the device on and off.

We are using the following configuration settings:

defaultConfiguration.deviceType = kFloBlePlus;
defaultConfiguration.scanSound = @YES;
defaultConfiguration.scanPeriod = @1000;
defaultConfiguration.powerOperation = kAutoPollingControl;
defaultConfiguration.transmitPower = kHighPower;
defaultConfiguration.allowMultiConnect = @NO;
defaultConfiguration.specificDeviceUuid = deviceId;

When I turn the device off, wait 10 seconds, and turn it back on, we see one of the two following sequence of events in our logs:

Flomio: didChangeStatus: communicationStatus 2
Flomio: didChangeStatus: communicationStatus 2
Flomio: didGetLicenseInfo

OR we see:

Flomio: didChangeStatus: communicationStatus 2
Flomio: didChangeStatus: communicationStatus 2
Flomio: didGetLicenseInfo
Flomio: didChangeStatus: communicationStatus 0

So as you can see, 50% of the time we see the two disconnected communicationStatus lines and then the license info, and 50% of the time we see the same but followed with a communicationStatus of 0 indicating that the device is connected and scanning. If the device does not connect it seems the only thing we can do is turn it off and on and try again.

Do you have any advice as to what we could be doing wrong here?

• This topic was modified 6 years, 6 months ago by  Sweet.
• This topic was modified 6 years, 6 months ago by  Sweet.

[RichardKeymaster]

Hi Sweet, we haven’t seen this behavior lately. What host device and OS version are you using for your testing??

best,
Richard

[SweetParticipant]

Hi Richard. Thanks for the reply. We are using iPads running the latest version of iOS 11. We have worked around the issue by forcing a re-initialize event which on iOS 11 is OK, but on iOS 10 doing that seemed to brick the reader for a while.

[JamesParticipant]

Following…

[ScottKeymaster]

Hi,

What version of the Flomio SDK are you using and what is the firmware version of your FloBLE Plus? I am having difficulty replicating the issue.

A temporary solution you could try, but should not be needed, is to call startReaders when the didGetLicenseInfo delegate is called.

Scott

[SweetParticipant]

Firmware: 3.00.05
SDK Version: 3.0.1

[ScottKeymaster]

Hi,

Please try the latest 3.0.3-beta SDK from
3.0.3-beta
or by using the 3.0.3-beta tag in your Cocoapods podfile.

This should solve the issue but please let me know if the issue persists for you.

Scott

[SweetParticipant]

That definitely seems to be more reliable! I am not watching the logs like I was before but on our production app it does seem to connect more reliably than before.

We are curious, what exactly was changed in your SDK to improve this?

[SweetParticipant]

Also, do you know when 3.0.3 will be out of beta?

[ScottKeymaster]

Hi,

There was an issue with a thread lock that would cause some escape commands (which configure the reader) to not fire.

It should be out of beta within the month.

Scott

[JeremyParticipant]

Hi Scott,

We’ve been testing 3.0.3 beta for the last few days, while it appeared to be more stable for the first bit, it appears there is still some oddness with the status changes.

Currently we are testing and on connection, we are I’m getting a status 1 or 0, then a 2, followed by the license, check followed by another 2? Those status changes are happening in rapid succession almost as if those callbacks are firing before the previous is processed.

Any other thoughts? Thanks!

[ScottKeymaster]

Hi,

Sorry to hear you are having more issues with reconnecting.

How often is this happening? The steps to reproduce are the same as above, turning it off and back on again after 10 seconds?

Scott

[JeremyParticipant]

Fairly regularly, I walked in this morning, cycled the device (off and back on), then typed the serial number in our app and clicked connect. I get a “disconnected” status, after I hit connect a few more times, it sticks and is now connected properly.

[ScottKeymaster]

What code are you calling when you click connect?
I would like to try reproduce this or see your code so that I can suggest a different way to avoid this error.

[JeremyParticipant]

At Connect time, our only code that we’re calling is this:

  FmConfiguration *defaultConfiguration = [[FmConfiguration alloc] init];
  defaultConfiguration.deviceType = kFloBlePlus;
  defaultConfiguration.scanSound = @YES;
  defaultConfiguration.scanPeriod = @1000;
  defaultConfiguration.powerOperation = kAutoPollingControl;
  defaultConfiguration.transmitPower = kHighPower;
  defaultConfiguration.allowMultiConnect = @NO;
  defaultConfiguration.specificDeviceUid = serialNumber;
  self.flomioSDK = [[FmSessionManager flomioSDK] initWithConfiguration:defaultConfiguration];

[ScottKeymaster]

Hi Jeremy,

One suggestion that may remove your issues:
You should use the setConfiguration method rather than calling initWithConfiguration on the FmSessionManager object. Reinitializing the flomioSDK can cause state issues.

Let me know if this helps.

Scott

• This reply was modified 6 years, 5 months ago by  Scott.

[ScottKeymaster]

Hi Jeremy,

You should try the latest beta (3.0.3-beta2) to see if it helps with your connectivity issues.

Scott

• This reply was modified 6 years, 5 months ago by  Scott.

[Author]

Posts