Jump to content


JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Ashish

  1. Please upgrade to VIPM 2013 and let us know what happens. Here is link: http://jki.net/vipm/download
  2. Kelvador, Can you try to run VIPM with "Run As Administrator"? See this article: http://support.jki.net/entries/21430776-VIPM-fails-to-launch-after-splash-screen-on-Windows
  3. ThiCop, Please send an email at support@jki.net to try additional debug support.
  4. markus4, Sorry for the delay in getting back to you. What version of VIPM are you trying to install? Here is link to download the latest and greatest VIPM for Linux: http://jki.net/vipm/download Here is link to download the appropriate LabVIEW Run Time Engine: http://support.jki.net/entries/20959253-LabVIEW-RunTime-Engine-for-VIPM For any issues refer to this article: http://support.jki.net/entries/21414632-Issue-with-Installing-VIPM-on-Linux Let me know how it goes.
  5. What is your computer configuration? Also, are you upgrading VIPM or installing for the first time?
  6. lverdier, Please contact National Instruments to get the correct LabVIEW Run Time Engine for your system.
  7. Yes. Please install labview2009SP1runtime_linux.zip.
  8. lverdier, Here is link to get the correct LabVIEW Run Time engine for VIPM. http://support.jki.net/entries/20959253-LabVIEW-RunTime-Engine-for-VIPM You will need to install the appropriate run time engine even if the newer run time engine is present.
  9. Tad, Can you verify with NI that it supports Scientific Linux?
  10. Tad, Can you verify if the LabVIEW 2009 Run Time Engine is installed properly?
  11. Arne, This article might be helpful: http://support.jki.net/entries/21414632-Issue-with-Installing-VIPM-on-Linux
  12. Arne, Here is link to get the correct Run Time Engine: http://support.jki.net/entries/20959253-LabVIEW-RunTime-Engine-for-VIPM
  13. manigreatus, I was not able to reproduce the behavior described by you. I had configured "Toolkit VIs" to "user.lib" folder: http://screencast.com/t/qxxzDvyIDeQu And, configured the "Source File Settings" to "Toolkit VIs": http://screencast.com/t/PnYerfikGIX If possible, please share the package source that can demonstrate the behavior.
  14. manigreatus, What OS and version of VIPM and LabVIEW are you using? Also, did you set the "Destination" under "Source File Settings" section of VI Package Builder? http://screencast.com/t/dgNCwfCcq4 For dedicated support, contact us at support@jki.net
  15. Nathan, The "jki_lib_easyxml v2.0-1" is actually the evaluation version.
  16. Nathan, I will recommend you to try the EasyXML evaluation version available through VIPM.
  17. Ok. But, are rest of the components installed in the palettes at least? If possible, you can send us the source folder (send email to support@jki.net) to get dedicated support.
  18. Sara, Have you referred to VIPM documentation: http://jkisoft.com/vipm/docs/2012/index.html?turl=editingthepalettes1.htm Here is an article: http://support.jki.net/entries/20674078-editing-the-functions-palette
  19. You will need VIPM API: http://support.jki.net/entries/21395113-VIPM-API
  20. You can programmatically change label for the specific components in the cluster: http://screencast.com/t/CwhtfNmG0
  21. Joachim, I am afraid that you will have to handle this by maintaining clusters for each driver and then using the appropriate cluster at run time.
  22. Balaji, Thanks for the suggestion on having a TortoiseSVN Toolkit API to be able to perform repository operations programmatically. We'll consider it but cannot assure you on when will it be available.
  23. Now....when I read your post carefully, I realized that you are asking for TortoiseSVN API in order to execute the commands programmatically. I am afraid that we do not have that yet. But, I will check with our TSVN Toolkit team for accurate response and get back to you.
  24. Balaji, Here is link to the TortoiseSCN Toolkit documentation: http://jki.net/tortoisesvn-tool/docs
  25. Uninstall existing VIPM. To do this you will have to uninstall VIPM using the VIPM uninstall and then delete the following folders manually: C:\ProgramData\JKI\VIPM C:\Program Files (x86)\JKI\VI Package Manager Then re-download VIPM (http://jki.net/vipm/download) and install it. Try the toolkit upgrade again.
  • Create New...

Important Information

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