deviceEnabled: (null) error with reader startScan

[JackParticipant]

I am utilizing the newest version (v1.9) of your Flomio SDK to communicate to the FloJack device and I am getting a deviceEnabled: (null) error when the [readerManager.reader startScan] method is being called. A valid reader and reader manager seems to be created and returns a valid memory address. I am assuming that maybe a new API method needs to be called or the API ordering has changed for starting a scan. A FloJack sample app with the latest version of your SDK would be helpful. Please advise.

[JimMember]

Hi Jack, This issue is currently being addressed and will be corrected in the next release of the SDK v1.9. This fix will not affect the API.

Jim

• This reply was modified 8 years, 9 months ago by  Jim.

[BorisMember]

Hello Jack,

This is the link to the updated README.md file with detailed instructions on how to build a Sample App with the new delegates.

https://www.dropbox.com/s/y5qloadwievtjp4/FlomioSDK.zip?dl=0

Please note that the most of the UI interaction has been removed as it’s particular to each implementation. Also, this version doesn’t include the fixes from Jim on the resetting of the reader after AirWatch reboot. He should have that for you tomorrow.

Boris

• This reply was modified 8 years, 9 months ago by  Boris.

[JimMember]

Hi Jack,

We just released v1.9 build 6 for testing on TestFlight. Please launch TestFlight and install v1.9(6). Here are the tests we would like performed and feedback on:

1. Check that you are able to install this version (no certificate errors)

2. Launch app, select FloJack, place a tag on the reader and leave it there, observe continuous scans, let the battery die(green light goes out) then reboot the iPad, launch app, select FloJack, !!!plug in Flojack charger!!!, and validate you are able to scan cards. Do not remove the reader during this test!!

3. Connectivity testing, Short test: remove the reader and immediately plug it back in. 5 Second Test: Remove the reader for 5 seconds and plug it back in. Sleep Test: Remove the reader until the green light goes out and then plug it back in.

Verify that the reader recovers and starts scanning indicated by a green communication light and a response to a tap. IF the communication light remains red for more than 10 seconds, select settings and cycle the Enable/Disable button. press Done and verify that the communications light turns green within 10 seconds. If not repeat the Enable/Disable cycle. Run all three tests and verify that readers are restored and can scan tags.

Note: When the FloJack is first selected there is a period of time of about 6 seconds where the communication indicator will be red, indicating there is no communication. This is a normal function of the reader. There is also a period of about 2 seconds during and after scanning a card when there is no communications, again a normal function of the reader.

• This reply was modified 8 years, 9 months ago by  Jim.

[RichardKeymaster]

Hi Jack, the new Flomio SDK v1.9 (Build 6) is now available. Download it from the same link as before:

https://www.dropbox.com/s/y5qloadwievtjp4/FlomioSDK.zip?dl=0

This build corrects the following issues:

– Read Data Blocks now working as in v1.6. API did not change.
– Auto-reestablishment of communication between Host device and Reader

Note 1: The auto-reestablishment algorithm can make the initialization of the reader slower than before. This is because there’s only one line of communication to the reader and in order to check all the problematic situations we need to momentarily halt that path way.

Note 2: There is one scenario that the auto-reestablishment algorithm cannot recover from. This is when the audio connector on the iPad is locked in Headset mode. This will exhibit itself and no Connect/Disconnect images overlaid on the screen while plugging and unplugging the reader. This doesn’t happen often but when it does we are forced to power cycle the iPad to regain notifications from the audio connector. This scenarios where this occur are due to faulty audio jack connections that create very fast Connect/Disconnect events. We don’t expect this issue to happen in the field with robust installation hardware holding Host to Reader connections in place.

Note 3: Scan sound from the iPad can cause momentary isConnected delegate method calls. The reason is because routing audio from microphone to speaker ceases the communication between the Host and Reader. So you may get seemingly false isConnected notifications when in fact the Reader is operating normally.

[RichardKeymaster]

I shot this video to help understand the notifications and UI controls on the Flomio Test application to help with troubleshooting issues, hardware or software.

thanks,
Richard

[Author]

Posts