Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Kring

  1. Hi Brett, That's great news. I'm happy that you've gotten everything working, finally. Thanks, -Jim
  2. Hi Brett, I'm happy to hear that it's not an issue with VIPM, specifically. I wish I could help more, but those security software suites tend to each have a million and one features. Please report back and let us know if you get it working and if you learn anything that might help other VIPM users who have Zone Alarm installed. Good luck. Thanks, -Jim
  3. Hi Brett, Can you try turning off Zone Alams and see if that fixes the problem? I'm not familiar with that software, specifically. Is there a way to manually add programs to the allowed list of applications? Do you have permission to change this list (or does your IT dept control this)? Thanks, -Jim
  4. Sorry for the continued trouble... The Tools>>Check the Network for Available Packages and the Package>>Download menu option should be enabled, but it is not -- that's a bug (Case 4979, resolved in VIPM 1.1). However, you should still be able to press the Check the Network for Available Packages button on the toolbar (see screenshot below). Now, for downloading the packages, you should be able to unselect the Show only Installable Packages in Package List option in order to display all the packages. However, this also appears to not be working unless a LabVIEW version is selected -- this is a bug (Case 4980, resolved in VIPM 1.1). This option selects whether to show only those packages that may be installed on the currently selected LabVIEW version or to show all packages that are available. Due to the aforementioned bug, we have to trick VIPM into thinking that you have LabVIEW installed. The steps listed below should work, but I have not tested them (since I have LabVIEW installed on all my computers)... 1) Close VIPM 2) Backup the "C:\Program Files\JKI\VI Package Manager\VI Package Manager.ini" file to a safe location. 3) Edit the "C:\Program Files\JKI\VI Package Manager\VI Package Manager.ini" file, adding (or updating) the following section and key-value pairs: [Targets] Names.<size(s)>=1 Names 0=LabVIEW Versions.<size(s)>=6 Versions 0=6.1 Locations.<size(s)>=1 Locations 0=/C/Program Files/National Instruments/LabVIEW 6.1/LabVIEW.exe Ports=<size(s)=1> 3363 Connection Timeout=60 Active Target.Name=LabVIEW Active Target.Version=6.1 4) Launch VIPM 5) Select LabVIEW 6.1 from the version selector ring (see screenshot, below). 6) Download the desired OpenG packages Please let me know if you are able to make this work. If not, there are still some other work-arounds. Thanks, -Jim
  5. Yes, you can easily do this. Take a look at this FAQ entry (which I just created): How do I install OpenG packages with VIPM on a non-networked computer? Let me know if you have any questions. Thanks, -Jim
  6. Hi Ton, Yes, that might be an option. The thing that I don't like about Data Socket is that you have almost no visibility into or control of the data transfer. Also, it is not cross-platform. Another alternative would be to simply have an option to use the Windows API functions (WinInet) for downloads. Thanks, -Jim
  7. Hi Chris, You beat us to the punch We will be announcing the release candidate today. Thanks, -Jim
  8. Hi Vix, Have you contacted NI support about this? I am pretty certain that it's an issue with LabVIEW. Thanks, -Jim
  9. Hi Jonni, Thanks for your feedback. Custom package URLs is not a restriction, it is a feature that does not exist -- there is a huge difference. If we allow users to specify their own package URLs, then we have to support the client-server protocol/format that VIPM uses. This is something that we want to reserve the right to change in the future and is not something that we wish to support right now. Plus, the Package Mirrors List in VIPM is a list of SourceForge mirrors -- it is not a list of package URLs. If you can describe to us what you would like to do, we will consider it carefully. We appreciate your feedback and will use it to make VIPM the best tool possible. Thanks, -Jim Kring
  10. Hi Vix, Yes, at this point you will probably need NI support to help figure out what is happening. Please let us know if and how you are able to resolve this issue. Thanks, -Jim
  11. Hi Vix, The labviewrc file(s) will probably not exist, already, in the labview installation folder(s). Try creating them, or copying them from your home directory. For example: cp ~/.labviewrc /user/local/natinst/labview/labviewrc Also, make sure that you don't have any settings in your .labviewrc file that overide the labviewrc files' settings. Just to be sure, you can try deleting your .labviewrc file. rm ~/.labviewrc Finally, you should be aware of file permissions. Make sure that the the labviewrc file in the labview installation folder is readable by users who will be running LabVIEW. Let me know if this works for you. Thanks, -Jim
  12. Hi Tks, On Linux, LabVIEW options for a user are stored in the home (~) directory, in a file called .labviewrc. This file is global for LabVIEW versions. However, you can (and should, in this case) create a labviewrc file in the (LabVIEW) program directory to store options that are the same for all users, such as the TCP port. For example, if you installed the LabVIEW files in /opt/labview, LabVIEW first reads options from /opt/labview/labviewrc. Note that entries in the .labviewrc file in your home directory override conflicting entries in the program directory, so you should make sure that the TCP port setting is not set in any user's .labviewrc file. Please take a look at the Customizing Your Work Environment document (specifically, the Linux section) on ni.com for more details. Thanks, -Jim
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. Because the classic version has system scrollbars, addressing the issue posed by Johan.
  19. 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
  20. Hi Steven, This issue seems to be pretty tricky. Let's take this off-line -- I'll send you an email. Thanks, -Jim
  21. 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
  22. 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
  23. Joe, You're very welcome and thanks for the kind words. -Jim
  24. 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
  25. 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.
  • Create New...

Important Information

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