LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

'Value(Signaling)' execution?

Does 'Val(Sgnl)' cause an immediate execution of the Event code inline (like a subroutine) or add to a queue to be executed later?

Thanks, K.Giles
0 Kudos
Message 1 of 7
(5,969 Views)
Value Signalling, just triggers the event case just like a normal user value change. The value will update immediatly but the event code will process whenever the event-case is idle.

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Message 2 of 7
(5,957 Views)


@TonP wrote:
Value Signalling, just triggers the event case just like a normal user value change.
... with the added bonus that it always triggers, even if the value actually does not change. For example of the current value is zero and you feed a zero to a value(sgl) property, the event will still trigger. 🙂
Message 3 of 7
(5,943 Views)

Is there a way to get a val signal to work just like a user clicking a button to get a value change event (boolean in my case). It just repeatedly keeps triggering the events even though the value is not changing. I'm sure this may be useful in some situations but I need the programmatic signaling  to work only when the value changes.

gtb

0 Kudos
Message 4 of 7
(5,825 Views)
Well, you can't get the val(sgnl) event to fire only when the value "really" changes, but the event data contains OldVal and NewVal data so in the event case you can test yourself to see if the datavalue really changed and only perform the desired action when they are not equal.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
Message 5 of 7
(5,820 Views)


@gtb1234 wrote:

Is there a way to get a val signal to work just like a user clicking a button to get a value change event (boolean in my case). It just repeatedly keeps triggering the events even though the value is not changing. I'm sure this may be useful in some situations but I need the programmatic signaling  to work only when the value changes.


Place the property node inside one case of a case structure and  execute the case only when the value changes (e.g. compare with shift register value from the previous iteration). The other case is empty and executed when the value did not change.

Simple enought? 🙂

Message 6 of 7
(5,813 Views)

Thanks for the suggestions.

gtb

0 Kudos
Message 7 of 7
(5,774 Views)