I'm not sure I understand 100%. Here's what I think I've gathered:
1. Both counters are doing edge counting
2. There's some kind of external pulse source. (Or sources?). It's wired into the default source input for Ctr 0 (PFI8, according to MAX pinouts for a simulated M-series device).
3. It's unclear what, if anything, is physically wired to Ctr 1's default source input (PFI3 according to MAX).
4. Ctr 0 counts successfully, Ctr 1 doesn't.
5. When you configure Ctr 1 to use an internal timebase as its source signal for counting edges, then it *does* count fine.
If I've got that right, then the next thing I'd do is configure Ctr 1 to count edges on the signal that Ctr 0 is also counting. That's allowed, 2 tasks can both count edges sourced from the same PFI pin.
If that works, I'd suspect there's a conflict or oversight between the physical wiring in place for Ctr 1's pulses and the task configuration settings that define what Ctr 1 should count. Maybe the signal is wired to a pin *adjacent* to PFI3 or something like that.
-Kevin P
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).