Main Tab
Start > Settings > Control Panel > Scanner > Main tabParameter | Function | |
|
| |
Port | Default: Port 1 is disabled.Port 2 is enabled. | |
Default: Port 1 COM3 is enabled. Port 2 is disabled. | ||
| ||
|
| |
Power Port 1 while | When Power Port 1 while asleep is checked, whichever serial port is enabled as Port 1 will remain | |
powered while the device is in Suspend, at the cost of reduced battery life. This allows a tethered | ||
asleep | ||
scanner to wake the device by pressing the trigger on the tethered scanner. | ||
| ||
|
| |
| Default: Enabled. | |
| If “Send Key Messages (WEDGE)” is checked, the Scanner Driver is in “Key Message” (also known | |
| as “character”) mode which sends the bar codes to the application with the focus as keystrokes. All | |
| data scanned is converted to keystrokes and sent to the active window. | |
Send Key Messages | If “Send Key Messages (WEDGE)” is not checked, the Scanner Driver is in “Block” mode which | |
buffers the data that can be read by an application from the WDG: device through the OS or APIs. | ||
(WEDGE) | ||
Note that this latter method is significantly faster than using “Wedge”. | ||
| ||
| Even if Send Key Messages is enabled (“key mode”), the data is still available using the scanner | |
| APIs (“block mode”). If two or more applications are reading the data in Block mode, ClearBuf must | |
| be set to Off so data is not erased when read. Please refer to the CE API Programming Guide for | |
| details on scanner APIs. | |
|
| |
| Default: Enabled. | |
| Functionality of the internal scanner driver engine includes audible tones on good scan (at the | |
| maximum db supported by the speaker) and failed scan. | |
Enable Internal | Disable this parameter when good scan/bad scan sounds are to be handled by alternate means e.g. | |
Scanner Sound | ||
| Rejected bar codes generate a bad scan beep. In some cases, the receipt of data from the scanner | |
| triggers a good scan beep from an external scanner, and then the rejection of scanned bar code data | |
| by the processing causes a bad scan beep from the MX3Plus on the same data. | |
|
|