Jump to content


JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Ashish

  1. Based on a workaround described on another thread by user named "Trigger" we have generated a knowledge base article that should solve the problem related to file permissions while installing VIPM on OSX 10.7. Here is the link: http://support.jki.net/entries/21234937-vipm-installation-error-on-osx-10-7 Your feedback on the article will be appreciated. Thank you.
  2. TobyD, Thanks for documenting your workaround to fix the problem.
  3. Osvaldo, Thanks for documenting your observations. I was able to recreate the issue and have filed it under Case 13224 for consideration by our VIPM Group. We will keep you posted about the resolution on this issue.
  4. Chuck, The feature is not yet available in the EasyXML Tool. Attached is a VI (LabVIEW 8.2 and above) to demonstrate one possible way for you to be able to append the XML data to an existing XML file. If the file is being created, I use the "Easy Write XML File" function. This ensures that the XML header gets recorded in the file. On subsequent run of this VI, you read the file, generate XML string using "Easy Generate XML" function, append to the read file data and save it back to the same file. I am using "File Exists" function in the code. It is part of OpenG File Toolkit. So, you will have to install the OpenG Toolkit using VIPM in order to be able to run the attached VI. Hopefully this will help. Thank you. XML File Append.vi
  5. Anand, It is certainly possible to manage your own repositories using VIPM. For that, you will need VIPM Enterprise edition. Here is a link that compares different VIPM editions: http://jki.net/vipm/compare Let me know if you have any additional questions regarding VIPM Enterprise. Thank you.
  6. Jim, You are on the right track. You will need: - VIPM Enterprise: minimum 1 - VIPM Professional: rest of the group, 1 per user - VI Package Enterprise Repository: Number of client users who should have access to your internal Enterprise repository. Here is link to the comparison chart for different VIPM editions: http://jki.net/vipm/compare. This link will help you to understand the features offered in each edition. Here is the link to the pricing of VIPM editions: http://jki.net/vipm/purchase Please note that there is discount on purchasing multiple licenses which will be automatically reflected in the shopping cart. Let me know if you need any further assistance to make a decision or need a formal quotation. Thank you.
  7. Mike, We want you to try to re-install 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-install VIPM. If that does not fix the problem, try re-installing LV2009 32bit (Full) Run Time Engine: http://forums.jki.net/topic/1430-where-do-i-get-the-labview-2009-run-time-engine/ Let me know what happens. - Ashish
  8. The DLL should be located inside the folder containing VIs to be included in the package. The package builder and VIPM will ensure that the DLL gets installed at appropriate location for use.
  9. Parag, Thanks for sharing this information. Isn't it easy to change the security settings and revert them back when done?
  10. JG, Regarding workaround, are you asking to get access to the data displayed in the dialogs (as shown in your screenshots) after successful build?
  11. JG, I realized that I had provided wrong link in my previous post. Here is the correct link about which I was talking in that post: http://screencast.com/t/r7iyxorPPF
  12. JG, I am assuming that you are talking about the Password parameter under "Source File Settings" of the VI Package Builder (http://screencast.com/t/r7iyxorPPF). This parameter is to password protect the VIs in the package. I am not sure what do you mean by the "string array". Can you provide more information/screenshot to explain?
  13. JG, Thanks for sharing your observations. It does help to improve our product quality. I was able to reproduce the behavior and filed Case 13110 for us at JKI to manage the issue for future VIPM release. Feel free to share any additional information related to this issue. Thank you.
  14. judomagyar, Thanks for testing this at home since that is how we have really isolate the problem most of the times. I would recommend login as an administrator while installing VIPM and packages. Some clarification: - VIPM 2011.0.1 has a bug where it hangs while installing certain packages with status (at the bottom of the window) displaying "resolving dependencies" This should not happen in VIPM 2011.0.0. So, if your VIPM 2011.0.0 hangs, please provide us with additional information/screenshot to help us investigate. Thank you.
  15. Brian, What you need is a "Subpanel" to display Front Panel of a VI (running independently) in another VI. Here is a link to an article on NI website describing the implementation of subpanel: http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/loading_panel_in_subpanel/ You do not have to make SubVI of one State Machine VI into another, but run them in parallel and independent and use Sub Panel to display front panel of one VI into front panel of another VI. Hope this helps.
  16. judomagyar, Thanks for your feedback. Are you saying that both the VIPM versions (2011.0.0 and 2011.0.1) hanged while installing the "MGI read/write anything" package?
  17. Kris, I was able to reproduce the issue using IE8. The PC had nothing related to LabVIEW or VIPM on it. The issues is caused dure to security settings in IE8 which identifies unknown file type (in this case, ".vip" file) and renames it to ".zip". i was able to disable this "feature" of IE8 by changing the security setting in IE8 to "Medium". Here is a video demonstrating the issue and the solution to fix the problem: http://screencast.com/t/MqiXFn9EfSb - Ashish
  18. Lee, You've experienced a bug in the VIPM 2011.0.1's dependency resolution. It probably only affects a small number of packages, but unfortunately “Structured Error Handler” is one of them. We have reproduced the bug and are working on a fix, but I don't have a timetable for when it will be ready. In the meantime, the only workaround I can give you is to downgrade back to VIPM 2011.0.0. Here is the link to download the old installer: http://jkisoft.com/updates/vipm-2011-windows-setup.exe I apologize again for the trouble, and I hope downgrading (for now) isn't a huge hassle for you. If you need anything else please post back and we'll be glad to help. Thank you. - Ashish
  19. Pat, Glad to know that you managed to build a new package. We will certainly look into possible reason for the issue you experienced. VI Package Icon Editor is part of the community edition of VIPM!! Here is the link to the comparison chart: http://jki.net/vipm/compare Here is link to an article describing on how to modify the package icon: http://support.jki.net/entries/20654736-editing-the-package-icon I will also recommend you to read this thread specifically for VI Package Icon Editor and labVIEW 2011: http://forums.jki.net/topic/1717-icon-editor-deletes-current-icon-and-prevents-future-edits-of-new-icon/ - Ashish
  20. Norm, Thanks for reporting the issue and the video description to demonstrate the issue. We were able to re-create the issue and it does seem to be a bug in VI Package Builder while using LabVIEW 2011 Icon Editor. The issues has been logged as Case 13057 and will be addressed in the next bug release. - Ashish
  21. Sorry for the problem, The JKI TortoiseSVN tool does not currently support TortoiseSVN 1.7.1. Please downgrade to version 1.6 or earlier. We are currently working on a patch release to address this issue. It should be released around November 15th, at the earliest.
  22. Hi, I had to transfer the EasyXML License to another PC. So, I uninstalled it from old PC using VIPM. And then, I installed EasyXML on the new PC....again using VIPM. Is there anything else I need to do? Thank you/ - Ashish
  • Create New...

Important Information

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