Troubleshooting Extra Scheme Components in Rapid SCADA

Clearing Firefox’s browser cache restored the Extra Scheme Components gauge pointer and level indication in one Webstation 5.0.7.0 installation; a separate Level-rendering report was resolved by changing the component’s channel-data lookup. These symptoms can look alike on the screen, but they point to different checks: browser assets, Webstation compatibility, or the Level component’s data binding.

What does the screen symptom tell you?

Use the point at which the component fails to narrow the fault. A gauge that displays a placement cursor but leaves no object in the scheme editor fails before runtime data binding. A Level object that places successfully but renders as an empty box fails later: the editor accepted the object, but the browser did not draw its indication. If the editor renders the Level but the browser does not update it, focus on runtime rendering and channel data rather than object placement.

A chart opening successfully is not a component test. The chart and the gauge or Level may use different rendering paths, so verify each control on its own.

Which Webstation version supports the plugin?

Match the installed versions before editing JavaScript or rebuilding the scheme. The components were published on July 30, 2018, and the stated minimum Webstation version is 5.0.6.1. In one reported installation, Extra Scheme Components 5.0.0.0 was paired with Webstation 5.0.6.0, which is below that minimum. That combination is a compatibility problem to correct first, not evidence that the scheme itself is malformed.

Version compatibility and browser caching are separate conditions. Upgrading to a compatible Webstation does not automatically prove that a browser has discarded older component files; test both.

How should you compare browser and cache behavior?

When a component appears in one browser but not another, keep the scheme and controller inputs constant while testing the browser path. One Webstation 5.0.7.0 installation displayed the extra components correctly in Chrome but not Firefox: the gauge pointer and Level indication were missing in Firefox. Clearing Firefox’s browser cache fixed that case.

1. Record the Webstation and plugin versions and note which browser shows the fault.
2. Open the same scheme in the working and failing browsers without changing its component configuration.
3. Clear the failing browser’s cache, reload the Webstation, and reopen the same scheme.
4. Check whether the gauge pointer and Level indication now render, rather than relying only on editor appearance.

If cache clearing restores the controls, treat stale browser-delivered assets as the immediate cause. If both browsers fail in the same way, continue with the channel binding and runtime checks. If only one browser still fails after a cache clear, collect the browser-specific error and the Webstation log before making a code change.

Does the Level have a working runtime input binding?

A visible Level object is not proof that it can read and render its input channel. One report showed a DynamicText configured with the input register while the Level bar itself failed to update. That distinction matters: a separate text object can display a value even when the Level component’s own lookup or rendering path is broken.

Check the Level’s assigned input in the scheme editor, then compare its runtime indication with a separate display of that same register if available. If the separate value updates while the bar stays empty, the controller value is reaching at least one display path; investigate the Level component’s binding or rendering. If both are blank or stale, trace the channel and controller data path before attributing the problem to the extra component.

The “Draw Diagram” action opening a chart with value curves is also a limited test. It demonstrates that the chart action can produce a plot, not that the Level reads its assigned channel or paints its bar.

What repair order avoids unnecessary code edits?

Use the least invasive checks first. Do not patch a JavaScript file to compensate for a Webstation version below the stated minimum or stale browser assets.

1. Record the installed Webstation and Extra Scheme Components versions. If Webstation is older than 5.0.6.1, bring it to at least that version before judging component behavior.
2. Confirm the component files were installed under the ScadaWeb installation and check whether the files are unblocked, as was done in the initial setup.
3. In the scheme editor, test whether each control can be placed. Save and reopen the scheme if placement succeeds.
4. Run the scheme in the browser and test the gauge pointer and Level fill separately. Compare the same scheme in another browser if available.
5. Clear the failing browser’s cache and reload. Recheck the exact missing indication.
6. If the Level still fails while its input value is visible elsewhere, inspect the component lookup and the Webstation log at SCADA\ScadaWeb\log.

For an activated trial setup, the reported activation path used a trial key obtained while running SCADA under an administrator account. If the component is not available at all, verify activation and file installation before investigating runtime channel values.

When is the channel-data lookup change relevant?

A reported Level-component fix changed the lookup in extracomprender.js from renderContext.getCnlDataExt(props.InCnlNum) to renderContext.curCnlDataMap.get(props.InCnlNum). Apply this as a targeted diagnostic only when the Level object places but fails to render or update its assigned channel, particularly when a separate DynamicText using the input register does update.

// Existing lookup
var cnlDataExt = renderContext.getCnlDataExt(props.InCnlNum);

// Reported replacement
var cnlDataExt = renderContext.curCnlDataMap.get(props.InCnlNum);

Back up the original file before editing, preserve the surrounding code, and change only the lookup line. Reload the Webstation in the browser after the edit; clear the cache if the old behavior persists. This change was reported for the Level rendering fault, not as a general remedy for a gauge that cannot be placed, a version mismatch, or missing controls caused by cached files. Confirm the exact component file in the installation and check the log if the edited script fails to load.

What should the log and final test confirm?

The Webstation log is the next diagnostic when the visual symptom remains after compatibility, cache, and binding checks. Read the entries under SCADA\ScadaWeb\log around a controlled reload and look for additional error descriptions associated with component loading or rendering. Record the Webstation version, plugin version, browser, and the exact failing action so the log can be interpreted against a reproducible test.

Close the diagnosis with a runtime check, not just an editor preview. Place the controls in the editor, open the scheme in the target browser, verify the gauge pointer and Level bar, and confirm the Level indication responds to its configured input. If using the lookup change, repeat the same test after reload and cache clearing; the fix is verified only when the Level itself displays the expected live indication.

FAQ