Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Same issue. Would love to know when to expect the update. Need to know if I should revert the machine's back to an old version instead of waiting. Thanks, Nick
  3. Last week
  4. Hi @Paul Torek. We did have some issues with VIPM 2020. There should be fixed/improved in 2020.1. You can get the latest release candidate and help us test in the VIPM 2020 beta forum. Sign up here to get access to that forum.
  5. Hi @drjdpowell, @jb1592, Sorry for the issues. We're working hard on VIPM 2020.1 and hopefully this issue will be resolved. It's odd that the package builder window opens, yet the VIPM main window and the system tray icon aren't showing. I've heard a few other reports of similar behavior and we've got it on our radar. I don't think it's related to the "Error 42 occurred at (http response "404". URL Requested)" -- I think that was an issue with a missing file on NI's LVTN package repository. Regards, -Jim
  6. Hi @Vollinger. The issue is that LabVIEW addresses items in the palette by their display name. So, if two items have the name "Connect.vi" then LabVIEW will show the first one it finds, even if it's for a different toolkit. The solution/work-around is to change the palette display name of your "Connect.vi" to something like "Connect (MyComponent)". Here's where you would change that name in the palettes, via the palette editor. Does that work for you?
  7. HI @JMA_1. We made some major installer improvements in VIPM 2020.1. We have a release candidate available for download in our beta testers forum -- sign-up here to access that forum. Thanks and hope we can get you working quickly!
  8. Hi @kosist and @wolfkil. We're working hard on a VIPM 2020.1 build. There are lots of improvements, one of which is that it does not use a sign-in to download packages from the VIPM Community Repository. You can get the latest release candidate and help us test in the VIPM 2020 beta forum. Sign up here to get access to that forum. We're working hard to make VIPM work well with new versions of LabVIEW. This latest 2020 release was difficult to full test, due to COVID-19 during the beta and launch, and a reduced number of beta testers. We're hoping VIPM 2020.1 addresses the issues people are facing, and works great for people. Thanks for your help in testing, if you're able. -Jim
  9. Thanks for letting us know, James! Yes, 2020 had a lot of work put into it and the beta/launch was in the middle of COVID-19, so things didn't get as many eyes as usual. We do have a version 2020.1 in beta right now (if you can't access this, please be sure you sign up for the beta and/or send me a PM).
  10. A recent conversation on LAVA: https://lavag.org/topic/21631-anybody-having-problems-with-vipm-2020-and-how-can-i-get-vipm-2019/?tab=comments#comment-132642 Suggest multiple LabVIEW developers are unhappy with the 2020 version of VIPM. I think you have been a bit aggressive in the number of changes, and you need to quickly get on top of some of the issues. You need a 2020.1 version soon.
  11. Hello? Any ideas or suggestions? Thank you. J -
  12. For reference, here is a support article: https://support.vipm.io/hc/en-us/articles/214135663-VIPM-fails-to-launch-after-splash-screen-on-Windows
  13. Solved by running as administrator.
  14. Earlier
  15. Hello Jim, I was looking for the Open Package File function (see attached). I think the right click on the package and add to library is what I am looking for. I was not aware of that feature. Thanks
  16. Hi Dan, Glad you're exploring VIPM 2020. What do you mean by "load packages"? Are you saying that you'd like to add them to VIPM's package list? You can double-click the package and open it in VIPM to install it. Also, in VIPM 2020.1 (currently in beta) we've added an "Add to Library" right-click option on Packages in Windows File Explorer. Does that answer your question? -Jim
  17. My problem persists... apparently I do not have necessary permissions for some Splash VI file?? Here is the text file from C:\ProgramData\JKI\VIPM\error June-29-2020.txt
  18. I'm having a similar problem (VIPM 2020) as the opening post of this thread. Since the solution of re-installing LV Runtime Engine worked for some people, I'm trying that (LVRTE 2019SP1) now. If I don't reply again, that probably means it worked.
  19. A little more info I found when playing around: I located .mnu file responsible for my palette in LabVIEW directory and deleted it. Now, as expected, show in palettes does not work. Also, my palette disappeared from LabVIEW funtions palette. When I restore .mnu file, palette is available once more, however, show in palettes displays Agilent 34401 palette after clicking again.
  20. Hi, I am having an issue with functions palette I generate in VIPM. The palette is generated and behaves correctly in LabVIEW, however, when I click "show in palettes" in VIPM after installing toolkit, instead of my functions palette, Agilent 34401 palette is displayed. Any idea what might be wrong?
  21. I've seen similar happening on two different PCs as well. Restarting fixed it on one; had to reinstall on another. Currently on this one it opens, but will automatically close itself after a maybe 20 or 30 seconds. I'm not sure what's causing all of this, but this is all I have in C:\ProgramData\JKI\VIPM\error. =========== START of VIPM 2020.0.0 (build 2302) Error Message =========== An internal VIPM 2020.0.0 (build 2302) Error has occured on: Sunday June 28, 2020 at 05:22:19 PM = Automated Message Start = Error 42 occurred at (http response "404". URL Requested: http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/austin_consultants_lib_finance_ohlc_plot/aus tin_consultants_lib_finance_ohlc_plot-1.1.0.14.spec) 85294761631CBC58471969C9E99FB95F:2980001 in 34ECF0FD9B9E81860D3E52C65FD0A442->15A1868D1CB3D6176D9B44B0ED323314->C898E814D7E422D8CA4487CB97FA7465 ->OGPM Class.lvlib:0A647C51DBC1AD7225F71A08D470BB08->OGPM Class.lvlib:4CD02F4728B5353B72E37139092E0B05->E1F6385E95370507176402E569A529D7->VIPM Main Window.vi . URL: "http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/austin_consultants_lib_finance_ohlc_plot/au stin_consultants_lib_finance_ohlc_plot-1.1.0.14.spec". Possible reason(s): LabVIEW: (Hex 0x2A) Generic error. = Automated Message End = = User Defined Message Start = Error downloading package info = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> E1F6385E95370507176402E569A529D7-> OGPM Class.lvlib:4CD02F4728B5353B72E37139092E0B05-> OGPM Class.lvlib:0A647C51DBC1AD7225F71A08D470BB08 = Error Handler Call Chain End = =========== END of VIPM 2020.0.0 (build 2302) Error Message ===========
  22. Hello, I was playing around with vipm 2020. I couldn't figure out how to load packages I created in previous versions of vipm and packages I downloaded. How do you load packages from your hard drive? Thanks
  23. Glad you figured it out, @Justin Thomas, and it was just an email issue. Hope Design Palette is working well for you.
  24. Similar issue, im not able to activate this via email. I send out the email request and never receive an Activation code. Is there an alternate method of activation available? Fixed now, looks like my account was not setup to receive emails from JKI
  25. Hello! Is there a way to give the VI Package Builder a relative path for the "Build Output Directory" and the "Source Directory" (in Build Information)? I try to build a package by calling a LabView executable that is using the VIMP API. I need to set a relative paths because the project is checked out from Gitlab into a temporary folder that will be deleted after the build process finished. I tried all kinds of path formats but can't make it work and always get the following error message: There was a problem building Test_Project. Error Details: Code: 1430 Source: Ordner erstellen in VIPM Create Dir if Non-Existant.vi->12585F9C94A7D59D3E260C29C9C1E906->161DA2F058D709ED4354707005A11FC0->31D8663ACFF1819471D28090923FC176->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610005->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi.ACBRProxyCaller.B8C000B4<APPEND> builds Maybe there is a way so set the new path after the checkout but I can't see a way to do it.
  26. 4.2.0b1 is a beta that was put on lavag.org, it has support for Linux RT targets that the previous one did not, unfortunately there is no official release with that functionality yet.The package had a slightly different name as well, which confuses VIPM a bit when trying to uninstall. See the discussion here: https://lavag.org/topic/21142-openg-zip-42/page/2/
  27. VIPM 2020 running in task manager, but main window does not appear, nor is VIPM icon in windows tray (Windows 7 on a Parallels virtual machine on a MacBook). Can open build specs and get that window, but cannot install packages. Attached is image of Build Spec window , but no main window.
  1. Load more activity
×
×
  • Create New...

Important Information

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