Comparison
Headless HMI Server Versus Operator Panel Selection
Short answer
Pick by sessions and screen location, not by programming: both run one project in the same tool. A panel gives one built-in touchscreen that VNC mirrors as a single shared session; a headless cMT-SVR has no screen and no VNC, serves up to three independent app clients, and takes its trend history on SD/SDHC beside 256 MB of flash.
On this page
Choose by where the screen sits and how many people navigate at once, not by programming: an integrated operator panel and a headless HMI server run the same single project from the same engineering tool. A panel carries its own touchscreen, and its remote access — VNC, on Weintek's non-cMT panels — mirrors that one physical screen to every remote user. A headless server such as the Weintek cMT-SVR has no screen at all: it serves up to three simultaneous client sessions to smartphones, tablets and Windows PCs, each navigating independently, and it has no VNC to mirror. Take the panel when a fixed touchscreen at the machine is the requirement; take the server when independent multi-device access and removable trend storage decide the job.
What each device is #
An operator panel is one box: project runtime, display and touch surface together, mounted at the operator position. A headless HMI server keeps the runtime and drops the screen. The cMT-SVR-100 and cMT-SVR-200/202 run a 32-bit RISC processor at 600 MHz with 256 MB of RAM; the -200/202 cool fanless, and the operator's tablet, phone or Windows PC supplies display and touch through the cMT Viewer application.
Programming does not separate the two. Both are programmed as one project in EasyBuilder Pro, Weintek's engineering software, and both execute exactly one project at a time. For where these devices sit among panels, panel PCs and PC runtimes, start from industrial HMI device types. What decides this choice is the display architecture, so that is what the rest of this comparison works through.
Where the two differ #
| Requirement | Integrated operator panel | Headless HMI server (cMT-SVR) |
|---|---|---|
| Local operator screen | Built-in touchscreen at the machine | None; a smartphone, tablet or Windows PC is the screen |
| Mounting | Cut-out at the operator position | Anywhere with power and network; no display position to plan |
| Remote access | VNC server on the non-cMT panels | cMT Viewer client application; no VNC management on the server |
| Session behavior | Panel and every VNC client share one screen and one session | Up to 3 simultaneous connections, each navigating independently |
| Projects at once | One | One, holding connections and page groups for several controllers |
| Trend history | Internal memory of the fitted model | 256 MB internal flash plus an SD/SDHC slot and one USB 2.0 host port |
| Network | Model-specific Ethernet | cMT-SVR-100: two Gigabit Ethernet ports; cMT-SVR-200/202: one Ethernet port plus Wi-Fi 802.11 b/g/n with WPA/WPA2 |
| Serial | Model-specific | cMT-SVR-100: COM1 RS-232 2-wire, COM2 RS-485 2/4-wire, COM3 RS-485 2-wire; the -200/202 carry three COM ports |
Every row that actually decides the choice — screen, sessions, history — favors a different device depending on the installation, which is why the architecture gets chosen before the screens are drawn.
Remote access: one mirrored screen or three independent sessions #
A VNC session to a panel is a remote copy of its physical screen: the local operator and the phone see the same page, and both reach for the same buttons. One shared session, however many clients attach. That is the right tool when one person at a time needs to look in, and the wrong tool the moment two people need different pages at once.
The cMT-SVR does the opposite. It has no VNC management, so a VNC viewer pointed at it finds nothing to talk to. Access is the cMT Viewer application on the viewing device. The -200/202 models reach wireless clients directly over Wi-Fi 802.11 b/g/n with WPA/WPA2 security and can run as their own hotspot; the -100 is the wired variant with two Gigabit Ethernet ports. Each of the three allowed connections renders and navigates on its own: one operator on trends, one on a machine page, one remote user on the overview, simultaneously.
Remote control from outside the building keeps per-device access credentials on the server, and anything that protects people — stops, interlocks — stays on the machine, never on the client link.
Trend storage: 256 MB inside, SD/SDHC beside it #
The server's internal storage is 256 MB of flash, and that flash also holds the project and system data, so it is the wrong ceiling for a continuously growing database. The documented removable media are the SD/SDHC card slot and one USB 2.0 host port. The data-sampling part of the project is where the storage destination is set: point the history at the card, and the capacity becomes the card you fit — SDHC media is sized up to 32 GB by the SD standard, over a hundred times the internal 256 MB. The decision writes itself: an installation that logs trends continuously writes its database to removable storage, and the internal flash stays for the project.
One project, several controllers #
The server executes one project at a time, exactly like a panel — but nothing stops that single project from containing the connections and page groups of several PLCs on the LAN. Group the pages by controller, give the combined application a common entry page, and use the per-device access credentials to decide which viewing device reaches which group. Users experience several separate programs; engineering backs up and downloads one project. The connection pattern is the one behind connecting one HMI to two PLCs. When the requirement is genuinely several projects running at once, that is a different host class — see how multiple HMI projects run on one server host.
Counting client sessions for two shop tablets and one remote phone #
Inputs:
- Documented limit: the cMT-SVR serves up to 3 simultaneous client connections (Weintek's documented limit for the family).
- Installation need, the typical case behind this question: one wall-mounted tablet as the fixed station at the machine, one office Windows PC used during production, one smartphone used from off site.
- Worst moment: a fault, when all three connect at once.
Rule in words: every viewing device connected at the same time consumes one connection, whatever the device is; independent navigation is included in the connection, not charged separately.
Arithmetic: 1 tablet + 1 PC + 1 phone = 3 sessions. Spare capacity: 3 − 3 = 0. When the maintenance laptop appears during the same fault: 3 + 1 = 4, which exceeds the limit of 3.
Decision: at three or fewer simultaneous sessions the headless server fits, with the working rule that one client closes before a fourth device joins. The moment a fourth simultaneous session is a standing requirement rather than an accident, this server is the wrong pick: move the visualization to a PC runtime whose client count follows its license.
The decision #
Choose the integrated operator panel when:
- A permanently mounted touchscreen at the machine is the primary requirement.
- Remote access is occasional, one user at a time, and mirroring the panel screen is acceptable.
- The display position is fixed and known.
Choose the headless HMI server when:
- Operators need independent navigation — different pages at the same time, local and remote.
- The viewing devices are shared or personal: tablets, phones, office PCs.
- Trend history belongs on removable storage, and the station itself lives in the cabinet rather than at a display position.
When the job needs both a fixed touchscreen and more than three independent sessions, the next tier is the vendor's PC runtime on industrial panel PCs, where client count and history scale with the runtime license rather than a panel's built-in screen.
Commissioning check, either architecture: open the project from the intended client and navigate before calling it the control station. Navigation proves the client-to-server link only — confirm one known value reads live and one permitted write lands in the controller before handover.
Questions asked
Can I open a headless HMI server with a VNC viewer?
No. The cMT-SVR has no VNC management, so there is no service for a VNC client to talk to and no setting that adds one. Remote access runs through the vendor's cMT Viewer application on a smartphone, tablet or Windows PC. VNC belongs to the non-cMT operator panels, where every client mirrors the physical screen and all users share one session and one set of buttons.
Should the trend database go on the SD card or stay in internal memory?
On the card. Internal storage is 256 MB of flash shared with the project and system data, while the documented SD/SDHC slot takes cards the SD standard sizes up to 32 GB, over a hundred times the internal space. The data-sampling part of the project selects the destination; set it to the removable medium and size the card to the retention period you must keep.
How many people can use the server at the same time?
Three simultaneous connections, each navigating the project independently: one user on trends, another on a machine page, a third remote, all at once. A fourth device connected in the same moment exceeds the limit, so decide in advance which three devices hold the sessions and close one client before a fourth joins.
Can one server run a separate HMI project for each PLC?
No, it executes one project at a time, exactly like an operator panel. The working pattern is one project holding several controller connections, with page groups per controller and per-device access credentials deciding who sees which group; users experience it as several separate applications. Watch the compiled project size as you add page groups, because everything now lives in one build.
Which one do I pick if operators still need a screen at the machine?
Pick the integrated panel when a permanently mounted touchscreen is the main requirement and remote access means one user at a time. If independent sessions matter as much as the fixed screen, the server still works: mount a dedicated tablet as the always-connected local client, and it becomes the station while phones and PCs join as the second and third sessions.