Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. JVA

    JVA

    Hello, I have tried multiple times to sign up for a JKI account but have not received any confirmation email after waiting for half an hour now. I verified I have not received it in my spam/junk folders and that the email is typed correctly. Any idea on why I am not seeing any email? UPDATE: using a personal gmail account worked.
  3. I can only seem to find version 20.0 via NIPM. Is there a special feed or something for 20.1?
  4. Last week
  5. I am trying to install the cRIO-PB-MS by KUNBUS GmbH package from NI's website. I cannot install VIPM on my internet facing machine therefore I must use the FTP option to download the package. However, the version of package downloaded via FTP is outdated and appears incomplete. The FTP package is 3.0.0.1 and should include the Kunbus configurator program (this package lists version 3.0.6.1). However, when I open the package on a computer that has VIPM, I get an error message that the configurator package file is missing and cannot be installed. I contacted NI support and they couldn't help but they were able to install the package via the VIPM download and the package version was 4.0.1.2 and configurator program in that download is version 3.1.3.1. Any help would be appreciated. Thanks.
  6. This is a minor annoyance, but one I wish would go away if it is easy to change. Because I change my monitor resolutions regularly, I frequently end up with windows that are only partially on screen. When VIPM ends up in that state hanging off the right edge of my screen, I cannot move it back on screen because there's no visible area that I can click on to drag the window. Right now, I have to resize the window wider, enough to get to the far right of the buttons, move the window, then size it back down. Suppose the rectangle shown in red is the only visible region of the window. I would like it if the blue box on the left of the button bar was not part of any button so I could click there to move the window. It can still be white -- no need to color it -- just make it not a left-click hit region. Thanks!
  7. 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.
  8. Hi There. I think you may need to also (separately) publish the system package to the repository, too, in order for it to be correctly downloaded/found by repository clients. Please try that, and let me know if that resolves the issues for the clients.
  9. 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).
  10. Earlier
  11. Hi @Jim Kring I was able to solve the problem by re-installing LabVIEW with NI package manager, It's not an efficient solution but it worked for me.
  12. Hi JKI Team, I'm facing an issue building a package since I've changed the dependent package's destination path. For the record, this impacts Antidoc open source project Let me explain. Antidoc package (called A) relies on the Asciidoc Toolkit package (called B). Library of B was formerly installed in ../B/Sources/B.lvlib. I modified the vipb to have the library installed in ../B/B.lvlib I made the same modification for A. As it worked fine for B, I now have an error for A. VIPM is expecting to find some VIs in ../B/Sources folder that not exists anymore. I checked that A code didn't keep any older links, but I still have the error. The only workaround I found to be able to build the package is to duplicate the content of the B folder in a ../B/Sources folder. This way, A code finds its dependency, and VIPM doesn't throw an error. Installing B (no duplicated Sources folder) and A works fine. I can't see where I did something wrong in the process. Did someone already come across this error? Any idea to fix that and avoid it in the future? Thanks in advance for any idea or help. Feel free to clone the Antidoc repository to reproduce the issue.
  13. Hi @Jim Kring, any updates on my issue ? Thanks in advance.
  14. Our build server fell over last Friday. Nobody noticed, this morning I am greeted with this: This is how it started: =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 05:29:08 PM = Automated Message Start = Error 2 occurred at Obtain Queue in JKI_LVConfig__jki_lib_configuration_file.lvlib:1188A4A91C005F423D89358A8C95F362->4F9D0428213F8F95FE3 A745133E46203->FF473C6B63ADACAEF90D52E8AFBDC45F->246E5055266A40F567071DB843B25FE8->1C008B1C8A190D0D7 176E93799F7534B->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001->5AB213F9CD1875C24859DB C20A7CDE64->VIPB_API.BuildAndPackageLibrary.vi->VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58->41AC743D0ED402FF42A432FD77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = User Defined Message Start = VI Package Builder Error = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0-> VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58-> VIPB_API.BuildAndPackageLibrary.vi-> 5AB213F9CD1875C24859DBC20A7CDE64-> VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 05:29:10 PM = Automated Message Start = Error 2 occurred at Obtain Queue in JKI_LVConfig__jki_lib_configuration_file.lvlib:1188A4A91C005F423D89358A8C95F362->4F9D0428213F8F95FE3 A745133E46203->FF473C6B63ADACAEF90D52E8AFBDC45F->246E5055266A40F567071DB843B25FE8->1C008B1C8A190D0D7 176E93799F7534B->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001->5AB213F9CD1875C24859DB C20A7CDE64->VIPB_API.BuildAndPackageLibrary.vi->VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58->41AC743D0ED402FF42A432FD77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== And after that it's just this: =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Monday August 03, 2020 at 09:13:31 AM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== and continuing to fill. Task Manager tells me there are still 2GB of memory available
  15. Hi @Rami_Saaidi, We've had another user report a similar issue recently. Have you tried re-running the installer after the error, to see if it works the second time? Also, I think one user said they resolved the issue by installing .NET 4.0 before running the VIPM installer. -Jim
  16. I tried to install VIPM 2020.1 but the following error occured. How can I fix it?
  17. This is not the case in LV19
  18. @Ruslan. Thanks for reporting this. Do you know if this also happens in newer versions of LabVIEW, too (e.g. LV 2020)?
  19. Hello. When using the "Text Only" control in the task manager, the processor load increases dramatically (up to 20% in my case). This is not the case with the other buttons.
  20. I see. Could you change your individual packages (that require none of their VIs are in memory) to require that LabVIEW be closed before installing?
  21. Hi @Jim Kring. We need to check whether the VIs in VIPC are in LV memory / running before applying VIPC
  22. Hi @ranjgith. No, there's no such feature for VI Package Configuration files. Packages, themselves, have such features but not VIPC files. Can you explain a little bit about what you need to accomplish? What's your use case? -Jim
  23. Is there any way by which we can perform some operation before / after installing a VI Package configuration? Or is there a way to restrict the installation of a VIPC file based on few conditions? Or is there a way to restart LV before / after applying VIPC?
  24. I found a method that works by using Darren's quick drop shortcut method. https://forums.ni.com/t5/Quick-Drop-Enthusiasts/Quick-Drop-Keyboard-Shortcut-Create-Place-VI-Contents-VI/gpm-p/3520372?profile.language=en I just put the JKI down in a new VI and edited it as I would normally for every new SM and then saved it as a quick drop.
  25. I noticed that whenever I drop down a JKI state machine I always have a routine set of states that I add for every single SM. Is there a way to premake this template with these additions so I don't have to spend time doing these steps for every SM?
  26. I had tested it in the Community version of VIPM and that works very well. But now I notice that it doesn't work in the Free version. It gives a dialog that says "This feature of the VIPM API does not function with the Free version of VIPM." Is this intended or a bug? Because I would expect that a shell menu just works no mather which version I installed (or that it wouldn't be available if I can't use it). In VIPM 2019 I could "Add Contents to VIPM Library" for a vipc file in the free version but in 2020.1 this also gives this pop-up. So it looks like there is no way to add a package to the library without installing it in the free version anymore. I like to have (all) packages added to the library and then apply a small vipc to switch between different projects.
  27. Hi @wolfkil. Thanks for letting us know it worked for you. We're trying hard to keep things working well. Please let us know if you have any more issues.
  1. Load more activity
×
×
  • Create New...

Important Information

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