Remove milliseconds from timestamp in write to measurement file

I'm logging data to a binary tdms file using the write to measurement file express vi. I choose my x axis to be time and see that an absolute timestamp is written with millisecond precision. I only need to-the-second precision. Is there anyway to change this default behavior?
Attachments:
remove.png ‏10 KB
remove.png ‏10 KB

Where is your data coming from. When I open the express vi to look, it looks like the time format doesn't determine that, but the
signal data cluster coming in does. So where does the data come from, and in what form?
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Similar Messages

Removing milliseconds from timestamp

Hello.
I'm having problems with a date value (of type java.sql.Timestamp).
I need to convert:
java.sql.Timestamp date1 = 2005-05-11 12:12:30.40
I want to delete the milliseconds from the date above and format it as:
05/11/2005 12:12:30
How can I do this? I've tried:
SimpleDateFormat sdf= new SimpleDateFormat("MM/dd/yyyy HH:mm:ss");
String tempDate = sdf.format(date1);
But how do I now convert tempDate back to a timestamp?
Thanks for your help!

The output I'm looking for is 05/19/2005 13:38:37.
I don't want to .0 at the end.Then create a SimpleDateFormat that doesn't include millis.
Also, if only strings, etc. can be formatted, how can
I convert a string to a timestamp?SimpleDateFormat.parse gives you a Date. Timestamp has either a constructor or a setter method that takes a Date or the Date's long from its getTime() method.
Dates and Timestamps are just numbers--how many millis or nanos or whatever elapsed since the epoch.

Write to measurement file loses timestamp data in tdms format

Hello all, I'm using the Write to Measurement File expressVI and I have created a loop in order to be able to individually label the column headers for each data signal that I'm writing. However, while the loop is successful in doing this the resulting TDMS file that the expressVI creates ends up losing the timestamp data that is used to record the time for each row and just writes a '0' instead. The timestamp data is present before the loop that adds column headers, which I have verified by adding an expressVI just before the loop. Please see the attached code for clarification.
How do I regain the timestamp info after the for loop executes and adds column header info? Thank you.
Attachments:
Write to measurement file specify column name.vi ‏106 KB

The problem with Express VIs and with the Dynamic Data wire is that they (almost) complete obscure what is being done "under the covers". They manipulate data in ways that are unseen and often unexpected. While they allow beginners to do extremely simple tasks quickly, they can easily lead to situations such as you are discovering.
If what you want to do is to write a TDMS data file, you should probably investigate the TDMS functions on the File I/O palette. I've not used TDMS myself, but I know there are examples and documentation in the LabVIEW Help. I suspect that if you do go with straight TDMS, you will probably save yourself further problems by not bundling your four inputs into a Dynamic Wire, but making them a 1D Array (or possibly a Cluster).
Bob Schor

Formatting the time stamp in "Write LabVIEW Measurement File"

When I use the "Write LabVIEW Measurement File" vi to write data
the files first column contains the number of seconds since the staart of the file
How can I get the computer date and time or at least the time HH:MMS???
Tom
PS, And how can I put some sensible label on each columns in the file?

Tom,
The vi I'm attaching demonstrates how to use the computer system time for the timestamp on your LVM file. It takes a reading from the DAQ Assistant and applies a system time stamp. It's in version 7.1, but let me know if you need it in version 7.0.
As for inserting meaningful column headers, you won't be able to do that with the express vi, but you could use the regular file i/o vis to create a file like that is similar to a LVM file, but is a little more customizeable and can be formatted however you like. The express vi is meant to be a quick solution, but does not offer all the versatility of the vis on the palette. I hope this helps you out. Have a good one, Tom!
Tyler S
Attachments:
LVM_timestamp_7_1[1].vi ‏265 KB

Help with saving time stamps to "write to measurement file" excel format.

I am having problems saving the timestamps from my data to the write to measurement express vi for excel. My incoming data is converted from dynamic data to a 1d array for processing, which I understand you lose the time stamp data. I added a new array for time stamps but this array then cannot be converted back to the dynamic data that is requested to go into the write to measurement file express vi. I would prefer to leave the data in an array to be saved rather than converting it to a waveform so is there any way to add the time stamps from my 1d array back into the write to measurement file?

I set it up to build a waveform now but I am still having issues with it saving the correct timestamp. The time just incriments for every second (as it did before converting the dynamic data to the waveform). I attached a screenshot.
Attachments:
waveform.png ‏36 KB

Write to measurement file Express VI - TDMS file has separate "channels" for each data point

