03-05-2012 11:27 AM - edited 03-05-2012 11:28 AM
Hello
I need to write .net code to generate two continuous pulse trains at the same time or with the 2nd pulse train at a fixed delay from the first on PCI 6723
I find the same question on http://forums.ni.com/t5/Multifunction-DAQ/Two-pulse-trains-with-fixed-phase-delay-using-USB-6216/td-.... The solution work successful on NI 6281, but I am fail on PCI 6723
I want to know does it possible create two continuous at the same time or with fixed delay using NI PCI 6723?
Thanks
03-06-2012 11:09 AM
Update: One Ni software engineer send ma a link regarding this issue https://decibel.ni.com/content/docs/DOC-10321. But i think PCI 6723 can not support arm start trigger.
03-06-2012 10:11 PM
Hi xinachilles,
Yes, I believe you're correct. The 6723 documentation doesn't say that it supports Arm Start Triggers.
Also, I was curious, what sort of frequency are you looking for? Are you using the AO and DIO for other tasks at the same time?
Regards,
03-09-2012 12:35 PM - edited 03-09-2012 12:38 PM
Hello,
It's true that the 6723 does not support the Arm Start Trigger (it uses the same underlying counter architecture as E Series if anybody is interested). However, these devices still support using a regular "Start trigger" so you should still be able to do what you want.
On hardware that supports it, the arm start is a dedicated line that can be used to enable the counter. On supported hardware, counter output tasks allow for both an arm start and a start trigger--the start trigger begins the output but will be ignored if the arm start has not yet been received. If you don't have a start trigger configured but you do have an arm start trigger configured, the effect is that the output will start immediately once the counter is armed (so the arm start and start trigger behave similarly if only one is configured).
Arm start triggers are more typically used for counter input tasks when you want to have control over when the counter actually starts counting (counter input tasks do not support the regular start trigger).
So, if you see reference to something that includes an Arm Start trigger applied to counter output task, in many cases you can get the same behavior using the regular start trigger instead (which is supported on your hardware). In your case, you can either implement a retriggerable single pulse to be triggered off of the continuous output of the other counter (would let you vary the delay on-the-fly), or you could configure two continuous counter outputs with the same trigger (or trigger one off of the other) but different initial delays (one counter output would end up with a pre-determined user-configurable delay relative to the other).
Best Regards,