Table of Contents

KEYENCE BT-A700G – Scanner Parameters

Purpose

This guide describes the required scanner settings on the KEYENCE BT-A700G so that COBI.wms can correctly recognize and process barcodes (e.g., EAN/UPC, Code128, EAN128/GS1). Key points:

Step-by-step instructions

1) Open Android Settings (Fig. 1)

  1. Open the app overview (home screen / list of all apps).
  2. Tap Settings.

2) Open Scanner Settings (Fig. 2)

  1. In Android Settings, select Scanner (scan parameters, code settings).

3) Open Data Formatting (Fig. 3)

  1. In the Scanner menu, scroll to the Data section.
  2. Open Data formatting.

4) Enable “AIM ID Prefix” (Fig. 4)

  1. Enable AIM ID Prefix (check the box).

Why this matters:

The AIM ID adds an identifier to the scanned data so COBI.wms can reliably determine the barcode type (e.g., GS1/EAN128 vs. Code128). This is especially important for GS1 logic (AI structures).

5) Go back and open “Data Output” (Fig. 5)

  1. Go one step back to the Scanner menu.
  2. Open Data output.

6) Set Transmission Type to “KeyEvent” (Fig. 6)

  1. Under Transmission type, set the value to KeyEvent.

Short note: “KeyEvent” sends scanned data as keyboard/event input (keystrokes), improving compatibility and handling of special characters/structures in input fields.

7) Enable Intent and configure Broadcast (Fig. 7)

  1. In Data output, tap Intent.
  2. Enable Intent (check the box).
  3. Under Action, enter this value exactly:

4. Set the Transmission type in the Intent section to:

Why this matters: COBI.wms expects scan data via a defined Intent action. Using Broadcast ensures the scan Intent is delivered to the app so the correct internal logic is triggered.

8) Set Intent extras: Code type / Raw data / Data (Fig. 8)

Scroll further down in the Intent settings and set these values manually:

These extras ensure COBI.wms receives the information in the expected structure and can process the barcode logic correctly (including type/source/payload).

Final step: Restart the app

  1. Fully close COBI.wms (remove it from the recent apps list / swipe it away).
  2. Open COBI.wms again.
  3. Start scanning and validate the result.

Troubleshooting / Support

If issues persist:

  1. Re-check all settings (especially AIM ID, KeyEvent, Intent + Action, Broadcast, Extras).
  2. Reboot the device and test again.
  3. If the problem still occurs, please send:

to: [support@cobisoft.de](mailto:support@cobisoft.de).