LabVIEW
Event-Loop and parallel while-loop or better two event-loops?
@JÞB wrote:
Oh where is that "trip to Grandmas' post of mine?
I think it starts here:http://forums.ni.com/t5/LabVIEW/Interrupt-a-an-unfinished-state-in-a-QSM/m-p/2820274#M825410
FYI, it is tagged with "Grandma" so you can find it quickly next time.
@crossrulz wrote:
@JÞB wrote:
Oh where is that "trip to Grandmas' post of mine?
I think it starts here:http://forums.ni.com/t5/LabVIEW/Interrupt-a-an-unfinished-state-in-a-QSM/m-p/2820274#M825410
FYI, it is tagged with "Grandma" so you can find it quickly next time.
That was tagged with Grandma about a minute ago while editing my last post here
@JÞB wrote:
@crossrulz wrote:
@JÞB wrote:
Oh where is that "trip to Grandmas' post of mine?
I think it starts here:http://forums.ni.com/t5/LabVIEW/Interrupt-a-an-unfinished-state-in-a-QSM/m-p/2820274#M825410
FYI, it is tagged with "Grandma" so you can find it quickly next time.
That was tagged with Grandma about a minute ago while editing my last post here
Regardless, it is one of the best analogies I have ever seen for a state machine gone mad. I'll definately be using it whenever I get my user group going.
@OnlyOne wrote:
I really would use a queue but the problem is that i then cannot stop the running vi.
1. I press "Start" in the event -> queue is starting my Measurement-vi which is running for some minutes
2. I press "Stop" in the event -> queue is queuing this command and waiting for start is finished before processing stop.
So with queue i cannot stop the vi, thats why i use globals.
1. Press Start will queue start which will setup measurement and queue Measure.
2. Measure measures (e.g. 0.1s worth of data) and queues measure until done.
3. Press stop will queue stop which'll stop the program after the next measure
/Y
