Jump to content

Recommended Posts

We develop a number of test systems for use in China at our production facility and when we ship it for whichever engineer is on site at the time to debug. Now because the PXI racks that are used may well have been bought in China we can not guarantee that the PXI rack will all the required software and drivers so we make sure that any software or drivers are included in the package we send as as access to the internet can be tricky or just so slow as to be unusable.

The question is that we a number of components that we install from the VIPM but that is not allays possible via the internet in China, is there a way to download the installer files and then use them locally on the PXI rack on site.

My thanks in advance.

Link to post
Share on other sites

We develop a number of test systems for use in China at our production facility and when we ship it for whichever engineer is on site at the time to debug. Now because the PXI racks that are used may well have been bought in China we can not guarantee that the PXI rack will all the required software and drivers so we make sure that any software or drivers are included in the package we send as as access to the internet can be tricky or just so slow as to be unusable.

The question is that we a number of components that we install from the VIPM but that is not allays possible via the internet in China, is there a way to download the installer files and then use them locally on the PXI rack on site.

My thanks in advance.

Yes, it is easy to download a package e.g. from LAVA-CR from one PC, e.g. USB it, then install it on another PC.

If you want to get access to packages on VIPN or LVTN then you need to download in VIPM, then go to the cache (under e.g. ProgramData\JKI\VIPM or something) and copy them out.

Link to post
Share on other sites

Conversely, you can build a VIPC for your project using one of the pay-to-play versions of VIPM. It lets you scan a project and make a list of all of the necessary packages, with the option to actually include them in the VIPC.

  • Like 1
Link to post
Share on other sites

Conversely, you can build a VIPC for your project using one of the pay-to-play versions of VIPM. It lets you scan a project and make a list of all of the necessary packages, with the option to actually include them in the VIPC.

This option also gives you the ability to keep track of the reus components' wrt versions of your system - you build a new vipc for each version you make, and are able to roll-forward and roll-back easily.

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.

  • Similar Content

    • By javier_r
      VIPM.io now allows you to post LabVIEW Resources, Ideas, and Tools. For example, you could post a link to a video tutorial or blog article about a package. You can also post ideas, like feature requests or new tools. Best of all, package developers are notified when you post your ideas and resources, and you can comment and discuss posts with the community. Take a look at this video to learn more: https://www.vipm.io/posts/664960df-f111-4e13-989a-24be8207182d/

    • By javier_r
      Hello everybody!
      Wondering how many people have tried the new vipm.io site. We have added a ton of features to make it easy to Discover LabVIEW Tools and there are some cool ones coming soon.
      Check it out and let me know what you think 😀
       
      Javier

    • By dblk22vball
      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).

       


    • By ThomasGutzler
      Hi,
      Over night something changed on my windows 10 build server and I can now no longer open VIPM. It just shows the splash screen and then closes again.
      Here's the log file:
      =========== START of VIPM 2018.0.0 (build 2025) Error Message ===========
      An internal VIPM 2018.0.0 (build 2025) Error has occured on: Tuesday August 20, 2019 at 03:19:48 PM
      = Automated Message Start = 
      Error 8 occurred at Open/Create/Replace File in NI_LVConfig.lvlib:Parse Config to 
      Queue.vi->NI_LVConfig.lvlib:Load.vi->NI_LVConfig.lvlib:Open Config Data 
      (compatibility).vi->DDEFA056211BA4DA4D215C322E067D90->621BFCD461979D3C7127139A69154E03->762BBE85A007
      171D5A65B48289D23361->46803A2448FAC5F85BFF8F5C199E9C6F->OGPM 
      Class.lvlib:7D7C5CD8C5D361C01081DF5613237E15->OGPM 
      Class.lvlib:D69AB3997B80ACD75689430E3922612C->OGPM Class.lvlib:OGPM Init.vi->VIPM Splash.vi
      Possible reason(s):
      LabVIEW:  File permission error. You do not have the correct permissions for the file.
      =========================
      DMA hardware error detected.
      C:\ProgramData\JKI\VIPM\cache\ngene_lib_deepltk_fpga_addon-1.0.0.45.spec
      = Automated Message End =
      = User Defined Message Start = 
          Error(s) Generated in Splash Window
      = User Defined Message End =
      = Error Handler Call Chain Start =
          VIPM Splash.vi
      = Error Handler Call Chain End =
      =========== END of VIPM 2018.0.0 (build 2025) Error Message ===========
      Any idea where the files are that it doesn't have the right permissions for?
    • By JKSH
      This is an offshoot of https://lavag.org/topic/19414-can-i-save-as-a-vipb-file-in-vipm-and-keep-the-old-palette-if-i-change-the-source-directory/. That thread discusses hand-modifying the XML data in a *.vipb file, which Jim Kring himself seems to accept as a viable solution in some cases. However, when I try that, VIPM says, "VI Package Builder was unable to open the build spec due to an error."
      I initially thought this was new behaviour introduced in VIPM 2016, but downgrading to VIPM 2014 SP2 didn't change anything. I'm now unable to downgrade any further, as my PC is convinced that 2014 SP2 is still installed (even though it's not...)
      Could someone kindly try the attached *.vipb file and see if it opens? It's a bare minimum default file, with only a description summary added. I've hand-modified the summary from "Lorem ipsum" to "Larem ipsum" and now VIPM refuses to open it.
      Thanks!
       
      Dummy.vipb
×
×
  • Create New...

Important Information

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