export waveform to spreadsheet

[jh5638]

Hi Rob, bad news, good news and more questions!

Bad:

I tried you're ideas, however the "DAWmx is task.." didn't appear to make a difference and seems to do a similar job as a stop/start operation.

Also taking the start stop out of the main loop doesn't work, because when the start is passed data is put into the buffer, by the time the read function comes up the buffer has filled an error message results everytime!

Good:

Finally tracked the problem... (fingers

[jh5638]

Hi Rob, bad news, good news and more questions!

Bad:

I tried you're ideas, however the "DAWmx is task.." didn't appear to make a difference and seems to do a similar job as a stop/start operation.

Also taking the start stop out of the main loop doesn't work, because when the start is passed data is put into the buffer, by the time the read function comes up the buffer has filled an error message results everytime!

Good:

Finally tracked the problem... (fingers crossed)

[jh5638]

Hi Rob, bad news, good news and more questions!

Bad:

I tried you're ideas, however the "DAWmx is task.." didn't appear to make a difference and seems to do a similar job as a stop/start operation.

Also taking the start stop out of the main loop doesn't work, because when the start is passed data is put into the buffer, by the time the read function comes up the buffer has filled an error message results everytime!

Good:

Finally tracked the problem... (fingers crossed),

[jh5638]

Hi Rob, bad news, good news and more questions!

Bad:

I tried you're ideas, however the "DAWmx is task.." didn't appear to make a difference and seems to do a similar job as a stop/start operation.

Also taking the start stop out of the main loop doesn't work, because when the start is passed data is put into the buffer, by the time the read function comes up the buffer has filled an error message results everytime!

Good:

Finally tracked the problem... (fingers crossed), annoyingly

[jh5638]

Hi Rob, bad news, good news and more questions!

Bad:

I tried you're ideas, however the "DAWmx is task.." didn't appear to make a difference and seems to do a similar job as a stop/start operation.

Also taking the start stop out of the main loop doesn't work, because when the start is passed data is put into the buffer, by the time the read function comes up the buffer has filled an error message results everytime!

Good:

Finally tracked the problem... (fingers crossed), annoyingly it

[jh5638]

Hi Rob, bad news, good news and more questions!

Bad:

I tried you're ideas, however the "DAWmx is task.." didn't appear to make a difference and seems to do a similar job as a stop/start operation.

Also taking the start stop out of the main loop doesn't work, because when the start is passed data is put into the buffer, by the time the read function comes up the buffer has filled an error message results everytime!

Good:

Finally tracked the problem... (fingers crossed), annoyingly it's one of those

[Robert_Lee_NIUK]

Hi Jon,

righto, though the clear task etc might not work, it was a bit of a long shot. I wasn't aware of your sampling rates so my apologies for the idea of placing everything in the first loop.

Keep me posted on how it goes

Cheers

[jh5638]

HI Rob thanks for your help!

Good news, bad news and more questions!

Bad:

The "is DAQmx finished..." doesn't appear to make a difference and seems to just to do what the start/stop are doing already!

Taking the start/stop out of the loop doens't work as as soon as the start is passed data is put into the buffer, by the time the read function comes up the buffer is full and so errors fire up!

Good:

Found what I think is the problem, a silly staring in your face thing. Using the elapsed time VI on the first run it works perfectly, then since it must auto-reset it feeds in the time when the reading stops. Then the sample cools and the current runs up again (at least 30s) so when the 8s for the loop is filled back in, the elapsed time sees plus 30s and so triggers straight away hence only one data point!

Questions:

How do I stop this? I can think of two options, putting another elapsed time into the main loop and feed that into the start time for the elapsed time VI? Or removing the loop and going off DAQmx timing, howvere I want a T/F constant once it has finished reading to feed into something else (a safety feature!). The timing is controlled by error paths atm, can I change a path somewhere to a True once passed? or similar? I.e  How to return a true constant once the DAQmx has finished reading?

Thanks

Jon

p.s sorry for double posting!

[Robert_Lee_NIUK]

Hi Jon,

Does this do the job for you? By resetting the Timing VI on the first iteration of the loop only (and ignoring the automatic reset completely), I think this behaves how you want.

Let me know

Cheers

Message Edited by Rob L on 04-09-2008 05:11 AM

[jh5638]

Brilliant! Yeah that works, I had been trying for ages to find a way to just reset it on the first iteration, a case of not being able to see the wood for the trees!

Thanks

Jon