Array threshold scan

[hiNI]

Hello,

In the attached VI in Labiew 8.5, I wanted to return the x and y-axis value the last time the temp value is above 100 (on the positive side) and the last time that the temp is below -100 (on the negative side).  I am not sure if it will be easier to scan the values from the right side of the graph to the left to return the correct values.  I wanted to return the following points:

positive side: 100.58, 68.077

negative side:-101.05, 43.93

Thanks,

hiNi.

[JÞB]

[altenbach · Accepted solution]

Here's a quick attempt:

Be aware that property nodes  execute to top bottom, so you should set the active cursor before setting the position. You also only need two points for the reference lines. I currently show the positions as complex numbers for simplicity. Modify as desired.

[P@Anand]

Christian, Am just curious to know the reason why you are dividing the array value by 1? Is there any functional difference when we do that?

[altenbach]

---

P@Anand wrote:

Christian, Am just curious to know the reason why you are dividing the array value by 1? Is there any functional difference when we do that?

---

I am not doing that, it was already in the original code. I left it there because I thought the original programmer might need to tune that factor later. 😉

[P@Anand]

My bad I didn't see the original code 🙂 (I thought its Christian trick )

[hiNI]

Hello Jeff,

Can you include your code in LV 8.  For some reason, I am not getting the correct "unbundle" data to go to the threshold block.

Thanks,

hiNi

[crossrulz]

Jeff,

Did you mean to have the unbundle give different sets of arrays?  Because you aren't.  Another danger of using the same name for controls/indicators.

[altenbach]

Change the label of the two arrays in the cluster to something unique, e.g. "X" and "Y" to keep things sane. Otherwise, use a plain (not "by name") unbundle.

[JÞB]

---

@crossrulz wrote:

Jeff,

Did you mean to have the unbundle give different sets of arrays?  Because you aren't.  Another danger of using the same name for controls/indicators.

---

It was a quick-n-dirty created constant from the original graph.  Not the way I normally program. just to show an alternate approach for a find last crossing index