AutoWedge

AutoWedge is an ‘automatic’ mode for configuring Scanner-as-Wedge. This feature was added to clients starting with v11.0 build 119 and newer. This allows the client to ‘estimate’ when scan transactions are coming through the keyboard interface based on the speed of the input. This feature has some limitations, since false positives and single character scans cannot be captured by the program logic. This feature is intended as a ‘common use’ solution, and has limited adjustments other than timing and an enabled/disable option. If more precise control is required, the scan delimiters discussed above are the best available solution.

Enabling AutoWedge is done by using a combination of two StayLinked client settings;

1. The first is the scanner as wedge option, which must be set to enabled.
2. The second required setting is to set the wedge delimiter to 0.

A third available setting can adjust the timing between characters.

Scanner as Wedge Mode = Enabled

None of the configuration choices for Scanner-As-Wedge will operate unless the setting group is enabled. Once enabled, the client will not use any standard communication with the scan engine and features that enable/disable the scanner will not operate.

Tethered Scan Delimiter = 0 Setting the delimiter to a 0 is the key to enabling AutoWedge. Any other delimiter will act as a standard delimiter to contain barcode information.

Wedge Character Gap Time = 10
(10 is recommended only for use with this feature)
This setting controls the number of milliseconds between input that will be grouped as a scan by the client. The default setting is 100 milliseconds, which may be long enough to capture keys that are manually depressed and automatically repeat. When a character comes across the keyboard input channel, the client will wait the listed delay for additional characters. If more than one character is seen within this time limit, they will be packaged, transmitted and processed by the server as a scan. This can include scan suffix or barcode rules that have been configured at the StayLinked Server.