IMDTouchKnowledge BaseShop main store

Explainer

RSView Studio ME vs ME Station for a PanelView Plus

HMI and touchscreens Published 5 min read

Short answer

To program a PanelView Plus you need only the development package, FactoryTalk View Studio for Machine Edition, catalog number 9701-VWSTMENE. The terminal already ships with the Machine Edition runtime embedded, so no separate runtime license is needed for it. ME Station is a runtime-only product for running compiled .MER applications on an ordinary PC, licensed by screen count.

On this page
  1. Two products, two jobs
  2. What the PanelView Plus already contains
  3. The Studio test runtime is time-limited
  4. Worked example: one PanelView Plus and one engineering PC
  5. What to order for each role
  6. Downloading the project to the terminal
  7. When Machine Edition Station is the right buy
  8. Questions asked

To program a PanelView Plus you order exactly one software product: FactoryTalk View Studio for Machine Edition, catalog number 9701-VWSTMENE. The runtime that executes the application is already embedded in the terminal, so nothing else is required to develop, test and deploy. The product this question confuses it with, Machine Edition Station, is a runtime-only license for running the compiled application on an ordinary PC, licensed by the number of screens in the project. If your operator interface lives on PanelView Plus hardware, you never buy it.

Two products, two jobs #

FactoryTalk View Machine Edition reaches you as two separately licensed deliverables, and the confusion comes from treating them as one.

Studio for Machine Edition is the development package: screen editor, tag database, alarm configuration, the download path to the terminal, and a built-in runtime for testing on the engineering PC. Rockwell Automation's published catalog-number answer for this product returns 9701-VWSTMENE, and current perpetual packaging lists the same development package as 9701M-VWSTNMRT10. It is licensed per development seat, one seat for each engineer who edits projects.

Machine Edition Station is the runtime-only package. It executes a compiled .MER file on a Windows PC and does nothing else; it cannot open a project for editing. You license it by the number of screens the running project displays, which is why the licensing moves with project size on a PC and not on a terminal.

The naming is the trap. RSView is the earlier brand of this family, and the field still says RSView Studio ME and RSView ME Station for the two products above; the same catalog numbers answer under today's FactoryTalk View name. Studio always marks the editing side; Station, or ME without Studio, always marks the runtime side. For the broader pairing of packages to panels, read which HMI software works with which HMI panel hardware.

What the PanelView Plus already contains #

A PanelView Plus is a display with an embedded computer, and the Machine Edition runtime ships installed on that computer from the factory. The terminal runs .MER applications out of the box; there is no runtime license to add for it and no screen count to declare. Buying Station for a terminal-only deployment buys you nothing. When you need to confirm what a specific terminal is executing, the startup reference is how to find the runtime file an HMI terminal actually loads.

The Studio test runtime is time-limited #

Studio embeds a runtime for testing, so you can launch the built project on the engineering PC and verify screens, tag values and alarms before you touch hardware. The run is deliberately time-limited: when the window ends, the application closes. That is enough to check an animation or a tag path, and it is never a production host. Do not leave a timed test run as the operator interface on a live machine, because the screens will close with the process still running. A PC that must host the application beyond testing takes a Station license, and the project then has to be built for that host, the same discipline as compiling the uploaded MER to the ME Station version.

Worked example: one PanelView Plus and one engineering PC #

Inputs, each with its source:

  • Terminals to program: 1 PanelView Plus — the case in the question.
  • Engineers editing projects: 1, working on 1 engineering PC — a typical single-seat setup.
  • PCs that will host the .MER in production: 0 — the application runs only on the terminal.

Rule in words: order one Studio seat per engineer who edits, one Station license per production PC that hosts the .MER, and no runtimes for terminals, because every terminal already contains one.

Arithmetic:

  • Studio seats: 1 engineer × 1 seat = 1 copy of catalog number 9701-VWSTMENE.
  • Station licenses: 0 hosting PCs × 1 license = 0.
  • Terminal runtimes to buy: 1 terminal − 1 embedded runtime = 0.
  • Order total: 1 product.

Variant: add one control-room PC running the same screens, and the Station line becomes 1 license sized to that project's screen count, for an order of 2 products.

