[Network Issues with JKIsoft.com]

I am having issues on all my PCs with accessing the "VI Package Network".

 

https://support.vipm.io/hc/en-us/articles/214135483-Solving-VIPM-Network-Connection-Issues

• http://ftp.ni.com/evaluation/labview/lvtn/vipm/
• http://www.jkisoft.com/packages/
• *.dl.sourceforge.net (This is the origin of the OpenG packages)

I am able to access sourceforge and ftp.ni.com (which seems to forward to download.ni.com), but I am unable to access jkisoft.com/packages.

Example: Trying to download the OpenG Variant Library via the web (https://www.vipm.io/package/oglib_variantconfig/)

 https://www.jkisoft.com/packages/packages/oglib_lvdata/oglib_lvdata-6.0.0.45.vip

Is this still a valid URL?

[Issue with System Packages]

Publishing the System Packages did solve the issue. 

 

 In order to find the System Packages to publish, I had to check the "Show sub-packages" in the VIPM Options > General tab.

 

[Issue with System Packages]

Cross posted on LavaG, but was not getting any replies.  So lets try here.

 

I am using the newest version (2020.1) of VIPM, but I had this same issue with the release of 2020.

For two of the packages that I have created for internal repos, VIPM has decided that I need a System Package.   The posts I have seem from JKI indicate that this is a sub-package that is used internally to the main package, and should be automatically included.

However, after I am seeing issues on any PC other than the PC where the package was built.

Is there a setting I am missing?

 

Showing the (System) package as a dependency:

 

Package Configuration in the VI Package Configuration Editor

 

 

Package installed, on the PC where the package was initially created (no issues, no exclamation mark)

 

 

 

Package when installed on another PC (NOTICE: the System Package name has changed and there is a red exclamation mark, but there are no errors shown on install of the package).

 

 

[VIPm Is copying vis from dependency vi into new directory]

Here is what I have done so far to reproduce the issue (I can reproduce on multiple packages, I used a simpler example for the post):

Build my FGV Package.  Shown below is the file locations on disk in the LabVIEW Project.   I then built the package, and installed the package.  After installation, the files are all in the FGV folder, with no extra files.

 

Now I want to build my File Path package, which depends on the FGV Package I just installed.  NOTE the FGV - Test Mode located in the FGV folder on disk.

VIPM correctly identifies that the BMI FGV package is required.

Save the configuration and build the package.

Install the package.

When the package is installed, the file that was in the FGV Package has been added to the directory File Path, instead of using the FGV - Test Mode located in the FGV folder with the FGV Package.

 

[VIPm Is copying vis from dependency vi into new directory]

I am creating some packages for our internal reuse code.

I create Package "Config Files".   This package does not have any other package dependencies, and installs as expected (using custom directory, not under LabVIEW).

I create a second package, "File Paths", which calls a vi in the Config Files package.  Since the Config Files package is installed, VIPM correctly says that the Config Files is a dependency.

When I go to build and install (using custom directory, not under LabVIEW) the File Path package, I see a copy of the vi from Config Files under the directory of File path, instead of the file that should have been used under the Config File path.

What I Expect:

C:\Config Files\test.vi

When Installed:

C:\File Paths\test.vi

 

I saw some older forum posts about Internal and external dependencies, but I do not see that option in LV 2019.   Has this option been removed?

[Unable to subscribe to local repository]

I am using the trial version of VIPM to evaluate whether our company wants to utilize VIPM Pro for our process.  I have been happy with it so far, and have been able to create a number of packages.

Now I want to start having other team members use the packages I created.   So I have published to a repo on a network drive.  When the other team members (who have the free version of VIPM) try to go to the Tools > Options, then click on "Network" to add a subscription to the local repo, they get a dialog that says "Subscribing to a VI Package Repository, requires upgrading your Free version of VIPM to Pro".

This is the method described in the tutorial video on the JKI website.  https://support.jki.net/hc/en-us/articles/214136483-Getting-Started-with-VIPM

Do all team members now need VIPM Pro to subscribe to a local feed?

I tried using VIPM 2018 and 2019, got the same error in both.