IMDTouchKnowledge BaseShop main store

How-to

Implementing operator screenshots in mappView with GetScreenCapture

HMI and touchscreens Published 5 min read

Short answer

Use the mappView GetScreenCapture action documented in Automation Help 6 for operator screenshots; do not carry the VC4 VcScrSht library into mappView. Confirm the action appears in the help of your installed Automation Studio release before you wire the button, because the feature shipped first as an Engineering Sample.

On this page
  1. Why VcScrSht stays behind with VC4
  2. Check the installed release before you build
  3. Build the control from the documented action
  4. The worked decision: one VC4 project, one mappView target, Automation Studio 6
  5. Verify the capture before operators rely on it
  6. When the release does not document the action
  7. Questions asked

Use the GetScreenCapture action. mappView does not inherit the VC4 screenshot library VcScrSht, and you should not try to bind it in: Automation Help 6 documents GetScreenCapture as the mappView action for screen capture, so the migration is a re-implementation on that action, not a library port. One gate applies before you build: the feature entered the field in an Automation Studio 6 Engineering Sample while still described as upcoming, so confirm your installed release documents the action before the operator's button depends on it. This article covers why the VC4 library stays behind, the build order for the capture control, one worked decision on a real migration, and how to verify the capture.

Why VcScrSht stays behind with VC4 #

VC4 and mappView are different HMI environments. mappView builds web-based HMI pages — the vendor's description is web-enabled HMI screens — while VcScrSht is a library written for the VC4 runtime, and nothing in the vendor documentation presents it as a mappView component. The mechanism documented for mappView is a single action, GetScreenCapture, specified in Automation Help 6. That asymmetry sets the whole migration:

Mechanism Environment Decision
VcScrSht VC4 runtime Keep it in the VC4 project it serves
GetScreenCapture mappView The only documented path; build on it

Check the installed release before you build #

One fact here is dated by design: the screenshot feature entered the field in an Automation Studio 6 Engineering Sample, described as upcoming, with the action already in the help. Documentation written against a sample does not guarantee the action in your build, so the gate is local. Open the help shipped with the exact installation that will build the project — not a newer install on another desk — and search GetScreenCapture, then read that version's release notes to see whether the feature is listed as released or as sample. The worked decision below turns that one search into a build-or-defer call.

Build the control from the documented action #

If the mappView application is new, Automation Studio 6 also ships new mappView templates to start from. The build order for the capture control:

  1. Open Automation Help for the exact Automation Studio installation that will build the project.
  2. Search GetScreenCapture and read the action's documented configuration, parameters and result handling. That page is the whole specification — the parameter names, where the action attaches to the control, and what it returns on success and on failure — and none of it carries over from VC4 habits.
  3. Place the operator button on the mappView page and bind its press event to the action, configured exactly as the help shows.
  4. Handle the action's result the way the help specifies, so a failed capture is observable instead of silent.
  5. Build and transfer the project: the runtime the operator touches is the transferred build, which is why an HMI edit needs a new runtime download.
  6. Test on the target, with an operator-permission account, on the page the operators actually use.

The worked decision: one VC4 project, one mappView target, Automation Studio 6 #

The case is the migration that prompted this article: operators take screenshots through VcScrSht today, and the replacement visualization is mappView built with Automation Studio 6.

Inputs. From that case: 1 screenshot mechanism in service — VcScrSht, inside the VC4 project. From the vendor documentation: 1 mechanism documented for mappView — the GetScreenCapture action in Automation Help 6 — and 0 sources that present VcScrSht as a mappView component. From the feature's introduction status: available in an Automation Studio 6 Engineering Sample while described as upcoming.

Rule. The migration uses the mechanism the target environment's documentation supports, and the build starts only when the help shipped with the installed release documents that mechanism.

Arithmetic. Mechanisms documented for mappView: 1. Mechanisms carried over from VC4 that are documented for mappView: 0. 1 − 0 = 1 supported path, so the choice of mechanism is forced. The deployment gate then counts a single input, the help search on the engineering station: a search that returns the GetScreenCapture page is 1, and the build proceeds; a search that returns nothing is 0, and the capture stays with VC4.

