08-01-2006 01:29 PM
08-02-2006 02:51 PM
Hello Jerry,
I think that the problem lies with the fact that you are using DAQmxCfgBurstHandshakingTimingExportClock. You are using DAQmxCfgSampleClkTiming to set the rate of the output, but then you use the other call to change that timing mode to burst. This will cause the problem that you are seeing because burst mode will not operate at a certain rate. If you need to export the sample clock, you should use DAQmxExportSignal instead.
Please let us know if you have additional questions.
Regards,
Laura
08-02-2006 07:33 PM
I tried using DAQmxExportSignal, however, it does not allow me to export the sample clock along "/Dev1/PFI5".
Thanks,
~Jerry Wu
08-03-2006 10:53 AM
Hi Jerry,
Can you give us more information about how this doesn't work? Do you get an error message? I just simulated your device and tried it and do not see a problem.
Regards,
Laura
08-03-2006 11:31 AM
I get this error when I try to run it on the real hardware.
DAQmx Error: Specified route cannot be satisfied, because the hardware does not
support it.
Property: DAQmx_Exported_SampClk_OutputTerm
Requested Value: /Dev1/PFI5
Suggested Values: PFI3, PFI7, RTSI0, RTSI1, RTSI2, RTSI3, RTSI4, RTSI5, RTSI6
Task Name: _unnamedTask<0>
Status Code: -89136
The hardware I'm using is PCI DIO-32HS
Thanks,
~Jerry Wu
08-03-2006 01:56 PM
Hi Jerry,
From that error message, the PCI-DIO-32HS does not support routing the sample clock to PFI5. Have you tried using PFI3 or PFI7? I was able to export the sample clock on a device in the same family for supported PFI lines, so I believe you should be able to do this on PFI 3 or 7.
Regards,
Laura
08-04-2006 10:42 AM
08-04-2006 02:17 PM
Hi Jerry,
That is certainly understandable. I have a work-around for using PFI5 that I just tested with the hardware. Before starting your task, use DAQmxConnectTerms to connect RTSI0 to PFI5. Then, use DAQmxExportSignal to export the sample clock to RTSI0. This will route the sample clock signal onto PFI5. Just be aware that once you use DAQmxConnectTerms, those terminals are connected until you run DAQmxDisconnectTerms or reset the device, so you may want to disconnect the terminals at the end of your program.
Hope this helps,
Laura
08-04-2006 04:46 PM
Hi Laura,
Another question, is there a maximum number of samples that functions such as DAQmxWriteRaw can handle at one time?
Thanks,
~Jerry Wu
08-07-2006 02:04 PM
Hi Jerry,
There is not a maximum, however, you will run into memory problems with your computer and development environment if you try to handle too much data at a time. If you have a large file that you are reading data from, you should break the data into smaller chuncks before using any write function. I know this isn't a very concrete answer, but it will be system dependent. How much data are you planning on writing at a time?
Regards,
Laura