Continuous Digital Waveform output from M-Series PCI-6229

[Dave_Karon]

I need some suggestions for continuous digital waveform output, as it is not clear from the examples or I do not find an appropriate example.

I am trying to convert a VI from 3rd party hardware to NI PCI-6229 with (2 of) BNC-2110 termination panels.

I have to be able to make AI, AO, and DO sampling on the same sampling clock rate and have to be able to trigger on the same signal.

I need to output a digital waveform, which will be a source for triggering AO and AI functions on the same DAQ card.

Or, I could use the sampling clock a and start trigger to time and start all three functions.

Basically, I am outputting 4 different sine waves out of the 4 AO channels and sampling 12 AI channels to provide feedback to control the AO signals.

I have to be able to output the digital waveform, for external device control.

I would prefer to output the digital waveform to either the PFI0 or PFI12 or in some other way be able to connect to an unused BNC connector on one of the BNC-2110 panels. (I am using all dedicated AI and AO connectors)

[Dave_Karon]

I've looked at the "Correlated Dig Write With Counter.vi" from the LV examples, but I guess my concern is how to best physically route the output signal that I want to use to an available BNC connector on one of the BNC-2110 termination panels.

thanks

Dave

[_kb]

Dave

You might find this tutorial article helpful.  The routing tables will provide a guide for all of the routing options for your device.  The article also describes the necessary DAQmx code to properly route your signals.

[Dave_Karon]

Kyle,

Thanks. That is helpful on a number of fronts, in this particular issue.

I've used another example as a basis for my digital waveform output, “Correlated Dig Write With Counter.vi” and replaced the last digital waveform with one of my own construction, which I can jumper to the User 1 terminal on the first BNC-2110 panel. I was a bit concerned about whether that DO can source loads of an NI-4772 channel and an external instrument and a PFI line to provide the start trigger for my analog tasks, but it seems to work okay.

More information on how to use the routing tables would be helpful, wrt how to do that in LV or CVI or MAX... e.g. route PFI1 to PFI13, route 80MHz Timebase to ai/sampleclock, ... , and when there are 2 or more entries in the "Subsystem Used" field, does that mean you have to pass through only one of those listed or do you have to pass through all listed subsystems. 

Thanks again

Dave

[_kb]

Dave

For CVI, check this out, specifically the Export HW Signals section.  The DAQmxExportSignal function supports routing clocks and triggers only -- not I/O channels.  This function has an equivalent LabVIEW VI.  LabVIEW also provides a DAQmx Signal Routing palette, with added functionality.  More info on the difference between LabVIEW implementations, here.

Often in the Subsystems Used field, MAX lists subsystems that you cannot access but through which your signal will be automatically routed.  If you run into a case where you see otherwise, let me know.  Typically, you will simply use the functions or VIs to define the source and destination.  It is very rare that you will need use two separate routing functions for the same signal.

[Dave_Karon]

Kyle,

Thanks for that info.  I use LV almost exclusively, but...

It has not been obvious to me that the routing or signal export VIs do the routing implicitly.

Thanks

Dave