LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

property nodes & Sequences

David,

Doing some research about the event structure is a very good idea because event structure is a very handy/powerfull/cool tool.

 

I think your question “How to extract the value of rolling so it can be used elsewhere in the VI” shows that your architecture might not be appropriate to what you’re trying to do.


I can give you different ways to read the value of “rolling” from another part of the VI, even from a different VI or a different application but the question that should be considered is “At the moment “rolling” is being read at the other part of the VI, is the value what you wish it is ?”… I am not sure I am being clear Smiley Indifferent

You said that this "rolling" control determines if you have to write something or not, correct ? So why not puting the bit of code that write (or not) in a subVI and place this subVI inside the loop.. this way you will be sure that when it comes to decide wether or not you will write, the value of rolling is the current value.



By the way, what are you writing ? and where to ?


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 11 of 13
(530 Views)
David,
also, if you need something quick that does what you said, you can just read (at the rate you want, I put 50ms but you might not need it to be that fast) the value of "rolling" with a local variable in a PARALLEL loop that has no link (wires) with the other.
see attached VI.

hope this gets you to the point 😉

We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 12 of 13
(524 Views)
Well, if you want exact timings, you should use a timed loop. 🙂 Remember, you can adjust the loop time during the run.
 
Attached is a quick draft to achieve your timings (I actually added an indicator to show the duration of the last state).
 
Good luck! 🙂
 
(I am sure it needs a tweak here and there to suit your exact needs, but see how much simpler the core code is! No sequences, one single timings array, no property nodes or local variables, etc. ;))
Message 13 of 13
(519 Views)