Why should I setup the Android device for delivery of scanned barcode to Glink using device specific setting?
Glink can either receive scanned barcode data as simulated keyboard input (Keyboard Wedge) or receive scanner data through device specific configuration. In most cases the device specific configuration is using Data Intents.
​
Most mobile computers are setup to use Keyboard Wedge by default. It is however recommended to use device specific configuration if available, as this gives better performance and more control of how scanned data is handled. In this case Glink can separate scanned data from keyboard data and the Scan options below is in effect for the scanned data input.
​
Glink supports device specific scanning on mobile computers from the following manufacturers: Zebra, Honeywell, Datalogic, AML, Point Mobile, M3 Mobile, Denso, Urovo, Seuic, Unitech and CipherLAB.
​
When device specific configuration is selected, scanned data is also displayed on the status line. If scanned data is received, but not displayed on the status line, you should check your settings, because this means that the scanned data is still received as keyboard input.
See the Glink User Guide on how to setup device specific scanning.
​
Scan options
Please note that most scanner software can be configured with options like the ones below. Make sure that these options either is set either in Glink or in the Device Scanner settings itself. Check the device's Scanner documentation.
​
Action after scan
None Do no action after scanning
Tab Do Tab after scanning
Enter Do Enter after scanning
FldExit Do Field Exit after scanning (5250 emulation mode only)
Remove char(s) at start
Removes one or more characters at the beginning of the barcode.
Remove char(s) at end
Removes one or more characters at the end of the barcode.
Add text before
Add text before the barcode.
Add text after
Add text after the barcode (the Action after scan will be added after this text).
Use keyboard mapping
Check this option if keyboard mapping should apply for scanned data. For example, if colon (:) is mapped to the Tab function and the semicolon (;) is mapped to the Enter function, a scanned barcode text 1234:5678; will be interpreted as key input 1234Tab5678Enter
​
Show on status line
Display the scanned data as a status message at the bottom of the screen as well.
​
Keyboard Wedge A
The Keyboard Wedge Advanced mode requires that the device specific settings for the scanner (not Glink) is set up with hex 0E (SO) as prefix character and hex 0F (SI) as suffix character. Some devices let you select SO (shift out) as the prefix and SI (shift in) as the suffix, others let you just type the hex value. For others it is not possible to specify these low ascii characters or low ascii characters is stripped off. In this case, specify the prefix as ^$0E and the suffix as ^$0F.
​
If the prefix and the suffix is not set up properly, the default Keyboard Wedge mode will be used instead.
When the Keyboard Wedge Advanced mode is selected, the options described under More options in Glink are available.
To check that Keyboard Wedge Advanced is configured correctly, the scanned data should be shown on the status line at the bottom of the Glink screen.
​
