Answer a few questions about the deployment and get a ready-to-hand-over project spec: a step-by-step plan, the network/firewall requirements for the customer's IT, and a generated config.xml for USB Preset. For EM13DX / EM32DX / EM32DX-A (FW 1120). Runs entirely in your browser — nothing is uploaded.
The handful of physical-device things that aren't obvious. Field-tested on EM13DX / EM32DX-A.
Press & hold the Power button ~2–3 s — a quick tap does nothing. Watch the LED for the state change.
Hold Mode + Power together for ~7 s, until the LED changes — watch the LED, don't count seconds. The device returns to the QR / OOBE pairing screen.
Note: the HQ manual's "Mode + Bluetooth, 5 s" is wrong in the field — use Mode + Power.
Fix the file on the stick, then hold the Bluetooth button ~2 s — the device re-reads the USB, no reboot needed. (The stick is only read on the QR/OOBE screen.)
The #1 cause of "it won't read the stick": everything must sit in one folder in the drive root — config.xml and the certificate folders — not loose on the root.
FAT32, ≤16 GB, USB-C; plug into the USB-data port (USB icon, not the power-plug port). Tip: the wizard's "full USB folder (.zip)" download builds this structure for you.
e-ink refreshes slowly: a few seconds (rainbow → solid colour) when a preset applies, and up to ~30 s for a full image change. This is normal — not a fault.
LP-radio models have a main radio (2.4/5 GHz) and a Low-Power radio (2.4 GHz only). Main Wi-Fi MAC = Bluetooth MAC − 1 (the BT MAC is in the OOBE QR). The LP MAC isn't derivable — read it from DHCP, hostname starts DA16200- (main starts Samsung).
There's no local edit once a preset is applied: either factory-reset + re-apply a new USB key, or change it remotely via the CMS / VXT. By design — the preset only does initial setup.