IMDTouchKnowledge BaseShop main store

Explainer

Where a FactoryTalk View ME Parameter File Links to a Faceplate

HMI and touchscreens Published 6 min read

Short answer

The parameter file-to-faceplate link is not in the parameter file and not in the PLC program. Each overlaid Goto Display button holds it: on the General tab, the Display field names the popup faceplate and the Parameter file field names the value set passed into it. The faceplate display then consumes those values through its global object's parameter definitions.

On this page
  1. The General tab carries both halves of the link
  2. Why the parameter file names no faceplate
  3. How the faceplate consumes the values
  4. Finding the button under the equipment symbol
  5. When the popup does not open at all
  6. What the PLC has to do with it
  7. Worked example: tracing GotoButtonFIC001 into its faceplate
  8. Repairs that keep the pattern intact
  9. Questions asked

Stop digging through the parameter file and the PLC program: neither holds this link. In a FactoryTalk View ME application built around popup faceplates, the pairing lives in the Goto Display button overlaid on each equipment symbol. Open that button's properties and the General tab carries both halves: the Display field names the popup that opens, and the Parameter file field names the value set that popup receives. The file itself only substitutes tag references for numbered placeholders, and the faceplate display consumes them through its global object's parameter definitions. Once you can select the button under the graphic, the whole chain reads in three steps.

Double-click the overlaid button, or right-click it and choose Properties. In the Display settings group on the General tab, two fields do all of the work this article is about. Display selects the destination, the popup faceplate display. Parameter file selects the .par file whose values that instance of the display receives; you browse to it, and the field stores a fixed file reference, not a tag expression.

That pairing is the linkage you were unable to find. The button combines a destination with the input set the destination needs, which is why one faceplate display can serve an entire equipment category: every symbol gets its own button calling the same display through a different parameter file. No table elsewhere in the project records the relationship, because the buttons are the table.

Why the parameter file names no faceplate #

A parameter file is a substitution list, not a navigation record. Its entries map numbered placeholders — #1, #2, #3 — to the tag references for one equipment item, and the numbers are positional: #1 in the file feeds #1 wherever the opened display uses it.

Writing the popup's name into the file would do nothing, because the runtime does not read navigation from the file. The split is what makes the pattern cheap to maintain: retagging a faceplate is a text edit in the file, and changing which faceplate opens is a field change on the button.

How the faceplate consumes the values #

The display named in the button is usually a thin container holding one faceplate global object. Right-click that object and open Global Object Parameter Definitions: the dialog lists the numbered inputs the object expects and shows how each is used inside it. Those definitions are the reusable object's required inputs; the parameter file is the per-equipment fulfillment of them. Inside the object, connections and animations reference the definitions rather than fixed tags, which is why the same object shows one loop's data on one tap and another's on the next.

One variant exists: some projects reference the parameter file in the global object's connections tab instead of on the button. If your button's Parameter file field is empty yet popups still carry per-equipment data, that is where the reference sits — same values, one hop later in the chain.

Finding the button under the equipment symbol #

The activation zone usually overlays the valve or pump graphic, so a click in development selects the drawing, not the button. Three ways in, fastest first:

  • Click just outside the visible symbol but inside its activation zone, and check which object type comes up selected. If it is the graphic, keep working outward.
  • Open the Object Explorer and pick candidate objects by name. A name like GotoButtonFIC001 tells you what it guards; the object type in properties is the verdict.
  • Record the current stacking order, then use Send to Back and Bring to Front to expose buried objects. Stacking decides what an operator's touch hits at runtime, so set the order deliberately before you finish. Overlapping objects hiding the thing you need is a general HMI editing problem, and overlapping graphics hiding HMI symbols works the z-order side of it.

If no button exists in that region, inspect grouped and global objects before concluding the navigation is missing.

When the popup does not open at all #

If the tap does nothing, you are no longer tracing a parameter link — the button itself is not firing. Displays with global connections configured on them can lock Goto Display buttons out entirely; Goto Display buttons locked by HMI global connections covers that failure. Restore navigation first, then return to the display-and-file pairing.

What the PLC has to do with it #

Nothing, as far as navigation goes. PLC tags supply the process values and states the faceplate displays, but which popup opens, and with which value set, is decided entirely inside the HMI project. Go to the PLC only after the button opens the right display, passes the right parameter file, and the definitions match the file entries — and a displayed value is still wrong. At that point the tag, its scaling, or the logic behind it is where to look.

Worked example: tracing GotoButtonFIC001 into its faceplate #

