IMDTouchKnowledge BaseShop main store

How-to

Using a VNC Viewer object on an HMI to display other panels

HMI and touchscreens Published 6 min read

Short answer

The VNC Viewer object is a VNC client, so a display-equipped host running the required OS can show any panel or PC that runs a VNC server, not just its own family. On cMT-series hosts the session appears only on the panel's own screen, never through the cMT Viewer app and never in online simulation. Use WebView for remote access.

On this page
  1. What the object connects to
  2. Check the host panel before anything else
  3. Prepare each target panel
  4. Place the object in the project
  5. Worked example: one host, two targets
  6. Where the session appears
  7. Commission the chain end to end
  8. Questions asked

Yes — a display-equipped host panel can show any other panel or PC through the VNC Viewer object, because the object is a VNC client and the manual note restricts the host, not the target. The host requirements are the real limits: eMT, iE, XE and mTV panels need OS 20160418 or later, cMT and cMT X panels need OS 20180928 or later and draw the session only on their own local screen, and the object never runs in online simulation. A cMT host displaying iP-series panels is therefore a supported configuration: enable each target's VNC server, give it a fixed address, put one object per target in the project, and read the session on the host touchscreen or through WebView.

What the object connects to #

The VNC Viewer object was added in EasyBuilder Pro V5.04.01 as a client that runs on the HMI to control a PC or another device remotely. As a client, it talks to any device running a VNC server: an iP-series panel, an eMT, another cMT, or an industrial PC. The family names in the manual note are host families with host OS requirements, not a list of permitted targets.

List every intended target by address and confirm each one runs a VNC server. A target without a server gives the object nothing to connect to, no matter how new the host OS is.

Check the host panel before anything else #

Host Minimum OS Where the session runs
eMT, iE, XE, mTV 20160418 or later On the panel's screen
cMT and cMT X with a display 20180928 or later Only on the panel's own screen, accessed locally
cMT unit without a display not applicable No local screen to host the object
Online simulation not applicable Not supported; the area stays empty

New production units are well past these cutoffs; shelf stock and spares may not be. An empty object area on a correctly configured panel is the classic symptom of an old OS.

  1. Open the panel's system information page and read the OS build date.
  2. Compare it against the minimum in the table for that family.
  3. If the build is older, update the panel OS with the vendor's update procedure before downloading the project.
  4. Record the build date on the commissioning sheet so a replacement unit gets the same check.

Prepare each target panel #

Most blank VNC windows trace to the target, not the viewer: the object is configured correctly and the target is not listening. Do this on every target before touching the host project.

  1. Enable the VNC server in the target's system settings.
  2. Set a VNC password; it must match the password you later enter in the object.
  3. Assign a fixed IP address, subnet mask and gateway. DHCP lease changes break the address stored in the object.
  4. Confirm the TCP port: 5900 is the standard VNC port unless the server was changed, and every firewall or managed-switch ACL in the path must pass it.
  5. Document address, port and password per target.

A VNC session hands the operator full control of the target panel, so treat that password as a machine access credential and keep the port inside the machine network.

Then pre-check from the engineering PC: open each target with any standard VNC client. If the PC cannot open the session, the host panel will not either — fix the server or the network before going further.

Place the object in the project #

  1. Open the host project in EasyBuilder Pro and create one window per target.
  2. Place a single VNC Viewer object on each window and size it to the target's resolution where possible; scaling a larger screen into a small area makes buttons hard to hit.
  3. Enter the target's address, port and VNC password in the object.
  4. Add navigation so the operator opens one target window at a time.
  5. Download the project to the physical panel.

Use one window per target and one live session at a time. Every open object holds a session and redraws continuously, so a single active session keeps the host responsive and the network load predictable.

Online simulation is still the right tool elsewhere — testing HMI simulation against a live PLC covers what it can prove — but it cannot render this object, so an empty area in simulation is expected, not a fault.

Worked example: one host, two targets #

Example addresses, not a measured test. Host: a cMT panel at 192.168.10.50 with mask 255.255.255.0. Targets: iP panels at 192.168.10.61 and 192.168.10.62.

Subnet check, with the arithmetic shown:

  • 192.168.10.50 AND 255.255.255.0 = 192.168.10.0
  • 192.168.10.61 AND 255.255.255.0 = 192.168.10.0
  • 192.168.10.62 AND 255.255.255.0 = 192.168.10.0

All three addresses resolve to 192.168.10.0/24, so the connections cross 0 routers and need no gateway configuration between host and targets.

The object settings that follow: window A gets address 192.168.10.61, port 5900 and that panel's password; window B gets 192.168.10.62, port 5900 and its own password. With navigation opening one window at a time the host carries 1 concurrent session; opening both windows carries 2 live redraw streams, which is exactly what the one-window-at-a-time rule avoids.

Where the session appears #

On a cMT host the object draws on the panel's physical display. The cMT Viewer app renders the project on the client device, with the panel serving data, so the client has no session to draw — that is the manual's accessed-locally clause, and no setting changes it. The app keeps its own navigation, and sessions can even change cMT Viewer pages independently on Android, but no page carries the VNC area because the client never receives it.

How the host is reached VNC area Verdict
Local touchscreen Shown and operable Primary use
cMT Viewer app Not shown Documented restriction, not a fault
WebView Shown and operable Preferred remote path
External VNC client into the host Shown, slower VNC inside VNC

Decide the remote path now: use WebView for remote access to a cMT host, because it mirrors the local screen including the VNC area without adding a second encode stage. A VNC client into a host that is itself running a VNC client compounds encode and refresh latency at every stage — acceptable for monitoring and occasional setpoint changes, wrong for anything an operator must hold or jog. If the remote need is watching rather than operating, making a read-only web client mirror of an HMI screen is a lighter path than driving two chained screens.

Commission the chain end to end #

  1. From the engineering PC, open every target with a standard VNC client before any host-side testing.
  2. On the host touchscreen, open each target window: the target screen must appear, update live, and respond to a touch.
  3. Power-cycle one target, reopen its window and confirm the viewer reconnects; if it does not, that target's address is not fixed.
  4. Change one target's VNC password, confirm the viewer fails authentication, restore it and confirm recovery — this proves the object uses the credentials you think it does.
  5. Repeat the touch test through WebView from a remote PC, then open the same window in cMT Viewer and confirm the area is empty there, so nobody files the restriction as a fault later.

Sign off only when every target answers from both the local screen and WebView. And if you push projects to the host over Ethernet, remember that a live VNC session proves the network path but not the transfer channel — when VNC works but an HMI project upload fails over Ethernet is its own failure to chase.

Questions asked

Can a cMT-series host display iP-series panels through the VNC Viewer object?

Yes. The object is a VNC client, so any iP, eMT, cMT or PC with a VNC server enabled is a valid target. The requirements sit on the host: a cMT or cMT X panel with its own display, OS 20180928 or later, and the project downloaded rather than simulated. Enable the VNC server and password on each iP panel first, then confirm each one from a PC with a standard VNC client before blaming the object.

Why does the VNC area stay blank in online simulation?

Because the object is documented not to run in online simulation, on any host family. Build and test navigation, tags and logic in simulation as usual, then download the project to the physical panel for the VNC check. An empty area in simulation with a working area on the panel is the expected behaviour, not a configuration fault, so do not rework the object settings to chase it.

Will operators see the VNC window through the cMT Viewer app?

No. On cMT hosts the session exists only on the panel's own screen, and the app renders the project on the client device, so there is no session to draw. Give app users the controls they need as native objects on a separate window, or point remote users at WebView, which mirrors the local screen including the VNC area.

The keyboard will not type into the VNC window. Is the object broken?

Not necessarily. The EasyBuilder Pro 6.09.02 release notes list keyboard input that may not function properly in the VNC Viewer under certain circumstances. Update EasyBuilder Pro and the panel firmware to current releases and retest before reworking the object or the target. For heavy data entry, plan an external keyboard at the target as a workaround while versions catch up.

Is operating through VNC inside VNC usable?

For monitoring and occasional setpoint changes, yes. Each stage encodes and refreshes the screen, so lag compounds: your client talks VNC to a host that is itself talking VNC to the target. Do not use the chain for anything an operator must hold or jog in real time; put those controls natively on the host project or walk to the target panel.

Keep reading

  • How-to

    Connecting two HMI panels to control one machine

    Yes. Connect the two DOP-107EV panels over Ethernet in a Host-Client arrangement: the Host keeps the controller link, and the Client controls the machine from its own screen. Each panel uses its own internal HMI memory, so any value both operators must see belongs in the controller, not in panel memory.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Transfer Fails in Initial Start Mode Despite Ping

    Ping success proves only that the panel's IP stack answers. On a new Magelis XBTG in Initial Start Mode, run three checks in order: build in the engineering version that still supports the target (Vijeo Designer 6.2 for XBTG), clear the license so the download command activates, then load runtime and application over one transport at a time.

    HMI and touchscreens

  • How-to

    Show a web visualization page on a PanelView Plus HMI

    Yes. Add the web browser object to a PanelView Plus display and set its URL to the page the other device serves, for example the host's webvisu.htm page on port 8080. The terminal then shows that page with zero tag mapping; test the URL from a laptop on the same subnet first, and expect the terminal's Internet Explorer-based engine to limit pages built on newer web features.

    HMI and touchscreens