10-05-2017 12:22 PM - edited 10-05-2017 12:25 PM
Though I only program in LabVIEW and have little to offer on the text-based API's, I *can* say that you need to use forward slash "/" instead of back slash "\". I suspect that might be the *only* thing you need to change.
-Kevin P
P.S. Oops, went and did a reply without refreshing the thread first. Kudos to protocoled for getting there first.
10-05-2017 12:30 PM
Sorry, that was my fault because I have it assembled in code and not hard coded. I do have the proper slashes "/" in the code. Now the cDAQ itself has device routes for the ai/SampleClock, but not the AI device itself. It only has a PFI0 and an AnalogComparisonEvent device routes. Maybe I need to use the PFI0 as an external clock. What needs to happen in hardware to use the external trigger? Do I wire a jumper between the two PFI0 lines of the two modules?
10-12-2017 09:41 AM
The thing that seemed to have solved the problem was to not use the different devices with their own tasks, but to create a single task for the CompactDAQ device and include all channels from all devices into a single task. Then you don't have to even specify a clock source because the only one available is the CompactDAQ clock. My errors were due to trying to reference the same clock between two tasks. It is the same clock. I now have to completely restructure that portion of the code because it was wrapped around having each device have its own task and receive and gather the data for each device independently. That is the way the PXI and PCI devices work because each card can be independent from any other device. All examples in code have each device with their own task.
Thanks for all of the suggestions. I did get this single task suggestion by emailing the support directly and it worked for me. Just wanted to make sure to share the solution to the problem.
Mike