At 10:12 AM 12/17/99 -0800, you wrote:
>
>Jason,
>
>It's been regularly reproducable, but absolutely inconsistent, if that helps.
>
>The workaround has been to leave the decoder on (and just disable the
>scanning) for the duration of the application. I got this response from a
>high-level Symbol developer:
>
>"For issue #1 I would leave the scanner on. The documentation is being
>ultra-conservative. When we predict our 10+ hour battery life we assume
>the scanner is left powered on at all times. If your unit is going to be
>place back in the charger once a day for a full charge then you should have
>no problem. Please note, it will take some time for the ScanCmdOpenDecoder
>command to execute. 20-30 seconds seems unreasonable, so we will look into
>why this is happening."
>
Hi Ben,
Did you ever get an update from Symbol as to why this is happening?