Im trying to write a VI to measure and record thermocouple data from an Advantech T/C DAQ. Using the "DAQNavi" express VI provided by them, connected to the Write to Measurement File express VI, I have managed to read in the data and create a TDMS file. However, when I open the TDMS file, each time step of temperature data is entered as a separate channel, instead of all of the channel data going into one tab. Obviously this is a huge problem as it creates hundreds of tabs after just a few seconds. Any thoughts as to what causes this?

Hi glibby,
How did you configure the Write to Measurement Express VI? Please select "one header only".
If you have your own timestamps to write, please merge your timestamp channel and measurement channels with "Merge Signals" before passing them to the Write to Measurement.
Best Regards,
Mavis

Write to measurement file at every n iterations

Hi guys,
I would like some help with saving data in labview 2010 SP1 (base development system). I am using a "Write to measurement fil express VI" inside a while loop and the data out from the DAQmn Read is wired to the signal in of the "Write to measurement fil express VI".
The way I have wired it is the VI saves the data as a text file after it has recorded 100 samples (the nuber of samples to read in this case was set to 100). I would like to know if there is a way to control the rate at which the express VI saves the data. As in, I want the express VI to save the data at specified time interval or at every nth iteration. I have attached the main VI and its 2 sub-VIs for reference. Please let know if anyone can help me resolve this issue. Thank you for your time and inputs in this regard.
Raj

Robert,
First, you must understand that the above code resides inside a loop. The blue square i terminal is known as the iteration terminal. It provides the current loop iteration count, starting from zero.
The first input (x) to the Quotient & Remainder Function comes from this iteration count (i) terminal of the loop.
The second input (y) to the Quotient & Remainder Function comes from the control N.
We wish to write to the measurement file every N iterations of the loop. If we take our current iteration count (i) and divide by our desired N, every Nth iteration of the loop, the remainder will be zero. For all other iterations, the remainder will be non-zero.
That being said, we check the remainder and compare it to zero. If it is zero, we will send a True value to the Enable terminal on the Write To Measurement File Express VI. Any time a True value is sent, we will write to file. Anytime a False value is sent, nothing will be written to the file.
The green new_file input on the Write To Measurement File Express VI is used when the "Save to series of files (multiple files)" radio button is selected in the Configure dialog box of this Express VI. When "Save to one file" is selected, this option does not apply, and so it is not included in the input list, which is why you are not seeing this.
This new_file input is used to tell the Write To Measurement File Express VI when to start writing to a new file.

Labview 9.0: Error 1 occurred at Write To Measurement File

Hi
Our University recently got the latest version of Labview (9.0 32-bit) which I installed today.The labview file I am using (my6008v6.vi) used to work fine with the older version (8.5 i think). My write-to-file VI is enabled at certain time intervals in order to log data. As soon as it is enabled for the second time I get the following error:
Error 1 occurred at Write To Measurement File->Copy of murray6008v6.vi
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
I made a simple file (simplew2f.vi) to test this, with a button which I can press to enable/disable the writing of data. I am able to start writing data and then stop writing data but as soon as I try resume the writing the same error occurs.
This confuses me greatly since this wasn't a problem using the old version and my Labview knowledge is minimal. Any help would be appreciated.
Attachments:
my6008v6.vi ‏214 KB
simplew2f.vi ‏64 KB

