Write To Measurement File Only One Line Of Data

Hello,
I have an express VI setup to acquire a single channel of strain running in a simple while loop. The output is wired directly to a Write To Measurement Express VI. However, the resulting measurement file contains only one line of data.
I have tried changing the settings of the VI to no avail. I feel that I must be missing something basic. My while loop is setup to take one measurement on demand for each loop. I am assuming the VI knows to write each loop as a new line of data?
Thanks for any help,

Did you choose "append to file" in the Express VI configuration settings?
You need to upload your VI for further help. It's impossible to help someone debug a problem without the code to look at.

Similar Messages

Time format in 'Write To Measurement File' express vi

Hi,
I'm using the 'Write To Measurement File' express vi to save data acquired using a PCI-6221 board and the DAQmx vi s. The acquisition is continuous.
When I set the 'number of samples per channel' property of the DAQmx Read.vi to -1 (ie, read all available samples), the time is saved in relative format. When I set any other value (ie a certain quantity of samples), the time is saved in absolute format.
Do you know why the vi does this, and if there's any way of controlling the time format ?
Thanks,
ps : I use Labview 8.0

Hi Scalpas,
I look into what I believe you are doing , but I didn't see the same results. Can you explain what datatype you are transferring to the Write to Measurement file VI? Or provide a sample of code that demonstrates the issue.
I think it might have to do with the DataType conversions when writing that file.
Sappster

"read from measurement file" reads only first line of data

Hello,
I have a problem when trying to read a .lvm file through "Read from Measurements file" with the following block diagram
Problem: it reads only the first line of data from what I can see in the probe window,.
A part of the lvm file for reference.
I haven't used Labview in a long long time, I'm trying to figure out what I am doing wrong.
Thanks

Sorry meant to attach the lvm. Here it is. (Actually I had to put it in .txt because the forum wont let me upload a lvm file)
I unfortunately cannot share the full vi that record the data as I am not its owner/creator. I'll try to give as much info as I can with the relevant pictures attached, I hope it allows us to at least have an hint of where the problem might be.
(this is in a while loop)
In the stacked sequence, the other pannels are similar to the one shown here: value read fron a variable, converted to dynamic and a signal attribute is set. The "start recording" control operation is "switch when pressed".
Here are the properties of the set signal attributes
And here are the properties of the "write to measurement file"
Attachments:
NoTarget_full circle__Rx_-10-SAMPLE.txt ‏60 KB

Write to Measurement File Defaults Back to "Save to One File"

I'm trying to use the "Write to Measurment File" to make a series of files - but as soon as I hit ok it defaults back to "Save to one file". Even without running the VI it just sets itself back. I've attached files of what it looks like before I hit okay, the settings, and what happens after I close it.
Perhaps this is a bug?
Also, if you can see, I don't want the file to be called testdata__ but there is no way to change the prefix of the file because the box is greyed out. Any way to change that either?
Solved!
Go to Solution.
Attachments:
Capture.JPG ‏70 KB
Capture2.JPG ‏66 KB
Capture3.JPG ‏47 KB

What version of LabVIEW are you using?
LV2009 has some bugs with the Write to Measurement File Express VI.
See this thread for more information. http://forums.ni.com/t5/LabVIEW/write-measurement-file-save-to-series-bug/m-p/1226104

Write To Measurement File, Comment

I have tried to use the Comment input on a Write To Measurement File vi and the results are not what I expected. What I want to do is place one line of text appended after a block of data to form an easily seen break between the data sets. The data is triggered in a stream prior to being sent to the Write To Measurement File. I thought that the description on the Comment would do this but I get the comment not only between the blocks but also interspersed within the data stream in a seemingly random manner. What am I missing in the behavior of the Comment input?

Dear ITElearner,
thank you so much for your post on our webforum. You are able to add a comment each time you write to the lvm file; this comment will be added to the first row you are writing. I created an example; 10 samples are generated, comment is added, this is written to file, another 10 samples are generated new comment is added and written to file.
Is this what you are trying to achieve? Else I would recommend to create a small example of your problem.
Best regards,
Martijn S
Applications Engineer
NI Netherlands
Attachments:
commentlvm.jpg ‏120 KB
Untitled 1.vi ‏112 KB

Problem with Write To Measurement File Express VI not writing to file if file was deleted after the first call (7.1)

I'm using the Express Write to LabVIEW Measurement File in LV7.1.
I have it set to "Save to one file" and have tried both "Overwrite file" and "Using next available file name" for the "If a file already exists" conditions.
The path/filename is passed into the function.
It works fine the first time around. If the file is deleted before the function is called again, an error occurs since LV is unable to find the file.
I have had to stop and re-run my program in order to write to use the function again.
Since I am able to delete the file I assume it was closed but it seems like LV expects it to be there, even though the function was supposed to create/open/close the file... Is there any way to reset this without stopping/restarting the program?
Since my application creates several files (only one using the Express VI) I am checking for the filenames and requiring that they be deleted (or a new filename be used) before acquiring data. Everything has worked great, except for the Express VI.
Thank you,
David

