04-19-2007 07:30 PM
04-20-2007 08:07 AM
I'm not near hardware to verify for sure, but I *think* the M-series boards' counters support a mode called something like "two edge separation" measurement. This only requires 1 counter which detects both edges.
So, generate a pulse with ctr0. Setup ctr1 to measure "two edge separation", using Ctr0 output as the earlier edge and your external response pulse as the later edge.
Another sneaky option would be to setup ctr1 for buffered period measurement. Ctr0 output would act as an "Arm Start" trigger and your external response pulse would be the Sample Clock. The 1st (and only? -- depends on your device) measured "period" would be the time from the trigger to the first response edge.
-Kevin P.
04-20-2007 10:46 AM
The full message looks like this:
Property: CI.CtrTimebaseActiveEdge
Source Device: Dev1
Source Terminal: 80MHzTimebase
Destination Device: Dev1
Destination Terminal: Ctr1Source
Required Resources in Use by
Source Device: Dev1
Source Terminal: PFI12
Destination Device: Dev1
Destination Terminal: PFI4
PFI12 being the output of ctr0 on this board and PFI4 is the gate input of ctr1.
Then I tried routing the 20MHz timebase signal to the ctr1 source. But that did not work either. The same error resulted. In retrospect, it is the same issue. So, I am kind of stuck at that point. Let me look into your second idea.
Aniket
04-23-2007 11:50 AM
04-23-2007 07:56 PM
04-24-2007 05:14 PM
Aniket,
I played around with your VI and have attached a much cleaner version of your code. The only thing I had to do was connect another TTl signal to PFI9 and it measured the seperation between the channels.