|
|
GPRS WIFI Error
Posted: 25 Aug 09 11:22 AM
|
Good morning. Every so often we get this message while trying to upload information to the ITSCriptnet server. We are connected OK via GPRS with a couple bars every time this happens, and not connected via USB. If we choose NO, we are returned to the application. If we choose YES, it attempts to connect, then we get "SendCollectData Failed! Check Omni Server For .ITC files.", and then "Unable to establish connectivity and transmit final data".
Wi-Fi Status Is: 0 | GPRS Status Is: 0
Are You Connected Via USB Cable?
NO YES
Any help would be appreciated. |
|
|
|
Re: GPRS WIFI Error
Posted: 12 Oct 09 10:52 PM
|
A clarification for others reading these forum posts.
These messages are not ITScripNet generated. They are generated by me (the programmer) in the particular program we are running at my organization.
These messages are my attempt to provide some information to users and/or our Help Desk personnel related to what I could detect using version 2.4 along with the Intermec CN3/Motorola client. ITScriptNet has since provided considerable work enhancing (especially) the Intermec CN3 client in version 3.x, subsequently allowing me to program more accurate connectivity detection, thus providing more accurate messaging.
Mark Robinson |
|
|
John Lathem
Posts: 76
|
 |
|
Re: GPRS WIFI Error
Posted: 14 Oct 09 8:22 AM
|
When this happens, does it fail immediately, or after a few seconds?
We've found that extending the timeouts on the OMNI Server and on the Device helps with the reliability of GPRS connections. If you haven't already done that, I'd suggest extending them to about 10 seconds instead of the default 5 seconds. It seems that long packet delays are normal over the GPRS networks. Let me know if that helps, or if you've already tried it. |
|
|
|
Re: GPRS WIFI Error
Posted: 14 Oct 09 1:47 PM
|
Yes, we have tried several settings.
The bottom line is GPRS connections can drop at any moment, even though indicators on the device show bars, etc. Folks understand that when they are talking on their phone and it drops, but it is somehow a greater irritation and more perplexing when running a piece of software.
I added some messaging to attempt to tell users what I could about the various modes of connectivity. Even though the Intermec CN3 client under 2.4 could not return much with accuracy beyond IsAssociated, I stuck them in there anyway in the hopes that someday they might work properly. With version 3.1, they do (with just a little re-work).
Mark Robinson |
|
|
|
|