02-06-2009 08:50 AM
02-09-2009 02:00 PM
Hey soon1-
By default, the example that was posted earlier in this thread ran for one iteration. To get the example to run continuously until you elect to stop it, simple click on the little arrow next to the run option and choose "run continuously." See the attached image for a little more clarification.
Let us know if this helps.
Ben
02-09-2009 02:23 PM
Hi Ben,
Thanks for your response.
I did have the the program run continuously. The output ASCII file shown multiple iterations but the time stamps for each iteration start from zero each time instead of continue counting from the previous iteration (same time stamps for each iteration). But if you output Excel file from the log then the time stamps for the next iteration will continue from the previous iteration until you stop the run.
Thanks.
Soon1
02-10-2009 03:53 PM
Hey soon1,
I apologize for the slight misunderstanding. I have been able to mess with signal express and have been able to confirm the behavior that you are describing. While using Signal Express, the Acquisition Mode set to continuous samples has the same characteristics and the N samples setting. While this is certainly not ideal behavior, there have been some previous reports of this behavior. There are a few product suggestions and corrective action requests on this same issue. So, unfortunately, there is no way to specifically change this behavior and there is not setting that we are overlooking.
As for some possible work arounds; if you have access to LabVIEW you could do your acquisition fairly easily using the DAQ Assistant. Also, you could use the absolute time setting instead of the relative time setting. Also, you mentioned that you were able to get the time stamp performance if you export to Excel, so that is another work around that you could use.
Hopefully this helps. Let us know if these work arounds do not work for you.
Ben
08-05-2009 12:08 PM
I too am trying to save the time stamp data in my ASCII files. I cannot figure out how to enable this. Your Save to ASCII step tab looks different than mine. I have no X value options.
Using SignalExpress Version 3.0.0.
08-05-2009 01:06 PM
~EDIT~
Okay- seems that by saving to ascii the DC signals in Amplitude and Levels does not allow me the option to save the timestamp.
If I save the raw signal only the options in Save to ASCII change and allow me configuration of x values.
Weird that I can't save time with the DC signal.
01-13-2011 06:29 AM
Hello
I'm also trying to add a timestamp against the readings in an ASCII file. For some reason I don't seem to have the X-value Colums and Time Axis Preference boxxes in the ASCII/LVM step_File settings. Do you know why?
My Signalexpress program attached
Thanks
01-13-2011 07:19 AM
Hello
I'm also trying to add a timestamp against the readings in an ASCII file. Like you I don't seem to have the X-value Colums and Time Axis Preference boxxes in the ASCII/LVM step_File settings. Did you ever manage to sort out the problem?
My Signalexpress program attached
Thanks
01-13-2011 08:12 AM
No, I'm afraid I was never able to get Single Express to behave properly. The only way the issue was resolved was using the soultion presented by the NI representative as a "work around" which was
writing a separate software program to calculate each time stamp using the start time, end time and dt and placing the value next to the data point. It is a shame a separate software program was necessary as requesting a timestamp next to a data point is not an usual expection when compared to other DAQ software available.
Good Luck.
01-13-2011 09:00 AM
OK thanks