Locating Files and Using 64-Bit Test Executives

When using a 64-bit version of a test executive such as LabVIEW, it will be necessary to use the 64-bit version of XJDeveloper. When using a 32-bit test executive, the 32-bit version of XJDeveloper should be installed.

Helping 64-bit LabVIEW Locate XJIntegration.dll

When 64-bit versions of software are being used, XJIntegration.dll will be stored in the 64-bit Windows directory structure. However, when loading projects that were created using 32-bit LabVIEW (such as the XJTAG examples), LabView will search for XJIntegration.dll in the 32-bit directory (Figure 1) and will therefore be unable to locate it.

LabVIEW will search for XJIntegration.dll in the 32-bit directory

Figure 1: Helping LabVIEW locate XJIntegration.dll

In this situation, the user will need to point LabVIEW to the correct path. For 64-bit installations, XJIntegration.dll can be found in the following directory:

Helping 64-bit TestStand Locate XJIntegration.dll

If the .NET example modules are used in a 64-bit version of TestStand, it will be necessary to adjust the path to XJIntegration.dll for each module to avoid it searching for files in the 32-bit program directory:

TestStand will search for XJIntegration.dll in the 32-bit directory

Figure 2: Helping TestStand Locate XJIntegration.dll

For 64-bit installations, XJIntegration.dll can be found in the following directory:

Helping LabVIEW Locate Necessary VI Files

When using the example LabVIEW projects, if LabVIEW fails to locate individual VI files such as DemoBoardpath.vi or ToArray.vi which reside in the Common subdirectory, it should be repointed to find the files on the following path:

\XJIntegration .NET Examples\XJDemo V4 Examples\Common\LabVIEW\Public\Configure\

Once the files have been located and LabVIEW has opened, a warning may be displayed with the message, "Dependency located from new path" as a result of these redirections; this can be ignored.

  • The VI Search Path options within LabVIEW allow the default search paths to be set to avoid the user having to adjust the path each time.
  • Because LabVIEW and TestStand hardcode the link to the XJTAG software, it will be necessary to point them to the new XJIntegration.dll whenever XJTAG is upgraded. See here for more details.