I have a flow rate tag, let's call it TagA and a target flow rate updated by a different department called TagA_target. I'd like my TagA to turn red and blink if below TagA_Target.
Any help would be appreciated
You could do this with using a PI Calc (dataset) instead for the multistate. Select your value tag and select the multistate symbol button. Instead of clicking Tag Search, click the drop down arrow to the right and then select PI Calc. Enter an expression such as
if 'VALUETAG' > 'TARGETTAG' then 1 else 0
then set your multistate to be 0-0.5 RED 0.5-1 GREEN
You might want to mess around with calculation intervals, I've always found datasets to be slow (also you're losing business logic within Processbook). A better option would be to create a Performance Equation tag which does the same calculation as above and use that tag for your multistate, or better, implement the logic in AF and use an AF formula for the multistate. If none of these are available to you however, the dataset route should work!
Hello - your MultiState configuration is actually completely independent of the object you place it on
Let's say you have a Value symbol on your display (in my example it's from tag BA:Active.1)
Highlight the symbol you want to apply the multistate to, then click on the "Multi-State Symbol"
You can now perform a Tag Search or AF Element Search to pull in any tag you'd like to base your multistate on. I chose CDT158, and I will now select my color values based on the values from CDT158
When CDT158 > 50 but <= 150, I will see:
Taylor Thanks for the quick reply! Sorry I wasn't descriptive enough. So the object that I want to turn color is TagA's value based on TagA_Target's value.
Above are two different tags... If the actual flow rate drops below the target tag then I'd like it to go from green to red and blink. The target tag value varies so I can't set a static number (or it would be annoying to have to every time it changes). Hopefully I am being more clear
Thanks! The dataset worked. I'll use it as a temporary solution, then further down the road I'll probably create the PE tags. We don't have/use AF.
Retrieving data ...