Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Hi, Paul. Yes, VI Package Configuration is the way to go!
  3. Is there a way to install all the packages into Labview 2018 that I already had in LV2017 (short of shift-clicking all the OpenG VI packages, then ctrl-clicking all the MGI packages and my favorite other goodies)? If it's part of VI Package Configurations, I might just upgrade.
  4. Last week
  5. Haha I initially had the same thought. I tried the command line thinking that I could avoid buying the pro edition.
  6. The real answer is I'm just making a single package for a project on my development machine. I have a 1-click build for executables and test-stand deployment so I can press run and walk away, but without a separate build computer there isn't really a significant enough need to buy the API -- it saves a few clicks. However, that does look to be the difference, either pro edition was always required or it is now, but when I turned on evaluation mode it worked.
  7. Earlier
  8. Jim Kring

    2013.0.1 Download

    Hi There. Please email support@jki.net and we'll point you in the right direction.
  9. It works for me with 2017 on windows. Out of curiosity, why do you want to use the direct command line? I find the direct command line call more of a burden to use. When called from batch it is none blocking by default. On completion of the build VI Package Manager remains open. Consider creating a simple VI and use the VIPM API. See attached picture. Call the VI from command line. It's blocking and will clean up all processes after itself.
  10. Where can I find a download link for VIPM 2013.0.1 for windows? I am using VIPM2013 in my CI system and I am running into a bug fixed in version 2013.0.1. According to the 2013.0.1 release notes it looks like I'm running into " Case 14540". The jki site only provides a link to the latest version. I tried being resourceful. I searched old LabVIEW CD's. I tried a ftp site I found hosted by NI. I have found a large number of installers but none which are 2013.0.1.
  11. Smoothtaker

    VIPM 2017 crash startup

    The problem isn't solved yet. Are there any suggestions?
  12. I stumbled across this post from a few years back: https://forums.jki.net/topic/2466-is-there-a-way-to-create-a-vi-package-in-vipm-using-command-line/ I've confirmed I have the format right and can at least open a specific package using the command line ("/command:vipm_open_build"), but the "build" command does nothing.. Is there still a command line build feature for VIPM 2017? Thanks
  13. @Nik and @Parth I would like you to install VIPM with administrator permissions as mentioned in this article: https://support.jki.net/hc/en-us/articles/214135583-VIPM-installation-error-on-Mac-OSX-10-7- Although the article is not related to this specific issue, it explains how to set permissions during VIPM installation. Let me know how it goes.
  14. Not totally sure what the issue is. Have you tried running both VIPM and LabVIEW as the root user? Also, might be because LabVIEW is running in Evaluation mode. Linux is a bit tricky, since it's so configurable and quirky...
  15. Jim Kring

    JKI SM conversion to LVNXG

    Thanks for the update @wyzromek. Yes, there's still a lot to do -- NXG 2.1 still isn't totally ready for upgrading existing projects and there is still a little work to do on the JKI SM side of things, too. We're hoping that NXG 3.0 will provide a bit more features and improvements to the process 🙂
  16. hoffiz

    VIPM 2017 crash startup

    I have the same issue. Clean Windows 10 Pro on Virtual Box with only LabVIEW 2016 32 bits installed. I tried all the suggestions without luck.
  17. Hi. I'm having the same issue. I have also tried both the the links. But it doesn't seem to work. Please let me know how to connect VIPM to my current Labview
  18. Hi there Just installed LabviewEvaluation 17.0f1 64-bit. Want to try Linx to run Labview on Arduino. Downloaded JKI VI Package Manager and now I try to "configure LabVIEW Versions". I have already followed https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9YmSAK and https://support.jki.net/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW which both didn't helped to solve this Problem. See my attachments. So what is the solution? How do I connect the VI Manager with my current LabVIEW? Best regards Nik
  19. Walter, If ain't broken, don't fix it. :) But if you face the problem in future, try adding machine name and ip address.
  20. wyzromek

    JKI SM conversion to LVNXG

    Sorry for my late answer, I am very bussy at work. Yes, I've tried. There a many placeholders. For examples: So, a lot of work to do. But OK. New technology (LV NXG), new philosophy, new tools... It is better to start the new project directly in NXG. But another problem in NXG 2.1. I have instaled JKI SM 2.0 and there is an option to start the new project with JKI SM. But... if I need to add JKI SM to new, empty VI I'm not able to do it. In new JKI SM project, there is also a lack of Close Reference in "Data: Cleanup" state. I am sorry for so many questions and comments, but I often use JKI SM and recommend it to my students as the next step with programming in LabVIEW (something more then a simple state machine). Regards
  21. I had followed those steps prior and didn't notice a difference, but i Just checked and seems to be working. (I did do a full uninstall and install of LabVIEEEW and all components just to make sure on some other issues I was having I just have: * 127.0.0.1 localhost Do you think I should add my ip address and machine name just in case?
  22. Please refer this article and let us know if it helps: https://support.jki.net/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  23. Ashish

    Error JKIUpdadeTask.job

    Johan, It sounds like some permissions issue. Try reinstalling VIPM with "Run As Administrator" settings that you get by RightMouseClick or Shift+RightMouseClick while launching VIPM Installer.
  24. Smoothtaker

    VIPM 2017 crash startup

    I've just tried that, no result. Here is the error code after the reinstallation. =========== START of VIPM 2017.0.0 (build 2014) Error Message =========== An internal VIPM 2017.0.0 (build 2014) Error has occured on: maandag april 16, 2018 at 09:17:47 = Automated Message Start = Error 19 occurred at [LabVIEW]:skip mass compile after install Read Key (Boolean).vi Possible reason(s): LabVIEW: Configuration type invalid. = Automated Message End = = User Defined Message Start = C:\Program Files (x86)\JKI\VI Package Manager\VI Package Manager.exe\OGPM Set Target.vi = User Defined Message End = = Error Handler Call Chain Start = VIPM Splash.vi = Error Handler Call Chain End = =========== END of VIPM 2017.0.0 (build 2014) Error Message =========== =========== START of VIPM 2017.0.0 (build 2014) Error Message =========== An internal VIPM 2017.0.0 (build 2014) Error has occured on: maandag april 16, 2018 at 09:17:47 = Automated Message Start = Error 19 occurred at [LabVIEW]:skip mass compile after install Read Key (Boolean).vi Possible reason(s): LabVIEW: Configuration type invalid. = 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 2017.0.0 (build 2014) Error Message ===========
  25. Hi. I can not install the VI PM correctly, I get this error: JKIUpdadeTask.job Does anyone know how to solve it?
  26. need some help figuring out why I cannot connect to the VI Package Network or Labview TOols network (I am getting an error on refresh) also, i can search for a program, and when i install it, Labview launches, but then nothing happensl; no software installed... any guidance, thoughts? i verified my VI Server settings and my Labview settings. - no proxy, network timeout 60 (also tried 60000) -VIPM Labview 2017 Port - 3365 -LabVIEW 2017 VI Server Port - 3365 -LabVIEW 2017 VI Server ; Machine Access (127.0.0.1, localhost, *) Any thoughts?
  27. Ashish

    VIPM 2017 crash startup

    Thanks for providing the error message. It appears to be a permissions issue. I will suggest to uninstall VIPM and Reinstall. But, this time while reinstalling, I want you to RightMouseClick or Shift+RightMouseClick on VIPM Installer and select "Run As Administrator" option. Let me know how it goes.
  28. Hi @Jim C I split this discussion into a separate discussion thread. I like you're idea about the JKI State Machine Follower. I've been collecting some ideas about possible run-time and debugging tools: https://github.com/JKISoftware/JKI-State-Machine-Editor/wiki/Roadmap#run-time-tools Here are a few ideas: State logging - Show which states executed in which order Data logging - Show what data was changed between execution of frames Single stepping - Execute one frame at a time and pause between execution Breakpoints on individual states - Pause when a state is executed, so that highlight execution can then be enabled (and maybe we could turn execution highlighting ON, but I'm not sure how to do that programmatically) These tools would probably require temporarily swapping the Parse State Queue function in the user's instance of a JKI State Machine with a special one that has debugging features under the hood (there could be a debugging and non-debugging version of Parse State Queue that we could script in/out of the VI to enable/disable the debugging features). Anyhow, I wanted to let you know that this is a direction we're looking into, in case you have any ideas you've already been thinking about or working on :-) Thanks,
  1. Load more activity
×

Important Information

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