Inputs, each read from the project itself:

  • Button: GotoButtonFIC001, the overlay around the FIC001 flow symbol, selected through the Object Explorer.
  • General tab, Display field: the flow-controller faceplate popup display.
  • General tab, Parameter file field: the .par file holding FIC001's tag references.
  • Faceplate's global object: Global Object Parameter Definitions lists two inputs, #1 and #2.

Rule in words: each entry in the parameter file feeds the definition carrying the same number, and the file must supply one entry per definition with none left unresolved.

The match, written out:

  • Definitions in the global object: 2 (#1, #2).
  • Entries in the parameter file: 2 (#1, #2).
  • 2 supplied against 2 required leaves 0 unresolved. In this project #1 carries the process-value tag reference and #2 the command tag reference, so both connections inside the faceplate close on FIC001.

Decision, with its thresholds:

  • File entries below the definition count — 1 against 2 — means the pairing is incomplete: correct the file. Never clone the display to fix a missing value.
  • Counts matched at 2 of 2 and the wrong equipment's data shows: the button passes the wrong file. Fix the Parameter file field on the button.
  • Counts matched and the data is right but the popup is wrong: fix the Display field on the same button.
  • Both fields right and one value inside the faceplate still wrong: only now move to the tag and the PLC.

Repairs that keep the pattern intact #

  • Change Display and Parameter file together on the existing button; they are configured as a pair on the General tab.
  • Do not add a second hotspot because the first button was hard to find. Two overlapping touch targets make operator selection unpredictable at runtime.
  • Do not move the display name into the parameter file to make the relationship visible; the runtime ignores it and the next maintainer loses the pattern.
  • After any stacking-order change, press the symbol at runtime before calling it done. The order that is easiest to edit is not always the order a gloved operator can hit.

Questions asked

Why does the parameter file contain no reference to the faceplate it opens?

Because the file is a set of substitution values, not a navigation record. The Goto Display button carries both halves of the link: the Display field picks which popup opens, and the Parameter file field picks which value set that popup receives. One faceplate can therefore serve many equipment tags, since each button passes a different file.

Can an HMI tag or expression decide which parameter file the button uses?

No. The Parameter file field on the General tab takes a fixed file reference resolved at design time, not a runtime tag expression. To vary the data, give each equipment symbol its own button pointing at its own file. The swap point between equipment items is the button, never a computed file name.

How do you select the Goto Display button when clicking keeps grabbing the graphic?

Click just outside the visible symbol but inside its activation zone, or open the Object Explorer and select candidate objects by name, such as GotoButtonFIC001. Names like that are a strong hint, but the object type shown in properties is the decisive reading. Record the stacking order before using Send to Back or Bring to Front.

Where do you see what the faceplate does with the parameter values?

Right-click the global object inside the destination display and open Global Object Parameter Definitions. That dialog lists each numbered input the object expects and shows how the supplied values are consumed inside the object. Compare that list against the entries in the parameter file the button passes; every definition needs a matching entry.

Should you look in the PLC program when the wrong faceplate data appears?

Not first. The PLC supplies the process values the faceplate displays, but popup selection comes entirely from the button configuration. Check the PLC only after confirming the button opens the right display, passes the right parameter file, and the global object definitions match the file entries, yet the displayed value is still wrong.

Keep reading

  • Troubleshooting

    Fixing Goto Display Buttons Locked by HMI Global Connections

    While the Global Connections remote display number is active — its DINT tag still holding 21 — FactoryTalk View ME disables every other form of navigation, so Goto Display buttons stay dead whether or not the popup is visible. Write 21 with a one-shot on bit A and let a startup macro on display 21 reset the tag to 0; the popup stays up and the buttons respond.

    HMI and touchscreens

  • Troubleshooting

    Why HMI SFTP Cannot See the SD Card Data Log Files

    On a PanelView Plus 7 Series B terminal, the SFTP service publishes internal storage only; the SD card and USB drives never appear to a remote client. A data log whose path root is removable media cannot be retrieved remotely until you redirect it to internal storage or copy it at the terminal with the file explorer application.

    HMI and touchscreens

  • How-to

    Displaying S7-200 Analog Inputs on a WinCC HMI

    Copy the channel word into V-memory with LD SM0.0 and MOVW AIW0,VW1000, put the CPU in RUN, then read VW1000 with a WinCC tag typed as a 16-bit integer and bind it to a numeric field. Four readings — channel word, destination word, tag, display — isolate any fault; the first one that fails names the layer to fix.

    HMI and touchscreens