Jump to content
Steamboat_Willie

Downloading VI Pkg file only

Recommended Posts

Usage of the VIPM is new territory for me. I have 2 PC's in my development environment. PC "A" is connected to the internet. PC "B" is NOT as it is on a dedicated private secure network and due to constraints connection to the "public" (outside world) internet is not allowed. I downloaded the VIPM installation file onto my "public" PC and was able to successfully install it on my "private" PC by first copying the installation file over via an external CD.

 

The problem I have is that I can't seem to figure out how to download a VI package "file" itself with the intention of NOT installing it because of the separation between the "public" and "private" networks I'm faced with. All my LabView development work is done on the private network.

 

When I posed my dilemma to the NI support desk when I wanted to obtain their VI scripting package, they provided me with an ftp link to the ".vip" file for that package. Thus I was able to download "only" (but not install) a VI package. That scripting pkg was subsequently copied via an external CD over to the private network machine and successfully installed.

 

Is there a way to do this and access the actual VIP files with the assorted openG VI packages I see that are available ? Looks like lots of neat utilities and time savers (stuff I'd like to "not be living without"). If my ultimate target machine was and could be connected to the public internet then, obviously, I wouldn't have this problem. FAQ's clearly explain how to "install" VIP's but only through usage of the VIPM app itself. Hope I've explained myself correctly.

Thanks.

Ed

Share this post


Link to post
Share on other sites

You can do this by upgrading to VIPM professional. Then you can use the VI Package Configuration editor to create a VI Package configuration file.

 

You can select multiple files from the VIPM main window and then drag them into the configuration. This can be saved to a VIPC file (*.vipc). You can then take this single configuration file (which contains all your packages) and apply the configuration onto the target machine. Since the configuration file contains the packages internally there is no network connection required.

 

More information can be found here.

Share this post


Link to post
Share on other sites
You can do this by upgrading to VIPM professional. Then you can use the VI Package Configuration editor to create a VI Package configuration file.

 

[...]

 

Michael,

 

There was a time that we could copy files from the VIPM installation directory instead of making a package. Has that changed with VIPM 2010?

 

Jim

Share this post


Link to post
Share on other sites

I would think that a user who is developing LabView applications in an environment where internet access is restricted for, legitimate reasons, (I'm not at liberty to provide more details here) would not be placed at a disadvantage just because there is no internet connectivity. I could see if one's interest in "upgrading" to a "professional" edition would be to utilize and enjoy additional benefits that an upgrade to a product yields. That's fine. But requiring an upgrade just to be able to use the product in the same manner that community edition users already do in the "internet connected" world does not make for an even playing field. I have no need to develop custom VIP packages and configurations. NI already demonstrated to me that a ".vip" file is ALL I would need to solve my problem. Seems quite simple. And what would be the downside in posting a .vip file along with each VI package that is released and available to the open community? An internet-connected user installs a new package by method "A" and the non-connected user by method "B". Simple. Easy. Done. And, certainly more happy VIPM campers.

 

I'd like to see the VIPM development team rethink this policy and provide users in the predicament that I'm in with the ability to merely access a .vip file. I'm sure the development team could work something out here.

Thanks.

Ed

Share this post


Link to post
Share on other sites

That sourceforge link was perfect. I was able to down load, one by one, all of the OpenG toolkit package files and then copy them over to my private/secure PC. VI Package Manager was quickly able to load and install everything. However in the VIPM column labeled "Repository" it says "UNPUBLISHED" and within my LV block diagram on my controls palette under "Add Ons" it is blank. (When I tried installing the OpenG toolkit on a PC that was connected to the internet, that's where the OpenG functions icon appears.) So what needs to be done in order to activate or publish these packages now that they've been successfully installed on this private/secure PC? I think I'm close, almost got it fixed.

Thanks.

Ed

Share this post


Link to post
Share on other sites

The package files (*.vip, *.ogp files) are always available in your local VIPM database after they've been downloaded from the network repository. All you have to do is select your packages from your list, right-click, and select download. Not all packages are available through Sourceforge. You can locate them here and transfer them to another PC using any means you wish. Keep reading below for how to add packages to the VIPM library.

 

On XP: C:\Documents and Settings\All Users\Application Data\JKI\VIPM\cache

On Vista\7: C:\ProgramData\JKI\VIPM\cache

 

I'd like to make a distinction here between Packages (*.VIP, *.OGP files) and Package Configurations (*.VIPC files)

 

VIP files contain VIs, DLLs etc. and installation information for those files. VIPM installs the package and places these files into your LabVIEW palettes or anywhere else required. Packages contain the source code which your projects requires so it's not broken when you open it. This is what is downloaded from the network.

 

The VIPC file on the other hand, can be thought of as a container of packages. You can include the entire package file inside the VIPC file if you wish, or you can include only the name of the package. Including only the name allows the VIPC file to be smaller in size. If you only include the name then when VIPM tries to open the VIPC file it searches all known online repositories for the actual package.

 

The intent of VIPC files is to take a snapshot, if you will, of your current project development environment reuse library configuration. This can be used to restore your LabVIEW environment to the state required to begin work on your project. This is why it also includes the LabVIEW version info so it knows which LabVIEW version it needs to be applied to. A typical use-case would be to include a VIPC file with every project source you are working on. The first thing you do before working on a project is to apply the VIPC file. This would reconfigure your LabVIEW environment (installing and uninstalling packages) as required so that your project isn't broken. So VIPC files are really a project reuse library configuration.

 

Transferring packages to non-networked machines is actually a secondary benefit of using VIPC files. Since the VIPC file can be configured to contain the actual packages (not just the names). It's easy to just add the packages you want inside the VIPC file from within the VIPM user interface.

 

Differences during the installation process:

Packages:

- You can install packages from within VIPM by simply selecting one or more package names in the VIPM list and clicking the install button.

- If you have the physical package, you can select "File>Open Package Files" from within VIPM to select it. Selecting a single file will prompt you to install the package. Selecting more than one file will prompt you to either: 1) Install the package or 2) A choice between installing the package or just importing it to VIPM's library.

- You can also just double-click the file in file explorer.

 

Package Configurations:

- You can apply a VIPC file by selecting "File>Apply a VI Package Configuration" from the VIPM main menu.

- A somewhat hidden feature: You can add the contents of a VIPC file to VIPM (without installing the packages) by selecting "File>Open Package Files" and pointing VIPM to the VIPC file instead of a package. You will then be prompted for the option to add the contents to the VIPM library.

 

So, in defense of VIPC files, I would say that it provides a professional feature for managing your reuse libraries across diverse projects and LabVIEW environment configurations. We offer trial versions of VIPM Pro as needed. Just contact us via this form and request your copy.

 

Hopefully I've given you some options here for how you can transfer your packages to non-networked computers.

 

One final note. The community edition of VIPM can apply VIPC files, it just can't create them. This means you can have one copy of VIPM Pro for creating package configurations for your projects and the target machines can run the community edition to handle applying the configuration.

Share this post


Link to post
Share on other sites

That's great information. Thanks for taking the time to pass that along. However I still have the issue that the OpenG toolkit is still no where to be found on my functions palette and I see no menu choice anywhere to activate it. Installation reported "no erorrs" and all the pkg's are listed under repository as unpublished. Could you provide me with the method to activate all those OpenG toolkit packages now that installation was successful? Much appreciated.

Ed

Share this post


Link to post
Share on other sites
That's great information. Thanks for taking the time to pass that along. However I still have the issue that the OpenG toolkit is still no where to be found on my functions palette and I see no menu choice anywhere to activate it. Installation reported "no erorrs" and all the pkg's are listed under repository as unpublished. Could you provide me with the method to activate all those OpenG toolkit packages now that installation was successful? Much appreciated.

Ed

The packages show as unpublished because VIPM does not have a network connection to make the link between the package and which repository they came from. This is normal and is what would happen if you added a package to the VIPM library the way you did. In other words, VIPM thinks the package has not been published on any known repository. So I wouldn't worry about the unpublished state.

 

Not seeing the items in the palette is of concern. There is no "activation" step required. Just installing the packages should suffice. I'm not sure why this is happening other than for some reason the palette refresh step of the install process failed somehow. Have you tried restarting LabVIEW? Also, how many LabVIEW versions do you have installed on that machine and are you loading the right LabVIEW version? It's possible you installed the package on version 8.5 and you are loading 2009.

 

The OpenG palette shows up in the Add-ons palette but also sometimes shows up in the root palette as a category. Make sure all your categories are visible in the palette.

Share this post


Link to post
Share on other sites

I've re-opened LabView numerous times. I've also uninstalled and reinstalled the OpenG toolkit numerous times as well with the same unsuccessful results. It doesn't work. It's nowhere to be found on the functions palette. I am running LV 2009 but I do have other versions of LV installed on the machine as far back as 7. However on my public internet connected PC I also have numerous legacy versions of LabView installed and the OpenG toolkit installs and "activates" just fine there.

 

I noticed that I have a total of 16 oglib_ files listed in the "Name" column along with the OpenG toolkit (version 1.0.0.5) name appearing at the bottom of that list. In front of each entry there is a red exclamation point appearing (on top of a LV icon). I've clicked on "Install Missing Dependencies" and it tells me that there is nothing to do and that all the packages are installed. And when I do a "Get Info" on all the openG listings they all indicate 2009. Could it be that when I downloaded all the files piecemeal from the sourceforge site that I missed something? Any suggestions? It would be nice to be able to use these utilities through the VIPM.

Share this post


Link to post
Share on other sites
I've re-opened LabView numerous times. I've also uninstalled and reinstalled the OpenG toolkit numerous times as well with the same unsuccessful results. It doesn't work. It's nowhere to be found on the functions palette. I am running LV 2009 but I do have other versions of LV installed on the machine as far back as 7. However on my public internet connected PC I also have numerous legacy versions of LabView installed and the OpenG toolkit installs and "activates" just fine there.

 

I noticed that I have a total of 16 oglib_ files listed in the "Name" column along with the OpenG toolkit (version 1.0.0.5) name appearing at the bottom of that list. In front of each entry there is a red exclamation point appearing (on top of a LV icon). I've clicked on "Install Missing Dependencies" and it tells me that there is nothing to do and that all the packages are installed. And when I do a "Get Info" on all the openG listings they all indicate 2009. Could it be that when I downloaded all the files piecemeal from the sourceforge site that I missed something? Any suggestions? It would be nice to be able to use these utilities through the VIPM.

Hmm. I think I may have an idea of what's going on. What exactly are you installing? Can you list the package names? I think the OpenG toolkit package should not be there. I'm not sure how it got there. You can copy the package names to your clipboard by going to "Edit>Copy Package Names" from the VIPM menu.

 

Where did you get the OpenG Toolkit 1.0.0.5 package? I would uninstall this and then just install the other packages. Basically, if you need 16 packages then you should have downloaded 16 packages and imported them to VIPM.

Share this post


Link to post
Share on other sites

One more thing I forgot. Most OpenG packages have a dependency on ogrsc_dynamicpalette. This is probably why the packages have an exclamation mark on them. In VIPM, when you select "Install Missing Dependencies", VIPM tries but can't since those dependency packages are not on your system and it cannot connect on the network to get them. So if you install ogrsc_dynamicpalette along with your other packages then they should show up in the palette.

 

This is another reason why VIPC files are so convenient. When you add a package to the configuration, VIPM pulls-in any dependancies automatically as well.

Share this post


Link to post
Share on other sites

The necessity to install the package ogrsc_dynamicpalette was key in my case. HOWEVER, it appears that the copy of that particular package, ogrsc_dynamicpalette-0.9-1.ogp that I found on that Sourceforge.net link is NOT the latest version. When I installed 0.9-1 the ONLY version of LabView that it allowed me to select to install was "7.1" (which I still keep installed on my PC) So I looked on my public PC and found that the version of that package was 0.19-1 Subsequently when deleting the older version and installing the NEWER version on my secure PC it DID provide me with an option to install as "2009" and then other packages installed without a hitch with the appropriate icons appearing on the LV block diagram functions "Add Ons" palette. Who maintains that Sourceforge.net listing of the OpenG toolkit files? Does anyone check it to see that the latest versions of the files are posted correctly?

Copying over files one by one is cumbersome, but it works. (when done correctly and with up-to-date ogp files) (campers are happy again) Thanks.

Ed

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.