Matthew Nevels Posted December 14, 2022 Report Share Posted December 14, 2022 VIPM 2022.0 (build 2371), LabVIEW 2022 Q3, DAQmx 2022 Q3 I get an error stating that DAQmx VIs are missing. See below. The VIs are, in fact, not in the path that VIPM is looking for them, I'm not sure how to get VIPM to look for them in their actual location. Instead of being installed in: C:\Program Files\National Instruments\LabVIEW 2022\vi.lib\DAQmx My files are installed in: C:\Program Files\NI\LVAddons\nidaqmx\1\vi.lib\DAQmx I've done nothing special during installation - using default values when presented with any options during LabVIEW / DAQmx installation. I've done a mass compile, hoping that would fix whatever links are no good but I still get the error. I've verified that my code is working so I know LabVIEW is happily linking to the path that these files actually exist in. I've searched the knowledgebase articles and NI forums but can't find anything that fits this situation and am not sure what my next step should be. Any ideas are welcome. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted December 14, 2022 Report Share Posted December 14, 2022 @Matthew Nevels Thanks for reporting this issue. NI has made some changes to where certain drivers are installed and it's broken VI Package Builder. We've opened a bug report for this issue, here: https://github.com/vipm-io/vipm-desktop-issues/issues/17 1 Quote Link to comment Share on other sites More sharing options...
Matthew Nevels Posted December 15, 2022 Author Report Share Posted December 15, 2022 Thank for opening a bug report. In the meantime I have determined that I can get around the issue by copying the DAQmx folder to the location that VIPM is expecting it to be, building my package and then deleting the files I copied. 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted December 15, 2022 Report Share Posted December 15, 2022 I’m glad to hear you found a work around that enables you to get your package built. You could probably automate the copying of the files before the build, and deleting them afterward, and invoking the package build programmatically using the VIPM API. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.