12-20-2007 06:00 PM
12-21-2007 09:14 AM
12-21-2007 09:15 AM
I don't fully understand your measurement goals. To help me out, let's consider the interval between the 1st and 2nd pulses of the 1 Hz clock. You can expect 100 pulses of the 100 Hz clock during that time. What data do you want to collect?
A. 1 measurement from the rising edge of the 1 Hz clock to the first subsequent rising edge of the 100 Hz clock
B. 100 measurements representing the time from the rising edge of the 1 Hz clock to the rising edge i of the 100 Hz clock
C. 100 measurements (actually 99) representing intervals between consecutive rising edges of the 100 Hz clock.
Also, it'll help to know what data acq board you have. Certain capabilities like "arm start triggers" and "two signal edge separation" measurements may be very useful, but are not available on all boards.
You probably want (or at least you probably *should* want) to perform a buffered measurement so you can achieve hardware-accurate timing. Your references to "continuously reading count values" sound like software-timed polling, which can't be nearly as accurate or precise.
-Kevin P.
12-21-2007 09:29 AM
Thanks guys for your reply.
For Kevin's post, I think I am try to do the B option. The 100HZ is only the average rate which is not exactly 100HZ and that's why I want to measure the time duration of each pulse of that train from the 1HZ pulse (my reference in this case) .
For ShotSimon's post, I am not using frequncy measurement and the two pulse I am measuring are both from external device. The 1HZ pulse is actually a 1PPS signal from GPS receiver which fires at each even GPS second (GPS time), The 100HZ train is the data sampling clock from Inertial Measurement Unit (IMU). I just want to timestamp each IMU sample clock pulse related to GPS second. Because there's fluctuation on the IMU sample clock, so it's not perfect 100HZ.
I am using DAQ-card 6036E. It looks like doesen't support arm trigger. We also want to implement the same application on a M-series board in future. So I would like to know what's the best options for each set of my instrumentations.
Thanks
Feilong
12-21-2007 09:44 AM
12-21-2007 11:23 AM
12-21-2007 04:10 PM
Hello,
Yes, you are correct the 6036E E-series card does not support the Arm Start Triggering, but the M series cards do support this feature. For the future possibility of an M series card, I would suggest using the two counters with the arm start trigger.
As for the E series card, I was a little confused about the setup you are describing. You mentioned that you wanted to use the two pulses (the 1 Hz GPS and the 100 Hz IMU) to be the same external sample clock for one counter (counter 0). However, later in the same post you mentioned wanting to use the two pulses as two different gates. I am going to assume that you want to use the two pulses as gates on the same counter in-order to have them share the same 100 KHz source. Then your question was how to differential in-between the two measurement, since you want to use an OR gate.
The problem is that whether you are using this setup (one counter) or utilizing two counter that share the same 100 KHz source on the E series … you still are not addressing the fact that the two inputs (1 Hz GPS and 100 Hz IMU) are not synchronized. This will result in an offset signals and your measurements will not be reliable. Thus the differential question is not as relevant
I would suggest using Buffered Period Measurements with a M series card for this application. However, I do realize that in the end you might be trying to find a quick solution with the E series card. For this, I would suggest taking the GPS out of the picture and just input the fluctuating 100 Hz signal. With this setup you explore software monitoring options.
I have included links to articles about counters and Buffered Period Measurements.
Period Measurement with a Counter
Measure Buffered Pulse-Period on 2 Counters Simultaneously (DAQ-STC)
12-21-2007 05:11 PM
12-21-2007 05:11 PM
12-21-2007 05:44 PM
And for the M series card, I read a post somewhere in the forum mention a setup like this:
1. use encoder reading setting for the counter
2. use my 100HZ pulse train as gate
3. use internal 100KHz as source.
3. use my 1PPS train as Z to hardware reset the counter to 0 on the fly
I would think this is a good way to derive the time elasped (the arriving time instant of each 100HZ pulses) since most recent 1PPS pulse.
Please comment this idea.
Thanks and Merry X mas for all you guys
Feilong