Jump to content


JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Ashish

  1. Daresh, Did you figure out the problem with LabVIEW connection with VIPM? Did you check if your Firewall (if any) is blocking the connection?
  2. Jason, As of yet, we do not officially support the packed libraries in VIPM 2012. I have created Case 13647 internally for tracking the status of this since we are working on it for the next release of VIPM. We really want to support this capability and are working through various issues. Thank you.
  3. Marco, Beginning VIPM 2012 we have just Pro and Free editions. Here is link to compare the features: http://jki.net/vipm/compare
  4. Norm, I was able to recreate the behavior and recorded as Case 13633 for the VIPM Team to investigate. At the moment, the workaround I can think of Custom Actions - Install Actions - Post Install VI to fix this behavior. Thank you.
  5. rhechtatssi, What version of EasyXML are you using? Can you send us an example project that produces a broken build? This will help us reproduce and investigate the issue. Also, any additional information/screenshots will be helpful. Thank you.
  6. UPDATED: Added the attachment. Hi, Thanks for sharing your observations. I tried to perform similar tests and the results appear to be linear. Attached is my test VI with the observations on the Front Panel. Am I doing anything different than you? Main Test.vi
  7. Ashish


    Svendsen, EasyXML ignores CDATA inside XML when parsing it into LabVIEW data. It does not provide any way to read in the CDATA or write to CDATA elements. Also, at this point there is no plan to implement this feature. I wonder if it is possible for you to build up a routine using some string operations to extract the CDATA from the XML String?
  8. Mellroth, Glad to know that you are back on track. I was able to recreate the problem in Pre-Post VI configuration that you had experience. This has been recorded as Case 13533 for consideration to be fixed in the next release of VIPM. If you happen to be in such situation again, the only way out will be to delete the ".vipb" file that is generated and managed by VIPM in the same folder that you had selected for building the package. WARNING: All the VI Package Building configuration will be lost if the ".vipb" file is deleted. You will have to redo the configuration.
  9. crelf, I could not recreate the problem. See the attached test project I created. After building the project, I was able to drop the VI and it connected to the appropriate typedef. FYI, I am using Windows 7, LabVIEW 2011 and VIPM 2012 environment. Typedef in Package Test.zip
  10. We have identified this as a bug and created Case 13445. The case is under consideration. Thank you for providing enough information about it.
  11. Just wanted to let you know that I was able to recreate the behavior described by you and currently it is under investigation. I will get back to you early next week with the analysis.
  12. dlanger, Did you perform "Mass Compile" on your code before building the package? I was able to recreate your situation. However, mass compiling the folder before building the package appears to solve the problem on my machine.
  13. dlanger, One recommendation I can have to to include the DLL name instead of the DLL file path in the "Call Library Node" as shown in this link: http://screencast.com/t/U7eATG2pNSn Also, 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. Let me know how it goes. Thank you.
  14. I really like the double click in VI Tester GUI which opens that specific test VI. Similarly, it will be really handy if we can access/open the "setup" and "teardown" VIs for any test by simply right clicking on the selected VI in the VI Tester GUI as show here: http://screencast.com/t/54C5UW26
  15. 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.
  16. TobyD, Thanks for documenting your workaround to fix the problem.
  17. 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.
  18. 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
  19. 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.
  20. 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.
  21. 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
  22. 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.
  23. Parag, Thanks for sharing this information. Isn't it easy to change the security settings and revert them back when done?
  24. JG, Regarding workaround, are you asking to get access to the data displayed in the dialogs (as shown in your screenshots) after successful build?
  25. 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
  • Create New...

Important Information

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