Data quality indicates whether Tag data is valid; process states such as running, stopped and alarmed are separate. In Script Text, select Use quality outline colors under Quality Override and set Good and Bad colors. State Color provides Follow data quality (border / hide), with an option to hide on bad quality.
Manual
Keep data quality separate from process state | Mingcedar Studio
Understand data-quality indicators, the behavior-specific meaning of Condition, and visibility options. Available controls depend on the behavior editor.
Keep data quality separate from process state
Understand data-quality indicators, the behavior-specific meaning of Condition, and visibility options. Available controls depend on the behavior editor.
Condition has a different role in each behavior. Use the table and the corresponding editor to configure it.
For example, enter the expression below in Script Text Condition to evaluate its text only when the specified Tag has good quality. Replace the example name with your project Tag and verify both good and bad quality. Configure the corresponding Quality Override when a persistent quality indication is required.
- Condition must return a Boolean immediately; do not use fetch, promises or timers.
- Condition does not replace Mingcedar write permissions or equipment interlocks.
- Move / Rotate / Scale currently have no separate Post Operations input.
ReadTagQualityGood("PLC_LINE01.PUMP01.SPEED")