Troubleshooting
Why HMI Objects Show White Boxes Only on Populated Pages
Short answer
Objects show a white box with a red border when the panel's optimized grouped read for that page spans a register the PLC never assigned; the same object reads fine alone because its single request stays inside assigned addresses. Recalculate the published variable addresses in EcoStruxure Machine Expert HVAC so the range has no gaps, reimport the mapping into Operator Terminal Expert, and download the controller and panel projects together.
On this page
An HMI object that draws as a white box with a red border is the panel reporting that its variable returned no value. When the same object displays correctly on a page by itself, the variable, its address and its binding are sound — what changed is how many variables the panel reads around it. EcoStruxure Operator Terminal Expert optimizes communication by combining a page's variables into as few read requests as possible, so a populated page sweeps one wide address span where a lonely page sweeps a narrow one. On an HMIST6400 reading an M171P controller, a span that crosses a register EcoStruxure Machine Expert HVAC never assigned fails the whole request, and every object in the group draws the white box. Recalculate the published addresses in Machine Expert HVAC so the range has no gaps, reimport the mapping into Operator Terminal Expert, and download both projects.
Why the failure follows the page, not the object #
The white box with a red border marks a failed read, not a broken object. Operator Terminal Expert groups the variables used on a page and reads them together, taking consecutive addresses in one telegram: the panel trades telegram count for span. The controller on the other side accepts a read only when every address inside it is assigned, so one unassigned register in the middle fails the whole telegram, and each object served by that telegram loses its value at once.
That is why the symptom looks random at the expansion level. Some expansion variables display correctly because their page's span happens to be fully assigned; others fail because a neighbor on the same page pushed the span across an unassigned register. Expansion membership never decides the outcome — the span of each page's grouped read does. The rule this hardware pair enforces is simple: no unassigned register may sit between the lowest and highest address a page reads.
Confirm the gap before touching the map #
Five checks separate a grouped-read gap from every other cause of a white box:
- Isolate one failing object. Move it to an empty test page. If it displays there, the variable's address, type and binding are sound and the map is the suspect.
- Record the full span of the failing page. List every variable used on that page with its published address, sort by address, and look for unassigned registers between the lowest and highest. A list of valid starting addresses proves nothing about the registers in between.
- Catch the refused request. Use the panel's communication diagnostics, or a protocol capture on the link, and read the start address and length of the failed request; interpret both in the connected driver's addressing convention.
- Rule out the connection. A dead controller link fails every object on every page and raises a connection alarm rather than scattering white boxes; if alarms need separating on the panel, the WinCC Flexible method for showing only a PLC connection alarm transfers directly.
- Separate cosmetic borders. A white border is not always a failed read. One harmless case is the selection border drawn on clicked objects, covered by hiding the white selection border on clicked objects in Citect HMI. Another is a symbol graphic bringing its own white frame, fixed by the Symbol Factory white border background fix in FactoryTalk View. Neither moves when page content changes; a read-failure white box does.
If the isolated object also shows the white box, stop here: the fault is that one variable's address, data type or PLC mapping, not the grouping.
Make the published range continuous #
The correction happens on the PLC side, then propagates to the panel:
- Save both projects. Archive the running Machine Expert HVAC application and the Operator Terminal Expert project, including the current exported variable list, before any address moves.
- Recalculate the addresses in Machine Expert HVAC. The tool's address recalculation packs the published variables into a continuous block. Where an address must stay fixed for another consumer, assign a real variable to every register in the gap instead — the requirement is a span with no unassigned register, not a particular layout.
- Check the recalculated map. Look for overlapping variables, wrong data widths and any register still unassigned before accepting the new allocation.
- Export, then import. Export the variable definitions from Machine Expert HVAC and import them into Operator Terminal Expert. Import behavior decides the outcome: as when importing a PLC tag CSV into an existing HMI tag database, verify that the import updates the existing variables instead of duplicating them, and that each object still points at the intended variable.
- Rebuild and download both projects together. The controller and the panel must run the same map. If the corrected project will not transfer, work through the Operator Terminal Expert download-failure guide before editing further.
One safety note: moving published addresses moves them for every client that reads them, so make the change in a controlled window with operator writes to the machine blocked until both projects run the new map.
Worked example: six unassigned registers break one page #
Example with illustrative addresses, not a documented map: a populated page shows three variables published at registers 100, 101 and 110. The panel serves the page with one read from register 100 through register 110 — a span of 110 − 100 + 1 = 11 registers. Registers 104 to 109 are unassigned: 109 − 104 + 1 = 6 registers the controller will not return. The telegram fails, and all three objects draw the white box with the red border.
Put the variable at register 110 alone on a test page and its request covers exactly register 110: one assigned register, so the value displays. That single success proves the variable is fine and the page's span is not.
After recalculation packs the block as registers 100, 101 and 102, the populated page's read spans 102 − 100 + 1 = 3 registers, all assigned, and the page displays. Nothing was wrong with the expansion at any point; the fault was six unassigned registers inside an 11-register span.
The decision for each symptom #
Match what the panel shows to the cause before editing anything:
- White box only on populated pages, object fine alone — an unassigned register inside the page's grouped read. Recalculate the published addresses to a continuous range, reimport into Operator Terminal Expert, download both projects. This is the case this article fixes.
- White box everywhere, even alone — that variable's own address, data type or PLC mapping is wrong. Fix the single variable against the controller map first.
- Every object fails on every page, values frozen — connection-level failure, not mapping. Check the link, the driver settings and the controller status.
- Objects disappear only in simulation over Modbus — a different mechanism, where the driver returns nothing for a read the slave cannot serve; why HMI objects vanish in online simulation over Modbus covers that case and its driver-side fix.
- Border on touch only, values still updating — cosmetic border or graphic background, not a read failure; leave the map alone.
Keep the map continuous after edits #
The failure returns the same way it arrived: a later edit adds variables to the expansion or reshuffles a page, a new span crosses a fresh unassigned register, and populated pages start drawing white boxes again. Treat export and import as one change unit — whenever variables are added or moved in Machine Expert HVAC, recalculate, export, import and download before the page set is reviewed. Moving failing objects onto empty pages hides the trigger without correcting the map, and the next page edit recreates the failure on a different page. The acceptance test for this repair is narrow and concrete: the original populated page displays every object with live values on the real controller, not in simulation.
Questions asked
Can I fill the gap instead of moving variables?
Yes. The controller only refuses reads that cover unassigned addresses, so assigning a real variable to every register between the page's lowest and highest address works as well as packing the block tighter. Machine Expert HVAC's recalculation normally packs variables together; when another consumer pins certain addresses, deliberately assign the intermediate registers instead. Either way the HMI never reads an unassigned address again, and the export and reimport steps are unchanged.
Does the same fix apply to an M580 programmed in Control Expert?
The grouped-read mechanism is identical, but Control Expert assigns addresses manually, so continuous means placing or reserving every intermediate address yourself in the variable table. After the map is aligned, export the variables and import them into Operator Terminal Expert just as with Machine Expert HVAC. On an M580 the symptom looks the same: objects bound to a refused read show the white box with a red border while the same objects read fine in isolation.
Why do some expansion variables display correctly while others fail?
Because the deciding factor is the page's read span, not the expansion. Sort the working and failing variables by address: the working ones sit inside spans that happen to be fully assigned, the failing ones share a span with at least one unassigned register. Recording that split page by page also tells you which grouped read to inspect first, which is faster than testing expansion modules one at a time.
Does the number of registers one telegram can read change this fault?
No. That maximum depends on the driver and the connection, but this fault does not involve exceeding it: a single unassigned address inside the requested span fails the whole read no matter how small the group is. Splitting a crowded page into several pages shrinks spans by luck rather than by design, so it can hide the failure on one page and recreate it on the next.