Differences

This shows you the differences between two versions of the page.

--- cobi.wms:keyence_settings [2025/12/12 13:49] – thuth
+++ cobi.wms:keyence_settings [2025/12/15 11:28] (current) – [KEYENCE BT-A700G – Scanner Parameters] thuth
@@ Line 1: / Line 1: @@
-===== KEYENCE BT-A700G – Scanner Parameters =====
+====== KEYENCE – 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:
+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)
+  * Enable AIM ID Prefix (reliable barcode type identification)
-* Configure **Data Output** correctly (KeyEvent + Intent/Broadcast)
+  * Configure Data Output correctly (KeyEvent + Intent/Broadcast)
-* Set **Intent extras (Code type / Raw data / Data)** (proper handover to COBI.wms)
+  * Set Intent extras (Code type / Raw data / Data) (proper handover to COBI.wms)
 ==== Step-by-step instructions ====
-=== 1) Open Android Settings (Fig. 1) ===
+==== 1) Open Android Settings ====
-. Open the **app overview** (home screen / list of all apps).
+  - Open the app overview (home screen / list of all apps).
-. Tap **Settings**.
+  - Tap **Settings**.
-=== 2) Open Scanner Settings (Fig. 2) ===
+{{:cobi.wms:keyence1.png?400|}}
-. In Android Settings, select **Scanner** (scan parameters, code settings).
+==== 2) Open Scanner Settings ====
-=== 3) Open Data Formatting (Fig. 3) ===
+  - In Android Settings, select **Scanner** (scan parameters, code settings).
-. In the **Scanner** menu, scroll to the **Data** section.
+{{:cobi.wms:keyence2.png?400|}}
-. Open **Data formatting**.
-=== 4) Enable “AIM ID Prefix” (Fig. 4) ===
+==== 3) Open Data Formatting ====
-. Enable **AIM ID Prefix** (check the box).
+  - In the **Scanner** menu, scroll to the **Data** section.
+  - Open **Data formatting**.
+{{:cobi.wms:keyence3.png?400|}}
+==== 4) Enable “AIM ID Prefix” ====
+  - Enable **AIM ID Prefix** (check the box).
+{{:cobi.wms:keyence4.png?400|}}
 === 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) ===
+==== 5) Go back and open “Data Output” ====
-. Go **one step back** to the Scanner menu.
+  - Go **one step back** to the Scanner menu.
-. Open **Data output**.
+  - Open **Data output**.
-=== 6) Set Transmission Type to “KeyEvent” (Fig. 6) ===
+{{:cobi.wms:keyence5.png?400|}}
-. Under **Transmission type**, set the value to **KeyEvent**.
+==== 6) Set Transmission Type to “KeyEvent” ====
+  - 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) ===
+{{:cobi.wms:keyence6.png?400|}}
-. In **Data output**, tap **Intent**.
+==== 7) Enable Intent and configure Broadcast ====
-. Enable **Intent** (check the box).
-. Under **Action**, enter this value exactly:
+  - In **Data output**, tap **Intent**.
+  - Enable **Intent** (check the box).
+  - Under **Action**, enter this value exactly:
    * `de.cobi.wms.action.DATAWEDGE_BARCODE`
@@ Line 59: / Line 72: @@
 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) ===
+{{:cobi.wms:keyence7.png?400|}}
+==== 8) Set Intent extras: Code type / Raw data / Data ====
 Scroll further down in the Intent settings and set these values **manually**:
-* **Code type** → `com.motorolasolutions.emdk.datawedge.label_type`
+  * **Code type** → `com.motorolasolutions.emdk.datawedge.label_type`
-* **Raw data** → `com.motorolasolutions.emdk.datawedge.source`
+  * **Raw data** → `com.motorolasolutions.emdk.datawedge.source`
-* **Data** → `com.motorolasolutions.emdk.datawedge.data_string`
+  * **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).
+{{:cobi.wms:keyence8.png?400|}}
 === Final step: Restart the app ===
-. **Fully close COBI.wms** (remove it from the recent apps list / swipe it away).
+  - **Fully close COBI.wms** (remove it from the recent apps list / swipe it away).
-. **Open COBI.wms again**.
+  - **Open COBI.wms again**.
-. Start scanning and validate the result.
+  - Start scanning and validate the result.
-=== Troubleshooting / Support ===
+==== Troubleshooting / Support ====
 If issues persist:
-. Re-check all settings (especially **AIM ID**, **KeyEvent**, **Intent + Action**, **Broadcast**, **Extras**).
+  - Re-check all settings (especially **AIM ID**, **KeyEvent**, **Intent + Action**, **Broadcast**, **Extras**).
-. Reboot the device and test again.
+  - Reboot the device and test again.
-. If the problem still occurs, please send:
+  - 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)**.
+     to: [[support@cobisoft.de|support@cobisoft.de]].