Adding delay to arm start Trigger

[n00b2992]

I need to add a delay to arm start trigger. Which triggers a counter. I have attached that part of my program. Have tried a few variations of this but cant get it to work. Any help is appreciated. 

[Kevin_Price]

I can't open your code right now, but in general I don't believe you can directly delay an Arm Start Trigger.

The first thing that comes to mind is to use a 2nd helper counter.  The helper will be triggered by your external signal and generate a single delayed pulse.  Your original counter task will use the helper's output as its Arm Start trigger source.

-Kevin P

[n00b2992]

i was looking in to doing that when i saw your reply. im wiring the second counter on my DAQ card how ever im still unsure about how to trigger a counter of another counter. ill attach all my files. you should have access to it all if you open the project.  

[Kevin_Price]

I only looked at "ClockSignalAcq.vi".  Since you're using Dev2/ctr0 for the edge counting task you want to Arm Start Trigger, I'll suppose you'll use Dev2/ctr1 to generate the delayed pulse.  

On the terminal constant where you presently specify "/Dev2/PFI7" as your Arm Start Trigger Source, right-click and pick "I/O Name Filtering...".  Then check the box to "Include Advanced Terminals".   THEN you'll be able to choose "/Dev2/Ctr1InternalOutput" as the Arm Start Trigger Source.  You shouldn't need to do any physical wiring.

-Kevin P

[n00b2992]

Im assuming that i have to make a block to run ctr1 to use it as in the said fashion. how do i set it up to trigger at a set count ? and who i connet the second counter circuit with the one i have.  

[Kevin_Price]

Attached is a modified version of your vi.  I added ctr1 to generate a delayed pulse after seeing a trigger edge at PFI7.  Your edge counting task on ctr0 uses the pulse as an Arm Start Trigger to start counting after this delay.

I made minimal changes to try to illustrate how to take some forward steps.

I suspect there are a lot more changes needed before you get all the behavior you want.  This sounds like an engine monitoring app.  I haven't done those but have helped a bit in several threads about them.  Do some more searching on the forums to see what else you can learn about similar apps.

-Kevin P

[n00b2992]

im looking at your version although im far from understanding it, i did run it. I got a weird plot for a couple of seconds and it crashed, Error 501103. The way i was hoping to trigger the second counter was after specific counts of the first  instead of milliseconds. You are right about the application and appreciate the advice. As you cant tell im very new at this.