How-to
Show a web visualization page on a PanelView Plus HMI
Short answer
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.
On this page
Yes. Add the web browser display object to a PanelView Plus screen and point its URL at the page the other device serves — for example http://192.168.10.40:8080/webvisu.htm — and the terminal shows that page with zero tag mapping. You build the interface once, on the device that hosts it, and the PanelView Plus becomes a viewer for it. The terminal's OPC capability is a different route, for moving tag data into native screens; you do not need it to see the page. What you do need is the sequence below: prove the page loads from a laptop, prove the terminal's subnet reaches the host, set the URL, and know where the terminal's older browser engine gives up.
Decide first: the picture or the data #
Ask one question before touching the software: does the terminal need the picture, or the data?
You need the existing visualization exactly as built. Use the web object. No tag mapping, no second set of graphics, and the rest of this procedure applies.
You need the values inside native PanelView Plus screens — alarms, trends, recipes, local logic. That takes a data connection and native graphics, which is a second HMI project, not a variant of this one. When that connection is OPC UA, settle which device runs the OPC UA server and which one connects before anything else.
Do not start with OPC setup when the goal is only to see the page: it adds server configuration and a screen rebuild for no gain.
Put the web object on the screen and set its URL #
- Open the display in the FactoryTalk View Machine Edition development software and add the web browser display object, the ME Web Browser Control. In a FactoryTalk Optix project the equivalent is added in Project view, under UI, with
New > Contents > Web browser. - Size the object to the area the page needs, and leave room for a navigation button. A full-screen object with no exit forces a restart to leave the page.
- Set the object's URL property to the exact address that loaded on the laptop — same host address, same port, same page name.
- Add the navigation button that returns to your native screens.
- Give the host a fixed IP address before you download. A DHCP lease that changes breaks the stored URL on the next power cycle.
- Download the application to the terminal and run it.
If the URL property will not hold the address in your project, the route other projects have used is a short VBA routine behind a navigation command that sets the URL at runtime.
Prove the page loads from a laptop first #
Rule out the page before you blame the terminal. Connect a laptop to the subnet the terminal will use and open the exact URL in a browser.
| What the laptop shows | What it means | What to do |
|---|---|---|
| Page loads and updates | Server, port and page name are good | Move on to the terminal checks |
| Connection refused or times out | The web visualization is not enabled or not running on the host, the port differs, or a firewall blocks it | Read the port from the host's visualization settings, enable the server, retest |
| Page not found | Wrong path or page name | Confirm the page name; webvisu.htm is the name in this example |
| Loads but stays blank, never updates | Host application stopped, or a client-side feature failed | Put the host application in run, then retest |
Do not touch the terminal until the laptop works. A page that fails on a laptop fails on the terminal too.
Prove the terminal can reach the host #
A working laptop proves the host side only. Read the terminal's IP address, subnet mask and gateway in its network settings, confirm the two devices share a subnet or a routed path, confirm no managed-switch VLAN, ACL or firewall rule separates their ports, and rule out a duplicate IP address — duplicates produce intermittent loads that look like a web fault.
Subnet check with real numbers #
Example: the host is 192.168.10.40 with mask 255.255.255.0, the laptop is 192.168.10.77, and the terminal is 192.168.100.5 on the same mask. With a 255.255.255.0 mask, each of the first three octets passes unchanged and the fourth becomes 0:
- Host network: 192.168.10.40 AND 255.255.255.0 = 192.168.10.0
- Laptop network: 192.168.10.77 AND 255.255.255.0 = 192.168.10.0 — same network, so the laptop loads the page
- Terminal network: 192.168.100.5 AND 255.255.255.0 = 192.168.100.0 — and 192.168.100.0 ≠ 192.168.10.0, so the terminal has no direct path
Decision from those numbers: re-address the terminal into the host's subnet — 192.168.10.61 AND 255.255.255.0 = 192.168.10.0, which matches — or add a route through the gateway. Changing the URL fixes nothing here. A 100 where a 10 belongs is the classic cause.
Know the terminal's browser limits #
The ME Web Browser Control renders with Microsoft Internet Explorer, the engine that ships with the terminal's Windows build, and it is older than any current laptop browser. CODESYS states the requirement for WebVisu plainly: a current browser with JavaScript and HTML5-Canvas support, with Firefox, Chrome and Internet Explorer 9 or newer given as examples. A page that leans on HTML5-Canvas can load its frame on the terminal and leave the visualization area blank, because the older engine cannot run it. Rockwell Automation limits the control to specific PanelView Plus 6 and 7 terminals, so confirm your catalog number is covered before building the screen. When the blank page is the URL's own fault rather than the engine's, check the address form against the trailing-slash URL fix for a blank WebVisu page.
| Symptom on the terminal | Likely cause | Action |
|---|---|---|
| Error text inside the object | Network path or URL | Repeat the laptop and subnet checks |
| Frame loads, content blank | Engine cannot run the page's scripts or graphics | Reduce the visualization's client features, or rebuild the screens natively |
| Values update slowly or freeze | Heavy page, weak terminal CPU, slow link | Cut animations and large images |
| Works for minutes, then stops | Host limit on simultaneous web clients, or a network drop | Check the host's client limit and the switch logs |
| Touch input misses | Page designed for a mouse or another resolution | Build the page at the terminal's native resolution with large buttons; the display-scaling fix for WebVisu rendering on an embedded panel covers wrong-size rendering |
Verify the result and protect the write path #
- Power-cycle the terminal and confirm the page loads at startup with no manual step.
- Change a value on the host and confirm it appears on the terminal within the update time you expect.
- Unplug the host's network cable: the terminal should show a clear failure, then recover when you reconnect.
- Press a control on the page and confirm it writes the intended variable, and that a button which starts motion cannot be reached by mistake.
A web page usually gives the viewer the same write rights as the original interface, so confirm the host's logins and user levels and keep the link on the machine network. Emergency stop and safety functions stay in hard-wired or safety-rated circuits — never behind a screen button on a web page.
The decision for each case #
- You need the existing page as built and the terminal renders it: use the web object with the laptop-tested URL. That is the whole job, and OPC stays unused.
- You need the values in native screens: build the data-connection project instead, with the OPC UA direction settled first.
- The page needs HTML5-Canvas the terminal's engine cannot run: reduce the page's client features, or move the visualization onto a PC-based panel — running a PLC-hosted visualization on a remote HMI panel PC is that architecture.
- The page loads on the laptop and on other terminals but never on this one, with addressing proven: stop and take the catalog number, firmware revision and the exact URL to the terminal vendor's support.
Questions asked
Which PanelView Plus terminals have the web browser object?
The object is the ME Web Browser Control, an ActiveX control that renders with Microsoft Internet Explorer. Rockwell Automation limits it to specific PanelView Plus 6 and 7 terminals, and not every catalog number is covered, so confirm yours is on the list before you build the screen around it.
What does CODESYS WebVisu require from the browser?
A current browser with JavaScript enabled and HTML5-Canvas support; CODESYS names Firefox, Chrome and Internet Explorer 9 or newer as examples. When a page stays blank on the terminal, load it in the oldest browser you can find. If it fails there too, the page is asking for features the engine cannot supply, and simplifying the visualization beats fighting the terminal.
What port does the web visualization use?
Port 8080 in the example URL, but the port is a setting on the host, not on the terminal. Read it from the host's visualization settings, and when the laptop test returns a connection refusal, check that port and whether the host's web server is enabled before looking anywhere else.
Why does the URL load on my laptop but not on the terminal?
Usually the terminal sits on a different subnet. With a host at 192.168.10.40 and mask 255.255.255.0, a laptop at 192.168.10.77 shares network 192.168.10.0 and loads the page; a terminal at 192.168.100.5 lands on 192.168.100.0 and cannot. Re-address the terminal into the host's subnet or route it through the gateway.