LabVIEW
Customized Warning sign
Solved!
Hey LabVIEW geniuses,
So I got a tiny situation which I'm having trouble working around. I've got a massive setup working with a bunch of sensors and I'm trying to put in some visual security features. I've taken an icon of a Decoration function and customized it to look like a warning sign. I want these to blink but the specific Blink property nodes works more in the dim/light sense with the boolean functions. Because of this I'm using the property node for Visibility. I've created a timed sequence which makes this warning sign be visible for 1 second and then be invisible for 1 second and alternates - this only occurs when a specific monitor reaches a threshold though. For example, lets say I manually set a threshold of 10 for a pH sensor - the warning sign will be invisible until the pH sensor reads 10. Once the pH sensor reads 10, the warning sign has a 5 second delay and then it starts blinking.
Now comes the issue, I currently have it so that it blinks which is working fine but after much effort without any progress, I find myself not being able to keep the warning sign invisible when its below 10 (for example) or above 0 (for example), it's supposed to only start blinking if its above 10 or below 1. I've tried using the "In Range & Coerce" or just basic comparison functions but even if I set these manual thresholds, the blinking function inside the secondary while loop is still dominant (secondary because this entire security system is inside another while loop).
Let me know if you guys got any advice on how to make this work better.
Also, right now I'm only using the 2 pH sensors as my reference with all the other sensors on standby. You can tell that pH1 has been fully developed while pH2 is mainly testing the toggling visible/invisible function. I also believe there is a way to merge the signals of these or something similar in order to reduce the used space in the block diagram. Tips for this are also welcome.
Hi PDB,
@PDBSteenhuisen wrote:
Solved it myself haha!
I don't think this loop, set to run forever, is a solution for your problem!
The loop inputs will never change once the loop starts, and there is no way to stop it…
