Archived: Sound and Vibration Toolkit for LabVIEW NXG 2.0

The Sound and Vibration Toolkit for LabVIEW NXG 2.0 enables you to migrate your existing sound and vibration applications to LabVIEW NXG 2.0 using the Code Conversion Utility in LabVIEW NXG 2.0. The Code Conversion Utility in LabVIEW NXG 2.0 supports applications built in LabVIEW 2014, 2015, 2016, and 2017. The Sound and Vibration Toolkit for LabVIEW NXG 2.0 supports most of the configuration, measurement-analysis, and data storage VIs included in the Sound and Vibration Toolkit and the Sound and Vibration Measurement Suite 2017 and earlier. The Sound and Vibration Toolkit for LabVIEW NXG 2.0 does not contain VIs or examples for new application development in LabVIEW NXG 2.0. The following table shows supported functionalities of the Sound and Vibration Toolkit and the Sound and Vibration Measurement Suite in LabVIEW 2017 and LabVIEW NXG 2.0.

Table 1. Supported functionalities in LabVIEW 2017 and LabVIEW NXG 2.0

The following table lists sound and vibration VIs and controls that are not supported by the Sound and Vibration Toolkit for LabVIEW NXG 2.0.

Table 2. Unsupported VIs and controls in LabVIEW NXG 2.0

You can use the Code Conversion Utility in LabVIEW NXG 2.0 to convert Express VIs. You need to edit an Express VI before or after conversion. If you edit an Express VI after conversion, you must edit every instance of the converted Express VI in the application. Do not reuse one instance for another if the instances have different configurations. The Code Conversion Utility replaces unsupported Express VIs with placeholder nodes.

Removing Unsupported Property Nodes

LabVIEW NXG 2.0 does not support some Property Nodes. You need to remove unsupported Property Nodes from Express VIs before or after conversion.

For example, LabVIEW populates the last data running through an Express VI in the interactive configuration pane when you reconfigure the Express VI. LabVIEW NXG 2.0 does not support the interactive configuration of Express VIs. You need to remove Property Nodes that record the last data running through the Express VI. The highlighted code in the following figure shows an example of unsupported Property Nodes that you need to remove.

Figure 1: Unsupported Property Node before conversion

Removing Unsupported Property Nodes before Conversion

Complete the following steps to remove unsupported Property Nodes before conversion:

1. Right-click the Express VI and select Open Front Panel.
2. Switch to the block diagram and remove unsupported Property Nodes.
3. Remove broken wires and save the changes.
4. Run the Code Conversion Utility for LabVIEW NXG 2.0 to convert the Express VI.

Removing Unsupported Property Nodes after Conversion

You can also remove unsupported Property Nodes after you convert an Express VI using the Code Conversion Utility. The following figure shows the diagram of an Express VI after conversion.

Figure 2: Unsupported Property Node after conversion

In Figure 2, the highlighted code contains an unsupported Property Node. Remove the highlighted code, clean up broken wires, and save the changes.

Disconnecting Unsupported Type Definitions

LabVIEW NXG 2.0 does not support some XControls and the type definitions connected to those XControls. You need to disconnect unsupported type definitions before or after conversion.

The following table lists unsupported type definitions.

Table 3. Unsupported Type Definitions

Name	Appearance on the front panel in LabVIEW	Appearance on the panel in LabVIEW NXG 2.0
svx_SC Line Data.ctl
svx_Polar_Plot_Data.ctl
svx_Orbit Data.ctl

Disconnecting Unsupported Type Definitions before Conversion

Complete the following steps to disconnect unsupported type definitions before conversion:

1. Select the unsupported type definition on the block diagram and switch to the front panel.
2. Right-click the type definition and select Disconnect from Type Def. 
3. Save the changes.
4. Run the Code Conversion Utility in LabVIEW NXG 2.0 to convert the Express VI.

Disconnecting Unsupported Type Definitions after Conversion

You can also disconnect unsupported type definitions after conversion. The Code Conversion Utility in LabVIEW NXG 2.0 converts type definitions to G Types, which serve a similar purpose to type definitions. 

Complete the following steps to disconnect the type definitions after conversion:

1. In LabVIEW NXG 2.0, find the unsupported G Type on the diagram.
2. Right-click the G Type and select Disconnect G Type. 
3. Save the changes.

Removing Unsupported Functionalities from an Express VI

The Code Conversion Utility in LabVIEW NXG 2.0 may not convert some of the functionalities that a sound and vibration Express VI uses in LabVIEW, so you must edit the Express VI for your application to run successfully in LabVIEW NXG 2.0. Some VIs in an Express VI may not be supported in LabVIEW NXG 2.0, but you can replace them with equivalent VIs in LabVIEW NXG 2.0. 

For example, the SV Standardized Filter Express VI applies the specified filter and calculates the frequency response of the specified filter. The following figure shows the unsupported functionalities on the block diagram of the SV Standardized Filter Express VI. You need to remove the unsupported functionalities before or after conversion.

Figure 3: Unsupported functionalities in the SV Standardized Filter Express VI

Unsupported code that calculates and returns the frequency response of the specified filter

Unsupported Property Node

After you remove the unsupported functionalities, the remaining code only applies the specified standard filter to the input signal and does not calculate the frequency response. Figure 4 shows the remaining code after you remove the unsupported functionalities.

Figure 4: The remaining code after you remove the unsupported functionalities

Refer to the Frequency Analysis of Filter Design example in LabVIEW NXG 2.0 to compute the magnitude response and test the measured response against target specifications.