Write To Measurement File VI for executables

[psuraff]

I wrote a small GUI to monitor a Measurement Computing USB DAQ on two channels with the option to write the data using the Write To Measurement File VI in Labview 8.2. I selected the option to "Use next available file name" to auto increment the files without overwriting them. The program works fine in Labview. When I build the exe everything works except auto incrementing the file name when writing the file. Is there a problem with the options in express VI's when these are deployed on non-labview machines?  

[Daniel_E]

It may be that you need the USI Driver (Universal Storage Interface) and do not have it installed on the target machine.  This is an additional installer that you can include in your application's installer.  This will cause the USI Driver to be installed with your application to the target machine.  The URL below shows how to do this.

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019N8tSAE&l=en-US

If you don't have an installer yet, the URL below is a good starting point.

https://www.ni.com/en/support/documentation/supplemental/19/introduction-to-the-labview-application-...

Hope that helps!!

Dan

[Herbert Engels]

It actually depends on which file format you use. LVM and TDMS should not require any additional installers. For TDM, you need to check "NI-USI" on the "Additional Installers" page of your installer definition.

Another thing that potentially can go wrong is that you might have more than one Express VI writing to the same file. In that case, you need to uncheck the box "lock file for faster access" in the configuration dialog of the Express VI. Otherwise, one VI has the file locked, while the other one is trying to close it in order to create a new one with an incremented file number.

Herbert