Assuming that this is what you meant:
Here is the tag's timestamp dataset, which correlates at each row to another dataset which shows its value at that time.
Here is the Value dataset.
So the value at "Line6[0,1]" is the value it held at the timestamp seen at "Line6[0,0]"
There is however a Different tag which records the same data, but instead of storing it in a big dataset like this, It just shows what the Current value is, so if needed something like that could also be used by enabling history on it and then pulling from that with a component.
You'd already be done if you just made the expression BOOL tag and enabled the history on it, like I said.
Okay so about that, I tried that yesterday and got stuck almost immediately. Keep in mind that any suggestions are falling on the ears and eyes of an idiot over here so sorry. But I can't seem to find a way to reference to my setpoint which is a bit of a hangup. The problem being that currently, the setpoints are calculated and held in Custom values of a perspective view for that line, where in those custom values already reference a tag. So if you know a way I can reference those view specific custom values I believe I could do it.
But without being able to reference those custom values in some way that is a bit of a dead end. The setpoints are not static, and actually change about every 20-45 minutes or so.
Can you not replicate the calculation in a tag?
If I understood the whole thing more or less correctly, views are not supposed to hold this kind of data.
I suggest you take a step back and tell us about the bigger picture, it seems to me there's something smelly in the way things were done.
Ok, with that in mind, without creating a new tag and based on the screenshot of the chart that OP has been able to create, even though it wasn't what they were looking for we might be able to work with it.
@D_Mitri_Tompkins can you create two series within the same chart and use a script transform on the flow to transform each to a 0/1 and 1/0 series.
Something like:
series 1:
if dataPoint <= flowSP:
1
else:
0
series 2:
if dataPoint <= flowSP:
0
else:
1
both of the series would still bind to the entire dataset
I'm sure I could, just don't know how to go about that? Would I make a reference tag and then transfer the custom values transform script to that reference tag's "value changed" script?
Something like this?
Where I would bind the same Tag to Both of those data values, then put a script transform on each binding with the above?
And if so what kind of binding do I want to use? Tag (indirect or direct) tag history, or a different one?
How did you make this chart?
The tag should likely be indirectly bound to a custom property on the view. Then you can reference that custom property throughout the view.
Export the relevant tag structure for us
This is where I am at, feels just shy of working.
And this is what the chart looks like with those bindings on the data (The ones which will check for above or below setpoint)
And then if I remove those bindings, the chart is clearly capable of functioning as it changes to look like this:
So this is Almost what I need, but there is some clear issues;
1: without that binding working, which though it correctly yields either a 1 or 0, I can't get this to actually show what I want.
2: even when it is working close to correctly such as above, it doesn't even work right? Nowhere in the entire object details do I have that light blue color selected, so not sure why that is showing.
What component is this?
Can you please give me your tag structure?
Did this dataset already exist? How is it populated?
So maybe I overlooked this, but if the original developer already had a chart created and working, why are you not able to copy/paste it and point it to the new line?
I do not know, I genuinely have no clue. The original chart is on a different view and bringing it into this view immediately broke it. I suspected it was because it referenced a lot of custom values of the page it was on, so I recreated all of those. No dice. Tried building my new chart on the old view just to check, again, no good.
Are there any scripts you're missing? Custom methods?
Almost definitely. currently the one that is working on the other view uses an incredibly complicated transform script, I can send it over if you'd like. But it references things that are specific to That data, like stuff that could not exist for my data.
To hopefully elaborate, this is the current script on the working component:
Changing the referenced tags on this tag history binding to the tag I want to display breaks the chart. Doing that and removing this script breaks the chart. Just removing this script breaks the chart.
