LabVIEW
property node outputs wrong values
Solved!
Two tangential questions:
- Why are you operating your LEDs in such a Rube Goldberg way?
- Why are you closing the references with every call inside the subVI? (SetCursorPosnMod.vi)
I was able to replicate the problem. I was also able to fix the problem.
First off, I added feedback nodes to keep track if the values had been triggered at all since the first run. The feedback nodes will only change their value on True, so they will always output True once it is written once. I also switched the logic so True is the Not Equal trigger and the boolean goes red on True. This makes more sense to me when I think about it like an error.
The solution: change the Preferred Execution System of your main VI to User Interface. This is in your VI Properties dialog via right-clicking the VI icon. After making this change, I can't get the LEDs to go red.
@JohnEE wrote:The LEDs were just a quick test, and I liked red and green, instead of on and off. I suppose I could go into the properties and change the on/off color,
No need for properties, just use the coloring tool to change the dark green (off) to red (shift-right-click...color tool, pick red...mouse down on the off led, repeat.). Much faster to "throw together" than to add all these duplicate steps. 😄
And if you need more than two colors, create a color LED where "the color is the data". Property nodes are relatively expensive and clumsy.