So, which VI are you having problems with? Sounds like both...
Okay... - sigh - where to start....
Well.. Let's start with a few comments.
1. Try to stay away from the Express VI. I know the Marketing guys at NI will not like me for saying so, but I am saying so. They are a nice marketing feature that Grumpy Old Men like myself do not like. They make it easy to write quick code.. And I will limit my comments to that. (It's not your fault.. )
2. The wiring on your diagram is not clear or easy to read. Yes, with additional time and double-clicking each wire I can tell where they are going. However, a rule of thumb, alway wire from Left to Right. Never right to left. And do not run the wires under objects, even the ones you are wiring to.
3. simplew2f.vi: You should put a small delay in the While Loop. I ran it three times and it wrote to the files without error. And yes, I used LV2009.
4. my6008v6.vi: Avoid wiring from the top of the While Loop. At frist, it looked like the data was coming out of the While Loop because the wires went to the left side of all the index node of the Index Array function.
You should set your Browse Option for the file path to "Files or Folders" and "New or existing". I did that and I was not getting the error message you described.
R
Message Edited by Ray.R on 03-03-2010 08:33 AM
Attachments:
pathProperty.PNG ‏13 KB

Write to measurement file timing

I am trying to make a VI that allows the user to turn on and name channels through the front panel. After the user has configured the channels, they can push a button and record voltages from the enabled channels and save them using the "Write to Measurement File".vi. I would like the user to be able to record a measurement file that is consistent in length each time they push the button...in this case, 5 seconds of data. The current VI doesn't appear to be doing this...everytime I push the record button, the data gets recorded for 0.045 seconds. Apparently I must be missing something as this isn't behaving how I expected it to. See attached VI.
Attachments:
Select Channel rev 3.vi ‏244 KB

It waits 5 seconds then saves the last 10 samples. Because that is the way you programmed it. The while loop returns only the data from the last iteration.
Two ways to do what you want: 1. Read 5 seconds * 200 samples/second = 1000 samples. No loop required.
2. Read 10 samples at a time and accumulate the data until you have 5 seconds of data. To avoid memory reallocations the way to do this is to Initialize an array with 1000 elements outside the loop. Wire it to a shift register. Inside the loop Read the samples and use Replace Array Subset to put the new data into the initialized array. Wire the output of the shift register to the file VI.
You generally should not put any time consuming code inside an event structure. Read the caveats in the detailed help for the event structure. Consider a Producer/Consumer architecture.
Lynn

Quickie: Write to measurement file VI, how to create new file?

I am using the write to measurement file express VI in my code and I have wired into it a control that sets the location to save the measurement file
The only problem is the measurement file has to exist first!! I cant for example, from the front panel, click the browse directory box, navigate to a folder and type in a name for the file. It just says file not found! Its like the file directory control is opening a file to save to, rather than creating a new file in that location
How can I solve this?
Solved!
Go to Solution.

Project attached
If I go in browse options what do i do? Just chose new and existing files?
Attachments:
engine.zip ‏119 KB

Strange data saved by write to measurment file

Hi all,
I have developed a simple program that permits to visualize data from a channel, but it records data, just when the saving data button is pressed. Data are saved through write to measurment file, but unfortunately there is something wrong since the saved data is strange. In the attachment there are the VI file and the saved data.
As you can see there are several header and dates are strange (i.e. the saving date is 23/12/1916) and I get much more sample than I should have. Why do I get this?
Any suggestion is appreciated.
23/12/1916
Solved!
Go to Solution.
Attachments:
simulated_data.xlsx ‏1426 KB
read a channel and save data.vi ‏63 KB

Your many headers may be because of this:
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Write to Measurement file wil not write data daily

I have been using the Write To Measurement File express VI to record daily values. The express VI is no longer saving daily files or is checking for file size. WTF. Does anyone have a more bullet proof way of saving data daily with a single header for the day?
Thanks,
Matt

MS UCD wrote:
Ravens Fan,
So to clarify, I meant local variable instead of shared variable. Shared variables will come into play when I construct the real-time embedded program on the cfp-2120 controller. Thanks for the clarification. So are you on the clock for all this?
Sometimes yes, sometimes no. Since today is a holiday, I'm off the clock.
Anyways, so if I need to have the user see the values on the front panel and also record the values later, how do you suggest one does such a thing other than writing an indicator and then making a local variable that is then recorded?
The local variable has nothing to do with recording the values later. It is just a way of accessing a control or indicator in more than one part of the program. If you used shared variables (and I think you would need to have the DSC module to have this functionality), you could write to the shared variable and have it set up to log its values to the Citadel database. It is a built-in method of logging that just requires configuration of the shared variable, no additional programming would be needed. Otherwise you will need to add the code to write to a log file like you are doing now.
The new/old mechanism for checking the date has brought the adequate functionality I was looking for- mainly new files for each day.
With respect to the race condition you mentioned, could a sequence structure be used to write the local variable to the output array? In essence, I would calculate the scaled values and then write them to the data array. Another solution could be a control in the last case that then is used to initiate a case structure in which the shared variables for the data acquisition iteration are then recorded in the output array.
A sequence structure (and a flat sequence is preferable to a stacked sequence for code readability and maintainability) would guaranteed that one section of code completes before another begins. However, it is still preferable to use wires. Wherever you are wiring to a local variable, just send the wire to the border of the while loop. Feed the wire from that tunnel to the build array function and eliminate the local variable that you are reading there. Your case structure in a while loop is really just functioning like a stacked sequence structure. Every iteration of the while loop executes the next case in the case structure. If you are sequencing through the data values in the same order that you are building them into an array outside of the loop, you could actually build the array element by element inside each case structure and use a shift register on that array to carry the data from one iteration of the while loop to the next. Then once you while loop is done, the array has already been built. If by chance you are acquiring the data in a different order then you want to build it into and array, then the array functions could get much more complicated inside the case structures. But you could initialize the whole array before the case structure, and use replace array subset to replace each specific element as you acquire it.
I am interested in the producer/consumer arrangement you speak of. Do you have an example you could send me that shows this operating?
Go to File then New.... Look under frameworks, design patterns, and Producer/Consumer Design pattern (Data). Also search the forum for producer/consumer and I'm sure you'll see plenty of examples.
As for the Time Signal controls being located in the Labview abyss, what can I say? Every learning experience has a few bugs. ; - ) If the Time Signals are constants what effects on the time in the chart will this have?
Since the time controls are way off, I assume that the program user will never actually go out into the space of the front panel to find them and change them during the execution of the code. (I am also assuming that those controls never get changed programmatically by writing to a local variable or property node or they are not part of the connectory pane where this VI is called as a subVI in another one that passes in a time stamp on every call.) If they never change, then they are effectively constant. Changing them into constants would clean up the code and make it slightly more efficient, but would not appear to execute any differently.
Thanks for helping this novice out!
Regards,
Matt

