Scanner

Configure a serial barcode scanner for scan-based data entry and scan-triggered actions

The Scanner page connects a serial barcode scanner to scan-enabled data entry fields. Scanned values can fill @SCASK values, flow into folder names, file names, and metadata, and optionally trigger a selected action. For the full ASK token syntax and data-entry workflow, open the ASK help page.

What it does

  • Opens a configured COM port and listens for scan text.
  • Removes the required scan wrapper from each scan.
  • Sends the cleaned value to the shared ask data-entry system.
  • Places the value into the current scan field or the focused scan field.
  • Optionally triggers a selected action when the scan matches Trigger with.
  • Shows connection, scan, and error messages in the Scanner page log.

Quick setup

  1. Use a USB wired scanner when possible.
  2. Put the scanner in USB serial mode, not keyboard wedge mode.
  3. Install the scanner driver if Windows does not already show the scanner as a COM port.
  4. Check Windows Device Manager. The scanner should appear under Ports as a COM device, such as COM3.
  5. Select that COM port on the Scanner page.
  6. Match the baud rate, data bits, parity, stop bits, and flow control to the scanner manual.
  7. Program the scanner to send ! before each scan and @ after each scan.
  8. Click Connect when the settings are correct.

Serial settings

  • Match the baud rate, data bits, parity, stop bits, and flow control to the scanner manual.
  • Do not guess the COM port number. Use the port shown in Device Manager.
  • If no COM port appears, install the scanner vendor driver or USB serial driver, then unplug and reconnect the scanner.
  • If the scanner was moved to another USB port, recheck the COM port because Windows may assign a new number.
  • If another app or terminal tool has the COM port open, close it before connecting from the Scanner page.

Required scan wrapper

  • Use ! as the prefix and @ as the suffix in the current scanner setup.
  • Example: !12345678@ becomes 12345678 after the wrapper is removed.
  • Without markers, quick repeated scans can blend together into one longer string.

Use scan fields

  • Use @SCASK tokens when a value should be filled by the scanner.
  • Use @ASK tokens for normal data-entry values.
  • When no scan field has focus, each scan goes to the current scan target and then advances to the next scan target.
  • When a scan field has focus, the scan goes into that focused field.
  • Scanned values can be used anywhere the ask value is used, including folders, file names, and metadata.
  • If a scanner-capable ASK field ends its descriptor with !, scanning into that field submits the configured app action after required ASK fields are valid.

Trigger barcode actions

  • Trigger actions are optional. Leave Trigger with empty if you only want scan-to-field behavior.
  • Set Trigger with to a specific barcode value only when you want a scan to fire an action.
  • Select the Triggered action that should run when that value is scanned.
  • A matching scan can fire the selected action, such as image capture.

Example barcode-only workflow:

  1. Scan the barcode value that should fill @SCASK fields.
  2. Scan the trigger barcode.
  3. The app fires the selected Triggered action.

This supports hands-off operation where barcode scans can both fill values and trigger capture.

ASK submit fields

ASK can also submit the app's configured ASK action from the data-entry form itself. Add ! at the end of an ASK descriptor when completing that field should submit the action.

For example:

@SCASK1#*1:ID#\@ASK1#2:City!#

This makes ID required and first in the entry order, then submits when City is completed. Required ASK fields must be filled before submit runs. The scanner setup ! prefix is separate from the ASK descriptor ! marker.

Why serial mode

  • Serial mode sends the scan directly into the correct data entry box.
  • You do not need to click into the box first the way you would with keyboard wedge mode.
  • This is the most reliable mode when you want fewer input mistakes.

Hardware guidance

  • A USB wired barcode scanner is recommended.
  • Many common scanners, such as the Zebra LS2208, can expose a COM port through a driver.
  • Wireless scanners can drop input when Bluetooth or Wi-Fi is busy, especially in crowded venues.
  • 1D codes are the safest choice because they resolve to a single text value.
  • 2D and 3D codes can carry more complex data structures, so they are not recommended for this flow.
  • Most scanner-supported symbologies can be used as long as the scanner can read them.

Test with a simple barcode first, such as an 8 digit 1D code, before using longer labels or complex symbologies.

Scan result

  • The cleaned scan value is sent to the shared ask system.
  • @SCASK tokens receive scanned values.
  • @ASK and @SCASK values can be used in paths, file names, and metadata.
  • Matching Trigger with values can fire the selected triggered action, such as capture.
  • The Scanner page log shows connection and scan status.

Troubleshooting

  • If the scanner does not connect, confirm the COM port and driver in Windows Device Manager.
  • If scans do not appear, confirm the scanner is in serial mode instead of keyboard wedge mode.
  • If scan values are missing or combined, confirm the scanner sends ! before each scan and @ after each scan.
  • If the wrong characters appear, confirm baud rate, data bits, parity, stop bits, and flow control.
  • If scans are garbled, try a lower baud rate from the scanner manual and confirm that data bits and parity still match.
  • If the scan goes to the wrong field, click the intended scan field or review the order of @SCASK entries.
  • If the trigger action does not fire, confirm the scanned trigger barcode exactly matches Trigger with.
  • If the wrong action fires, confirm Triggered action selection on the Scanner page.