LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Spikes in Elapsed Time (Variation in Code Performance)

@altenbach

Did you mean implementing a state machine within subVI for saving code? 

0 Kudos
Message 11 of 16
(533 Views)

NO, I mean more like an "action engine". (Sorry for the poor terminology). Yes, everything is in the subVI.

Message 12 of 16
(526 Views)

@altenbach

That is interesting. I am not familiar with "action engine" but I will learn more about it and try to implement it in the code. Thank you for the input.

0 Kudos
Message 13 of 16
(522 Views)

Here's a very rough draft of what I had in mind:

(Very rough! Needs more TLC to be safe to use, so modify as needed. You can use a feedback node (shown) or a shift register in a dummy loop. "Mode" should be a typedef, of course. "Save" is the default, so you typically don't need to wire the mode in the caller)

 

altenbach_0-1669045634015.png

 

 

Message 14 of 16
(519 Views)

@altenbach

Thank you, I will look into it. This looks interesting.

0 Kudos
Message 15 of 16
(513 Views)

Also note that since the ref is kept open, it will keep track of the file position and always correctly write right after the previous data. I would probably turn off "convert EOL", less overhead.

0 Kudos
Message 16 of 16
(497 Views)