I'd still say to go back to the original shipping examples that are known to work. Yes you can generate AO and capture AI at the same time. You could also generate DO and capture DI and generate counter pulses while doing counter measurement too. Like I said, the 63xx series of devices are *very* capable and flexible.
A couple specific things I see in your screenshots:
1. There's no good reason I can figure for you to run your For Loop to make an array of duplicate waveforms.
2. Later you feed that array into a DAQmx Write function that wants a 1D array of voltage values, not a 1D array of waveforms that *each* contain a 1D array of voltage values.
3. Further, if you intend to write a waveform-like set of samples to an AO task, you should have previously called DAQmx Timing to set up a sample rate and let the task know that it needs to create a buffer to hold the samples you will later write to it.
4. And once you do *that*, you'll find that you need to write at least *some* of the data to the task before you start it.
5. A screenshot gives me very little idea what the AI DAQ Assistant is configured to try to do.
It's with a combo of all these things in mind that you can more quickly confirm the board's essential capability of capturing what you generate by reverting to the shipping examples. Then you can change your own code to use normal DAQmx functions for AI instead of the very limited DAQ Assistant.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
