Configuration "use next available filename" in "write measurement file" function

My project recording signal and saving using "Write to Measurement File" function. I want to perform record multiple segments signals should have configured option "use next available filename". For example, if the original file is data.tdms then it will save the file into: data_1.tdms, data_2.tdms, data_3.tdms, ...
To do that I use a button control enable and disable write functionality.
In the past I have done normally. Now, I can not make it anymore, now every write new data were add into one file created without the next new file as desired, it has almost become a option "Append to file".
I use LabVIEW 2013
Solved!
Go to Solution.
Attachments:
write measurement file.vi ‏54 KB

Hello ducta9,
It looks like you currently have the Write to Measurement File Express VI configured to "save to one file" - this means that all data from a given session will be saved to the same file. The file number will only be incremented once the application is restarted or the Reset Boolean input is set to True. If you want to save to a series of files, select the "save to a series of files" option and configure the Express VI as needed to generate new files at intervals.
If you want to write variable-size chunks of data to a new file every time the user clicks the Enable button, you might be able to get away with just wiring a True constant to the Reset. I would still recommend taking a look at the options available in the save to a series of files settings.
Best Regards,
Tom L.

Similar Messages

URGENT: Autonumber to use next AVAILABLE value

Hi All
I urgently need your help: I am writing a Java assignment using a MS Access database. Some of the columns are AutoNumber used as primary keys in a relationship.
The program sometimes needs to delete records. The problem I have is that when I add new records the driver should use the next available number not the next sequential number.
ie.: If I have the records 1 2 3 4 5 and I delete record 3 I have
1 2 4 5.
When I now add a record, I want it to assign the number 3 to the record instead of the number 6.
There must be some work-around. PLEASE help me here!
Kind regards,
Comlink

What you need is called a sequence. Access doesn't have this. But you could make a table with one number field and write code to increment or decrement this number on confirmed updates.
Just an idea.

Thousands of individual .txt files being created while using "next available file name" option in Save to ASCII step

I'm using Signal Express to record Load vs Displacement data and export it to a format our engineers can work with (in this case ASCII is okay). It would seem that by selecting the Next Available File Name from the drop down arrow it would do just that. For instance a typical save path for me would look like C:\....Desktop\Project Number and Description\Run_1.txt within that Run1.txt file would be all the data points for that run. When I hit record again Signal Express would (SHOULD) create a Run_2 since it's the Next Available File Name.
But instead what it does is creates a single txt file for every single sample point being read. Needless to say, If I'm recording 6 second of data at 1khz I end up with thousands of txt files!
The first thing that comes to mind is, why would anyone want this?
Second is how can I record multiple individal runs for the same project and have the file name increment?
SCXI- 1000 Chassis w/ 1346 adapter
PCI 6281 DAQ card
SCXI- 1520 Bridge Board w/ 1314 Terminal Block (x2)
SCXI- 1180 Feedthrough Panel w/ 1302 Block
Signal Express 2014.
Win7 Enterprise

...and more attachments of the ASCII save path, before and after acquiring 4 seconds of data along with one of the files from that folder.
Again, this is 4 seconds of two-channel spring plot data at 100 Samples to Read @ 1k Rate (Start Run.... wait 4 seconds or two full test sample cycles... Stop Run).
~EDIT~
The .txt file would not attach (I think it's too small). Here's what it looks like if you were to open it:
Load vs Displ - Displ (inches) Load vs Displ - Load (lbs)
3.736323 273.751906
Also, for some reason it won't let me attach my project file. It's a .seproj extension but the forum thinks it's 1k in size and "empty"
Message Edited by OKors on 06-05-2009 05:57 PM
SCXI- 1000 Chassis w/ 1346 adapter
PCI 6281 DAQ card
SCXI- 1520 Bridge Board w/ 1314 Terminal Block (x2)
SCXI- 1180 Feedthrough Panel w/ 1302 Block
Signal Express 2014.
Win7 Enterprise
Attachments:
FolderBeforeSave.JPG ‏39 KB
FolderAfterSave.JPG ‏239 KB

Using auto-indexing tunnels to write data files?

Hi,
I am using ni-motion controller to control a servo motor and collect position and torque data. I want to write the collected data to TDMS files.
Recently I learned about the producer/consumer design pattern and I figured that would be a good approach to ensure that writing the files didn't slow down my data collection timed loop.
However, I also figured out that my program seems to run well if I wire the data I collect to auto-indexing tunnels. Then I use a structure that only executes after all the data collection is done to write the arrays I built to TDMS files.
Is there any reason that the latter method would be advised against? Can the auto idexing tunnels slow down my loop enough for it cause concern? I am only collecting about 5000 data points for each channel.
Cheers,
Kenny
Solved!
Go to Solution.

Well, autoindexing tunnels don't write data files, they just accumulate data until the loop completes. If this is a FOR loop with a known number of iterations, the size of the output data can be allocated in one swoop, which is very efficient. If you are autoindexing on a WHILE loop, the final array size is not known, so LabVIEW needs to make a guess and and requires occasional new memory allocations whenever the last guess is exceeded. This is inefficient.
One problem with these approaches is if the program or computer crashes. In this case the data in the shift register is lost forever, while if you would stream it to disk, you would have most of the data acquired so far.
If you use a proper producer/consumer architecture, you should be able to asynchronously write the data and it will not slow down your acquisition. No need ot wait for the competion of data gathering.
LabVIEW Champion . Do more with less code and in less time .

RMAN backups not using next available volume: uses next unlabeled volume

Greetings.
I've noticed that sometimes (haven't zeroed in on when yet) when RMAN backs up using OSB, the first tape in the library, an RMAN volume, is grabbed and backed up to.
There are about 10 other RMAN-labeled volumes right below that first one. But RMAN will take an unlabeled volume further down in the library, label it as an RMAN volume, and proceed to back up to it.
This is happening often enough where my library is filling up with partially used RMAN volumes.
Three jobs (that I can see so far) are cron jobs calling an RMAN script. I'm looking for the other jobs which, I think, are run via OEM.
Any thoughts?
-Jeff

