Jim Kring

Fantastic!

Hi @Dataflow_G. We just made some changes to our SSL certificates to work around some issues experienced by LabVIEW (and some older browsers/devices). Can you try again and let me know if it's working (or not) now? Thanks

I'm glad you found a work-around. Also, there's one network setting in VIPM that may be helpful for understanding why the package download is failing. You can try changing this setting and see if it helps...

One idea is to try an older version of VIPM. I might start with VIPM 2019.0 (build 2029), which uses the LV 2015 Runtime Engine. Also, I've been chatting with NI's R&D team to learn more about this issue running Windows in Parallels on M1 Macs w/ Intel emulation for Arm. The short answer is: "it's not officially supported"

Can you check to ensure you have write permissions on the “C:\ProgramData\JKI\VIPM\cache” (or similar) folder.

Can you look in the error log to see if there is a recent error related to that? you can also delete the most recent log file, then repeat the refresh package list, and then look at the contents of the new error log file to see what is specifically related to this operation. You can feel free to attach that log file or copy paste the contents.

Thanks for that extra info. Can you try refreshing the package list?

Hi There. If you go to VIPM's main package list and right-click on one of those packages and choose "Download" does that work?

Would you try installing LV 2019 (full install / evaluation activation is OK) We had one user let us know this worked for them. I have not personally tested this. note: We have an M1 coming in for testing.

Thanks for reporting this. Which VIPM version do you have installed? Which LabVIEW versions do you have installed on this computer?

Yes, it should work just fine on 64-but LV. If you run into any issues, let us know.

@Mohammed Ashiq S, I've created an initial repository with the start of these tools, here: https://github.com/vipm-io/VIPM-Package-Building-Tools They have been sitting around for a while, so I figured I would at least share them in their current state.

Hi @Mohammed Ashiq S, My reply is going to be in multiple parts, since this is a long discussion and not all of the finer points are well documented. You're right that VIPM's package format supports what you're trying to do, however the VI Package Builder does not directly expose all the features you'll need. The good news, is that you can use a combination of pre-/post-build custom actions to do what you need. One approach is to do the following: 1) Use a post-build custom action to temporarily "unpack" the package file (extract the package's contents to a folder, as it's a ZIP archive) 2) In the unpacked/extracted package folder, add the required multi-platform PPLs to the package and/or modify the package spec file to adjust it to have the desired settings. 3) Repack the package folder into the original package file location, so it can then be double-checked by the package builder and finalized. Note that there are some tools for doing this (e.g. scattered around this forum), but they have not been officially released as a package. I would be happy to assist in organizing these, so they are generally available and useful to the community.

Hi There. Warning: These instructions involve opening important files in VIPM's package installation database. Be very careful not to change anything in these files, or it could corrupt your installation and cause errors that are very hard to recover from. On your Windows installation, take a look at the following text file: C:\ProgramData\JKI\VIPM\databases\LV 21.0\mb_master\files-installed This lists the files that were installed by the Plasmionique Modbus Master package. Also, note that there may be some other packages installed that the above packages depends upon. You can take a look in this folder to see what other packages are installed in LabVIEW 2021. C:\ProgramData\JKI\VIPM\databases\LV 21.0 I hope that helps keep you moving in the right direction...

One not-so-great solution is to install the packages in a Windows machine and then copy the installed files over to a Linux machine. We're working to improve VIPM for Linux, in general, but don't have a target release date.

Hi there. Please take a look at this guide and let us know if that helps: Configure VIPM to Download LabVIEW Add-Ons for macOS

Thanks for reporting this. We've updated the OpenG Dictionary Homepage.

LabVIEW Tools Developers (VIPM Community Publishers) must decide, when working on their tools, which LabVIEW version they want to use to edit/create the tools. Generally speaking, a LabVIEW Tools developer will want to support the largest number of users as is practical (and only users with the same or newer version of LabVIEW will be able to use the tool). We've put some of the VIPM web search data into a chart to show LabVIEW Version Popularity over the past year or so. We hope this is helpful to LabVIEW Tools Developers (and LabVIEW users in general). ------------ Side Note: Forward Compatible PPLs in LabVIEW 2017+ Another useful bit of information is that since LabVIEW 2017 you can compile a packed project library to be also used with newer versions of LabVIEW. In the build specification properties choose Advanced in the sidebar and enable the option Allow future versions of LabVIEW to load this packed library. This option is enabled by default.

Hmmm, that’s very odd. I’d be curious of VIPM 2021 would resolve this, since there were various fixes in that release. Would you be able to upgrade and try?

Thanks for posting the screenshot. What does the dialog show after you press OK? It should indicate the caller of that missing vi. it’s hard to know for sure if A mass compile of your Source folder would fix the issue. Possibly, yet sometimes the linkages can be crossed up across different projects.

Does the VIPM error dialog state which calling VI is trying to find that missing VI? The dialogue has two parts: one that shows you the missing VIs, and the second that shows you which project source VIs are calling the missing VIs also, often the culprit is a VI on disc that is not actually being used anymore, but it’s broken. The package builder is including it, even though it’s not being called by anyone

Awesome! Glad that worked. Also, VIPM Pro has lots of other great features, too

The easiest way is to save them into a VIPC file. This is a VIPM Pro feature, which we created to address this challenge. How-to-use-VI-Package-Configurations (VIPC files) However, I'm curios why the other dependencies can't be found -- is that a network issue?

I just emailed you some instructions. I did this privately, since the steps involved are tricky and I don't want anyone trying this at home without a safety net.

Hi @Horsechilli I saw this happen recently, too, and it was also in LabVIEW 2017. I'll gather my notes on this to try to help you out. Stay tuned... -Jim