Rockwell Automation
PanelView and FactoryTalk View: Rockwell HMI and Visualization
PanelView terminals and the FactoryTalk View families explained: machine edition versus site edition, the PanelView 5000 split, migration paths and the failures that only appear after download.
The HMI is the only part of a control system most of the plant ever touches. It is also the layer where a poor decision is most visible daily and hardest to reverse, because replacing it means retraining every operator on every shift.
The product split
Rockwell’s visualization portfolio contains two lineages that are frequently confused, and the confusion is expensive because the software is not interchangeable.
| Terminal | Designed in | Notes |
|---|---|---|
| PanelView Plus 7 | FactoryTalk View Machine Edition | The mainstream terminal. Standard and Performance variants |
| PanelView 5000 (5310, 5510) | Studio 5000 View Designer | A different product line with a different design tool. Tightly coupled to Logix, tag browsing rather than mapping |
| PanelView Standard / PanelView Plus 6 | Legacy | Discontinued or approaching it. Check the catalogue number |
Studio 5000 View Designer is not FactoryTalk View. They share a vendor and nothing else. An application built in one cannot be opened in the other, and a plant standardising on PanelView 5000 has standardised on a separate toolchain from every PanelView Plus terminal it already owns.
Machine Edition or Site Edition
The choice that gets made wrong most often.
| FactoryTalk View ME | FactoryTalk View SE | |
|---|---|---|
| Runs on | A PanelView Plus terminal, or a PC as a standalone runtime | Windows servers and clients |
| Scope | One machine or one line, one screen at a time | Plant-wide, multiple clients, distributed |
| Architecture | Standalone. No server | Client-server. Local or distributed, optionally redundant |
| Users and security | Basic | Full FactoryTalk Directory security, per-area access |
| History and alarming | Local, limited | Server-side alarming and event history |
| Real cost | Terminal plus licence | Servers, Windows licences, FactoryTalk licences, and the IT support to keep them patched |
The rule we apply: if the answer is one machine and one operator position, use ME. If you need more than one simultaneous view of the same process, alarm history that survives a terminal replacement, or user-level access control across areas, you need SE and should budget for the server infrastructure honestly at the start rather than discovering it at commissioning.
Where plants go wrong is choosing SE for a single line because it sounds more capable, then carrying a Windows server, its patching burden and its licence renewals for one screen. The opposite mistake, stretching ME across a plant with six terminals that each need the same alarm history, is less common but harder to unwind.
How HMIs actually fail
It works on the desk and fails on the panel. The most common support call in this whole category. The application tests clean in FactoryTalk View Studio, gets downloaded, and then loses tags and throws communication errors.
The cause is almost always the communication path, not the application. FactoryTalk Linx, previously RSLinx Enterprise, resolves a named shortcut to a controller path. Anything that changes that path invalidates the shortcut: a controller firmware flash, a chassis slot change, a new IP address, a restored backup from a different machine. The application is fine. The path underneath it is not. Start at the shortcut, not at the code.
Tag browse works, runtime does not. Browsing tags in the editor uses the engineer’s workstation path. Runtime uses the terminal’s path. They are configured separately and can disagree, which produces an application that looks correct in every offline test.
Graphics imported from elsewhere. Screens built by importing artwork from a drawing package render slowly on terminal hardware and scale badly. Native graphics objects, drawn in the tool, consistently outperform imported assets on the same terminal.
Screens designed for the designer. Colour used decoratively rather than for state, buttons sized for a mouse rather than a gloved hand, and label hierarchies that read well on a twenty-seven inch monitor and not at all on a ten inch panel at arm’s length. ISA-101 is the reference standard here; on a standalone machine it is worth applying selectively rather than wholesale.
Migration
The PanelView Plus 6 to 7 path is generally straightforward, an application conversion plus hardware. The paths that are not straightforward:
- PanelView Standard to PanelView Plus is a rebuild. Different software lineage entirely
- PanelView Plus to PanelView 5000 is a rebuild, because ME applications do not open in View Designer
- ME to SE is a rebuild plus an infrastructure project
Budget migrations on the software lineage, not on the hardware generation. Hardware that looks like a like-for-like swap frequently is not.
What we do here
- Decide ME or SE against the actual operational requirement, and state the infrastructure cost up front
- Review screen design against ISA-101 where it earns its keep on the equipment in question
- Diagnose communication and path faults rather than rebuilding applications that were never broken
- Plan terminal migrations by software lineage, with the rebuild cost identified honestly
- Set HMI standards so screens across a plant behave consistently for operators moving between lines
Deeper
- PanelView Migration Paths — which upgrades are conversions and which are rebuilds
- FactoryTalk View SE vs ME — the decision, the real infrastructure cost, and how to avoid buying a server for one screen
Back to the Rockwell Automation hub, or across to Networks and Communications, where most HMI communication faults actually originate.