Read from channels

[kdm7]

okay

But, if you stack 6x25 components horizontally, transpose , append and again transpose as explained earlier, (to see results column wise), what is the size of the final array line?

[kdm7]

If directly taken (250 samples read per channel), then, is there a buffer overflow of errors?

Can you explain about the error buffers please?

[kdm7]

Here is my daq snippet.

Is it that the buffer overflows when I directly take 250 samples to read and taking ten 25 samples read will avoid this problem? (Sampling rate is 1000).

Anyone please explain this concept.  

[Dennis_Knutson]

None of that code makes much sense. I kept asking about a loop and it turns out you have nothing like what I thought. Just take the samples with a single read. None of that array manipulation is necessary.

[kdm7]

Here is the loop.

The array manipulation is just to log data column wise (I think).

These ten daqmx reads are used probably to avoid overflow of buffer.

Can anyone explain what happens and how?

[Dennis_Knutson]

You still don't make any sense to me, sorry. You've already been given a much more reasonable example and there are shipping examples to look at. Your code is way too complicated.

p.s. I was assuming a loop around a single read.

[kdm7]

I am actually documenting a VI.

This code is just for better comparison studies (25 samples of 6 channels are placed column wise for easy reading(for the user) of data in the file.) Eventually loop time should be 0.25 seconds.. Therefore 10 of these 6x25 components are stacked. 

My question is , does this code have any other purpose like .. it avoids buffer overflow error?

[crossrulz]

I see absolutely no point in breaking it up like that.  You are dealing with a total of 1500 samples.  A DAQ buffer should be able to easily handle that.  Get all of the samples in 1 read and save yourself the headaches.

But then you have the saving to a text file to go into the last sequence frame (sequence structure isn't necessary, BTW).  For the saving to disk, I highly recommend you go with a Producer/Consumer architecture.  The idea is that you have one loop reading from the DAQ and then sending it to another loop that writes the data to a file.  The communication is done with a Queue.