11-16-2007 01:56 PM
11-20-2007 09:58 AM
Hello Paul,
Thanks for your reply and for the VI. I will use this to try to recreate your issue and see what modifications to your code I can suggest.
12-14-2007 05:24 PM
12-17-2007 06:05 PM
Hello Paul,
I am still trying to find where this issue is occurring. I should have an answer for you in the next few days. Thanks for being patient.
12-26-2007 09:46 AM
Hello Paul,
One odd thing I noticed is that sometimes I can get the LabVIEW shipping example Multi-Function-Ctr Retrigg Pulse Train Generation for AI Sample Clock to miss triggers when using certain combinations of trigger rates and sample rates that should work according to the specifications of the card. Since your VI is based on this example, I feel that these issues can be related. I have found that removing the DAQmx Configure Input Buffer VI from the task configuration, which makes DAQmx automatically configure the input buffer, eliminates this "hanging" behavior. I am not sure what causes this, but I have shown the issue to R&D and as soon as I find anything out I will post a reply to this forum to let you know. Please let me know if removing this buffer configuration helps.
02-04-2008 03:23 PM - edited 02-04-2008 03:26 PM
Hi Browning,
Sorry for the slow response; I hadn't noticed your latest response. I tried eliminating the DAQmx Configure Input Buffer and it didn't appear to help (results from the test vi I posted earlier were similar). Any word from R&D? I've been able to ignore this problem during development of my program since it happens relatively infrequently but recently I've gotten to the point where I'm running my data acquisition for long periods of time and have noticed it hanging every once in a while so it is starting to be problematic...