Check that what you are getting out of your pulse measurements vi is what you are expecting.
Even if you input a waveform with 100 pulses, you'll only get 1 measurement out (of the first pulse). You may need to put this function in a while loop incrementing the pulse number to be measured until there are no more pulses. That way you'll get a measurement for each pulse.
There is also an automatic conversion going on at the input to the pulse measurement vi to convert from a dynamic data type to a waveform.
It may be converting it correctly how you want it, it may not. You might want to insert a "convert from dynamic data" vi in there and select the correct convertion type.
As far as the problem writing to a measurement file goes, you'll have to hope someone who is an expert on express vis answers your question.
They seem to be fickle beasts those express vis. I steer clear of them.
I can only suggest you handle the file writing without the express vi. Doing it with discrete functions. Then you will actually be able to tell what is going on rather than function being handled by a mysterious black box.
As far as I can tell, the solution suggested by Matthew will stop it writing new files every second when flow = 0, but you will only get 1 file total, rather than one file every day.
And it doesn't explain why the express vi changes from expected behaviour (writing one file a day) to writing a new file every second.
Message Edited by Troy K on
03-18-2008 10:33 AM
Troy - CLD
"If a hammer is the only tool you have, everything starts to look like a nail." ~ Maslow/Kaplan - Law of the instrument
