LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does a control go to zero when clicking outside of it?

I have a moderately high risk test application where I am using a labview program to control hydraulic actuators through PID. Recently when adjusting control parameters, I clicked outside of the control, and it immediately went to zero. This condition has only been replicated three times, and after program restart has not been seen again. I am very concerned this could happen again, and each time it does, it results in a catastrophic part failure. Does anyone know anything about this condition? Your help is appreciated. 

0 Kudos
Message 1 of 22
(3,017 Views)

Is anything else in your code writing to the control through a variable or property node? Is it possible that the data entry property for minimum is set to 0 and coerce? If you set a value less than that it will go to 0 when you click outside of the control.

=====================
LabVIEW 2012


0 Kudos
Message 2 of 22
(3,005 Views)

Is anything else in your code writing to the control through a variable or property node? Is it possible that the data entry property for minimum is set to 0 and coerce? If you set a value less than that it will go to 0 when you click outside of the control.

 

Edit: Weird. I don't know how the double post happened!

=====================
LabVIEW 2012


0 Kudos
Message 3 of 22
(3,004 Views)

Normal execution of LabVIEW should not cause this to happen.  Without seeing an example of your code, I can only suspect that you have some race condition by using local variables or property nodes where some other section of code is resetting your control back to 0.

0 Kudos
Message 4 of 22
(3,002 Views)

Unfortunately, I cannot post code at this time, however it is pretty basic, and there are no variables or property nodes that would force the control. Also, there was no minimum limits set. This is asn intermittent issue.

0 Kudos
Message 5 of 22
(2,979 Views)

What type of control?

 

If all that stands between your program and catastrophic failure is a user, you can count on trouble.  Sounds like you need a little range checking in your software.  Added bonus would be method of logging the frequency of these intermittent, and the time stamps can often be traced by back to certain people being in the room....

0 Kudos
Message 6 of 22
(2,965 Views)

There is range checking in place, and logging. I personally had this happen to me, and another one of my techs did as well on an entirely different control.

0 Kudos
Message 7 of 22
(2,955 Views)

Sorry, I did not specify control. It is a simple numeric input control.

0 Kudos
Message 8 of 22
(2,948 Views)

Is it a Integer/Unsigned numeric control?

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 9 of 22
(2,930 Views)

It is double.

0 Kudos
Message 10 of 22
(2,920 Views)