08-27-2014 01:03 PM
Don't. Just start the acquisition on its own.
08-27-2014 01:09 PM
How do you suggest it? I need this automated so that the pulse train is telling the program when to acquire and when not to.
08-27-2014 01:45 PM
08-29-2014 07:23 AM
What? If the counter isn't connected to anything and he has set a trigger, then the acquisition will never start.
08-29-2014 08:02 AM
08-29-2014 10:22 AM - edited 08-29-2014 10:23 AM
> If the counter is truly nor connected to anything else, your acquisition will start when you call the DAQmx Read.
He will have to change the program to get rid of the trigger. Simply not having anything connected to the counter is not sufficient.
08-29-2014 10:41 AM
08-29-2014 10:58 AM
Right. We're agreeing. The problem was, in the quoted post, you didn't reiterate that he'd need to change the program. You made a prediction, and did not conclusively close off the possibility that it applied to the program he already had.
08-29-2014 11:03 AM
09-02-2014 08:17 AM
Yes, the program would certainly have to be changed.
I did alter it a different way, however.
Based off how the old code was written, I did the following:
Linked CTR0 and CTR1. CTR1 is physically wired to a digital line.
When this line reads high, nothing happens, when it is low, the acquisition and logging occurs.
Thanks for all the help.
Dennis: using the front panel boolean to trigger the acqusition is NOT what I need. I need the user to use the front panel boolean to start the pulse train which triggers acquisition/logging when the train is low.