I have a customer who needs to scan several hundred items at a single delivery site with an imager. The problem is that after a few scans the device seems to need to "catch up" and remains locked with the hour glass on the screen until it can process the scans. They can then resume scanning until the buffer once again gets full and locks the device while it processes it. The customer is using the scan API in the SDK and not data wedge
Intermec CN3 does not display this behavior and seems to allow continuous scanning
Any Suggestions??
Intermec CN3 does not display this behavior and seems to allow continuous scanning
Any Suggestions??
Points: 0
You voted ‘up’
Thanks
Points: 1
You voted ‘up’
it helps. It may help if the developer used bigger buffers and wrote
to the suggested flash.
https://devcentral.symbol.com/shwmessage.aspx?forumid=52&messageid=703
Points: 0
You voted ‘up’
Points: 0
You voted ‘up’
I have often seen this behaviour (eternal hourglass) on some customer/3rd-party applications... and -as usual- they complained about our stuff.
Eventually -in most cases- it was because of wrong non-optimised whatsoever processing.
Sometimes it was because of slow memory access... but this is history now
Points: 1
You voted ‘up’
If you'd like some formal assistance with this, contact Luke Petrozza (my Manager). Our group is part of ECRT and is chartered with performing Applications Support for Customers. One of the tasks that we can help with is to look at the customer's code and suggest improvements.
If it turns out to be a scanner problem, we'll create the SPR and help track it.
Points: 0
You voted ‘up’
Is the scanner opened/closed (or if managed a new instance created) each time a scan is processed?
The symptoms really sound like the CF garabage collector, but as Dave points out without additional information is difficult to diagonse.
Points: 0
You voted ‘up’
Points: 0
You voted ‘up’
Is this a .NET application?
As some one on this thread has mentioned, you will have to handle this situation with multiple threads. If this is a .NET application, I may be able provide you a sample application that shows you how to accomplish this.
Points: 1
You voted ‘up’
Mike Holman is working to have a con call with ECRT and the ISV..
thanks for everyones feedback
Points: 0
You voted ‘up’
Intermec CN3 does work fine.
Obviously not using the same application.
Intermec can either use their APIs, either use an "embedded" factory-installed "datawedge" of their own.
Which way are they using the imager on CN3?
On the other hand, does this lock-up happen after a few scans despite the rate of readings (i.e, how fast they read barcodes)?
Do they initialise the imager (including SCAN_AllocateBuffer), then loop on scanning all the barcodes, and when done, close the imager (so SCAN_DeallocateBuffer)?
Or do they instead init->read one->close for every barcode?
Points: 0
You voted ‘up’
Yes--They are running the same application--obviously with a modified API for Intermec
_____________________________________________________________________
Intermec can either use their APIs, either use an "embedded" factory-installed "datawedge" of their own.
Which way are they using the imager on CN3?---
API's
_____________________________________________________
On the other hand, does this lock-up happen after a few scans despite the rate of readings (i.e, how fast they read barcodes)?--
It is related to the rate of readings
_______________________________________________________
Do they initialise the imager (including SCAN_AllocateBuffer), then loop on scanning all the barcodes, and when done, close the imager (so SCAN_DeallocateBuffer)?
The imager is initalized at the beginning of the job and closed after all scanning is done
__________________________________________________________________
Or do they instead init->read one->close for every barcode?Obviously not using the same application.
No
__________________________________________________________________
Intermec can either use their APIs, either use an "embedded" factory-installed "datawedge" of their own.
Which way are they using the imager on CN3?
On the other hand, does this lock-up happen after a few scans despite the rate of readings (i.e, how fast they read barcodes)?
Do they initialise the imager (including SCAN_AllocateBuffer), then loop on scanning all the barcodes, and when done, close the imager (so SCAN_DeallocateBuffer)?
Or do they instead init->read one->close for every barcode?
Points: 0
You voted ‘up’
Log in to post comments