Our daily backup is doing the same thing. That is, it's not backing up to tapes I assume it'll use. This is in the transcript:
2010/06/08.22:00:17 (mmr) volset containing oid 21601 (vid PASDLY-000665, tag 000020L3, create_time 1275530931, mediainfo 0) is closed
2010/06/08.22:00:17 (amh) 18 oid 21601 doesn't meet mount requirements - volume set is closed to further update (OB device mgr)
2010/06/08.22:00:17 (mmr) volset containing oid 21607 (vid PASDLY-000667, tag 000114L3, create_time 1275617100, mediainfo 0) is closed
2010/06/08.22:00:17 (amh) 19 oid 21607 doesn't meet mount requirements - volume set is closed to further update (OB device mgr)
2010/06/08.22:00:17 (mmr) volset containing oid 21597 (vid PASDLY-000664, tag 000004L3, create_time 1275444068, mediainfo 0) is closed
2010/06/08.22:00:17 (amh) 20 oid 21597 doesn't meet mount requirements - volume set is closed to further update (OB device mgr)Where do I find how the mount requirements are configured?
-Jeff

Error 43 when accessing LabVIEW 2009 write/read file functions through the web server functionality

Is there any way around to avoid Error 43, "Operation cancelled by user" when using Web server?
I am using the example VI:s RemotePanelMethods-Server.vi and RemotePanelMethods-Client.vi to acces the MainGUI.vi from my workstation to a lab computer. * LabVIEW 2009 is installed in both machines.
* MainGUI.vi is wired to the VI access list in the Server VI but it also contains a hierarchy below that isn't, is this a problem?
* Several functions in MainGUI calls file read and write operations
The problem ocurrs when file read/write operations with no preselected path are selected through the Client. The traditional popup window requesting the file to read or write is never seen in the Client, but only the Error 43.
Thanks in advance

See this

I'm new to the LabView. How do I pass data from VI configured using Serial (CMTS using CLI commands to set Parameters ) to VI configured using GPIB(vector signal analyzer ) to measure such as RF frequency or power on the instrument? Thanks

I'm new to the LabView. How do I pass data from VI configured using Serial (CMTS using CLI commands to set Parameters ) to VI configured using GPIB(vector signal analyzer ) to measure such as RF frequency or power on the instrument?
I just want to set something on the front panel that will execute the Serial parameters first and then pass these settings to vector signal analyzer
Thanks
Phong

You transfer data with wires.
Frankly, I'm a little confused by your question. I can't think of any reason why you would want to pass serial parameters (i.e. baud rate, parity) to a GPIB instrument. Please explain with further detail and attach the code.

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

Error filename measurement file

Hi.
In my project, I have used the Read Measurement File function to read .tdms file. When I run the program on another folder or another PC, then select Open file name an error occurred, error window appears. Although it did not do wrong program operation but It is very uncomfortable. So I hope how could this error window does not appear?
Thanks.
Solved!
Go to Solution.

Thanks for your answer - Proven Zealot.
I deleted all the Start Path and Filename. Now only the first Browser to open filename new error window appeared and notice that "Location is not available" - Access is denied. Then open filename next time isn't fail again. Error only appear once - the first read.
Attachments:
Read Measurement file.vi ‏34 KB
tdms_data.zip ‏342 KB

Labview 8 crashes when using Read Labview Measurement File

Hi All,
I am a new user for Labview. I installed Labview 8.0 from the CD (evaluation copy). I was just testing the sample code provided by NI. I opened the "Load from File and Display" example and I was trying to open the properties for the Read Labview Measurement File component when Labview crashed. I tried it a couple of times and everytime it happens the same way (when I double click the component or right click on it).
I am using Windows XP with all the updates done. In the Windows crash report, the application version is 8.0.0.4005.
Other problem I encountered is a missing component on the Input Palette (no DAQ Assistant present) and the Instrument I/O Assistant raises the error "Measurement & Automation Explorer or the Instrument I/O Assistant is not installed correctly. Please install these from the Labview Driver CD". For the last problem, I will try to run the Labview Driver CD, once I get it. But I am not sure if the DAQ Assistant will show up then or not.
Any ideas?
Regards,
Nick

