After clearing the affected Gateway’s Designer cache and relaunching with a matching Designer version, the indirect binding editor should again display the tag path and editable property references. Follow the data from the remote Designer to the Gateway, then isolate the local cache before changing working tag logic.
Where does the indirect binding request stop?
The Designer requests the project from the Gateway, loads project resources into its local workspace, and renders the property-binding editor. Selecting an indirect tag then combines the configured tag path with one or more property references. The reported project follows this path successfully on the Gateway computer, but remote Designers show three editor failures: the Indirect Tag Path field is initially absent, selecting a tag reveals that field but leaves the Property Path uneditable, and existing references appear unpopulated.
| Path stage | Observed result | Diagnostic meaning |
|---|---|---|
| Gateway-hosted Designer | Indirect bindings work normally | The stored binding and referenced tags can function. |
| Remote Designer project load | Project opens | The request reaches the Gateway and returns project content. |
| Remote binding-editor render | Fields are missing, locked, or empty | Investigate the Designer version, local cached resources, and project serialization before rewriting tag paths. |
| Other projects on the same remote PC | Indirect bindings work | A general workstation or network failure is less likely; the fault is associated with this project-Gateway context. |
Check: Open an existing indirect binding in both the Gateway-hosted Designer and one remote Designer. Record which fields render and whether each reference value appears. Proceed only after reproducing the difference on the same project resource.
Does the physical and network path carry the project?
Layer one first. Confirm the remote workstation has an active link, a valid route to the configured Gateway address, and a stable Designer session. A complete project load and normal operation of other project editors already show that substantial traffic crosses the path; a dead cable, incorrect route, or fully blocked Gateway connection would not normally isolate the failure to indirect-binding controls.
| Item | Gateway-hosted Designer | Remote Designer | Value to compare |
|---|---|---|---|
| Gateway address | Local connection entry | Remote connection entry | Read the active Launcher entry; the evidence supplies no address. |
| Gateway port | Configured connection port | Configured connection port | Compare the entries exactly; no port number is stated. |
| Session timing | Project opens without interruption | Check for reconnects or timeouts | Read the Designer and Gateway diagnostics; no timeout value is stated. |
| Project selected | Affected project | Same affected project | Confirm name and Gateway before comparing editor behavior. |
Intermittent link loss can leave an editor partially initialized, so reopen the project after the connection is stable. If the remote Designer remains connected, browses tags, and opens other bindings while this editor alone is malformed, move to the client-version and cache checks.
Check: Browse to the intended tag through the tag-selection control, then open a non-indirect binding without a session reconnect. Both actions must succeed before treating this as a cached UI-resource fault.
Are all Designers running the same version?
The Gateway-hosted and remote Designers must interpret the same serialized project resources and binding-editor schema. A version mismatch can make one client render controls differently even though the Gateway accepts the connection. Compare the complete version shown by every Designer involved, not just the product family or major release.
- Record the version from the working Designer on the Gateway computer.
- Record the version from each affected remote Designer.
- Verify that the remote launch entry opens the same Gateway and supplies the same Designer version.
- Close any older Designer instance before retesting; an already-running process may not represent the client just launched.
Do not edit or recreate indirect bindings while clients disagree. Saving a resource from a client that renders it incorrectly can replace usable configuration with incomplete values.
Check: Relaunch one remote Designer at the matching version and reopen, without saving, a known working indirect binding. If its references populate, the mismatch was the decision point. If the UI remains malformed, isolate the local Gateway cache.
How do you rebuild the remote Designer cache?
The Designer keeps Gateway-specific cached material in the Windows user profile. A stale or damaged cache can affect one Gateway or project while unrelated projects continue to work. The relevant cache location is c:/users/<user>/.ignition/cache/gw.
- Close every Designer connected from the affected Windows account.
- Locate
c:/users/<user>/.ignition/cache/gw. - Move the affected Gateway cache entry to a temporary backup location when it can be identified. Otherwise, move the
gwcache directory so it remains recoverable. - Relaunch the Designer from the intended Gateway. Allow it to rebuild its local cache.
- Open the affected project and inspect an existing indirect tag binding before saving any resource.
Moving the cache rather than permanently deleting it preserves a rollback point. The first launch may need to retrieve resources again; judge the result only after the project finishes opening.
Check: The Indirect Tag Path field must appear without first forcing it into view, the Property Path must accept editing, and stored references must populate. If these controls remain broken on a rebuilt cache, test whether the defect travels with the project.
Does the fault travel with the project?
A copy or export/import test separates a damaged project resource from Gateway-specific cached state. Keep the original unchanged while running the comparison.
| Test result | Likely fault domain | Next action |
|---|---|---|
| Original fails; project copy works | Original project metadata or resource state | Compare or replace only the affected resource from the working copy. |
| Original and copy both fail on one remote PC | Remote client environment or remaining cache state | Repeat the version and per-user cache checks. |
| Export/import into a new project works remotely | Original project container or resource serialization | Validate all bindings in the imported project before adopting it. |
| Every form fails remotely but works locally | Shared difference between local and remote Designers | Compare exact versions, launch targets, accounts, and diagnostics. |
- Create a project copy, or export the project and import it as a new project.
- Open the copy from the same remote Designer that reproduces the fault.
- Inspect the same component and binding without modifying the original.
- If the copy works, transfer or rebuild only the affected project resource and confirm each indirect reference explicitly.
Check: Repeat the same editor operation in the original and copy during one Designer session. A different result identifies the project resource as the changing variable.
How is the repair verified end to end?
A visible editor is not enough. Verify configuration entry, reference substitution, tag resolution, and the bound property’s live value.
- Open a component with a known indirect tag binding.
- Confirm the Indirect Tag Path and every saved reference are populated.
- Edit one Property Path, apply the binding, close the editor, and reopen it to prove persistence.
- Change the reference input to select another valid target.
- Confirm the resolved tag changes and the component property follows the selected tag.
- Save, close the remote Designer, relaunch it, and repeat the binding inspection.
Check: The repair passes only when the remote Designer can edit, save, reload, and execute the indirect binding while the Gateway-hosted Designer reads the same configuration.
FAQ
Why does an Ignition indirect tag work on the Gateway PC but not remotely?
The working Gateway-hosted Designer proves that the binding can function. Compare exact Designer versions and rebuild the remote Gateway cache at c:/users/<user>/.ignition/cache/gw before changing the binding.
Why is the Indirect Tag Path field missing?
A malformed binding editor points to failed client-side rendering of the project resource. Relaunch with a matching Designer version and a rebuilt cache, then inspect an existing binding without saving it first.
Why are existing indirect tag references empty?
The remote Designer may not be loading or interpreting the saved reference metadata correctly. If cache rebuilding does not restore it, open a project copy or exported/imported copy to determine whether the problem travels with the project resource.
How do I prove the indirect tag repair is complete?
Edit and save a Property Path, reopen it, switch the reference to another valid target, and confirm the resolved tag and bound property both change. Relaunch the remote Designer and verify that the path and references remain populated.