Jump to content

Ashish

JKI Team
  • Content Count

    292
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Ashish

  1. 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.
  2. Balaji, Here is link to the TortoiseSCN Toolkit documentation: http://jki.net/tortoisesvn-tool/docs
  3. 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.
  4. AnandkumarSP, You will have to rebuild the package with updated display information.
  5. Hi, You will have to contact National Instruments for any support related to NI products. (www.ni.com). This discussion forum is for JKI Products (http://jki.net/products). But, if you are trying to install LabVIEW Run Time Engine for VIPM: - Link for getting correct LabVIEW Run Time Engine: http://support.jki.net/entries/20959253-LabVIEW-RunTime-Engine-for-VIPM - VIPM installation error on Mac: http://support.jki.net/entries/21234937-VIPM-installation-error-on-Mac-OSX-10-7-
  6. Anooj, Thanks for the updates and glad to know that VIPM is up and running on your machine. I will pass on this information to VIPM group for investigation.
  7. Tejas, Can you refer to this article? It is similar to what you have done but there are some instructions for setting Firewall. http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW Also, did you verify if the TCP/IP ports in LabVIEW match with those in VIPM config?
  8. Austin, This is possible. Please refer this NI site which gives all the info about licensing and trial creation. https://decibel.ni.com/content/groups/third-party-licensing-and-activation-toolkit
  9. We have recorded this bug as Case 13976 for consideration in next release of VIPM.
  10. seanj, The problem might be related to VIPM getting access to the internet. Have you tried to install any other package? Here is an article to resolve network configuration issues: http://support.jki.net/entries/20589198-solving-vipm-network-connection-issues If you need any further assistance, please contact us at: http://jki.net/contact
  11. I think that the "IMAQdx Ref" component in the cluster is causing error. But, to get more accurate help on OpenG, I will recommend you to use this forum on LAVA: http://lavag.org/forum/45-openg/ The JKI Discussion Forum is dedicated for support related to JKI Products: http://jki.net/products
  12. Another VIPM user has experienced that installting .NET Framework 4.0 solved the problem with VIPM crashing. (http://forums.jki.net/topic/2065-crash-on-startup/page__view__findpost__p__5078) Here is link to download .NET Framework 4.0: http://www.microsoft.com/en-us/download/details.aspx?id=17851 Let me know if that helps anyone.
  13. Steve, Thanks for the information. It will help in our investigation.
  14. flarn2006, What is your OS and other PC parameters? Was VIPM ever working for you before? Please provide some screenshots if possible.
  15. qbits, Glad to know that you are good to go. Also, thanks for the information. It will help us debug the issue.
  16. RocketHacker, We have recorded your observation as Case 13874 for consideration in our next release of VIPM.
  17. qbits, I am unable to recreate the behavior on my 64 bit Windows 7 virtual machine. I have LabVIEW 2012 (32 and 64 bit) and installed VIPM 2012.0.1 (build 1818). It launches successfully. Here is the screenshot: http://screencast.com/t/gCODbPuHBA VIPM launched successfully from no-admin account as well. While I am still investigating, let me know if you find anything that I can try.
  18. qbits, Thanks for your observations. We will try to reproduce it and let you know.
  19. One of the VIPM users got this problem fixed by reinstalling NI Device Drivers for LabVIEW 2012. If possible, please try that out and let us know if it helps you as well.
  20. Here is an article that is made for Mac users but is valid for anu other OS platform as well: http://support.jki.net/entries/21888011-connecting-vipm-mac-to-labview
  21. Nina, Better place for such questions is http://lavag.org/
  22. Becky, Using VIPM 2012.0.1 (build 1818), I was not able to recreate the behavior described by you. Here is how I tested it: 1. Build package. Do not publish. 2. Install the package 3. Update and build package. Publish the package. 4. Refresh repository to check for new packages. This shows that the new version of the installed package (in step 2) is available 5. Install the upgrade Any more details to recreate the behavior will be helpful.
  23. Bjarne, This capability is not yet available in VIPM.
  24. We have recorded this issue as Case 13848 for consideration in future release of VIPM. Thank you.
×
×
  • Create New...

Important Information

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