Error -2564 occurred at SoundVib_UFF58.lvlib:SVT while trying to execute a labview built executable

[nidbid]

One of my goals has been to build reasonably standard labview VIs that can be built and distributed to universities for teaching purposes in the domain of modal testing. 

To this end, I took the impact test VI template in the sound and vibration toolbox and made some modifications and tried to see if this can be run on machines that don't have a LabVIEW license. In other words, I want to just distribute the executable. 

I am using a plugin for exporting files in the UFF 58 format (https://www.ni.com/en/support/downloads/dataplugins/download.international-electrotechnical-commissi...). 

So the "setup" for running my executable should be:

1. Install labview runtime
2. Install the UFF plugin above
3. Install NI DAQmx

then run. All the above don't require a LabVIEW license, which is fantastic!

But when I run my executable on machines without a labview license, the block I'm using to export to UFF seems to always lead to an annoying error:

```

Error -2564 occurred at SoundVib_UFF58.lvlib:SVT UFF58 Open File.viOpen Data Storage

Possible reason(s):

LabVIEW: (Hex 0xFFFFF5FC) The software installed on this computer does not support the file format you requested. The Storage/DataPlugin VIs access files through plug-in libraries LabVIEW and DIAdem install.

```

I'll be very thankful if someone can provide me a solution/a suggested modification that I can make in my program that will let me run this on machines that don't have access to a labview license. 

1. Here's a link to the VI project: https://drive.google.com/drive/folders/1qDsn6IwCMeiYyoHQp2ATI35Sv46Io3KJ?usp=sharing
2. Here's a link to executable: https://drive.google.com/drive/folders/1ELnzrsGnHfHKCQTWLqtM2jp51pLuB5Mn?usp=sharing

[dsb@NI]

Out of curiosity: do you get this error if you try to build an EXE out of either of these SV examples?

• Read Time Waveforms with Records (UFF File)
• Write Time Waveforms (UFF File)

I will have to check, but I thought one has to register each USI plugin.

If blocked by this frustrating silliness with the UFF plugin, you can work around by replacing the binary implementation with the ASCII implementation:

Writing ASCII UFF files does not require the UFF Plugin for TDMS.
Impact Test sample project doesn't read the UFF File. The sample project generates the UFF File so the FRF results can be post processed by other software.