MATERIAL FLOW · ENGINEERING TRIAL V0.3
A shared electronic-paper label, local workbench and device gateway for electronics stores, general warehouse bins and production lineside replenishment. Connect the displayed task to a recorded material movement.
Software and target builds verified. Physical prototype and site acceptance pending.
01
01
Match component code, bin and pick quantity to a work-order reference. Reserve stock when a pick is created; deduct it only after business confirmation.
Example: issue 30 resistors from A-01 against a production order. Lot, date-code, MSL and FIFO rules need a separate integration.
Plan an electronics-store pilot02
Show part code, storage location, available task and unit. Flash the location indicator to help find the bin, then check the part and location in the workbench.
Example: pick 12 fasteners from B-03. Weighing, RFID and automatic quantity sensing are future integration options.
Plan a warehouse pilot03
Use the shortage button to create a replenishment call. Keep the request, delivery task and reference together; add stock when delivery is confirmed.
Example: a station calls for 20 terminals. A call alone does not increase inventory or prove delivery.
Plan a lineside pilot02
The current trial runs on one controlled computer. USB supplies power; USB serial or authenticated BLE carries data. The built-in demonstration mode can be used before the hardware arrives.
03
A pick reserves quantity. Other open picks remain in the queue; only the selected task is shown on a label.
An immutable command carries its UUID and display version. Firmware reports driver completion after observing BUSY; this is not optical screen verification.
The workbench requires part code, location and operator ID. Wrong codes are rejected. Button 1 confirms the particular task previously reported as displayed.
The backend persists each event UUID. A lost ACK can be retried without a second stock deduction. Display receipts alone never alter inventory.
The compatibility API also accepts a legacy empty completion body. Physical-button confirmation does not provide scan evidence, and the entered operator ID is not an authenticated account. A mandatory-scan or role-based process needs additional policy controls.
04
The target is the non-Plus, non-Sense Seeed XIAO nRF52840 with a Waveshare 2.9-inch black-and-white V2 finished module. The carrier is a passive 70 × 50 mm, two-layer interface-board candidate.
Start with wired modules, then lock the BOM and check connector, USB and antenna clearances before ordering the carrier. CAM is supplied for engineering review; capacitor MPNs, mechanical fit and manufacturing release remain open.
05
A USB command opens a 60-second pairing window. The SDK supplies a dynamic PIN, printed only over USB. Firmware requires authenticated encrypted mode and a 16-byte key; the gateway also checks label and device identity.
20-byte BLE writes feed a bounded NDJSON parser. CRC and two journal slots detect damaged records; storage faults stop normal processing. Reconnection resends pending event UUIDs.
The management tool checks database integrity and creates a consistent SQLite backup. Restore writes to a new path. Reconcile post-backup movements and restart tags for fresh display versions.
This is an ordinary BLE NUS GATT implementation, not the Bluetooth ESL / PAwR standard. Pairing, bonding, RF coverage, flash endurance and fault behavior still require physical tests.
06
No boards have been flashed or assembled for this trial. Check the screen, GPIO, PIN/bond behavior, three-device radio concurrency, power loss, current, heat, ESD, mounting and a week of real operations. Software and CAD checks do not establish those results.
V0.3 · ENGINEERING TRIAL CANDIDATE
07
Four XIAO boards, four V2 panels, ten buttons, five LEDs and USB/wiring accessories. Match the supplied display revision and signal names.
Check supply, USB identity, full-text display, buttons, locate indicator, duplicates and restart behavior before BLE commissioning.
Bind one label per workflow, execute the acceptance sheet and reconcile actual stock. Collect coverage, refresh latency and failure data before setting deployment limits.
08
The complete public package includes software and firmware source, pinned dependency archives, binaries, native KiCad files, CAM candidates, drawings, procurement documents and test reports. Local machine paths are removed; runtime databases, environments and credentials are excluded.
Page text is available in five languages. The new implementation guide and procurement checklist are in English; original detailed development documents are mainly Chinese. Upstream licenses are retained, including GxEPD2 GPLv3 and font notices. Do not treat the downloads as an unrestricted proprietary product license.
Discuss a material-tag pilot09
The present design focuses on material movements and local task confirmation. Retail price engines, enterprise fleets, ESL/PAwR, multi-store operation and battery optimization require a separate product architecture.
The local API and protocol are documented. An integration needs field mapping, ownership of inventory, an order-ID strategy, retry and reconciliation rules, and acceptance tests using your system.
The download is an engineering trial candidate. Share requirements to define a prototype or custom PCBA project. BOM locking, samples, DFM/DFA, RF/EMC, enclosure and product-specific release criteria precede a production order.
Share the application, number of locations and simultaneous tasks, power source, shelf/mounting photos, target viewing distance, update frequency, ERP/WMS interface, language and target date. We can scope electronics, firmware, gateway software, enclosure integration and prototype verification.