Decision: with no production PC host, buy 9701-VWSTMENE and nothing else. The threshold to watch is simple — every PC that hosts the .MER beyond the Studio test window adds exactly one Station license, and every additional engineer editing at the same time adds one Studio seat.

What to order for each role #

Role Product Catalog number License metric
Engineering PC: develop, test, download FactoryTalk View Studio for Machine Edition 9701-VWSTMENE 1 per development seat
Production PC hosting the .MER Machine Edition Station (runtime only) current numbers in Rockwell's Machine Edition catalog answer screens in the running project
Operator interface on the terminal Embedded Machine Edition runtime included with the PanelView Plus nothing to buy

Downloading the project to the terminal #

Deployment to the terminal is a download, not an installation. Build the project in Studio as a .MER at the runtime version the terminal runs, connect the engineering PC and the terminal over Ethernet, put the terminal into its configuration mode, and send the file from Studio; the terminal loads that .MER from then on. The version match is the step that bites when it is skipped, and fixing an HMI MER runtime version mismatch covers the symptom. Remember what you sent: the .MER is the compiled deliverable, which is why the compiled HMI project view is not for editing — changes happen back in the Studio project.

When Machine Edition Station is the right buy #

Three cases justify a Station license. One: evaluating an application on a desktop before any terminal hardware exists. Two: a permanent PC-based operator station in a control room. Three: hosting screens on a PC at the machine where no terminal is mounted — in that case the host is a computer you specify, and industrial panel PCs are the usual choice at the machine, with the Station license sized to the screen count of the project it runs. Every deployment that ends on PanelView Plus hardware stops at the single Studio purchase.

Questions asked

Is RSView Machine Edition the same software as FactoryTalk View Machine Edition?

RSView is the earlier brand of the family sold today as FactoryTalk View, so the names refer to the same product line. The label tells you which side you are buying: Studio marks the editing package, catalog number 9701-VWSTMENE, while ME or Station without Studio means the PC runtime. Buy by function, not by the brand printed on the quote.

Can one Studio ME license program several PanelView Plus terminals?

Yes. The Studio license is counted per development seat, not per terminal, so one seat can build, test and download to as many PanelView Plus terminals as your line needs. Buy a second seat only when a second engineer must edit projects at the same time. Terminals never consume Studio licenses, because each one already contains its runtime.

Does the number of screens in my project change what I buy for a PanelView Plus?

No. Screen count is the licensing metric only for Machine Edition Station running on a PC. The runtime embedded in a PanelView Plus terminal is included with the hardware no matter how many screens the .MER contains, so the practical ceiling on the terminal is its memory, not licensing.

What happens when the Studio ME test runtime reaches its time limit?

The running application closes when the time window ends. The test runtime exists so you can verify screens, tags and alarms on the engineering PC during development; it is not a production host. Any PC that must run the application beyond testing needs its own Station license, sized to the project's screen count.

Keep reading

  • How-to

    How to find configuration software for a legacy TP070 touch panel

    A TP070 is configured with TP Designer, the add-on that shipped in the STEP 7 Micro/WIN Toolbox era and runs under Micro/WIN V4 — not with WinCC flexible, ProTool or TIA Portal. Read the order number on the rear label to match the toolset to the panel's firmware generation, source the package through the manufacturer's own channels, and transfer over PPI at 9.6 kbit/s.

    HMI and touchscreens

  • How-to

    Replacing a Fleet of PanelView 550 Terminals on DH-485

    There is no direct swap: the PanelView 550 is Silver Series, so each terminal is a migration. The PanelView Plus 6 600 keeps the 550 cutout but needs a third-party DH-485 adapter; a Plus 6 700 takes the 2711P-RN6 but modifies the cutout. Audit all 25 catalog numbers, convert one application in FactoryTalk View Studio ME, pilot one machine, then buy the fleet.

    HMI and touchscreens

  • Troubleshooting

    OP15 project recovery: ComText, ProTool or ProSave

    Recovering a project from a Siemens OP15 starts with the panel's generation, not software preference. First-generation OP5 and OP15 hardware belongs to ComText, second-generation hardware belongs to ProTool, and firmware version 2.2 draws the line. ProSave is not in the decision: it writes a backup image, not an editable project, and the OP15 is not on its supported-device list.

    HMI and touchscreens