Ok, I've edited the VI you posted to reproduce my error (this time with 8.0).
I added a "master stop" and "start log" button. To demonstrate my problem:
1. Run the VI
2. Click "START LOGGING" - c:\test.txt is created
3. Click "STOP" - c:\test.txt is closed
4. Delete the file c:\test.txt with Windows shell or explorer
5. Click "START LGGING" - a new c:\test.txt file should be created but instead an error is raised in the Write LabVIEW Measurement File function.
Any ideas?
Thanks,
Dave
Attachments:
Write LV Meas File 2.vi ‏96 KB

How to populate column titles for y values when using Write to Measurement File Express VI with a tab delimited text-based .lvm file?

The .lvm file generated by the Write to Measurement File Express VI includes column heading titles for the y values, but they are a default value of "untitled". See attached example of a sample file when opened in Excel, the values in question are highlighted. Is there a way to specify the column titles when the file is written?
This is a similar question to this posting, which received a work around response to use the Write to Spreadsheet File.vi, rather than a solution when using this VI.
Message Edited by Hightop Raven on 05-02-2007 03:37 PM
Attachments:
column_titles.gif ‏13 KB

Sorry for the late reply. I was out of the office Friday.
You can do it, but the code can get rather ugly. Under the hood, the dynamic data type (the dark blue wire) is an array of waveforms. In your case, the scalar values you convert to a dynamic data type are being converted to an array of waveforms, each waveform having one element. You have two options.
Explicitly convert your scalars to one-element waveforms (t0=0, dt=1) and add the title before conversion to a dynamic data type.
Convert your dynamic data type to an array of waveforms and loop through them to add the column labels. The conversion blocks are in the Signal Manipulation Express palette.
I would recommend 2, since it is the easiest to add. It is also the easiest to run only on the first iteration. Just put a case selector around the loop, wire the selection to the While loop iterator, and set the case containing the label code to 0. The default case simply passes through the dynamic data.
My apologies for not including a screen shot. I am in the process of upgrading my machine and can't run LabVIEW. If you need one, let me know and I can post one tomorrow.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Write to measurement file

Hello,
I have to measure my spectrometer values every thirty seconds and have to write it to a text file. I need to create a new text file each time for writing my values. So i used the write to measurement File option for doing this. The problem is that this block measures the values only every one minute, but i need to measure the values every thirty seconds. Could any one help me out with this ?
Thanks in advance
Swarna

Some issues you have for the timing part of your code:
1. Use the Time has Elapsed output of the Elapsed Time VI. It already does the comparison for you, so just use it.
2. I'm pretty sure you want the Write Measurement File to be in the TRUE case.
3. Use the AutoReset option on the Elapsed Time VI.
But those do not point to a data point every 1 minute. How long does it take your instrument to do the sweep before sending it to you? I have seen some take a long time, so it is worth looking into.

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 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.

Write to measurement file - Create or replace with confirmation

I'm using the "Write to measurement file.vi" and I want it to ask for confirmation if I try to save with a filename that already exists and then allow me to choose another file name or overwrite the old one. How can I do this?
Solved!
Go to Solution.

smercurio_fc wrote:
Ben wrote:
smercurio_fc wrote:
That Express VI does not have the capability you are seeking. ...
Help us Obe Wan, you're our only hope.
Ben
Did I misunderstand the question again?
No.
Spoiler (Highlight to read)
Your wording reminded me of the scene from Star Wars when Ben Kanobe di dthe force thing on the strorm troopers telling them "These are not the droid you seek."
Your wording reminded me of the scene from Star Wars when Ben Kanobe di dthe force thing on the strorm troopers telling them "These are not the droid you seek."
Its just Friday.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Time with 'Write to measurement file'

Hello,
I am making an acquisition waveform. The integration time is 1s divided in 128 samples. When I execute the software, the datas are stored in a text file with 'Write to measurement file'. This text file is a continuous list of 128 numbers-packs in rows.
I want to add the time column (date+hour+minutes+secondes+1/10sec+1/100sec) in front of each number acquired. (And not only in front of the first number of the 128 package)
I have don t know how to add this.
Can you help me?
Thanks a lot.
(See file attached)
Attachments:
test3.vi ‏148 KB

