Just to expand a bit:
1. Install the Counter/Timer Palette update:
http://digital.ni.com/softlib.nsf/websearch/abc2de0382fb157a86256ad90068986e?OpenDocument
2a. Once installed, place the vi named "Counter Start Trigger (NI-TIO).vi" (found under the "Util" icon in the Counter palette) into the config chain of both the counters you are using for buffered period measurement. Feed the same Trigger Spec cluster to both. (Note: trigger config must occur *before* starting the counters!)
OR
2b. Make use of the new multi-counter config vi's under the main Counter palette. They appear handy for such circumstances. Caution: Unlike choice 2a which I have done numerous times succesfully, I have not yet tried the multi-counter vi's. A
brief peek at the one for configuring the trigger looks questionable to me -- there is no place to wire in the trigger spec! (Sure,
it's easy to add it, but if *that's* missing, I have to wonder how thoroughly the stuff was tested, knowwhatImean?).
3. If an external TTL trigger signal is necessary or convenient, set config specs to use it. If not, you're still ok and here's how to do it without a screwdriver: set trigger selection to a PFI line corresponding to the output of an otherwise unused counter. You can then simply issue a single pulse on that counter via software to create a trigger that guarantees both your buffered period measurements are using the same instant as time=0. Just be sure that both your buffered period counters are configured *and* started before generating the single trigger pulse.
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.