How-to
Install and persist HMI software on a Windows CE touch panel
Short answer
Install the application to the panel's flash storage — SD card or USB mass storage — through ActiveSync or Windows Mobile Device Center, never to the RAM object store, because RAM-resident files on Windows CE 5.0 panels are lost when power drops. Then set a static IP, drop a shortcut in `\Windows\Startup`, and prove it with a full cold-boot test.
On this page
- How do I install software on a Windows CE touch panel from a PC?
- Where do I install files so they survive a power loss?
- Why does Windows CE 5.0 lose files in RAM at power-down?
- How do I set a static IP between the panel and the controller module?
- How do I make the application launch full-screen at boot?
- How do I prove the install really survives a cold boot?
- How should I power the panel so lock-ups stay recoverable?
- Questions asked
Install to the panel's flash storage — the SD card or a USB mass-storage drive attached to the panel — and never to the RAM-based object store. On Windows CE 5.0 touch panels, anything left in RAM is gone after a real power loss, and losing a freshly deployed client to a power cycle is the most common failure in these installs. The full deployment is short: connect over USB with ActiveSync or Windows Mobile Device Center, run the installer with flash as its destination, set a static IP against the controller's Ethernet module, drop a launch shortcut into \Windows\Startup, then prove the whole thing with a cold-boot test. The steps below use a documented example — an ElkRM client on a Windows CE 5.0 panel talking to an ELK M1 controller through its M1XEP Ethernet module — but the destination rules and startup mechanics apply to any third-party client on this class of panel.
How do I install software on a Windows CE touch panel from a PC? #
Connect the panel to a PC over its USB client port with ActiveSync on Windows XP or Windows Mobile Device Center on Vista or Windows 7, let the partnership form, then run the installer and choose flash as the destination when it asks.
- Power the panel from its DC terminal block and wait for the Windows CE 5.0 desktop.
- In ActiveSync, open Connect Settings and enable Allow USB connection. Windows Mobile Device Center needs no equivalent toggle.
- Plug the USB cable and wait for the partnership; a guest partnership is enough.
- Run the application's installer on the PC. It detects the connected device and offers to install onto it.
- At the destination prompt, pick the SD card or attached USB mass storage, covered next.
Panels sold with a full CE 5.0 image typically carry the .NET Compact Framework pre-installed and accept standard Win32 and .NET Compact Framework applications, so there is usually no extra runtime to chase. If the unit boots into a locked runtime instead of a desktop, entering configuration mode on a touch HMI is the way to the settings you need.
Where do I install files so they survive a power loss? #
On flash: the SD card or a USB mass-storage drive attached to the panel, both of which hold their contents with power off; the panel's internal object store does not, and on most of these panels it comes back empty after a cold boot.
The trap is that the object store looks like an ordinary disk in File Explorer, and installers default to it. Treat it as scratch space for temporary files only. Everything that must return after an outage — the executable, configuration files, and logs — goes on flash. The example deployment kept all three on the SD card, and that is the rule to copy.
Why does Windows CE 5.0 lose files in RAM at power-down? #
Because the object store is plain RAM and persistence is an OEM build option, not a feature the operating system hands you: it survives power loss only where the panel's builder added that support to the board software.
Windows CE divides RAM between program memory and storage memory, and you can move that division at any time without rebooting — which is exactly why people mistake the storage side for a disk. It is RAM. The registry tells the same story: with an object-store-based registry the hive lives in RAM and is restored from persistent storage at boot only if the OEM defined that restore. At least one mobile-computer vendor documents a persist utility for CE 5.0 through CE 7.0 that pins the storage-versus-program ratio across cold boots, which tells you this behavior lives in vendor tooling. If your panel vendor ships an equivalent, use it to keep the memory ratio stable, but it still does not turn RAM into file storage. Decision: flash for everything that must come back.
How do I set a static IP between the panel and the controller module? #
In Control Panel > Network and Dial-up Connections, open the Ethernet adapter's properties and assign a fixed address on the same subnet as the controller's Ethernet module; the worked example puts the panel at 192.168.1.50 against a module at 192.168.1.10, mask 255.255.255.0.
- Open Control Panel > Network and Dial-up Connections and double-tap the Ethernet adapter.
- Assign the IP address, subnet mask and default gateway. DNS matters only if you address the module by hostname.
- Apply, reboot the panel, then ping the module from the panel.
- Confirm the module's TCP port is open along the whole path.
| Setting | Value |
|---|---|
| Panel IP | 192.168.1.50 |
| Module IP | 192.168.1.10 |
| Subnet mask | 255.255.255.0 |
| Default gateway | 192.168.1.1 |
| Client TCP port | 2101 |
The subnet check is the arithmetic that decides this: 192.168.1.50 AND 255.255.255.0 = 192.168.1.0, and 192.168.1.10 AND 255.255.255.0 = 192.168.1.0. Both hosts sit on 192.168.1.0/24, so the panel reaches the module directly and the gateway at 192.168.1.1 plays no part in this traffic. In this pairing the module listens on TCP port 2101 by default, so the only rule needed permits the panel to that port. On the module side, give the M1XEP its own static values from the controller's programming utility, and note it occupies an address on the controller's expansion bus — default 1 — that must not clash with a keypad. Decision: same /24 plus an open port 2101 means the connection should establish; if ping fails, fix addressing before touching the client.
How do I make the application launch full-screen at boot? #
Copy the executable, paste a shortcut into \Windows\Startup, and put the full-screen switch on the shortcut's command line; in the example deployment the target read \SD Card\ElkRM\ElkRM.exe /fullscreen, so the client comes back on its own after every power-up.
- In File Explorer, navigate to the SD card root and copy the executable.
- Browse to
\Windows\Startupand paste a shortcut. - Open the shortcut's properties and set the command line to the full quoted path plus
/fullscreen, or whatever switch the client's documentation names. - Reboot and confirm the client launches by itself and binds to the module.
One catch: on most CE 5.0 images \Windows\Startup itself lives in the object store, so a cold boot can take the shortcut with it. The test in the next section tells you which kind of panel you have. If the shortcut vanishes, get the vendor's documented persistent-launch method instead of re-copying it after every outage. When the client ignores the switch, the techniques for running an HMI application touch-only in forced full screen are the fallback.
How do I prove the install really survives a cold boot? #
Pull the panel's power completely and leave it off a full minute before restoring it, because a software restart proves nothing and even a brief power blip can falsely look persistent — hold-up capacitance keeps RAM alive through short outages on some hardware.
- Confirm the application files are on flash and the Startup shortcut is present.
- Remove panel power at the supply, not a restart from software.
- Restore power after the minute.
- Check three things: the files are still there, the client auto-launches, and it connects to the module.
Decision: anything that vanished was living in RAM — move it to flash and repeat the test once. A pass here is what makes the deployment done.
How should I power the panel so lock-ups stay recoverable? #
From a switched, relay-controlled DC output you can toggle without opening the cabinet, because CE 5.0 panels of this class occasionally lock up and a full power cycle is the only reliable recovery.
Land the panel's supply through a relay or contactor driven from the controller, and label it, so an operator or a remote command can cycle the panel when it freezes. De-energize the branch before landing wires on the terminal block, and match the supply to the voltage and current printed on the unit's label. When the volatile object store, the ActiveSync-era toolchain and the lock-ups stop being worth the effort, industrial panel PCs running a full Windows image take the RAM-versus-flash question off the table. Sizing RAM, SSD and Windows for an HMI panel PC covers what to specify at that point.
Questions asked
Why do my registry edits on the panel vanish after every reboot?
Same root cause as the vanishing files. With an object-store-based registry the hive lives in RAM and is only restored from persistent storage at boot if the panel's builder implemented that support. If edits made through a remote registry editor are gone on the next boot, the panel is rebuilding its registry each time, so keep launch settings and configuration in files on flash instead of registry keys.
Can I stop files disappearing by giving storage memory a bigger share of RAM?
No. The storage-versus-program split only decides how the panel's RAM is divided, and it can be moved at any time without rebooting, but both sides are still RAM. A bigger storage share protects nothing at power-down, and shrinking program memory can starve the running client. Anything that must survive belongs on the SD card or USB flash.
Can I plug in a keyboard for passwords and one-time setup?
Yes, on panels whose USB host port takes HID-class devices; a combined wireless keyboard and mouse set was reported working on one such unit. That is far faster than the Windows CE on-screen keyboard for entering addresses and credentials during commissioning. Finish the typing, then remove the keyboard and leave the touch interface to run the client.
Could I skip installing on the panel and remote-desktop into a PC instead?
You can, within limits. A remote desktop session to a workstation-class Windows PC allows one connection at a time and locks the local console while it runs, unlike VNC, which mirrors the same session to every viewer. Two operators needing independent screens at once means the software must run somewhere multi-user, or on a panel at each station.