ND_RETRIG_PULSE_GNR in NIDAQMx single pulse generation

Share icon

Hi,
In the old NIDAQ tools I used to configure a "Retriggerable" pulse for a counter with the function fNIDAQ_Param_Constant:

Variable single_pulse_gnr=fNIDAQ_Param_Constant("ND_RETRIG_PULSE_GNR")

and then

fNIDAQ_GPCTR_Set_Aplication (DeviceNumber, counter1,single_pulse_gnr)


How can make the same thing in NIDAQmx ?

Thanks in advance for any help
Wow. That takes me back... I'm a little rusty on the old-style functions, so help me out. If I recall correctly, that would make a single pulse that can be extended by a trigger that comes in during the pulse, right?

John Weeks
WaveMetrics, Inc.
support@wavemetrics.com

February 18, 2014 at 09:43 am - Permalink

Hi John,
basically I used this command to trigger a Counter several times (to give just one pulse) without need of restart the counter every time (the counter just sit waiting for the right trigger source), that is the ND_RETRIG_PULSE_GNR mode for.
Seems that in the new NIDAQmx there no way (as far I know) to do that.

Thanks for any advice in this matter

--
Carlos Rozas,PhD
Research Fellow
Albert Einstein College of Medicine
Department of Neuroscience
Kennedy Center, Room 429
1300 Morris Pk. Ave.
Bronx, NY 10461
Profile: http://www.researchgate.net/profile/Carlos_Rozas/

February 18, 2014 at 04:34 pm - Permalink

Thanks John for your help.

Basically I was expecting that the operation DAQmx_CTR_Outputpulse after being triggered and deliver the pulse will "re-arm" the Counter (without using fDAQmx_CTR_Start again) and then wait for the next defined trigger in /TRIG parameter (either internal or external source). I used this way before in the old NIDAQTools.

Thanks for posting my question in NI.



--
Carlos Rozas,PhD
Research Fellow
Albert Einstein College of Medicine
Department of Neuroscience
Kennedy Center, Room 429
1300 Morris Pk. Ave.
Bronx, NY 10461
Profile: http://www.researchgate.net/profile/Carlos_Rozas/

February 18, 2014 at 05:23 pm - Permalink

Ah- OK, so you don't need to extend the pulse, you just need to be able to retrigger the pulse after it has been produced once.

You are correct, NIDAQ Tools MX didn't have that option. Now it does: I have added a flag to DAQmx_CTR_OutputPulse, /RETR=1 will now make the operation retriggerable.

John Weeks
WaveMetrics, Inc.
support@wavemetrics.com

February 19, 2014 at 01:16 pm - Permalink

Thanks John,

I will be waiting anxiously to test your modifications for DAQmx_CTR_OutputPulse,

as always you are very helpful.


johnweeks wrote:
Ah- OK, so you don't need to extend the pulse, you just need to be able to retrigger the pulse after it has been produced once.

You are correct, NIDAQ Tools MX didn't have that option. Now it does: I have added a flag to DAQmx_CTR_OutputPulse, /RETR=1 will now make the operation retriggerable.

John Weeks
WaveMetrics, Inc.
support@wavemetrics.com

--
Carlos Rozas,PhD
Research Fellow
Albert Einstein College of Medicine
Department of Neuroscience
Kennedy Center, Room 429
1300 Morris Pk. Ave.
Bronx, NY 10461
Profile: http://www.researchgate.net/profile/Carlos_Rozas/

February 19, 2014 at 03:16 pm - Permalink

Hi Carlos,

 

How you fixed it? I have the same problem. I would like to retrigger the  DAQmx_CTR_OutputPulse. I have the problem with the counter.

 

Thanks,

Pedro.

October 29, 2019 at 02:15 pm - Permalink

Hi Pedro.

I ask John Weeks for a fix of that issue and he gave me back a modified version of NIDAQTools. But he said (back in 2014) they included that fix in the new release of NIDAQmxTools.

Best regards

Carlos Rozas,PhD
Assistant professor

Laboratory of Neuroscience
Biology Department
Faculty of Chemistry and Biology
University of Santiago
Alameda 3363, Santiago, Chile.

56-2-27181088
carlos.rozas@usach.cl

 

October 29, 2019 at 03:16 pm - Permalink

Woops. I have added the documentation for the /RETR flag to the NIDAQ Tools MX reference help file. You have it, it's just not in the help file.

October 30, 2019 at 10:20 am - Permalink