How-to
One FactoryTalk View ME Project Builds One PanelView Runtime
Short answer
One FactoryTalk View ME project creates exactly one .mer runtime, and that runtime runs on one PanelView Plus terminal. Two terminals therefore take the same .mer loaded on both, or two separate projects. For one controller and two identical 2711P terminals, build once and load twice; split into two projects only when screen size, resolution or communication targets differ.
On this page
You cannot hold two PanelView Plus terminals inside one FactoryTalk View ME project. Each ME project compiles into exactly one .mer runtime file, and that file runs on one terminal. With one 5069-L306ER controller and two 2711P panels, that leaves two designs that work: build one .mer and load the same file on both terminals, or maintain two separate ME projects. The choice is mechanical: same model, screen size and resolution on both terminals, firmware that accepts the runtime version, and one shared communication path take the single .mer. A different resolution, different communication targets, or screen sets that must be cleanly separated take two projects. Below are the decision rule, the build and deploy steps, the security pattern for splitting screens between stations, and a worked deployment for the one-controller, two-terminal case.
What one ME project builds #
One ME application bundles every part of the operator interface: graphic displays, the HMI tag database, global objects, parameter files, project settings that include screen resolution, and the RSLinx Enterprise communication configuration. The Create Runtime Application command compiles all of it into one .mer. The terminal loads one application at a time, and nothing inside the file points to a second station or a fleet. Open a project in Studio and look for a place to add a second terminal: there is no node for one, and no multi-target setting hides behind it. That settles the architecture question in ten seconds — one project, one compile, one terminal.
Two projects side by side share nothing. You can open two instances of the development software on one computer and copy-paste objects between them, but neither project sees the other's graphics screens, HMI tags, global objects, parameter files, or project and terminal configuration. Every change that should reach both stations gets made twice, in both places, by hand.
Choose between one shared .mer and two projects #
Run one shared .mer on both terminals when all four checks pass:
- Both terminals are the same model with the same screen size and resolution. Read each from the terminal configuration screens before you build anything.
- Both terminals run firmware that accepts the runtime version you build. The vendor's tested answer documents a PanelView Plus 6 on version 8 firmware running a pre-version-6 .mer built for 5.10, so an older runtime on newer firmware is often acceptable — match your exact pair against the published runtime-to-firmware compatibility table.
- Both terminals reach the controller through the same communication path.
- Every screen may exist on both terminals, with access limited by security where the stations have different roles.
Identical terminals earn their keep in the field: when one fails, operators move to the other and lose nothing, and while you troubleshoot, any part of the process is reachable from either station. Large DCS and SCADA systems run the same way — any operator station sees everything — and the identical-station discipline is written up for Siemens platforms in configuring multiple identical PCS 7 OS stations in Simatic Manager.
Split into two projects when any check fails: the terminals differ in size or resolution, the stations have genuinely different roles that security gating would tangle, or each terminal needs its own communication target. Two projects cost double maintenance for the life of the machine: one change touching both stations is edited twice, compiled twice, and transferred twice.
Build the runtime and deploy it to both terminals #
- Read the model, screen size and firmware revision from each terminal's configuration screens. If they differ, stop and split into two projects, or bring both terminals to matching firmware first.
- Create the ME application at the terminals' shared resolution.
- In RSLinx Enterprise Communication Setup, create one device shortcut to the controller. Set the Design (Local) tab to the path from your development computer and the Runtime (Target) tab to the path the terminals use at runtime.
- Point every tag reference at that one shortcut name, and never hard-code a communication path inside an object's tag string.
- When both terminals share that path, run Create Runtime Application once and put a revision number in the .mer file name so the floor can tell builds apart.
- When the terminals reach the controller through different paths, define every target in the communication configuration, select the correct target, compile that .mer, switch targets, and compile the second one. Name each file with its terminal ID and revision number.
- Transfer the file to each terminal, load it, and set it to run at startup.
A job like yours — one controller, one path — stops at step 5. Step 6 exists for split routing, such as one station behind a different network segment or bridge, and it is also where each two-project variant is compiled once per project.
Split screens per station with security groups #
If both units run the same .mer but each station should reach only its own screens, gate access with users and security codes. The working pattern for two stations:
- One super user belonging to both groups — the programmer's account, whose credentials nobody else gets.
- Admin1 in group A only, for station 1 screens and parameters.
- Admin2 in group B only, for station 2 screens and parameters.
- Each screen's security code assigned to group A or group B.
- On terminal 1, change Admin2's password at runtime so nobody there can log in as Admin2; on terminal 2, change Admin1's the same way.
The lockout works because a runtime password change stays local to the terminal where it was made. Confirm your transfer-and-load procedure does not overwrite runtime user accounts, because a later download can silently undo it. The alternative is two runtimes, each carrying only its own group: that removes the password juggling but returns you to two builds, and both schemes get convoluted fast with many users and no directory service behind them. Moving authentication into the controller scales better — an RFID badge reader feeding the PLC, whose logic grants permission tags that both terminals read — and adding a user then never touches either terminal.
One safety limit on this pattern: gating must never hide alarms or stop controls from the station nearest the hazard, and every operator position has to be able to see and act on what its own process is doing.
Deploying one .mer to two 2711P terminals on one 5069-L306ER #
Inputs, and where each comes from:
- One 5069-L306ER controller and two 2711P PanelView Plus terminals — the case at hand.
- Both terminals at the same screen size and resolution — assumed here, verified in step 1 before the build.
- One communication shortcut to the controller shared by both terminals — step 3.
- A runtime version both firmware revisions accept — the published tested example is a 5.10 .mer running on a PanelView Plus 6 with version 8 firmware.
The rule, in words: one project compiles once into one .mer for one terminal configuration, and identical terminals take the same file loaded once each.
The arithmetic: builds = 1 project × 1 compile = 1 .mer. Loads = 1 .mer × 2 terminals = 2 loads. A later shared change costs 1 edit, 1 recompile, and 2 transfers. The two-project alternative for the same two stations costs 1 change × 2 projects = 2 edits, 2 compiles, and 2 transfers, every time.
Result: one build and two loads put both stations live on identical screens, and every future change ships as a single rebuild pushed twice.
Decision: with the terminals matching in model, size, resolution and accepted runtime version, and one shared communication path, build the single .mer and load it on both terminals. If size or resolution differs, the firmware pair will not take the runtime version, or each terminal needs its own target, build two projects and name each .mer for its terminal.
When two stations really need one application #
If the requirement is one application serving several operator positions at once — shared graphics, one tag database, the same screens reachable everywhere — that is the distributed HMI architecture, not the terminal architecture, and no project restructuring in ME will deliver it. FactoryTalk View Site Edition, the network-distributed member of the same family, is built for multiple clients against shared servers, and other platforms offer the same shape. That kind of runtime runs on industrial panel PCs mounted at the line, and one PC can serve several operator screens from a single application — the pattern in running one HMI interface on multiple touchscreens from one PC. That route removes the one-runtime-per-terminal limit, and the two-project maintenance tax with it. If it still feels like a missed feature in ME, that is because multi-terminal operation was never the terminal's job.
Questions asked
Can I get the project back out of a .mer file?
Yes, through the vendor's documented restore procedure, which recovers an editable application from the runtime archive; the published walk-through covers restoring from a version 4.0-era runtime file. Treat it as recovery after a lost project rather than version control, and keep the original Studio project as the master copy that you edit and recompile.
Do the two terminals open separate connections to the controller?
Yes. Each PanelView Plus opens and maintains its own connection and reads the same controller tags independently, so nothing in the controller program changes when the second terminal is added. The limit is connection capacity: the controller's published specifications state how many connections it supports, and every HMI, programming terminal and SCADA client consumes one, so check the spare count before adding stations.
Can I load the .mer without FactoryTalk View Studio?
Yes. Studio is only needed to compile the file. The terminal's own configuration menu, Terminal Settings, is where you point the terminal at a runtime file on storage or the network, load it, and set it to run at startup; the vendor's published walk-through shows copying the .mer to the terminal this way. That is also how a spare terminal gets a runtime with no development machine on site.
Why does a value entered at station 1 never appear at station 2?
Because it was written to an HMI tag. HMI tags live only inside each terminal's runtime, so two terminals running the same .mer keep separate local values for them. Controller tags live in the 5069-L306ER and both terminals read them independently, so any value both stations must share, such as a setpoint, a batch counter or a mode bit, belongs in a controller tag.