Request suggest for tool or card that can provide precision timing record during voltage change.

[KennyNg2012]

Good day to All.

Kenny here.
I am working oin a tasks that need to measure precision timing record during voltage change via LabView program.

Condition:
Need to continue monitoring interrupt voltage from 3V~3.3V drop to 0.1V(or lower) , need o get the timing in mili second.

Ideal steos:
1) LabView send command to it(card/tool) to trigger start monitoring volatge (Above 3V ~ 3.3V), it start record the timing in mili second.

2) The Card/tool when detect the volatge had drop to a given volatge (example 0.1V or below). It will stop measuring vlatge and record the time.

3) LabView send command to ask for item(2) Timing data. (Timing form trigger start unitl volatge drop to 0.1V)

Seeking advices and suggestions, your kindly feedback would be highly appreciated! Man thanks and have a great day to you.

[santo_13 · Accepted solution]

If all that you need is timing accuracy in ms, you can use counters in DAQ.

An alternate technique is to acquire the analogue signal using a DAQ at high speed and post-process the timing in software.

[KennyNg2012]

Hi Santhosh good day to you.

First of all, thank you so much for your advice. 

I will try use a NI DAQ PXIe-6321 for study signal trigger and capture. 

If you have any vi that doing same signal capturing, if possible kindly do share with me.

Thank you and wish you have great day! 

If you 

Thank you.

Best Regards,

Kenny Ng

[santo_13 · Accepted solution]

Please check out NI-DAQmx Data Acquisition Triggering Techniques Using LabVIEW - NI for some triggering techniques and acquire the signal of interest.

[Henrik_Volkers · Accepted solution]

ms doesn't sound much, however the scale is also important, if you want ms over some seconds or hours or days ..

absolute or relative to something else (easy part: other signals captured with the same(!) timebase) 

[Kevin_Price · Accepted solution]

If I understand your requirements correctly (and I'm not entirely sure I know *all* of them), this sounds to me like a good use for a straightforward continuous analog input task in a Producer loop and some code to monitor and evaluate the data on-the-fly in a Consumer loop.

A good rule of thumb is to read about 1/10 sec worth of data each Producer loop iteration and do nothing else in the loop except send the data to to the Consumer loop via Queue (or Channel Wire).  You may find the built-in analysis function for "software triggering" useful in the Consumer loop because it's already coded to handle the seeming discontinuity from receiving continuous data in discrete chunks.

-Kevin P