Ignition SCADA can show a red cross even when a tag object exists because accepting an address string is not the same as validating that string against the selected communication driver. Start with what the operator sees, then trace the failing path through the component binding, tag quality, driver, and controller. Treat page-change latency and localization as separate engineering problems rather than evidence that the entire platform must be replaced.
What is the screen telling you?
Classify the visible symptom before editing the project. A red tag indicator, a static symbol, a slow page change, and untranslated text occur in different parts of the runtime path.
| Screen observation | Reading to take | Likely fault boundary | Next check |
|---|---|---|---|
| Red cross on a tag | Tag quality and diagnostic message | Address, driver, connection, or controller path | Validate the address against the selected driver |
| Correct tag value but unchanged symbol color | Component property and binding result | Property binding or symbol capability | Test the property with a simple dynamic object |
| Page change takes 5 seconds or as much as 7.8 seconds | Navigation time with scripts and bindings isolated | Page initialization, data requests, scripts, or rendering | Time a minimal page, then add dependencies incrementally |
| Text remains in the original language | Text source and translation-key coverage | Literal object text, tag-supplied text, or HTML-formatted content | Inventory every runtime text source before translation |
The installation reporting these symptoms used version 7.9.9. Record the installed version before troubleshooting, because behavior observed there must not be projected automatically onto other releases.
Does the tag address match the selected driver?
The first decision point is tag quality. A configuration editor may accept a free-form address such as HELLO WORLD without proving that the selected driver can parse or resolve it. The later red cross means the runtime path failed; it does not prove whether the failure is syntax, device connectivity, or controller data availability.
| Setting | Location | Effect |
|---|---|---|
| Communication driver | Tag or device connection configuration | Defines the address grammar and protocol used to request data |
| Tag address | Tag definition | Identifies the controller item interpreted by that driver |
| Connection target | Driver or device configuration | Selects the controller or endpoint receiving the request |
| Component binding | Screen object property | Maps the resolved tag value or quality to the visible property |
- Open the tag diagnostics and record the quality plus the full diagnostic text.
- Confirm which driver owns the tag. Validate the address using that driver's documented grammar; visual acceptance by the editor is not validation.
- Read the same controller item through the driver's diagnostic or browsing facility. If the item cannot be read there, remain at the driver/controller branch.
- If the driver reads the item but the tag remains bad, compare the tag's address and connection selection with the working diagnostic request.
- If tag quality becomes good, continue to the screen binding rather than changing the controller.
Does the driver actually reach the controller item?
A syntactically valid address can still fail when the connection points to the wrong endpoint, the controller does not expose the requested item, or the communication session is unhealthy. Separate these cases by testing from the bottom upward.
First verify the controller item in the controller engineering environment or another approved controller-side diagnostic. Then verify device connection health in Ignition. Finally request the exact item through the selected driver. This order distinguishes a missing controller item from a broken session and an incorrect tag address.
| Reading | Outcome | Meaning | Next action |
|---|---|---|---|
| Controller item | Missing or inaccessible | The SCADA request has no valid source | Correct the controller-side definition or access path |
| Connection health | Bad | Address testing is premature | Correct endpoint and session configuration |
| Direct driver read | Bad while connection is healthy | Driver-specific address or item resolution is wrong | Correct the address grammar |
| Direct driver read | Good | The controller and driver path work | Inspect tag configuration and component binding |
Is the tag right but the binding wrong?
When a tag has good quality and the expected value, stop editing the driver. The tag is right; the binding is wrong. Select the visible component property, inspect its binding, and confirm that the evaluated value changes when the tag changes.
For a background-color problem, build a temporary basic object whose background property is directly driven by the same condition. If that object changes, both the tag and condition work; the original symbol either exposes a different property, overrides the property internally, or does not support the intended dynamic behavior. If neither object changes, inspect the binding expression, value type, and quality propagation.
Two configurations can work: bind the visual property directly to the tag when the tag already represents the display state, or bind it through a transformation when process values must map to visual states. Direct binding has fewer failure points. Use a transformation only when the display rule requires conversion, range handling, or multiple conditions.
Where does the 5-to-7.8-second page delay begin?
Measure navigation independently from communication quality. A page can wait on initialization scripts, synchronous work, large numbers of bindings, remote data requests, or expensive rendering. Changing tag syntax will not correct a page whose delay begins after all data has arrived.
- Create or identify a minimal page with no process bindings, complex symbols, or startup work. Measure navigation to it from the same client.
- If the minimal page is also slow, inspect client, gateway, and network timing at the navigation boundary.
- If the minimal page is fast, copy the affected page and disable its startup work and data dependencies in controlled groups.
- Reintroduce scripts, bindings, and visual groups one group at a time. Record the elapsed time after each change.
- Move slow or blocking work out of the navigation path where the project architecture permits it, then repeat the same measurement.
The reported 5 seconds at best and 7.8 seconds in slower cases are baseline observations for that installation, not acceptance limits. Use the same client, route, and page state for before-and-after measurements.
How do you fix the resolving branch and verify it?
Localization requires the same source tracing discipline. Literal component text, text supplied by tags, multiline labels, and HTML-formatted content are separate sources. Translating objects one by one late in development creates omissions and makes formatted strings difficult to hand to a translator.
The installation used export plus an Excel VBA macro to extract translatable strings and rebuild HTML after translation. That can recover an existing project, but a controlled text inventory is the better engineering habit: separate human-readable text from formatting, assign stable translation keys during screen construction, and include tag-supplied text in the inventory. A prefix such as # can help identify marked text, but it cannot discover unmarked literals or safely separate language from embedded HTML by itself.
- Correct the driver-specific address until the direct driver read succeeds.
- Confirm that the configured tag reports good quality and follows the controller value.
- Bind a simple test component directly to that tag and prove that its visible property changes.
- Apply the confirmed binding pattern to the production symbol, checking for internal property overrides.
- Profile the affected page from a minimal baseline and remove the measured navigation bottleneck.
- Inventory literal, tag-supplied, multiline, and HTML-formatted text; translate content separately from markup.
- Retest every language, page transition, tag quality state, and symbol state from the operator client.
FAQ
What happens if Ignition accepts an invalid tag address?
The editor can retain the string, but runtime resolution fails and the tag can show a red cross. Read the diagnostic text, confirm the selected driver, and rewrite the address using that driver's grammar.
What happens if the driver reads the value but the symbol does not change?
The controller path is working, so inspect the component property binding. Prove the condition on a basic test object, then check whether the production symbol overrides or lacks the targeted property.
What happens if page changes still take 5 to 7.8 seconds?
Time a minimal page first. If it is fast, restore the affected page's scripts, bindings, requests, and visual groups incrementally until the delay returns.
How do I verify the Ignition SCADA fix?
From the operator client, confirm a direct controller value change reaches a good-quality tag, drives the intended symbol property, survives a page transition, and displays correctly in every configured language.