DAQ-MX version of Traditional Ni-DAQ's "AO Control.vi" iteration parameter?

[Martin F]

I'm trying to convert some existing LabVIEW code for synchronized AO, AI, and DO on PXI-6115/6120 cards from traditional NI-DAQ to DAQ-MX. In the existing code I have used the "iterations" parameter on the "AO Control.vi" in order to repeatedly output the same analog buffer a finite number of times.

How do I do the same thing with DAQ-MX? I don't see a corresponding "iterations" parameter.

[McKala[DE]]

Hi Martin,

To generate a finite number of iterations of a buffer in DAQmx you set the "sampler per channel" property of the DAQmx Timing VI to your (number of iterations) X (number of samples per channel in the buffer). 

I'm excited that you are converting your code, the DAQmx driver is so much easier to use.  Here are some great references about converting from Traditional DAQ to DAQmx:

What are the Terminology Changes in NI-DAQmx?

Transition from Traditional NI-DAQ to NI-DAQmx

Good luck!

Message Edited by Micaela N on 11-03-2005 08:55 PM

[McKala[DE]]

Here's that first link again:
What are the Terminology Changes in NI-DAQmx?

[Martin F]

Thanks for your help Micaela. That's simple enough.

Unfortunately my transition to DAQmx isn't going too smoothly so far. Specifically it seems to be exacerbating a problem I have seen in the past with traditional NI-DAQ where I loose some anlog input data while doing simultaneous analog out, analog in, and digital out, at high rates on a PXI-6115 board. With DAQmx I not only see the problem at even lower data rates than with traditional NI-DAQ, but as I bump up the rates some more (but still well within the specs of the board) I have the fun experience of entirely locking up the PC.

The reason I'm frustrated about this is that when I brought this problem to NI support's attention some months ago (in the traditional NI-DAQ version) they were able to reproduce the problem, but told me that the problem didn't occur with DAQmx, which had just then added support for the 6115. But now that I actually try it (having updated my DAQ software) I have the same, and worse, problems.

Anyway, I've sent my code (DAQmx version) to NI support and hope we can finally resolve this problem once and for all. We'll see.

Thanks again for you help.