"Write to measurement file" express VI (TDMS foormat) keeps file opened

Hello!
I am trying to use "Write to measurement file" express VI to write TDMS data obtained from DAQmx in LV2011. Each run of the same write function creates new file.
It seems that last written file remains to be opened until program stops or next file written. It has 0 size and it is not possible to access it from other programs.
Is it possible to save file immediately and close it?
Solved!
Go to Solution.

It seems, that wiring "DAQmx task" (for AI task) to "Write to measurement file" express VI does not works in my case (only in exe).
The error is the same as file not found (error code 7), but file is created. Something gets wrong inside express VI. I am unable to debug exe, so I have just disconnected DAQmx task from express VI (really don't specially need it anyway).
For sure, the same LabVIEW version and drivers are installed on target and VI is working in it as well as at dev machine.
Debug error which I had encounter is already published in the forums elsewhere. It seems that the problem is in VI without block diagram inside hierarchy. Maybe with Express VI.
PS test app writing tdms files the same way is working like a charm (without DAQmx task wired).
So, thank you for yor advices, the problem seems to be solved. Maybe I will have a look in more details about the reason of such error, but can't do it now.

Write to Measurement File Express VI: file name prompt

I am using the Write to Measurement File express VI to write some data.
Even though I have not selected "ask user to choose file" and have set a default filename, the vi still prompts me to choose a file. I tried restarting my pc and it used the default filename the first time and then went back to prompting me. I have set the default to overwrite my existing file each time, so I don't understand why I keep being prompted. If you look in the express VI the "ask only once" radio button is selected and greyed out, but I don't know why; I didn't select it.
(I have the express VI in a while loop and want it to write a line of data to the file each time the loop executes, so it's not convenient to be prompted for the filename each time)
I'm sure this is my own silly fault but would appreciate some advice
Thanks, klara
Attachments:
2PDCal_USB1v3.01.vi ‏441 KB

I'd suggest changing the mechanical action of your stop button from "Switch When Pressed" to "Latch When Released". This might be the only problem. If you didn't manually change your stop button back to false before running again, your loop would run once and stop, and you'd immediately see the file dialog from the Format Into File function. Changing the mechanical action would prevent you from needing to manually change it back to false before the next run.
Message Edited by Jeff B on 02-07-2008 08:48 AM

Write to measurement file will not ask for file name once as selected.

When using the Write to Measurement file Express VI. I select "Ask user to choose file" and "Ask only once" with the intention that the data from each iteration simply be appended to the chosen file.
I select "Run continuous" and the VI asks for me to choose a file repeatedly anyway instead of just appending the first file. Selecting "Write to one file" properly appends data to the file specified in the box.
Am I doing something wrong?

DianeS wrote:
Personally I can't figure out why that particular button even exists (I'm told it's occasionally useful for debugging).
I find it useful if I am creating a subVI that is supposed to be a part of another VI. No while, loop just some inputs and outputs as a function. If I want to test it out stand alone and try a variety of inputs, then Run Continuous and change the inputs, then I see immediate feedback on the outputs. Once I'm satisfied its working right, then there is no need to clean up. Just save it and drop it in the large VI as a subVI.
Beyond that, I see no need for Run Continuous.

Remove milliseconds from timestamp in write to measurement file

Similar Messages

Maybe you are looking for