12/11/2022 0 Comments Property node labview![]() ![]() Add the XJTAG bin directory to this list to tell LabVIEW that it should search there as well. Here select VI Search Path in the drop down list to show all the paths LabVIEW searches when it looks for unresolved paths. To do this the XJTAG bin directory should be defined in LabVIEW’s VI search path.įrom LabVIEW select Tools > Options… and pick the Paths category this will display the paths options screen. The first step is to ensure that LabVIEW can find the reference when it comes across an invalid path to the assembly. Updating the references to XJRunnerIntegration.dll Unfortunately that does not exist, because LabVIEW keeps hard-coded references to the assembly in all VIs that make a call to the assembly. This problem would be trivial to deal with if there were a straight-forward way of pointing to the correct path in LabVIEW. a machine running a 64-bit version of windows where XJTAG is installed in “Program Files (x86)”), LabVIEW is not able to find XJRunnerIntegration.dll. This means when the examples are run on a machine where the XJTAG bin directory is on a different path (e.g. These examples were developed on a 32-bit XP machine where the XJTAG bin directory (containing the XJRunner integration binary and it’s dependencies) is located at “C:\Program Files\XJTAG X.x\Bin”. These examples have been added to since that release. This came with a new set of LabVIEW examples detailing how the API could be used within the LabVIEW environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |