How-to
Making a read-only web client mirror of an HMI screen
Short answer
The read-only mirror is a second web client on the same CODESYS WebVisu visualization, allowed only when the runtime license covers the project's tags and a viewer-only user group is enforced, then verified by attempting a setpoint change from the mirror and watching it fail. VNC works only where the panel documents view-only access. A second browser window or a separate network is not a permission boundary.
On this page
- A web client session and a pixel mirror are not the same tool
- Read the runtime version, license and tag ceiling at the device
- Enforce the restriction in the user group, not in the room layout
- The tag budget, with the arithmetic shown
- Commission the mirror and prove it read-only
- The decision for each case
- Questions asked
A read-only mirror of a WebVisu HMI is a second web client opened on the second computer and logged in under a viewer-only user group, and it counts as read-only only after a setpoint change attempted from that client fails. Three gates come first: the runtime must contain a web server with WebVisu support, the installed license must cover the project's bound-tag count, and the configured connection ceiling must leave a seat for the extra session. Where the platform offers no web client, the panel's documented VNC view-only access is the fallback. A second browser window or a separate network segment enforces nothing and proves nothing.
A web client session and a pixel mirror are not the same tool #
WebVisu serves the visualization from the runtime itself: one CODESYS runtime instance runs the control code, the visualization and the web server, and any browser that reaches that server renders its own session. Each session logs in separately and shows what its user's rights allow, which is exactly what makes a per-client restriction possible. The client end is only a browser pointed at the runtime, so the same PLC-hosted visualization that serves a remote HMI panel PC serves your mirror; that arrangement is described in running a PLC-hosted visualization on a remote HMI panel PC.
VNC is the other tool. It copies the pixels of the panel's own display and follows whatever that screen does, under whatever account that screen holds, so it can be read-only only if the panel's documentation offers a view-only access mode. When the requirement is a duplicate of the physical display, that is a display-output task of its own; how to mirror an HMI screen on an HDMI TV walks through that case. The two tools are not interchangeable: the web client is an independent session you can restrict, the VNC mirror inherits the source screen's rights.
If the real problem is a remote desktop session into a PC that already runs the HMI, that is an RDP restriction problem, not a web-client one. Making remote HMI access read-only over RDP covers that case; a browser client still needs its own enforcement.
Read the runtime version, license and tag ceiling at the device #
Executing a visualization as WebVisu has one documented prerequisite: the runtime system must contain a web server with WebVisu support. Without it, no browser connects and the rest of the checklist is moot.
The version rule, as reported for CODESYS runtimes: before version 3.6 there was no client-count limitation, and from 3.6 the limit that remains is on visualization tags. Treat that as the working hypothesis, then confirm it on your device before promising anyone a mirror: read the installed runtime version and the installed license. There is no fixed client constant to quote. Questions about whether 500 clients can connect end in the same place, because the ceiling is whatever the runtime configuration and the license on that controller define. The number you need is 2 seats, and you confirm it at the device.
Variant matters as much as version. On the panel family in this case, the WR21xx.1 and WR21xx.2 shipped with different operating systems, so the screen-out procedure documented for WR21xx.1 does not work on WR21xx.2. Read the documentation for the variant printed on your panel, not for the family.
Enforce the restriction in the user group, not in the room layout #
CODESYS visualizations carry their own user management: groups hold rights, users join groups, and every client session presents a login. Build a viewer group whose rights cover display only, with no write and no input elements, and create the mirror's user inside it. This is the same structure that sets granular user access on a CODESYS touch panel, and the walkthrough there is the recipe for the group and its rights.
Add the session cap where the runtime exposes one: size the maximum-connection setting to the seats you actually run, one interactive operator seat plus the viewer seats, so no unplanned interactive client can attach while the mirror is open. For VNC the same principle bites harder: view-only mode with its own password enforces the restriction, while a single shared control password hands the mirror full command of the machine.
What enforces nothing: a second browser window on the operator's PC, a firewall rule, a dedicated VLAN. Those change who can reach the client, not what the client may do once it logs in. If the login is an operator account, the mirror can run the machine no matter which network it sits on.
The tag budget, with the arithmetic shown #
Count bound tags first: every variable tied to an on-screen element across the whole project. Each input field, lamp, button and trend reference is one tag.
Worked example. Screen_Fill binds 34 variables, Screen_Alarms binds 21 and Trend_1 binds 7. Total: 34 + 21 + 7 = 62 tags. Read the visualization scope from the installed license; 80 tags is the example figure here, and the real number is on your license sheet, not in this article. 62 is within 80, leaving 18 tags of headroom: every client renders every value, and the second session is approved for display.
Fail case, scope 50: 62 - 50 = 12 tags over. Cut exactly 12 where they cost the least: move Trend_1 onto a screen the mirror never opens (-7) and trim the alarm list from 21 to 16 elements (-5), leaving 34 + 16 = 50, at scope with nothing over. If the screens cannot give that much up, the license level has to rise instead. A mirror over budget cannot be trusted to render every value, and a mirror that hides a value is worse than no mirror.
Commission the mirror and prove it read-only #
- Record the baseline at the device: runtime version, license scope in tags, configured connection ceiling, panel variant and operating system.
- Count bound tags as above and check two inequalities: total tags at most the licensed scope, and a ceiling of at least 2 seats.
- Create the viewer group and the mirror user in the visualization user management, with display rights only. Leave the operator account's write and command rights untouched.
- Open a browser on the mirror computer, point it at the runtime's address and log in as the viewer user. If the mirror belongs at the machine rather than on a desk, this is the step to choose among industrial panel PCs built for door and console mounting. Confirm the expected screens and live values render.
- Prove the restriction on a dummy setpoint: attempt a new value from the mirror, the input must be refused, then make the same entry from the primary HMI and watch it take. Leave 10 s between the attempts and confirm the value never moved from the mirror side. Run this on a dummy tag or an idle machine, never against a live axis or a safety function.
- Interrupt the mirror's network for 10 s and let it reconnect. The session must return under the viewer login with the refusal still in place; a reconnect that lands on an interactive account silently undoes the whole setup.
- Sign off with the primary HMI recorded as the authorized control point and the mirror recorded as display-only.
The decision for each case #
| Case | Method | What enforces read-only | Gate to clear first |
|---|---|---|---|
| Observer screen beside the machine | Second WebVisu client under the viewer group | The session's user-group rights | Tags within scope, ceiling 2 or more |
| Duplicate of the panel's own display | VNC in view-only mode | View-only access with its own password | Panel documents a VNC server |
| Several remote observers | One web client per observer, all viewer users | User-group rights per session | License scope covers the tag budget |
| Remote desktop into a PC that runs the HMI | RDP restriction, not a web client | Policy on the RDP session | Separate method, separate setup |
The decision rule underneath the table: the mirror is read-only when the session runs under a viewer-only group and the write-refusal test passes on the record. If any gate fails, no web server in the runtime, tags over scope, ceiling under 2, no viewer group, you do not have a read-only mirror. Fix the gate, or leave the second screen dark.
Questions asked
Can two computers view the same WebVisu at the same time?
Yes. Multiple simultaneous clients are the normal case for a web-served visualization, as long as the license and the runtime's configured connection ceiling allow it. Each client logs in on its own, so the mirror can sit on a different screen of the same visualization than the operator's client, with different rights. What limits you is the tag budget and the license level, not the existence of the second screen.
Is a second browser window on the operator's PC a read-only mirror?
No. Rights follow the login, not the window: both windows share the operator account, and either one can command the machine. It is one control point with two views. A real mirror needs its own session under a viewer-only user on separate hardware, and the write-refusal test has to pass on that session before you call it read-only.
Does VNC work on any HMI panel?
Only where the panel's documentation lists a VNC server among its remote-access features. It is a hardware and firmware capability, not a given. Before planning the mirror around VNC, confirm the exact model documents it and that the access mode includes view-only with its own password. A VNC server with a single shared control password gives the mirror full command of the machine.
How do I stop someone at the mirror from logging in as an operator?
Treat the mirror station like any restricted seat: it gets only the viewer account, operator passwords are never typed there, and the browser does not save an interactive login. If the runtime exposes a maximum-connection setting, size it to your seats so an unplanned interactive client cannot attach while the viewer session is open.