Answer a few questions. You get a project spec to share with whoever runs the network: what to deploy, which network rules to open, and a ready config.xml file for USB setup. Works with EM13DX, EM32DX and EM32DX-A. Everything runs in your browser. Nothing is uploaded.
Practical notes about the device that are not obvious from the manual.
How to use the Samsung Color E-Paper EMDX — official Samsung channel. Covers the factory reset, a firmware update and the Samsung E-Paper mobile app on a real device. Useful if you have not set one up before.
Press & hold the Power button ~2–3 s — a quick tap does nothing. Watch the LED for the state change.
A ~60–70 s, multi-phase sequence. The colour-blinks, full refresh and flicker are the panel resetting — not a fault. Don't count seconds — watch the LEDs; each phase changes them, as animated below.
0–2 s — from OFF (white screen) hold POWER ~2 s → red indicator starts blinking (power-on / charge check).
~12–15 s — keep holding (~10 s total); after ~3 s the red turns to green blinks, a full refresh (~20 s), then the indicator goes blank.
~35–42 s — hold MODE + BLUETOOTH together ~5–7 s → red & green blink, screen flickers (~15 s) → white screen.
~57–72 s — hold POWER ~2 s → red (4 s) → blue (3 s) → blue+green blink, flicker → QR codes appear. Done.
Download S-RSEDWWC-1130.7 (USB package, all EMDX models). USB-preset Wired/PoE and fleet auto-IP need 1130.7+ — update before provisioning.
1. Extract the .zip to the root of a FAT32 USB-C stick, keeping its folder structure — the files must land at \S-RSEDWWC\image\ (with upgrade.msd and info.txt inside), directly in the root, not nested.
2. With the device powered on, insert the stick into the USB-data port (USB icon, not the power-plug port). The update starts automatically when the stick holds a newer version.
3. Let it finish and reboot (a few minutes) — don't cut power or pull the stick mid-update. Then verify the version in the Samsung E-Paper app.
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 draws slowly. A preset takes a few seconds to apply (you see a rainbow, then a solid colour). A new image starts appearing after about 9 seconds and takes up to 30 seconds to finish drawing. 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).
For demos and trials the site network is often not ready yet, so a phone hotspot gets used. A phone hotspot frequently gives the screen a different IP address after it is switched off and on. The app finds the screen by its address after pairing, so it then reports "device not found".
Use a travel router or a spare access point instead. If you have to use a phone hotspot, leave it switched on, and re-pair in the app if the screen drops off.
Power the screen over Ethernet with a PoE-to-USB-C adapter. Confirm the switch's per-port budget: PoE+ (~30 W) is the safe target; plain PoE (15.4 W) can be marginal.
NAC: the adapter may present its own MAC — use one with MAC pass-through (MAPT) or whitelist the adapter. Remote wake: a PoE+ dongle alone won't wake a sleeping unit — add a separate USB-C power source.
You can change many settings after first boot with the Samsung E-Paper mobile app (or remotely via the CMS / VXT): device name, date / time / NTP, sleep & idle timer, orientation, picture mode.
What you can't change this way — Wi-Fi credentials, EAP certificates, Terms, and Content Source — needs a factory reset + new USB preset, or VXT. And pushing content from the app needs network reachability to the device: client isolation blocks it (use the CMS path on isolated networks).