Here are a few off-the-cuff observations to try to help move you forward some.
1. Both your simple event counting task and your buffered event counter are trying to use Ctr1. (The actual channel wired in doesn't agree with your comments).
2. The terminology "other counter" actually has a very particular meaning under the traditional NI-DAQ driver. Certain types of functions treat the counters as pairs, and "other counter" refers EXCLUSIVELY to the other member of the pair. The possible pairs are: (0,1), (2,3), (4,5), (6,7). You can't specify which counter you *want* it to mean by wiring the 'attribute value number' input.
3. I *think* you probably mean this on purpose, but did you realize that the simple event counter will start immediately after the buffered event counter? The 2 second delay will begin simultaneously, then both tasks will be stopped.
4. I don't see how you are trying to make the buffered event counter use your retriggerable pulse. It *appears* to me that you'd like the simple event task and the buffered event task to paired counters. Then the PMT pulses coming into the simple event task's Source pin can be successfully referenced in the buffered tasks gate config as "other counter source," causing it to buffer a time value on each incoming pulse.
5. Perhaps (?) you want to let the PMT pulses come into the retriggerable pulse task then have your other counter tasks respond to its output? That could make some sense if you'd like to use the retriggerable pulse task as a type of filter to suppress high-freq PMT pulses. I've recommended such things in the past myself.
However, the retriggerable pulses you are making never appear to get used for anything at all by the other tasks.
6. If you do indeed want to do something like that, I would highly recommend the use of "Route Signal.vi" to send the retriggerable pulse up to a RTSI line. Then you can configure your simple event counting task to use that RTSI line as its source and configure your buffered event task to use it as its gate.
7. I would then further recommend starting the two counting tasks first, then start the retriggerable pulse task. When you are done with your acquisition (2000 msec later), stop the pulse task first then the counting tasks. This method will keep your counts in sync.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
