How-to
How to Mirror an HMI Screen on an HDMI TV
Short answer
An HMI terminal has no video output: its USB ports are host ports for keyboards, mice and storage. To mirror the panel on an HDMI TV, put a small PC at the TV and connect a VNC viewer in view-only mode to the terminal's VNC server, the only method that follows the panel screen for screen. A web session or a second runtime of the same project works where VNC is unavailable, but each shows an independent screen.
On this page
- Rule out an adapter on the terminal's USB port first
- Ping the terminal from the TV-side PC before picking a method
- Worked example: a TV-side PC at 10.1.1.50 and a terminal at 10.1.1.10
- Choose the method: VNC mirror, web session, or a second runtime
- Set up the VNC mirror in view-only mode
- Match the symptom to the cause
- Prove the mirror follows the panel and cannot drive it
- Questions asked
You cannot mirror an HMI terminal on an HDMI TV from the terminal itself: its USB ports are host ports for keyboards, mice and storage, not a display output. The dependable setup puts a small PC at the TV, gives the terminal a fixed address such as 10.1.1.10, and connects a VNC viewer from the PC to that address over TCP 5900 in view-only mode — the only method that shows a true mirror, the same screen and popups, screen for screen. A browser session through web access, or a second runtime of the same project on the PC, each shows an independent screen that drifts from the panel the moment someone navigates. Work through it in this order: confirm the terminal has no documented display output, ping the terminal from the TV-side PC, pick the method, then set up view-only and prove it before anyone treats the TV as a display.
Rule out an adapter on the terminal's USB port first #
Open the manual for the exact terminal and read its connector list. PanelView documentation describes its USB ports as host ports — the PanelView Plus 7 startup procedure connects a USB keyboard to a USB host port, and the family's selection guide lists Ethernet, serial and two USB ports with no external display output on USB. If the manual for your model documents an HDMI or other display output, use it and stop there.
That is why the USB-to-HDMI adapter everyone tries first fails: a USB display adapter needs a driver on the host to appear as a display head, and a closed HMI terminal is not built as a USB display host, so it never loads one. USB on these machines carries device data inward, not pixels outward — the same division behind why HDMI video works but USB touch does not on a panel.
One field installation does run this way: a USB-to-HDMI device, a very long HDMI cable down the line, and a mouse on a very long USB extender. Treat it as an untested branch on any other model, and borrow an adapter to test before buying anything.
Ping the terminal from the TV-side PC before picking a method #
Every method below feeds the TV from a PC, so first prove the IP path from the control room to the terminal. Ping the terminal's address from the PC that will drive the TV. A reply means you can go pick a method. No reply means fix the network first: the terminal's IP and subnet mask, the switch port it lands on, and any VLAN or firewall between the HMI network and the control room. No viewer or browser setting fixes a dead path.
Worked example: a TV-side PC at 10.1.1.50 and a terminal at 10.1.1.10 #
Inputs. Example addresses for the layout in the question — terminal in the PLC cabinet, PC in the control room; substitute your own. Terminal at 10.1.1.10, subnet mask 255.255.255.0, PC at 10.1.1.50 in case A and 10.2.1.50 in case B, the same mask on every device. The VNC server listens on TCP 5900, the VNC default.
Rule. Two hosts exchange frames directly only when their addresses, ANDed octet by octet with the subnet mask, produce the same network number. Different numbers mean a router must carry the traffic, and every firewall on that path needs an explicit allow rule for TCP 5900 toward the terminal.
Arithmetic. Case A: 10.1.1.10 AND 255.255.255.0 = 10.1.1.0 (10 AND 255 = 10, 1 AND 255 = 1, 1 AND 255 = 1, 10 AND 0 = 0), and 10.1.1.50 AND 255.255.255.0 = 10.1.1.0. Case B: 10.2.1.50 AND 255.255.255.0 = 10.2.1.0 — a different network number.
Result. Case A is a direct Ethernet path; case B must cross a router.
Decision. Equal network numbers: enable the terminal's VNC server and connect the viewer, no routing work to do. Different network numbers: add a firewall rule allowing TCP 5900 from the PC address to the terminal address — plus the terminal's documented web-access port if a browser session is planned — or put the TV-side PC on the terminal's subnet.
Choose the method: VNC mirror, web session, or a second runtime #
Decide one thing before configuring anything: must the TV show exactly what the operator at the panel sees, or can it show its own page? The three methods behave differently, and the wrong pick produces a TV that displays a different screen than the panel.
| Method | What the TV shows | What it needs |
|---|---|---|
| VNC viewer, view-only | A true mirror: same screen, same popups, screen for screen | VNC server enabled on the terminal, a small PC at the TV |
| Web access in a browser | An independent session with its own navigation | Web-access license, a browser pointed at the terminal IP |
| Second runtime of the project | The same project running locally on the PC | The compiled runtime file (a .mer on PanelView terminals), a PC with its own controller connection |
If the TV must follow the panel screen for screen, use VNC. If a separate overview is acceptable, use web access and build a dedicated overview screen that needs no navigation, then leave the browser pointed at the terminal. If neither is available, run the second runtime: the same project then runs in both places, but not the same screen at the same moment.
Watch the controller load. The browser session and the second runtime each open their own tag connection to the controller — the same question as connecting multiple HMIs to one PLC over 200 ft serial — while VNC traffic stays between the PC and the terminal and adds nothing to the controller.
Set up the VNC mirror in view-only mode #
First confirm what your terminal's VNC feature publishes. On most terminals the server shares the terminal's own screen, which is what makes VNC the true mirror; on some models it is documented as a remote session of the runtime without a copy of the local display — the PanelView 800 VNC remote session without local screen mirror page covers that distinction for one panel family.
The PC at the TV only has to run a viewer and drive the TV over HDMI; where the TV hangs at the line rather than in an office, an industrial mini PC is the compact kind meant to live at the machine for exactly this job.
Set view-only at the server and again in the viewer, and require both: until both are proven, the TV is a live operator station and anyone at it can press Start on a running machine.
- Give the terminal a fixed IP address and record it; a DHCP lease that changes silently breaks the viewer overnight.
- Enable the VNC server the way the terminal's manual documents. Manuals keep this in their configuration or security tools: WinCC flexible, for example, activates Sm@rtServer under Device Settings in Runtime Services, and panels that manage access by level set VNC rights under Tools, Security Administration, on a VNC tab, one access area at a time with its own password. Pick the lowest level offered — observe or view-only — and set a password.
- Install a VNC viewer on the PC, connect it to the terminal's IP address, and enable the viewer's own view-only option as the second layer.
- Set the viewer to full screen, to start at login, and to reconnect automatically after a dropped session.
- Disable PC sleep, screen blanking and automatic update restarts so the TV never goes dark between shifts.
- Connect the PC's HDMI output to the TV, turn TV overscan off, and set scaling to fit rather than stretch if the terminal and TV aspect ratios differ.
- Keep the PC on the HMI network, or behind a firewall rule that allows only the VNC port to the terminal.
Match the symptom to the cause #
| Symptom on the TV | Cause | First fix |
|---|---|---|
| TV dark when the adapter goes into the terminal USB port | The terminal is not a USB display host | Move to the PC-based methods |
| Viewer refuses the connection | Server off, wrong password, wrong port, or a firewall in the path | Ping the terminal, confirm the server is enabled, confirm the port (VNC defaults to 5900) |
| TV shows a different screen than the panel | Browser session or second runtime used instead of VNC | Switch to VNC, or accept an independent overview page |
| Someone at the TV can press buttons | Access level or viewer allows input | Set view-only at the server and in the viewer |
| Image freezes after a network blip | Auto-reconnect off | Enable reconnect, or restart the viewer from a scheduled watchdog task |
Prove the mirror follows the panel and cannot drive it #
- Navigate to a different screen at the terminal; the TV follows without a manual refresh.
- Click and tap at the TV; nothing changes on the terminal.
- Pull the PC's network cable and reconnect it; the viewer returns on its own, no keyboard needed.
- Power-cycle the PC; the viewer starts full screen and connects with no login prompt left on the TV.
If you used the browser session or the second runtime instead, verify the PC's controller connection and watch the communication load, because each additional session adds its own. The same read-only discipline applies to every remote window onto the panel, including making remote HMI access read-only over RDP.
Questions asked
Can I plug a USB-to-HDMI adapter into the terminal and skip the PC?
Not as a dependable path. The terminal's USB ports are host ports for keyboards, mice and storage, not display heads, and a USB display adapter needs a driver the terminal will never load. If you still want to test one, remember two limits: a passive USB 2.0 cable run stops at about 5 m, so a distant TV needs an active extender, and borrow the adapter rather than buying it. One reported installation works this way with a very long HDMI run; treat it as untested on your model.
Does the VNC mirror add load to the PLC?
No controller load at all. VNC traffic runs only between the viewer PC and the terminal; the terminal keeps polling the controller exactly as before, because the mirror just draws the screen the terminal already composed. What does add controller load is giving the TV its own connection: a second runtime or a browser session opens its own tag exchange with the controller on top of the panel's own. The mirror's cost is network bandwidth between terminal and TV, shared with everything else on that segment.
What should I have ready before calling the terminal vendor's support?
The exact terminal catalog number and firmware revision, the manual's answer on whether that model offers VNC or web access at all, the license level if web access is the goal, and the ping result from the TV-side PC to the terminal's address. Escalate on two symptoms: the terminal answers ping but its VNC server will not start or accept connections, or the manual documents no VNC and no web feature for the model.