Jim Kring

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.

@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

Hi @Shyam Can you please look to see if there are any error log files in this folder and let us know what the errors are, if any? C:\ProgramData\JKI\VIPM\error Thank you. -Jim

I’m not sure where a good example might be at the moment… Here’s what you would do: - unzip the VIP file to a folder, - load and re-save all the VIs without diagrams, - (re)zip the folder back into a VIP file (same name and location as passed into the post-build action VI) I’ll see if I can find an example…

Hi @coco. Thanks for posting your question. One possible solution would be to remove BD's in a post-build custom action. Another possible way would be to build your library into a PPL (removing BD's during the PPL build process) and then create a package from the PPL. Have you tried either of these approaches? -Jim

VIPM 2023 for Windows has been upgraded to use the LabVIEW 2022 Q3 64-bit Runtime Engine. Before we get into the details, let's address a big question... Question: Will VIPM 2023 work with older versions of LabVIEW (including 32-bit LabVIEW)? Answer: Absolutely, Yes! Here are the details. VIPM is actually written in LabVIEW and is built as a stand-alone executable. It uses VI Server to communicate with LabVIEW for various things and works fine with older LabVIEW versions (including 32-bit and 64-bit LabVIEW). Also, we've made an improvement to VIPM's installer so that it downloads the LabVIEW Runtime Engine installer from NI's servers, only when it's needed. So, if you already have the LabVIEW 2022 runtime engine installed on your system, VIPM's installer won't download or install it. Also, installing the LabVIEW 2022 runtime engine will install NI Package Manager on your system. This is how you install modern versions of LabVIEW, so that shouldn't be a problem for VIPM users 😉 This means that the VIPM 2023 installer is much smaller than previous releases, which means it's faster to download, install, and update. 🚀

Here's a nice improvement for package building... When you edit the pallet location it can take a while for the tree to populate. Now (in VIPM 2023) it’s much faster—when you reopen the window, it will only populate the tree once (for each LabVIEW version) and will reuse the cached state until you press the “refresh” button.

I'm glad you figured out the issue and a workaround.

OK, we've added a deprecation notice to the old package's homepage. We will also mark it as deprecated in the package repository so that it doesn't show up in VIPM Desktop package list, by default.

Sure. Has the new/replacement package been published yet? Is it this one? The names were slightly different so I wasn't sure. https://www.vipm.io/package/neosoft_technologies_inc_lib_open_dqmh_request_message_diagram/

Sure, no problem. We can do either/both of those options.

@JimPanse, I haven't seen that error before. You could try changing the proxy settings in VIPM's options dialog to see if that helps at all. You could also try talking to your IT department 😕 https://support.vipm.io/hc/en-us/articles/214135483-Solving-VIPM-Network-Connection-Issues http://jkisoft.com/vipm/docs/2014/?turl=networkoptions.htm Let me know how it goes -- I'm curious what the root problem is for your system.

👇Update there is a release candidate of VIPM 2023 Q3 available 👇 VIPM 2023 for Windows Beta Tester Release What's New Please see the Release Notes Also check out the 2023.1 Improvements tagged topics here in the beta forum Download Latest beta build is here: vipm-2023-beta-setup.exe Notice This software will only work through mid Feb, 2023. At that time, you will be required to upgrade to a final public release. Questions or Comments? Post your questions and comments here in the beta forum.

The solution was to remove the extra/duplicate data in the repository index and fix the bug that caused it to appear in the file. This is a server issue (it was sending the client too much data) and not related to VIPM Desktop itself.

Sorry for the trouble everyone. The issue has been fixed.

Fixed. Thanks.

Issue Over the past 24 hours there was a VIPM issue where the client was showing out of memory errors. This has been resolved. How to Fix Please try restarting VIPM Desktop and refreshing your package list (the refresh button) a couple times. If you still have problems, try deleting the “C:\ProgramData\JKI\VIPM\cache” folder and restart VIPM. Background The problem was on the vipm.io server — the the repository index file had grown exponentially large due to a character encoding bug that was causing one special character of a certain package name to get duplicated on every package release (and the duplications kept getting duplicated). The repository index file grew to ~64 MB (it was growing in powers of 2... 4, 8, 16, 32, 64) and then caused all the VIPM Desktop clients to have out of memory errors! Some Lessons Learned The littlest bug can sometimes cause big problems — like a mosquito when you’re trying to sleep. Exponential Growth sneaks up on you and then gets out of control very fast. The out of memory error in VIPM Desktop showed several places in the codebase that could be further optimized as the total number of packages continues to grow. The LabVIEW Configuration File (INI) VIs don’t handle extremely large files well. Parallel For Loops allow work to be done on large arrays much faster (operating on elements in parallel), but it also takes more memory. There is a trade off. We are looking into a build of VIPM in 64-bit LabVIEW to make more memory available, when needed.

@russellblake It should be working now. Please try restarting VIPM and refreshing your package list a couple times.

@russellblake Thanks for reporting this. We're aware of the issue (it just started happening late yesterday) and are working on a fix.

Hi @Vishal. Can you try uninstalling VIPM and then re-installing VIPM 2022? I'm not sure why it's having this issue. The shortcut references to VIPM File Handler are correct for that version of VIPM.

We can’t guarantee it, but we’re working on it.

Sorry, I mistyped that. I meant to say, "in 2023Q1 you'll be able to use VIPM Community Free Edition to call the API..."

@LeahEdwards Yes, in 2023Q1 you'll be able to use VIPM Community Free Edition to call the API and edit the vi package build spec. And, you should still definitely buy VIPM Pro...