How Do I Compare Two VIs in LabVIEW?
Primary Software: LabVIEW Development Systems>>LabVIEW Full Development System
Primary Software Version: 8.0
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Development Systems>>LabVIEW Professional Development System
How do I compare two VIs in LabVIEW?
In LabVIEW, you easily can compare two VIs with different names. To compare two VIs with the same name, refer to the instructions below. You can use the Compare VIs dialog box to compare two VIs that are open in LabVIEW (in memory). If no VIs are in memory, LabVIEW grays out the Compare VIs menu item.
Note: To compare two VIs that are not open in LabVIEW, use LVCompare.exe (LabVIEW 2011 Help: Configuring Source Control with LVCompare.exe) to compare VIs using a third-party source control provider or the command line.
Complete the following steps to compare two VIs that are open in LabVIEW.
Select Tools»Compare»Compare VIs to display the Compare VIs dialog box.
In the dialog box, select the VIs you want to compare. Choose which items from the VI you would like to compare by placing a checkmark next to those items. After you select the VIs to compare and the attributes to compare, click the Compare button. LabVIEW shows the two VIs side-by-side, along with the Differences dialog box.
Click a difference in the left pane to see its details. The details describe what type of difference each item refers to. Place a checkmark in the Circle Differences checkbox to place a red circle around the item in each VI that a particular difference refers to. If you highlight a difference and click the Show Difference button, LabVIEW highlights and places a red circle around the item in each VI that contains that difference, as shown in the following block diagram.
Comparing Two VIs with the Same Name
You can compare two VIs with the same name, but these VIs must reside in different LabVIEW projects, and you must open these VIs from the project.
After you open the VIs, select Tools»Compare»Compare VIs to compare the two VIs. Refer to the beginning of this document for more information.
Report Date: 01/11/2005
Last Updated: 10/30/2012
Document ID: 3HAAL5N8