cobi.wms:keyence_settings
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| cobi.wms:keyence_settings [2025/12/12 13:47] – created thuth | cobi.wms:keyence_settings [2025/12/12 13:51] (current) – thuth | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== KEYENCE BT-A700G – Scanner Parameters ===== | ===== KEYENCE BT-A700G – Scanner Parameters ===== | ||
| - | ### Purpose | + | ==== 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/ | 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/ | ||
| - | * Enable | + | |
| - | * Configure | + | * Configure Data Output correctly (KeyEvent + Intent/ |
| - | * 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 | + | ==== Step-by-step instructions |
| - | ### 1) Open Android Settings (Fig. 1) | + | === 1) Open Android Settings (Fig. 1) === |
| - | 1. Open the **app overview** (home screen / list of all apps). | + | - Open the app overview (home screen / list of all apps). |
| - | 2. Tap **Settings**. | + | |
| - | ### 2) Open Scanner Settings (Fig. 2) | + | === 2) Open Scanner Settings (Fig. 2) === |
| - | 1. In Android Settings, select **Scanner** (scan parameters, code settings). | + | - In Android Settings, select **Scanner** (scan parameters, code settings). |
| - | ### 3) Open Data Formatting (Fig. 3) | + | === 3) Open Data Formatting (Fig. 3) === |
| - | 1. In the **Scanner** menu, scroll to the **Data** section. | + | - In the **Scanner** menu, scroll to the **Data** section. |
| - | 2. Open **Data formatting**. | + | |
| - | ### 4) Enable “AIM ID Prefix” (Fig. 4) | + | === 4) Enable “AIM ID Prefix” (Fig. 4) === |
| - | 1. Enable **AIM ID Prefix** (check the box). | + | - Enable **AIM ID Prefix** (check the box). |
| - | **Why this matters:** | + | === 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). | 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” (Fig. 5) === |
| - | 1. Go **one step back** to the Scanner menu. | + | - Go **one step back** to the Scanner menu. |
| - | 2. Open **Data output**. | + | |
| - | ### 6) Set Transmission Type to “KeyEvent” (Fig. 6) | + | === 6) Set Transmission Type to “KeyEvent” (Fig. 6) === |
| - | 1. Under **Transmission type**, set the value to **KeyEvent**. | + | - Under **Transmission type**, set the value to **KeyEvent**. |
| **Short note:** | **Short note:** | ||
| “KeyEvent” sends scanned data as keyboard/ | “KeyEvent” sends scanned data as keyboard/ | ||
| - | ### 7) Enable Intent and configure Broadcast (Fig. 7) | + | === 7) Enable Intent and configure Broadcast (Fig. 7) === |
| - | 1. In **Data output**, tap **Intent**. | + | - In **Data output**, tap **Intent**. |
| - | 2. Enable **Intent** (check the box). | + | |
| - | 3. Under **Action**, enter this value exactly: | + | |
| * `de.cobi.wms.action.DATAWEDGE_BARCODE` | * `de.cobi.wms.action.DATAWEDGE_BARCODE` | ||
| Line 60: | Line 59: | ||
| 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. | 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) | + | === 8) Set Intent extras: Code type / Raw data / Data (Fig. 8) === |
| Scroll further down in the Intent settings and set these values **manually**: | 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` | + | * **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/ | These extras ensure COBI.wms receives the information in the expected structure and can process the barcode logic correctly (including type/ | ||
| - | --- | + | === Final step: Restart the app === |
| - | + | ||
| - | ## 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 | + | === Troubleshooting / Support |
| If issues persist: | If issues persist: | ||
| - | 1. Re-check all settings (especially **AIM ID**, **KeyEvent**, | + | - Re-check all settings (especially **AIM ID**, **KeyEvent**, |
| - | 2. Reboot the device and test again. | + | |
| - | 3. If the problem still occurs, please send: | + | |
| * the **exact workflow** (module, input field, what you scan), | * the **exact workflow** (module, input field, what you scan), | ||
cobi.wms/keyence_settings.1765543652.txt.gz · Last modified: by thuth