ceties
2008-07-08 14:40:16 UTC
In our measurements we perform retriggerable DAQ. The application is complicated but attached code represents the core of the DAQ. We encountered following problem(s).
1] If I simulate the process everything seems to work smoothly. But if I use the real device (PCI 6110) and I utilize it to acquire 8000dbls on each trigger it acquires into the buffer only 7994dbls on the first trigger. Following trigger has already 8000dbls but the first 4dbls obviously belong to the end of the data from the previous trigger.
What could cause this? I am able to do some workaround by acquiring 8004 and cutting first four dbls but I would like to know why is this happening and why exactly 4dbls.
2] Is it possible to simulate trigger occurrence in retriggerable DAQ? My problem is that if I use simulated device the triggers occur immediately and it's not what I want. Would be nice to generate trigger on button press.
Thanks for any help
We used LabVIEW 8.2 and NiDAQ 8.3
Retrigger_example.vi:
http://forums.ni.com/attachments/ni/250/41398/1/Retrigger_example.vi
1] If I simulate the process everything seems to work smoothly. But if I use the real device (PCI 6110) and I utilize it to acquire 8000dbls on each trigger it acquires into the buffer only 7994dbls on the first trigger. Following trigger has already 8000dbls but the first 4dbls obviously belong to the end of the data from the previous trigger.
What could cause this? I am able to do some workaround by acquiring 8004 and cutting first four dbls but I would like to know why is this happening and why exactly 4dbls.
2] Is it possible to simulate trigger occurrence in retriggerable DAQ? My problem is that if I use simulated device the triggers occur immediately and it's not what I want. Would be nice to generate trigger on button press.
Thanks for any help
We used LabVIEW 8.2 and NiDAQ 8.3
Retrigger_example.vi:
http://forums.ni.com/attachments/ni/250/41398/1/Retrigger_example.vi