===== 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:

  * Enable AIM ID Prefix (reliable barcode type identification)
  * Configure Data Output correctly (KeyEvent + Intent/Broadcast)
  * Set Intent extras (Code type / Raw data / Data) (proper handover to COBI.wms)


==== Step-by-step instructions ====

=== 1) Open Android Settings (Fig. 1) ===

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

=== 2) Open Scanner Settings (Fig. 2) ===

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

=== 3) Open Data Formatting (Fig. 3) === 

  - In the **Scanner** menu, scroll to the **Data** section.
  - Open **Data formatting**.

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

  - 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) === 

  - Go **one step back** to the Scanner menu.
  - Open **Data output**.

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

  - 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) === 

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

   * `de.cobi.wms.action.DATAWEDGE_BARCODE`
4. Set the **Transmission type** in the Intent section to:

   * **Broadcast**

**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**:

  * **Code type** → `com.motorolasolutions.emdk.datawedge.label_type`
  * **Raw data** → `com.motorolasolutions.emdk.datawedge.source`
  * **Data** → `com.motorolasolutions.emdk.datawedge.data_string`

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 === 

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

=== Troubleshooting / Support === 

If issues persist:

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

   * the **exact workflow** (module, input field, what you scan),
   * **screenshots** of the settings,
   * the **affected barcodes** (sample data)
     to: **[support@cobisoft.de](mailto:support@cobisoft.de)**.