Troubleshooting
Why a Call Recipe Object Disappears Inside a Popup Window
Short answer
The C-more Call Recipe object is not supported inside a popup window: the panel drops it instead of showing it, because it opens its own Recipe Sheet over the display. Move the Call Recipe button to a normal screen and keep parameter entry in the popup, or test the plain Recipe object for loading values in place.
On this page
The Call Recipe object is not supported inside a popup window: the panel draws nothing for it instead of showing it, while the same object renders on a normal screen. Move the button to a normal screen and leave the parameter fields in the popup. This is an object-placement limit, not a damaged Recipe Database and not a communications fault. The reason is structural: the Call Recipe opens a Recipe Sheet over the display, and a popup screen will not host an object whose job is to open another window.
What you are seeing #
The pattern is repeatable, which is what separates it from a data problem:
- The Call Recipe button appears every time its screen is displayed directly.
- The same object, placed on the screen a Pop-up Window Frame shows, is simply not drawn.
- Recipe data itself is intact; the button works from any normal screen that hosts it.
The two documented object functions explain the split. The Pop-up Window Frame displays one preselected screen as a window on top of the current screen. The Call Recipe creates a button that displays a specific Recipe Sheet from the Recipe Database on the panel. Both objects open a window; only one of them can be on top.
Why the panel drops the object #
Inside a popup, the documented action of the Call Recipe — putting a Recipe Sheet over the current display — becomes a window on top of a window. The panel resolves that by not rendering the object at all. The same missing render is reported for the popup screen selector and the alarm history, and both of those open their own displays too, which fits one rule: a popup screen does not host objects whose function is to open another window.
The deciding factor is what the object does, not its size, layer order or tag configuration.
Call Recipe and Recipe are not interchangeable #
The two objects are close in name and different in action:
| Object | Documented action | In a popup window |
|---|---|---|
| Call Recipe | Creates a button that displays a specific Recipe Sheet from the Recipe Database on the panel | Not rendered by the panel |
| Recipe | Loads stored recipe values into tags; reported to load them without opening a selection display | Bench test before relying on it |
| Pop-up Window Frame | Displays one preselected screen as a window over the current screen | The container that triggers the limit |
Decide by what the operator has to do:
- The operator picks a material from a recipe list: keep the Call Recipe, on a normal screen. The recipe function exists for exactly that job — viewing and selecting from a list of multiple recipes.
- The popup only has to end up holding the right values: test a Recipe object in the popup and accept it only if it loads values into the tags without opening a second window. That load-without-a-window behavior is reported by users rather than spelled out in the documentation reviewed here, so confirm it on a bench copy of the project.
The fix: move the button to the base screen #
- Back the project up, and verify the HMI project data is inside the platform backup — screens and Recipe Database both — before you restructure anything.
- Open the popup screen in the C-more project software and delete the Call Recipe object from it.
- Place the Call Recipe button on the base screen that opens the popup, beside the control the operator already touches for parameter entry.
- Rework the flow: recipe selection happens on the base screen, then the popup opens to confirm and adjust the values that were just loaded.
- Download to the panel and run.
Staying inside the popup #
If the selection has to happen inside one window, the Call Recipe is out. Two workable shapes remain:
- Bench test the plain Recipe object in the popup and accept it only if all three hold: the object renders, the values land in the tags the popup displays, and no second window opens.
- Design per-case popups instead. The Pop-up Window Frame shows the one screen you selected for it at design time, so giving the operator different content per material means multiple frames or a selector on the base screen — a layout change, not a property of any recipe object.
Verify the move with a counted check #
Illustrative numbers for a cell with 20 material recipes, where each recipe writes 6 parameter values and 1 robot program number chosen by pick position:
- One full recipe check: 6 value comparisons + 1 program-number check = 7 checks.
- Full sweep: 20 recipes × 7 checks = 140 checks.
- Smoke test of the boundary and middle recipes, numbers 1, 10 and 20: 3 × 7 = 21 checks, one bench session.
Run the 21-check smoke test after every download while the screens are being reworked, and the full 140-check sweep once at acceptance. Because a recipe selects robot motion, do both with the cell in a safe state and the panel on test tags before it goes back on the line. If the button now renders but no live data appears anywhere, that is a communications fault on a different path — why a program runs but the C-more panel reads nothing.
Dead ends worth skipping #
- Rebuilding or re-importing the Recipe Database. The object renders on a normal screen, so the database loads.
- Tag and address checks. The failure is placement, not addressing.
- Bring-to-front and layer order. The panel is not drawing the object behind anything.
- Repeated downloads and panel resets. The behavior is fixed by the project design, not by runtime state.
Questions asked
Is there a setting that makes the Call Recipe render inside the popup?
No documented setting changes this. The behavior follows where the object is placed, not how it is configured, so tweaking properties, size or layer order will not bring it back. Moving the button to a normal screen is the fix, and the plain Recipe object is the only in-popup alternative worth bench testing.
Which other objects should I keep out of popup screens?
The popup screen selector and the alarm history are reported to fail the same way, and both open their own displays. Treat any object whose documented job is to open another window as a poor fit for a popup screen. Place a copy on a bench screen in both positions before you build a design around it.
Could a newer panel or software release add popup support for the Call Recipe?
Nothing in the documentation reviewed here says popup support was added, so plan the layout around current behavior. If an upgrade happens for other reasons, retest the object in a popup on the bench afterward instead of assuming anything changed. An untested upgrade is not a migration plan.
How is this different from an object hidden by a visibility condition?
A visibility condition hides the object everywhere until its tag or bit goes true, on normal screens and popups alike. Here the object renders on a normal screen with no condition attached and vanishes only inside the popup frame, which points to placement support rather than project logic.