Also, in the setup dialog for the Write Measurement File, there's an option to include an "X Column Value" that normally holds a timestamp.
Enable one of these options and any included timestamp in your waveform will go into this column. If you don't have a waveform, you can build an extra column in your array of data points with the needed timestamp and it will work the same.
Ed
Message Edited by Ed Dickens on 02-20-2007 03:37 PM
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Attachments:
WLVMF Time Column.gif ‏9 KB

Samples number is not properly set with VI Express Write To Measurement File

Hello,
I have a strange problem with the VI Express Write To Measurement File.
When I generate the .lvm file the samples number for each channel is equal to 1
instead of 34 !
So when I use the VI Express / Input / Generate an arbitrary signal and I want to import
the generated signal... only one point (the first one) is imported...
I can manualy fix it by changing samples number in the lvm file using a text editor but that's a (very) dirty hack !
Here is an example of the generated LVM file
LabVIEW Measurement
Writer_Version    0.92
Reader_Version    1
Separator    Tab
Multi_Headings    No
X_Columns    One
Time_Pref    Absolute
Operator    scls
Date    2008/04/12
Time    10:35:58,322057
***End_of_Header***
Channels    2
Samples    1    1
Date    2008/04/12    2008/04/12
Time    10:35:58,323057    10:35:58,323057
X_Dimension    Time    Time
X0    0.0000000000000000E+0    0.0000000000000000E+0
Delta_X    1.000000    1.000000
***End_of_Header***
X_Value    Untitled    Untitled 1    Comment
0.000000    0.000000    20.000000
0.082000    10.000000    20.000000
0.182000    10.000000    25.000000
0.282000    20.000000    25.000000
0.382000    20.000000    30.000000
0.482000    30.000000    30.000000
0.582000    30.000000    35.000000
0.682000    40.000000    35.000000
0.782000    40.000000    40.000000
0.882000    50.000000    40.000000
0.982000    50.000000    45.000000
1.082000    60.000000    45.000000
1.182000    60.000000    50.000000
1.282000    70.000000    50.000000
1.382000    70.000000    55.000000
1.482000    80.000000    55.000000
1.582000    80.000000    60.000000
1.682000    90.000000    60.000000
1.782000    90.000000    65.000000
1.882000    100.000000    65.000000
1.982000    100.000000    70.000000
2.082000    110.000000    70.000000
2.182000    110.000000    75.000000
2.282000    120.000000    75.000000
2.382000    120.000000    80.000000
2.482000    130.000000    80.000000
2.582000    130.000000    85.000000
2.682000    140.000000    85.000000
2.782000    140.000000    90.000000
2.882000    150.000000    90.000000
2.982000    150.000000    95.000000
3.082000    160.000000    95.000000
3.182000    160.000000    100.000000
3.282000    170.000000    100.000000
PS : I also post my problem at
http://forums.lavag.org/Strange-behaviour-of-VI-Express-Write-LVM-t10570.html&gopid=44101#entry44101
Attachments:
generate_step_lvm.vi ‏119 KB

If I use the "one header per segment" option I get the following LVM file (see below)
But the problem is same !
I can't import this file in VI Express / Input / Generate Abitrary Signal (I only get one row... the first one)
I see three solutions :
- VI Express Write LVM has a bug ?
- I don't know how to use this VI Express correctly !
- VI Express / Input / Generate Abitrary Signal has a bug ?
LabVIEW Measurement
Writer_Version   0.92
Reader_Version   1
Separator   Tab
Multi_Headings   Yes
X_Columns   One
Time_Pref   Absolute
Operator   scls
Date   2008/04/12
Time   16:38:37,578
***End_of_Header***
Channels   2
Samples   1   1
Date   2008/04/12   2008/04/12
Time   16:38:37,592999   16:38:37,592999
X_Dimension   Time   Time
X0   0.0000000000000000E+0   0.0000000000000000E+0
Delta_X   1.000000   1.000000
***End_of_Header***
X_Value   Untitled   Untitled 1   Comment
0.000000   0.000000   20.000000
Channels   2
Samples   1   1
Date   2008/04/12   2008/04/12
Time   16:38:37,717   16:38:37,717
X_Dimension   Time   Time
X0   1.3899993896484375E-1   1.3899993896484375E-1
Delta_X   1.000000   1.000000
***End_of_Header***
X_Value   Untitled   Untitled 1   Comment
0.139000   10.000000   20.000000
Channels   2
Samples   1   1
Date   2008/04/12   2008/04/12
Time   16:38:37,739999   16:38:37,739999
X_Dimension   Time   Time
X0   1.6199970245361328E-1   1.6199970245361328E-1
Delta_X   1.000000   1.000000
***End_of_Header***
X_Value   Untitled   Untitled 1   Comment
0.162000   10.000000   25.000000
and so one ...

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.

Write To Measurement File Only One Line Of Data

Similar Messages

Maybe you are looking for