09-06-2007 05:15 AM
09-10-2007 03:39 AM
Richard Keromen
09-14-2007 03:21 AM
Richard Keromen
09-14-2007 05:54 AM
09-17-2007 07:36 AM
Berenguel,
It is not possible to run two task simultaneously on the same material. A task can also (you have done so with the DAQ assistant) contain several channels. Because of this, if you stop the task, you stop the reading of all channel defined in your task.
Do you really need to stop the acquisition when you detect a peak? You could imagine ignoring the records for a specific channel made after this detection.
Cordially,
09-17-2007 08:49 AM
I don't need to stop when the program detect a peak. But I need the value of time in the first peak of each sensor (different time). I don't need nothing more.
I need to make some calculations to discover the distance of the fracture to the sensor! (it's not done for now). It's anyway of doing that?
I had try using the statistics block, using maximum peak and maximum time, but the value of time it's so stupid (ex: 3272880361,495139). It's impossible to have a time of this value.
Best Regards,
Berenguel09-18-2007 04:02 AM
Berenguel,
First, the timestamp you generate in your code is not correlated with your acquisition timestamp: The DAQmx driver can provide these informations through a waveform data format. It contains the origin timestamp (t0), the time between two sample (dt) and an array of sample ([Y]). Use the VI Convert from Dynamic Data.
Second, the timestamp value you get in second is coherent: it corresponds to the time elapsed in seconds since the 1st january, 1904. And if you only need the elapsed time between two timestamps, do a simple difference.
An other thing: do you know when will appear the peaks? Do you have a maximum time between they occur?
Regards,
09-20-2007 07:31 AM
10-04-2007 10:46 AM - edited 10-04-2007 10:46 AM
Message Edité par Mathieu R. le 10-04-2007 05:46 PM
10-10-2007 05:25 AM - edited 10-10-2007 05:25 AM
Message Edited by berengas on 10-10-2007 06:17 AM