Hello Nick,
While it is not my area of expertise, I would expect the DAQ Assistant would appear after installing the driver CD as you said you would be trying.
What caught my attention was the crash. The easiest way to resolve the crash is to delete the instance of the Read LabVIEW Measurement File on the diagram and place a new one from the Express Input palette (now called "Read From Measurement File"). In that situation, I would expect just pressing OK to accept the default configuration should work. The crash occurs in certain circumstances when the Read / Write Measurement File Express VIs are dropped from a previous version of LabVIEW and then their config page is opened in 8.0.x. This issue should be resolved in a future release, sorry for the inconvenience.

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.

Db- put blocks sometimes, mulit-thread uses Db- put to write DB file

My environment : redhat Linux 5, gcc version 4.1.2
BDB version: 4.8.24
Hi Guys
I used multi-thread application to write DB file. The application used Transactional Data Store and I used flags DB_TXN_NOSYNC . The DB file type is BTREE. I give 180M for the buffer cache and 8M for the log cache. And I used Db->put to write DB file ; five threads is used.
But the Db->put will block for one or two seconds sometimes.
Now I have found that the problem is in the lock/lock.c :: __lock_get_internal , line 953 : MUTEX_LOCK(env, newl->mtx_lock);. My application blocks here .+_
Could anyone give me some advice to avoid these blocks as possible as we can?
By the way, I have tried many of the lock set APIs which BDB offered. No effect -_- .
Thanks

Hi,
You should have posted this new piece of information in the original thread you opened:
Db->put block sometimes , when mulit-thread uses Db->put to write DB file
In the future please do not open a new thread for a problem you already reported.
Now I have found that the problem is in the lock/lock.c :: __lock_get_internal , line 953 : MUTEX_LOCK(env, newl->mtx_lock);. My application blocks here .+_This only confirms that one of your threads is blocked waiting for a requested lock, which is already held by another thread. Until the thread that holds the lock will not have released it, your thread waiting on it will not make progress.
You can collect the locking statistics at the moment you observe the slowness using either the db_stat utility with the -CA or -Co options (if the environment is not opened with DB_PRIVATE, that is, backing its region files into per-process private/heap memory) or programmatically using DB_ENV->lock_stat_print():
[http://www.oracle.com/technology/documentation/berkeley-db/db/api_reference/C/db_stat.html]
[http://www.oracle.com/technology/documentation/berkeley-db/db/api_reference/C/lockstat_print.html]
Examining the locking statistics will help determine what is the problematic lock, what is the locked object and which thread is holding it.
In addition to standard deadlock detection you can look into configuring lock timeouts. If your lock request is not satisfied within a given time it will time out and return DB_LOCK_DEADLOCK or DB_LOCK_NOTGRANTED. Lock timeouts may be configured per environment wide basis or per-lock or per-transaction basis:
[http://www.oracle.com/technology/documentation/berkeley-db/db/programmer_reference/lock_timeout.html]
[http://www.oracle.com/technology/documentation/berkeley-db/db/gsg_txn/C/lockingsubsystem.html#configdeadlkdetect]
As Mike already suggested it would help if you could put together a test case program to demonstrate this issue.
Regards,
Andrei

Write to measurement file pda

hi, ive been learning labview on v.7.1 and now im trying to create simple programs on labview pda 8.21.
i want to continually record a signal to text file like an lvm. i was previsously just using the 'write to measurment file' function and connecting my simulated signal straight to it. now when i try to run it in a windows 2003 mobile emulator i get the error 'subVI is not executable'
what would be the best way of getting around this? as this is a big sticking point for my project.
thanks alot
andrew
Message Edited by lav on 03-17-2008 07:47 AM

Hi Andrew,
I hope you are well. Thanks very much for your post. I have taken a look at your problem and I think it may be due to some incompatabilities between LabVIEW and the PDA that you are using. I was wondering if it would be possible for you to post the code on the forum so that I can take a closer look at it to try resolve the problem.
Thanks very much.
Kind regards,
Prashant M
Applications Engineer
NI UK & Ireland

Write to measurement file, adding column name in text file.

Hello,
Is it possible to add own column name for a text file using Write to measurement file function?
In the created file I have three different columns (I want to name them Time/Voltage/Date&Time).
Maby I should choose different write option like write to spreadsheet?

You are going to have to post some actual code if you want us to help here. Otherwise it is a complete shot in the dark. Posting an example CSV file of what you have and what you want would also be beneficial.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

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

Configuration "use next available filename" in "write measurement file" function

Similar Messages

Maybe you are looking for