LabVIEW Sound and Vibration Toolkit 2023 Q3 Known Issues

Overview

This document contains the LabVIEW Sound and Vibration Toolkit known issues that were discovered before and since the release of LabVIEW Sound and Vibration Toolkit 2023 Q3. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.

Bug Number

Legacy ID

Description

Details

410911 632043

Continous Sweep THD VI Takes Too Long to Execute When Max Harmonic is High

Continuous Sweep THD VI takes too long to execute when max harmonic is high.

Workaround:

1. Sample faster. 2. Break the sweep into two segments (high and low frequency) and decrease the maximum harmonic for the high frequency sweep. 3. Parse the acquired waveform and perform explicit resampling to angular domain (see Continuous Sweep* (Advanced) example VI). Explicitly maintain multiple resampled signals (each with appropriate sampling for the frequency resolution).

Reported Version:

S&V Measurement Suite 2016

Resolved Version:

N/A

Added:

Apr 24, 2017

1044289

Opening Any SVT Executable on a Target Computer Causes Errors

When you open an executable that includes SoundVib_MCM Examples.lvlib on a target computer, the executable errors out due to a missing dependency, LVASPT_TFA.dll.

Workaround:

In Application Properties, in the Source Files category, add LVASPT_TFA.dll to your application as Always Included in the build configuration, as shown below. The LVASPT_TFA.dll file is located in the C:\Program Files (x86)\National Instruments\LabVIEW 20xx\resource\ folder. image

Reported Version:

LabVIEW Sound and Vibration Toolkit 2021

Resolved Version:

N/A

Added:

Jul 17, 2023

2432236

"File Not Found Error" Occurs When the SVFA API Is Used with Appbuilder

Some of the Sound and Vibration Toolkit Frequency Analysis (SVFA) VIs cause Application Builder to fail generating an application. Note that you can still use Application Builder with SVT (Sound and Vibration Toolkit) to build applications that do not use SVFA. This issue occurs with SVT decoupled versions on LabVIEW 2022 and LabVIEW 2023. Application Builder fails with the following message: LabVIEW cannot find a file that is a dependency of a Startup, Exported, or Always Included VI. File Not Found: C:\Program Files\National Instruments\LabVIEW 2022\ vi.lib\addons\_NISVFA\_Shared subVIs\Spectrum Averaging\svfa_Average Array (complex) No State.vi The missing file might be referenced by one of the libraries included in the build or by the file - Multifunction FFT (Simulated).vi. To fix this issue: - Open all Startup, Exported, or Always Included VIs, recompile them (CTRL+SHIFT Click the Run arrow) and save them to update their dependencies.

Workaround:

To build applications with SVFA, copy the Spectrum Averaging folder from C:\Program Files\NI\LVAddons\nisvt\1\vi.lib\addons\_NISVFA\ _Shared subVIs\Spectrum Averaging to the following path: C:\Program Files\National Instruments\LabVIEW 20xx\vi.lib\addons\ _NISVFA\_Shared subVIs\

Reported Version:

LabVIEW Sound and Vibration Toolkit 2023 Q3

Resolved Version:

N/A

Added:

Jul 17, 2023

2360991

SVT Shock Response Spectrum Is Not Working As Expected

In the SVT Shock Response Spectrum (SRS) function, Absolute Acceleration (the default value), works correctly but Relative Displacement does not work as expected. In the image below, relative displacement is expected to decrease with an increase in frequency. DIAdem (left side) shows the correct result, but the SVT SRS (right side) displays an incorrect result for relative displacement. image

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW Sound and Vibration Toolkit 2021

Resolved Version:

N/A

Added:

Jul 17, 2023

2636239

Sound and Vibration Toolkit sample projects with channels do open from the LabVIEW getting started wizard

SVT sample projects with channels do not instantiate from the getting started wizard and throw file permission errors. Go to C:\Program Files\NI\LVAddons and find nisvt Right-click on the nisvt folder and remove the read-only flag Run LabVIEW in Administrator mode and then try to instantiate the sample project from getting started wizard. image Whether running LabVIEW in normal user mode or as an administrator, the error was observed with the following sample projects (which all use channel wires): Dynamic Signal Analyzer Dynamic Signal Generator 1/3 Octave Analyzer

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW Sound and Vibration Toolkit: 2023 Q3

Resolved Version:

N/A

Added:

N/A

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).