Hi Marcos, thanks for the reply.
Sorry about the overlap of constants in the screen shot. It was one of those things you see after you hit send.
Changing the configuration call as you suggested didn't change the performance, and actually caused an error further down the line.
I did find/learn two things:
- I was expecting the "trigger" out of the PFI0 and PFI1 ports to be a continuous pulse train (one for every pulse out of Ch0 and Ch1). That was an assumption on my part, which was wrong as a colleague pointed out to me. I equate the word "enable" to single events, not "trigger". My bad. Something in the documentation explicitly saying this would be nice. Setting the o'scope trigger appropriately showed that the PFI0,1 pulses were there, sometimes.
- The real fix was to set the first NI FGEN VI (far left on image) Reset to TRUE. That made everything behave as expected, consistently. Problem solved.
Thanks!
John
"Praise the Lord and pass the ammunition."- Lt. (j.g.) Howell Forgy, Sky Pilot, USS New Orleans, 12/7/41