Identify the Boundary Mode
A channel value remaining in the normal state below its configured lower boundary can result from misinterpreting the Linked to channels option. This option does not link the boundary definition to the monitored target channel. It makes the boundary values come from separate channels.
| Configuration | Boundary source | Required action |
|---|---|---|
| Linked to channels cleared | Static values stored in the boundary definition | Enter the required setpoints directly in the boundary. |
| Linked to channels selected | Values held in designated channels | Create and populate the referenced channels that store the setpoints. |
The available reports include Beta_10 and version 6.2.2.0, but they do not establish a version-specific defect. Check the boundary mode and its source values before treating the behavior as a software fault.
Correct and Verify the Configuration
- Decide whether each limit must remain static or be stored in a channel so it can change during operation.
- For static limits, clear Linked to channels and enter the boundary values directly.
- For adjustable limits, select Linked to channels, create the referenced setpoint channels, and ensure those channels contain the intended values.
- Transfer the configuration and refresh the browser cache.
- Move a test or calculated channel above and below the configured limits. Confirm that the channel status and value color change in both the table and schematic views.
If the value crosses a limit but the status remains normal, inspect the current values of the setpoint channels. An enabled channel link without populated source channels does not use the static numbers as the active limits.
Use the Common Boundary Option Correctly
The Common option does not change the boundary evaluation algorithm. It marks a boundary as intended for multiple channels and allows the Administrator channel-editing form to filter for common boundaries. Select it when several monitored channels should reuse the same boundary definition.
Account for Display and Trend Limitations
In the described implementation, schematics support only the first configured status color; the additional color fields were reserved for later schematic development. Therefore, assigning status-based color to text or background can still produce Color 1 rather than distinct use of every configured color.
Chart Pro version 6 can color trend lines from channel status using TrendColorAsStatus in PlgChartPro.xml. Channel status is not necessarily derived only from boundaries because a formula can set it. Static boundary changes can therefore make displayed limits disagree with recorded status. To plot changing limits, store them in channels and add those channels to the view; automatic boundary-line display was not implemented in the described behavior.
FAQ
Why does a Rapid SCADA value stay normal below its lower limit?
Check Linked to channels. When selected, the limits must come from referenced setpoint channels; clear it if the boundary should use static values.
What does Common mean in Rapid SCADA boundaries?
It identifies a boundary intended for several channels and supports filtering in the Administrator channel-editing form. It does not alter boundary evaluation.
How do I color a Rapid SCADA trend by channel status?
In Chart Pro version 6, configure TrendColorAsStatus in PlgChartPro.xml. If changing limits must also appear on the chart, implement them as channels and include those channels in the view.