A handheld that shows the HMI's screens in its browser can still refuse the remote-access client: on a Windows CE 5.0 scanner, the client returns "This is not a valid CE application" while the web server pages display. Treat viewing, remote control and scan-to-PLC entry as three separately tested paths, and buy only a handheld whose exact OS the client's documented support list names.
Buy the handheld last. The deciding document is the HMI vendor's supported-platform list for its remote-access client, because a handheld that shows the screens in its browser can still refuse the client at launch. On a Windows CE 5.0 handheld scanner, that is the documented outcome: the HMI's web server pages display, and the client returns "This is not a valid CE application". Plan three paths separately: viewing screens away from the panel, remote control of the HMI, and getting a scanned value into a PLC with no PC in between. Each path has its own requirement, and all three need testing on the exact handheld and the warehouse network it will use. This article gives the check that decides the purchase, the requirement for each path, a worked example, and the questions to ask both vendors before you order.
What decides the purchase
The web server and the remote-access client are two different programs on the HMI, and they make two different demands of the handheld. The web server serves pages to whichever browser opens them. The client is an application written for named operating systems, and the handheld runs it or refuses it at launch.
Treat a CE version number as a kernel label and check the actual list. Windows CE is a component operating system: the handheld vendor builds the OS image and selects which components ship, so two devices both labelled CE 5.0 can carry different software. The documented requirements for the Windows CE remote desktop control read as a named OS list, Windows CE .NET 4.0 and later, and that is the shape every useful compatibility check takes: a list of named versions, matched against your exact device.
The purchase rule follows. Ask the HMI vendor for the remote-access client's supported-platform document and buy a handheld whose operating system appears on it. If you already hold a CE 5.0 scanner, budget for the launch failure: the error "This is not a valid CE application" says the client does not run on that OS build, and no scanner setting changes that, so a reinstall costs a shift and returns the same screen.
The same order of decision applies to the wireless side: pick the client, then the hardware, as set out in remote HMI wireless access: choose the client first.
The three paths, and what each one needs
Score the handheld on three separate jobs. One passing tells you nothing about the other two.
| Job | Route | Must be true before you buy |
|---|---|---|
| View screens away from the panel | HMI web server pages in the handheld's browser | Your actual screens render and stay usable on the handheld's screen |
| Remote control | The HMI vendor's remote-access client | The client's supported-platform list names the handheld's exact OS |
| Scan a value into the PLC | A named receiver: an HMI text-entry object, a barcode module on the controller, or a client the vendor documents for scan input | Scanner output mode, delimiters and field length match the receiver |
| One handheld for all three | All of the above on one device | All three paths pass on that device and your network; otherwise split the job |
Viewing. Field guidance on selecting HMI remote access options describes the browser as the normal route for monitoring data, which is what most warehouse viewing is. Test with your real screens at the handheld's screen size: typical handheld screens run 3.5 to 5 inches, and a page that reads fine on a workshop monitor can be unusable at that size.
Control. Without your device on the client's list, treat the path as unavailable and plan around it. Where the client is a remote desktop client, the HMI listens on the remote desktop default TCP port 3389, so test that the handheld opens that port from the aisle operators work in, not just from a bench next to the switch.
Scan to PLC. The scan needs a receiver you can name, and on many HMI projects that receiver is a text-entry object writing a string tag, the setup covered in USB barcode scanner setup for an HMI text entry object. Match the scanner's output mode, USB keyboard, serial or Bluetooth, to what the receiver accepts, agree the start and terminator characters, and check the field length. The symbology sets the worst case: the Code 39 symbology caps a symbol at 43 data characters, so a 43-character label is the longest test scan worth running.
Example: three tests on one CE 5.0 scanner
Scenario: a warehouse wants one handheld per operator. The operator should see the HMI screens at a rack, occasionally adjust a value, and scan a lot number into the controller. You are holding a handheld scanner running Windows CE 5.0 and about to order ten more.
Test 1, viewing. Open the HMI's web server in the handheld's browser. The screens draw and the values update. Pass.
Test 2, control. Launch the vendor's remote-access client on the same device. It fails at launch with "This is not a valid CE application". Fail.
Test 3, scan to PLC. The project has a text-entry object that writes the scanned string to a tag. Scan the label LOT-2024-0458773, which carries 16 characters. The tag receives 16 of 16 characters, terminator stripped. Pass.
Score: 2 of 3 paths, and the failing path is the client path, the one that carries remote control. Ordering ten more of this scanner puts a device in every hand that cannot do the adjustment job. The fix is a second device named on the client's support list for control, with the scanners kept for scanning if the lot-number path holds up for the way operators actually work.
Test the network where the work happens. In this scenario the farthest pick aisle sits 120 ft from the access point, so the handheld has to reach the web server over HTTP and the HMI over TCP 3389 from there. A bench test one desk from the switch leaves the far aisle untested, and coverage problems show up as slow screens and timeouts in exactly the spot where the operator stands.
When to split the job
If the client's supported-platform list names no handheld scanner you can buy, stop trying to make one device do everything. Give the scanner its own path into the controller and move screens and control to a device the list does name. Many crews end up with the scanner in one hand and a supported client device holstered, which is faster than a stack of workarounds on an unsupported OS. The view-versus-client trade is the same one covered in mobile PLC operator interface: remote view or separate client.
If the need at a fixed bench is a status board the whole crew reads, that is a different product class: see shop-floor signage screens, which play offline content or run your own Android app.
What to ask for before you pay
From the HMI vendor:
- The remote-access client's supported-platform document, with operating system versions named.
- The web server's browser requirement.
- The receiving method for a scanned value: which object writes which tag, and the field length it accepts.
- Whether a different client build supports a device you already own; some vendors keep several client generations.
From the handheld vendor:
- The exact OS version and build, plus the browser version. A spec sheet line reading "Windows CE 5.0" names the kernel; the support list is the compatibility statement.
- The scanner's output modes: USB keyboard, serial, Bluetooth.
For the network:
- HTTP reachability of the web server and TCP 3389 for remote desktop, tested from the farthest aisle.
New purchases start from a list you can satisfy: current remote desktop client documentation names Windows 10 and Windows 11 Pro and Enterprise editions as supported operating systems for client connections. A CE 5.0 device starts from a support list written when CE 5.0 was current, in the mid-2000s.
The decision
Recommendation: Buy the handheld only after the HMI vendor's supported-platform document names its exact operating system for the remote-access client. Before ordering quantity, run the three-path test on that device and your warehouse network: your screens in its browser, the client launching without error, and a full scan-to-PLC transaction with your longest label, checked at the controller. If no scanner-class handheld appears on the list, split the job: a handheld scanner for data entry into a receiver you have checked, plus a supported client device for screen control.
Questions
Why does the remote-access client say "This is not a valid CE application"?
The handheld refuses the program at launch: the client binary does not match that device's OS build, so the application never starts. Reinstalling, rebooting or changing scanner settings will not clear it, because nothing in the scanner configuration is wrong. Before replacing hardware, ask the HMI vendor whether a different client build supports your device; some vendors keep several client generations. If none does, the fix is a pairing: a client version and a handheld whose OS the vendor lists together.
Can a barcode scan reach the PLC with no PC in between?
Yes, through a receiver you can name: a text-entry object on the HMI that writes a tag, a barcode interface module on the controller, or a client application the vendor documents for scan input. The scanner's output mode, the start and terminator characters and the field length all have to agree. If the tag arrives short or doubled, the usual causes are a suffix the scanner appends and a field that accepts fewer characters than the label carries. Test the full transaction with your longest label and read the value at the controller.
Which operating system should a new handheld run?
Whatever the HMI vendor's supported-platform document names for its current client. Current remote desktop client support names Windows 10 and Windows 11 Pro and Enterprise editions, and some HMI vendors ship Android clients as well. Ask for the document, buy a device it names, and get the answer in writing before you order quantity. If the list names no integrated-scanner handheld, split the job: a scanning device writing into a receiver you have checked, plus a supported client device for screens.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.