What gets reset with "retriggerable" for CO pulses?

[cstewa]

When using the Trigger property node, and a boolean TRUE wired to the "retriggerable" option, what gets reset? It does not seem to include the "initial delay time." Unfortunately, I must have a user-adjustable delay prior the pulse triggered by another channel. Is there any way to do this? My board is a PCI 6024E. Thanks, matt

[chericks1]

Dear Matt (cstewa),

Thank you for contacting National Instruments.

To address your question, retriggerable pulse generation is simply an extension of single triggered pulse generation. However, the counter remains armed after generating the first pulse instead of disarming itself. While it is armed, the counter responds to triggers on the gate by generating a pulse on the counter's output line. The initial delay time between receiving the trigger and outputting the pulse generation is user-adjustable. Use the DAQmx Trigger property node to reconfigure the initial delay. This property is located under Start -> More -> Delay.

Let me know if you have any further questions or if this does not resolve your issue.

Thanks again and have a great day!


Chad AE
Applications Engineer - National Instruments

[cstewa]

Dear Chad,
Thank you for your response. I had tried your suggestion without success earlier. I just added it to a functional vi, with an error result, as follows:

[Error -200452 occurred at Property Node DAQmx Trigger (arg 1) in AI Master_Buffer_AI_CO_10.vi

Possible reason(s):

Specified property is not supported by the device or is not applicable to the task.]

I can't tell if the initial delay, described as applying to the first pulse, gets reset.

I have a very simple task for a simple multi-function vi. I thought the CO pulse would be a good and easy solution, but have been completely stymied. What I am trying to do is record and stream to disk a few analog input channels. I am using one channel as an input to PFI0, to trigger a pul
se out. What I absolutely need is a single pulse only, with a user adjustable delay from the time the trigger is received until the CO pulse.

The periodic signal that drives the vi ranges from 50 to 150 Hz. I have to adjust the various high and low times to only output a single pulse. My vi is almost there, it has a 'phase-locked' pulse that is consistent over time over the bandwidth needed. My last task is to add the delay. I would prefer to solve this using a counter property in order to exploit hardware timing, rather than a software trigger.

Do you have any ideas? Thanks again. I can correspond by email or phone if that is easier, take care, matt.