Home › Forums › Ask the Flomies › Register devices
Tagged: Flashing firmware, Flomio SDK
-
AuthorPosts
-
November 16, 2017 at 11:13 am #61622
Hello,
Can you register the following 5 devices:
Model: ACR1255
P/N : ACR1255U-J1
Readers : FLO17805
Order : 61336S/N : RR431-000029
S/N : RR431-000031
S/N : RR431-000014
S/N : RR431-000045
S/N : RR431-000033November 16, 2017 at 6:12 pm #61628Hi Anton, all those readers were registered prior to shipping them to you. What issues are you encountering that makes you believe that the readers are not registered? Make sure you’re using the latest released Flomio SDK v2.3.1.
best,
RichardNovember 21, 2017 at 8:11 am #61663Hello,
We previously purchased one ACR1255 reader and build an app using the 2.2 sdk. That app and reader is working fine. The five new readers we purchased were supposed to be used with the same app on other devices. We’re able to connect the new readers to the app through bluetooth, but we’re not able to scan any tags. I can see that the reader that’s working has the firmware version 1.16.03 while the new readers have 1.17.00.
Is it possible to downgrade the firmware of the new readers?
//Anton
November 21, 2017 at 9:28 am #61664Hi Anton, the issue is that the new firmware only works with the latest SDK release v2.3.1. So you can either upgrade your app to use the latest SDK or downgrade the firmware on the readers you have to v1.16.03. You can follow these instructions for flashing new firmware into the readers.
best,
RichardNovember 21, 2017 at 10:06 am #61666Okey, thank you for the information.
A question, will SDK version 2.2 continue to work in the future.
We read somewhere that the licensing-auhentication server will stop working for 2.2.//Anton
November 21, 2017 at 10:20 am #61667We will continue to support v2.2 through to the end of the year but then expect to turn off the old license server since the new one is much more effective. Switching to the new v2.3.1 SDK is a direct swap so we don’t expect your app functionality to be impacted. Sorry for the inconvenience.
best,
RichardNovember 21, 2017 at 10:29 am #61668Okey. We have a pro sdk license and I expect that we wont be affected by the old licensing server shuting down, since the pro sdk dont auhenticates against a server. Correct?
//Anton
November 21, 2017 at 10:35 am #61669Yes, that is correct. We can send you the v2.3.1 of the Pro SDK if you’d like as you’re within your 1 year of updates and support. Actually the same download link we originally sent you for the Pro SDK will have the new version. It’s preferable that you run the latest rather than downgrade your reader firmware.
best,
RichardNovember 28, 2017 at 2:47 am #61701We’ve decided to upgrade the sdk in our app.
Can you please send the 2.3.1 pro sdk to us?//Anton
November 30, 2017 at 2:38 am #61720Hello,
Would just like to remind you to send us the pro sdk if possible.//Anton
November 30, 2017 at 7:07 am #61721Hi Anton, sorry for the delay. I just sent you an email with your latest download link for the Pro SDK.
best,
RichardNovember 30, 2017 at 9:19 am #61723I got the link and the pro sdk is working.
Thank you!//Anton
-
AuthorPosts
You must be logged in to reply to this topic.