Michael Aivaliotis December 6, 2011 •
Other Products / General
If you need help (With products or services) and the articles below do not answer your question, please submit your request:
Jim Kring May 16 •
VIPM / Release Notes
Note: Other release notes can be found here.
What's New in VIPM 2016.0.0
VIPM 2016 is a major release for for Windows that adds performance improvements and fixes some bugs. It is recommended that all VIPM users on for Windows upgrade.
Note: You will need an active VIPM Pro subscription in order activate VIPM 2016 into Pro Edition.
- Various Performance Improvements - Users can expect noticeable performance improvements, especially on multi-core machines, during launch, check network for packages, search box results while typing, and package list sorting by column.
- Packages built with VIPM 2016 can only be installed on VIPM 2014 or newer. Package built with VIPM 2016 cannot be installed on versions of VIPM 2013 or older. Details.
16733: Specifying package installation requirement of LabVIEW 32-bit or 64-bit was resulting in packages that could be installed on any LabVIEW bitness. Packages now specify the correct LabVIEW bitness requirement and are only installable on the specified LabVIEW bitness.
16809: Source Only VIs were not being mass compiled during installation. Now, VIPM will force a mass compile in the target LabVIEW version, even when LabVIEW would otherwise not notify users of unsaved changes (e.g. a “dirty dot” asterix).
17093: Repository Manager UI sometimes showed packages in wrong folders of tree-view. This now works correctly.
17173: OS bitness showed up twice in package info dialog text (cosmetic bug). This now shows correctly.
17175: Password manager not working with HTTPS (SSL) package repositories. Username and passwords are now correctly stored and recalled for HTTPS (SSL) package repositories.
17196: Some non-system packages were being shown when switched to System target.
- 13790: VI Package Builder - This issue affects package building of classes. The issue appears to be isolated to VIPM. It's possible to build a package where members of a friend class cannot access members of a community scoped class. This occurs if you set a password on the community scoped class in the VIPM source files settings page.
Michael Aivaliotis May 21, 2012 •
VIPM / Support
Note: If the problem you are having is that your list of LabVIEW versions list is empty in VIPM, then look here.
For Mac OS: See also Here
Sometimes VIPM has trouble connecting to LabVIEW to perform installation of Add-ons. The following is a list of things you can try to fix the problem.
- LabVIEW machine access list - Make sure you have the following IP addresses configured in your VI Server setting in LabVIEW:
- asterix (*)
- Sometimes: <your IP address on the network>
- Sometimes: <your PC name>
- Exported VIs list
- LabVIEW VI Server Settings - Make sure you have the following VI Server settings in your LabVIEW Options. Note that the Port number will be different on your system. If you have multiple LabVIEW versions, then you should assign a different port number for each LabVIEW version. Normally you should not have to adjust your port numbers since VIPM will set these automatically
- VIPM port list configuration - If you have multiple LabVIEW versions, then you should assign a different port number for each LabVIEW version. Normally you should not have to adjust your port numbers since VIPM will set these automatically. However, in case of problems, you should make sure that VIPM has the correct port identified in the VIPM options window.
- Check LabVIEW connection to web server by trying to open "Example Finder" (Help >> Find Examples)
- If Example Finder does not open, repair LabVIEW and then try VIPM
- Configure the Windows Firewall:
Restart LabVIEW - If the above setting appear correct, then you should restart LabVIEW.
Restart Computer - If this does not work then you should restart your computer and try the connection again. Sometimes, restarting your computer resolves the problem.
- Click Start in windows. Type: "allow a program through windows firewall" then select it.
- Make sure LabVIEW 20xx and VIPM are added to this list and are allowed to communicate through the windows firewall.
- Launch VIPM with "Run As Administrator" Privileges:
- Right mouse click on VIPM shortcut and select "Run As Administrator" option
- If the option is not listed, try SHIFT+RightMouseClick