November 16, 2016 at 11:24 am #57336
We really want to get to the bottom of this issue because it’s very strange. Could you send us a zip of your Xcode project so we can try see what is causing it?
Or you can add me to your Github repository, my username is scottire.
I understand any reservations you have, but this will definitely help us to go forward with this issue.
ScottNovember 16, 2016 at 7:19 pm #57344
Thanks for getting back to me. I am using the 2.1 SDK. The 2.1 SDK is working fine with the devices my company ordered for the second time. This issue only persisted in the first device. I was of the view that it had to do with a faulty device so Richard suggested I make a video of the faulty behaviour so he can forward it to the manufacturers. After looking at the generated logs, Richard reckoned that the logs showed some odd behaviour. I don’t think it’s to do with the SDK but the device itself as the same SDK and my code works fine with the rest of the devices.
The other request I had was that if it was possible to disable the sleep timeout in the SDK that I am using since I was having some issues with updating the firmware of the new devices from 1.16.00 to 1.16.03 in order to run SDK 2.2(which already has the sleep timeout disabled). Richard mentioned a step that wasn’t in the Upgrade guide so I’m going to give it a go and see if that solves the problem. I’,, get back to you guys on that.
As for sharing the Xcode project, unfortunately I’m not at liberty to disclose that information since it contains information that is the company’s sole proprietary.I’m more than happy to answer any questions and disclose information in regards to my usage of the SDK.November 16, 2016 at 9:15 pm #57347
Hi Malik, it’s unfortunate you can’t share the code you’re running. Perhaps you can create a sample project that mimics the same code structure that you’re using and exhibits the problem for us to assess on our side. Otherwise, we’ve reached the end of our rope on solving this issue for you. You’re welcome to use the ACS driver directly and code up your system from the ground up. You can find all our reader drivers on GitHub here.
RichardNovember 16, 2016 at 10:09 pm #57350
This is not an issue anymore and haven’t been for quite sometime. We’ve already resolved it. It was evident that the problem was with the device. The only reason I was trying to regenerate the issue is to make the video that you needed to send to the manufacturers. Other than that, the SDK 2.1 works fine on the new devices without any connectivity issues.
The actual issue I am dealing with at the moment is that of sleep timeout mentioned in this thread. I’d appreciate it if you can help me with that.
CheersNovember 16, 2016 at 10:59 pm #57352
Sent you feedback on the sleep timeout thread.
You must be logged in to reply to this topic.