Studio 5000 ยท Track 12 ยท FactoryTalk View

The Window into Logix

The controller runs the machine; the HMI is how humans run the controller. Rockwell's answer is FactoryTalk View โ€” ME on PanelView Plus terminals at the machine, SE for distributed plant-wide SCADA โ€” talking to Logix through FactoryTalk Linx. The superpower: displays bind directly to controller tags. No register map, no middleman.

๐Ÿ–ฅ๏ธ ME ยท PanelView๐Ÿญ SE ยท distributed๐Ÿ”— Linx shortcut
01 ยท A PanelView, live

Push buttons write tags, displays read them

A PanelView Plus screen for a mix tank, wired to the controller tags on the right. Press START โ€” watch HMI_StartPB pulse true, the controller's logic latch Pump_Run, and the level climb. Past 85 % the tag-based alarm fires and the banner takes over. Then flip to ๐Ÿ”ง Design mode to see what the screen really is: graphic objects with tag bindings.

MIX TANK 3--:--
โ–ฎ {::[Mixer]Tank_Level}
32.0 % # {::[Mixer]Tank_Level}
PUMP RUNNING โ— {::[Mixer]Pump_Run}
โฌ“ momentary โ†’ {::[Mixer]HMI_StartPB} / {::[Mixer]HMI_StopPB}
PANELVIEW PLUS 7 ยท 9"

ControlLogix ยท controller tags (via Linx shortcut "Mixer")

HMI_StartPB0
HMI_StopPB0
Pump_Run0
Tank_Level32.0
ALM_HiLevel0

The HMI never "owns" these โ€” it reads and writes the controller's tags over EtherNet/IP. The start/stop logic (the seal-in, the alarm compare) lives in the PLC, where it belongs.

runtime โ€” press the buttons drain valve is always open a little โ€” stop the pump and the level falls

That yellow chip syntax โ€” {::[Mixer]Tank_Level} โ€” is a direct tag reference: shortcut name in brackets, then the live Logix tag, browsed straight from the controller's tag database. Rename the tag in Studio 5000 and View's cross-reference finds every display that breaks. Compare that to the register-mapping ritual every non-Rockwell HMI still performs.

02 ยท The vocabulary

ME, SE & the rules of good screens

๐Ÿ–ฅ๏ธ View ME (Machine Edition). One operator station: runs on PanelView Plus terminals (or a PC) as a compiled .mer runtime. Standalone, robust, lives at the machine. Most plants are full of these.

๐Ÿญ View SE (Site Edition). Distributed SCADA: a FactoryTalk Directory, HMI servers with redundancy, clients anywhere on the network, plant-wide alarming and history. When twelve screens must agree on one truth, it's SE.

๐Ÿ”— FactoryTalk Linx & shortcuts. The comms layer. You define a shortcut (a named pointer to a controller) once; every tag reference rides it. Re-point the shortcut at a new PLC and the whole application follows.

โฌ“ Momentary buttons need PLC logic. A momentary PB writes 1 while pressed, 0 on release โ€” so the latch must live in the controller (seal-in or ALMD-style logic). Never use a maintained HMI button as the only thing keeping a machine running: if comms drop, the controller must decide, not the screen.

03 ยท Check yourself

ME or SE?

A plant has twelve machines, each with its own PanelView Plus terminal showing only that machine's status. No shared history, no central alarm view needed. Which FactoryTalk View edition fits?