Troubleshooting
PlantPAx faceplate display not found at runtime creation
Short answer
Runtime creation fails with display not found because the PlantPAx faceplate button computes a display name that matches no display in the project. With HMI_Lib = P and HMI_Type = Motor, the expression builds "(P-ME) Motor-Faceplate", not the P_Motor-Faceplate you named. Compare the computed string against the display list character by character, rename the display to the computed name, and rebuild the .mer.
On this page
- Why does runtime creation report the PlantPAx faceplate display as not found?
- What display name does the expression actually build?
- How do I compare the computed name with the display name character by character?
- Do missing Parameter Files or String Servers cause this error?
- Could a patch rollup fix the display not found error?
- How do I isolate the failing button when the Diagnostics List shows nothing?
- What is the fix that makes the .mer build?
- Which FactoryTalk View ME versions support the PlantPAx faceplates?
- Questions asked
The display-not-found error during runtime creation is a name-resolution failure, not a missing screen: your P_Motor-Faceplate and P_ValveC-Faceplate displays exist, but the PlantPAx faceplate button never asks for those names. By design its Variable Screen Name expression concatenates the object's HMI_Lib and HMI_Type parameter values into a different string, and the .mer build stops at the first display reference it cannot resolve to a display in the project. Fix it in this order: evaluate the expression with the failing instance's actual parameter values, set the result beside the display name in the Studio display list, and make the two strings identical character for character — usually by renaming the display. Run that comparison before Parameter Files, String Servers or patch rollups enter the picture, because it decides the case on its own. The numbers below use the reported case: FactoryTalk View ME Studio and runtime at version 15, PlantPAx library 4.10.06, placeholder #102.
Why does runtime creation report the PlantPAx faceplate display as not found? #
Runtime creation stops because the faceplate button's Variable Screen Name expression computes a display name string that matches no display in your project exactly, and the .mer build refuses a display reference it cannot resolve to a real screen.
Runtime creation resolves every navigation target in a ME project against the flat display list before the .mer is written, and the PlantPAx library's release notes document the display-not-found message as the outcome when a name an object builds does not resolve. The failing button is the shipped PlantPAx global object, so Variable Screen Name is its intended behavior, not an option you mis-set. Because the target is computed from parameter values at build time, a display that merely looks similar never satisfies the lookup, and the Diagnostics List stays vague because the build trips on a string, not on a tag, a driver or a device. That is why a project can hold both faceplate displays and still fail the build.
What display name does the expression actually build? #
With HMI_Lib set to P and HMI_Type set to Motor, the expression builds the 22-character string (P-ME) Motor-Faceplate, and runtime creation searches the display list for exactly that name, leading parenthesis and space included.
The expression on the reported global object button is:
"(" + {#102.HMI_Lib} + "-ME) " + {#102.HMI_Type} + "-Faceplate"
Work it with the values the display names imply — HMI_Lib = P, HMI_Type = Motor — and concatenate term by term:
"("produces(— one character, a left parenthesis."(" + "P"produces(P— two characters."(P" + "-ME) "produces(P-ME)— seven characters, the seventh a space."(P-ME) " + "Motor"produces(P-ME) Motor— twelve characters."(P-ME) Motor" + "-Faceplate"produces(P-ME) Motor-Faceplate— twenty-two characters.
That 22-character result is what the build searches for. The project's display list holds P_Motor-Faceplate, 17 characters whose first character is P. Position 1 already differs — ( against P — so nothing matches and the build reports the display as not found. The valve fails the same way: HMI_Type = ValveC computes (P-ME) ValveC-Faceplate, against P_ValveC-Faceplate. Both computations are worked examples using the values the display names imply; read your instance's real HMI_Lib and HMI_Type before trusting the result, because one different character moves the target somewhere else.
How do I compare the computed name with the display name character by character? #
Open the parameter file the failing instance references, read the values it passes to #102 for HMI_Lib and HMI_Type, build the string by hand, and set it beside the display name in the Studio display list for a left-to-right character comparison.
- Read HMI_Lib and HMI_Type from the parameter file the failing instance references. Each placed copy of a global object substitutes its own values into #102, so read them from the failing instance, not from a working sibling.
- Concatenate the expression term by term on paper, keeping every parenthesis, hyphen and space, and write the result between quotes.
- Set the result beside the display name in the Studio display list and compare left to right: first character, each separator, the -Faceplate suffix.
- If the full build message prints a path or a prefix, compare that the same way. A ME display list is flat, so for the display itself the name is the whole comparison.
A spacing-only check misses this fault. The reported case had already ruled out spacing because nothing sits spaced wrong — the difference is the entire leading (P-ME) segment, a different string from the first character on. If your hand-built string does equal the display name exactly, the mismatch theory is dead for that instance; go isolate the object and capture the full message instead of re-reading the expression.
Do missing Parameter Files or String Servers cause this error? #
No — a missing parameter file or string server produces its own error about that resource, and adding either on a guess costs a rebuild without touching the real fault, so the computed-name comparison stays ahead of both.
A parameter file's job here is to hand the button the placeholder values the expression concatenates, HMI_Lib and HMI_Type included, and where a FactoryTalk View ME parameter file links to a faceplate walks that connection in detail. A wrong value in the file changes the computed name, which the character comparison already catches; a missing or broken file raises its own parameter-file error, not a display that cannot be found. String Servers hold translated text for language switching and add no displays to the project. Your displays exist and the build is asking for a name nobody carries, so added resources cannot close that gap: keep Parameter Files and String Servers as they are until the comparison says otherwise.
Could a patch rollup fix the display not found error? #
Only if the captured build message shows a corrupted path — one field report on this fault claims FactoryTalk added a period into a file path after an update, but it names no confirmed fix, so check the printed path before touching any patch level.
The PlantPAx library release notes document the display-not-found message as a name-resolution outcome, and they are where a genuine patch defect would be published for your exact library version. The field report naming an added period cites no knowledge base entry and no rollup. So the decision is: read the path in the full build message. If it shows an added period or another corrupted segment, take that message to the vendor's official support channel and apply the fix they publish for your version. If the path is clean, updating FactoryTalk View is a detour that leaves the computed-string mismatch in place.
How do I isolate the failing button when the Diagnostics List shows nothing? #
Reproduce the runtime creation, keep the entire error text instead of the summary line, and cut the project down — one object type or one button at a time — until the failure names the instance that computes the bad string.
- Save the complete runtime-creation message with the versions attached: Studio 15, runtime 15, PlantPAx 4.10.06 in the reported case.
- Note the object type and the instance. Motor and valve faceplates compute different names, so one type can fail while another builds.
- Swap the global object button for a plain navigation button with the display name typed literally. If the .mer then builds, the computed expression is the difference.
- Remove or disable one parameterized object type at a time until the error moves or disappears; the last one you touched is the failing instance.
The library release notes also record that the ME version cannot build a display command the way the SE version does and navigates through its own mechanism instead, so there is no checkbox you mis-set to hunt for. Hunt the string the mechanism produces, per instance, and the Diagnostics List's silence stops mattering.
What is the fix that makes the .mer build? #
Rename the displays to the exact strings the expression computes — (P-ME) Motor-Faceplate and (P-ME) ValveC-Faceplate from the reported values — rebuild the .mer, and the display-not-found error goes away; the alternative is editing the parameters so the computed string equals your existing display names.
Renaming is the committed fix because every placed instance of the global object computes from the same expression: align the display names once and motor, valve and every other object type resolve together. Editing the expression or the parameters instead means repeating that work across every library update and re-import. After renaming, search the project for the old names — other buttons, trends, alarm links — and repoint anything still calling P_Motor-Faceplate or P_ValveC-Faceplate.
Then verify: rebuild the .mer and confirm the error is gone, run the runtime, and press each faceplate button — motor and valve at minimum — to confirm the intended faceplate opens on the terminal, not merely that the file compiled. If the .mer now builds but the transfer to the terminal fails, that is a different fault, and why an HMI transfer fails in initial start mode despite ping covers that path.
Which FactoryTalk View ME versions support the PlantPAx faceplates? #
The published PlantPAx library documentation carries a minimum of FactoryTalk View ME 6.0 for the process objects and their faceplates, so Studio version 15 with runtime version 15 sits far above the floor and version support is not what is failing.
The release notes carry the 6.0 minimum on the ME side with the SE counterpart at the same floor. What version still decides: build the .mer on the same Studio version the terminal's runtime runs, so the compiled file matches the target, and keep the Studio-side graphics and the controller-side add-on instructions on one PlantPAx library generation so the two sides agree on what they pass each other. Versions beyond that are not your fix; the computed string is.
Questions asked
Can two instances of the same global object compute different display names?
Yes, and that is what makes the fault confusing. The expression lives in the global object definition, but each placed instance substitutes its own parameter file values into the #102 placeholders, so a motor instance can compute (P-ME) Motor-Faceplate and build fine while a valve instance on another screen computes a string with no display behind it. Always read HMI_Lib and HMI_Type from the failing instance's own parameter file, never from a working sibling.
What goes into a support request if the names match and the build still fails?
Bring the complete runtime-creation message text, the Studio and runtime versions, the PlantPAx library version (4.10.06 in the reported case), the failing object type, its parameter values, and the exact computed string beside the display name. Names proven identical character for character plus that package turns a guessing session into a case: a confirmed defect comes back tied to a specific patch level, and your captured message is the evidence that decides it.
Does the same mismatch also fail at runtime after the .mer builds?
Yes. If a project builds while the expression still computes a name no display carries, pressing the button on the terminal fails the same way: the runtime looks up the computed string, finds no display behind it, and reports the same condition. The diagnosis does not change. Evaluate the expression with the instance's parameter values and make the result identical to a real display name before the next download.
Why does the PlantPAx faceplate button compute its target name instead of using a fixed display name?
One button definition serves every motor, valve and other object placed from the library, so the target cannot be typed as one fixed display name. The Variable Screen Name option lets the expression build the target from each instance's own HMI_Lib and HMI_Type values, which is how a single button design opens the correct faceplate for whichever object it sits on. That design is also why the lookup happens at build time, on the computed string.
Can I keep the P_ display names and rewrite the expression instead?
Yes, but it is the heavier path. The expression is editable text on the navigation button, so it can be rewritten to compute P_Motor-Faceplate directly. The button is a shipped library object, though, so the edit has to be repeated whenever the PlantPAx graphics are updated or re-imported, and every instance must be retested afterward. Keep the expression edit for a site naming standard that makes the P_ names mandatory; otherwise renaming the displays once is the smaller change.