Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Kring

  1. Hello, There is a known issue in LabVIEW 8.5. The problem occurs when the LabVIEW Getting Started dialog is open you try to install a some packages (specifically, those that need to run code inside of LabVIEW during the installation). The solution is to open a VI (or even a new/untitled VI), and then perform the installation. Please give this a try and let me know if it works for you. Thanks, -Jim
  2. Hi Danny, I'm glad you were able to figure this out. Yes, the Add Package is the preferred way to add packages to your package list. However, another great way of achieving this is to use a VI Package Configuration file. -Jim
  3. Hi John, I'm sorry to hear that you had a frustrating experience with VIPM and trying to get OpenG installed, especially since one of the main reasons that VIPM exists is to make it very easy to install the OpenG VIs on your LabVIEW version. Unfortunately there is no procedure for how to manually install the OpenG VIs. And, this process is much more difficult than simply using VIPM. The OpenG libraries have dependencies between them and VIPM automates the process of correctly resolving these. Also, each package contains information inside of it that describes where and how it needs to be installed. And, many packages are installed slightly differently on different versions of LabVIEW. Where did you get stuck installing and using VIPM? Did you have a chance to watch the tutorial video on Getting Started with VIPM and Installing OpenG Libraries into LabVIEW? Please let me know. We care a great deal about solving any problems that you encountered and are committed to making VIPM a very usable product. Also, which packages, specifically, are you having trouble installing? I just recalled that you posted on OpenG.org some questions on the OpenG Class Templates for Object-Oriented Programming. Thank you, -Jim Kring
  4. Thank you for letting us know about this. The forum permissions have been adjusted so that non-registered users can download files and watch the tutorial videos. Thanks, -Jim
  5. Hello, > I have just registered in this forum and VIPM. Of course, I read FAQ but there is no solution. I am very wondering if my quesiton is suitable to this forum. Yes, this is the right place for your questions. I'll do my best to answer them > 0. Is VIPM for distributing user defined VIs? or some other VI under Labview? Yes, VIPM can be used for installing your own VIs that are packaged using the OpenG Package Builder tool. However, this process is very simple for beginners. We're working hard to simply the package building process and you'll see more information, coming soon. > 1. How to check the available packages without installing the manager? Or what is the contents in the professional library? The best way to check for new packages is to monitor the file release forum, here. > 2. What is the requirement in making and distributing after building application software? (Some additional libraries excep NI libraries) If you're asking about the licensing terms of the OpenG libraries, these are licensed under the BSD license (which is a very flexible and user-friendly license). You can find out more information about this here. Also, you can look at the front panel of any OpenG VI to find out the license terms. > 3. Is there some VIs for windows API commands? No, there are no VIs, currently, in the OpenG libraries for doing WinAPI commands. > 4. How to buy the professional library? How much the updating price for future version? The annual maintenance subsciption is $349 and includes direct email support and upgrades. Here is the detailed VIPM Professional pricing breakdown: VIPM Professional with Subscription: $943 VIPM Professional: $699 VIPM Pro. Subscription Renewal: $349 We are currently having a pre-order special for 15% off of VIPM Professional with Subscription. See here for more information. You can learn more about the difference in features between the free Community Edition and the paid Professional Edition, here. > Thank you in advance. You are very welcome. Please let me know if you have any more questions. I'm happy to answer them. Thanks, -Jim
  6. Because the classic version has system scrollbars, addressing the issue posed by Johan.
  7. Hi Chuck, Yes VIPM can be used to install toolkits on multiple LabVIEW versions. Let me explain... NI generally proposes that you can install a toolkit on multiple LabVIEW versions by copying the toolkit's vi.lib\addons components (as well as examples and some other files installed beneath the LabVIEW root) into other LabVIEW development environment installations. VIPM can certainly automate this task. Please see the attached file (create_package_nilib_database.zip) -- it contains everything you need to create a package of the NI Database Toolkit v1.0.1. NOTE: The NI toolkit packages that you create are for your own personal use and must not be redistributed to others. It is your responsibility to abide by the terms of the NI Software agreement. This technique is used to automate the instructions provided by NI for installing toolkits (that you have legally licensed) on multiple LabVIEW versions. Thanks, -Jim create_package_nilib_database.zip
  8. Hi Steven, This issue seems to be pretty tricky. Let's take this off-line -- I'll send you an email. Thanks, -Jim
  9. Hi Daniel, VIPM 1.0 does not support LabVIEW 8.5. Please upgrade to 1.1. It's a lot better -- I promise And, the upgrade is painless. Simply download the new version and run the installer. Also, I posted this message, recently, discussing VIPM Professional Edition with respect to the free Community Edition, which we are committed to supporting. There is no beta version of 1.1 Community Edition, since it is simply a subset of the Professional Edition. Thanks, -Jim
  10. Hi Steven, First, thanks for you patience on this issue. Most of the JKI Team was at NIWeek, all last week Second, can you please download a package file try opening it with WinZip to verify that it is a valid ZIP archive file (OGP files are actually ZIP files with a special structure). You can download a package by right-clicking on it and choosing Download. You can find the downloaded file inside the following directory: C:\Program Files\JKI\VI Package Manager\cache Also, is there anything atypical about your machine configuration? For example, did you install VIPM or LabVIEW in a non-standard location? Are you running as a user with non-admin rights? Thanks, -Jim
  11. Joe, You're very welcome and thanks for the kind words. -Jim
  12. Hi Joe, I posted this message, recently, discussing VIPM Professional Edition with respect to the free Community Edition, which we are committed to supporting. Thanks, -Jim
  13. VIPM 1.0 does not support LabVIEW 8.5. Please upgrade to 1.1. It's a lot better -- I promise And, the upgrade is painless. Simply download the new version and run the installer.
  14. Hi Ton, Thanks for reporting this -- it's a bug. We'll look into it and post a trackable bug ID, shortly. Thanks, -Jim [uPDATE] This is bug has been entered into our tracking system as Case 4702.
  15. Hi Steven, Can you try changing package mirrors order on the Advanced tab of the Options dialog? Mirrors that are geographically closer to you, should be at the top of the list (drag and drop them to reorder). Please let me know if this helps. Thanks, -Jim
  16. Hi Steven, Could you please attach any error log files located, here: C:\Program Files\JKI\VI Package Manager\error\ Also, it might be helpful to increase your TCP network timeout (to 60 seconds, for example) in the VIPM options dialog. Thank you, -Jim Kring
  17. Boris, That's great news! Thanks, -Jim
  18. TiTou, I just learned that JKI will be making some announcements at NI Week about VIPM Professional Edition pricing. So, you won't have to wait too long to find out Thanks, -Jim
  19. The OpenG VIs do not appear under the Addons category of the palettes. There should be a category called OpenG -- everything's in there. If the OpenG category is not visible, you might want to select... View>>Always Visible Categories>>OpenG From the palette's menubar. Also, you might want to check out this tutorial video (especially the last part where it shows how to find the OpenG VIs in the palettes): Getting Started with VIPM and Installing OpenG Libraries into LabVIEW If that doesn't work, please let me know. Thanks, -Jim
  20. BTW, I've added a new FAQ item on this issue: Can I install VIPM on Windows Vista
  21. Toby, Thanks for taking the time to test the VISTA installation and provide us with your experience. I'm happy to hear that you've gotten to the point where you're installing packages -- that's great news! If you have any more issues or experiences using VIPM in VISTA, please post them to this thread -- that's valueable feedback for JKI as well as the VIPM user community. BTW, our testing team is provisioning a VISTA system right now for doing some detailed tests. Hopefully we can resolve the one hiccup that you experienced -- I'm thinking that there's got to be a way to launch an EXE from the command-line in compatibility mode by using some special command/switch. Thanks again, -Jim UPDATE: I just looked online and it appears that you can include a "manifest file" (a special XML file) along with an executable that contains information telling VISTA about your executable and how it needs to be run. We should be able to create a manifest file for each of the EXEs that tells VISTA to run them in Windows XP compatibility mode.
  22. Dear VIPM Users, Over the past year, I've been amazed at the response to VI Package Manager and the increased interest it has generated in the open source LabVIEW community. In March of 2007, JKI reported that OpenG usage increased by an astounding 20x immediately following the release of VI Package Manager 1.0! To know that our team is helping to bring these powerful software reuse libraries to LabVIEW developers everywhere means a lot to us, as the LabVIEW community is such an important part of who we are as a company. With the release of VIPM 1.1, there will be two versions available: VIPM Community Edition, which will be free and offers a variety of amazing features and VIPM Professional Edition, which will be a paid product and, in addition to all the features of VIPM Community Edition, include powerful configuration and dependency management tools. To learn more about the differences between the Community and professional editions of VIPM, please read the "What is the difference between the Community Edition and Professional Edition?" FAQ entry. Releasing VIPM Professional Edition as a commercial product will provide a financial engine that will allow JKI to commit expert LabVIEW developer resources to the growth and support of the VI Package Manager as well as other exciting LabVIEW tools under development. As I've mentioned before, at JKI we are committed to promoting LabVIEW by aspiring to develop some of the best software applications written in LabVIEW, and we are excited about the possibilities VIPM will provide to open source software for LabVIEW. Thank you for the opportunity. Best Regards, Jim Kring President and CEO JKI
  23. Tibobo, That's great news! Can you tell us which setting was causing you problems? We're working on ways to allow VIPM automatically adjust LabVIEW's settings and knowing what your issue was will help us focus on the right areas. Thank you, -Jim
  24. I agree with your sentiments. If I were you, I would focus some energy on trying to convince NI to start opening up the project environment to third-party developers. That's what's going to make this possible.
  25. Hi Ton, Since VIPM runs as a stand-alone executable, this is a little bit trickier than it would be if VIPM were running inside the LabVIEW development environment. However, it is something that we are considering for the future. What sorts of use cases do you have where this would be useful? Thanks, -Jim
  • Create New...

Important Information

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