Result and decision. Build the operator button on GetScreenCapture alone. Threshold: 1 documented action in the installed help means build now; 0 means defer.

Verify the capture before operators rely on it #

Trigger the button and confirm the observable result the help documents. When no capture appears, read the runtime diagnostics and the action's result handling before touching tags: the failure has one of two homes — the control or its event binding, or feature support missing from the installed release — and the diagnostics say which. Two observations prove nothing on their own: a button that renders on the page, and a VC4 project that captured correctly yesterday.

If the same button captures and then navigates, order the actions so the capture completes first. On other HMI platforms, a capture fired at the same instant as a screen reset has produced an image of the wrong screen — the screenshot delay before a reset action failure.

This is the same function-by-function discipline as validating HMI variables during a software migration: the new environment proves everything the old one did, one feature at a time.

When the release does not document the action #

Deferral is not abandonment: the operators keep the VC4 capture until a release that documents GetScreenCapture is installed, and the screen migration proceeds without it. Do not rebuild the capture from screen objects — widgets assemble a page, but an image of the rendered page is a runtime capability, and only the documented action reaches it. Working around a missing feature is familiar elsewhere; one legacy SCADA package had its inactivity auto-logout implemented without a native function, but that was timer and tag logic a platform can express, and capture is not. Community samples fill adjacent gaps, not this one: a mappView data-recorder sample built on mappData is documented for up to 3 concurrent web clients, and that limit belongs to the sample, not to the capture action.

Questions asked

Can I bind the VC4 VcScrSht library into a mappView project?

No. VcScrSht belongs to the VC4 runtime and nothing in the vendor documentation presents it as a mappView component. Keep it in the VC4 project it serves and implement the mappView capture with the GetScreenCapture action. Carrying the library over as a drop-in is the fastest way to lose the screenshot function mid-migration.

Is GetScreenCapture available in every Automation Studio 6 installation?

Not automatically. The feature entered the field through an Automation Studio 6 Engineering Sample while described as upcoming, so availability is settled per installation: open the help shipped with the exact build, search GetScreenCapture, and read that version's release notes for released versus sample status. Two stations on different versions can differ, so check each one that builds or runs the project.

The operator presses the button and no capture appears. Where do I look first?

Read the runtime diagnostics before touching tags. The failure has two possible homes: the control or its event binding, or feature support missing from the installed release, and the diagnostics separate them. A rendered button proves the control exists, not that the action is supported. Re-test after every Automation Studio upgrade, because support can arrive or change between versions.

Can I rebuild the capture myself if my release does not document the action?

No. A page is built from widgets, but an image of the rendered page is a runtime capability, so the capture cannot be re-created with screen objects. Keep the operators on the VC4 capture meanwhile and cut the function over only after the mappView button passes its test in the target runtime.

Keep reading

  • How-to

    How to migrate a WinCC flexible project to TIA Portal

    One TIA Portal installation replaces both STEP 7 Classic and WinCC flexible, but the two project types move differently: the STEP 7 V5.x project is imported, and the WinCC flexible 2008 project is migrated through an intermediate release because the newest TIA Portal versions no longer offer that migration. Verify the exact S7-300 CPU and panel against the device lists and license STEP 7 and WinCC Comfort separately.

    HMI and touchscreens

  • How-to

    Loading an ST6400 VML upload into Operator Terminal Expert

    A program pulled from an ST6400 panel is a VML file, and EcoStruxure Operator Terminal Expert V3.1 SP1 and V3.2 have no project-upload function that converts it into an editable PC project. Load the VML back through the panel's hardware configuration screen using USB storage. To edit the application, get the original engineering project.

    HMI and touchscreens

  • How-to

    Reading an old HMI program before panel replacement

    The software family that programs the replacement panel cannot read the old one: an EA9-family release such as C-more 6.40 will not open or upload a project from an EA7-T8C. Install the EA7-family software, read the project with it, keep the original upload untouched, and convert only a copy through the documented path to the EA9-T8CL.

    HMI and touchscreens