Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Kring

  1. Sometimes there are issues installing VIPM when anti-virus, anti-spyware, or firewall software is running on your computer. If you get an Error 5 message when installing VIPM, try turning off your anti-virus, anti-spyware, and firewall applications and then installing VIPM.
  2. Sorry about that. Yes, VIPM only supports LabVIEW 6.0 and greater and most OpenG libraries are 6.1 or greater. At what point in the process does VIPM hang? How far do you get? Honestly, we haven't tested this extensively (since 5.1 is not supported and most of the JKI developers don't have anything older than 6.0 on our machines). Thanks, -Jim
  3. Jon, That's great news! I'm happy that we were able to get VIPM working for you. Thanks, -Jim
  4. Thanks for the clarification. Also, is there anything special/unusual about your system or configuration? For example: Are you running with non-administrator privileges? Is your computer under configuration lock-down by your IT department? Are you running Windows Vista? Are you using any special firewall or anti-virus software? (if so, try disabling it and then installing VIPM) Thanks, -Jim
  5. Hi, I'm sorry that you're having trouble. It appears that the issue is occurring during a self-extracting step of VIPM's installation process. I agree that the "File Already Open" error is misleading. I have a few questions: Does the installation work if you try again? (If so, maybe it was simply a one-time occurrence) Have you tried rebooting your computer? (Sometimes this helps if there is some OS lock on a file) Are you installing VIPM 1.1 or 1.1.1 (the latter, was just released today)? Hopefully, we'll get you up and running, soon. Thanks, -Jim
  6. That's good news. I'm glad you got it working.
  7. Hi, Thanks for reporting this. By the look of your screenshot, you appear to be running Windows Vista. If so, we know about this issue and it doesn't seem to cause too much of a problem. We've even got an FAQ item on this topic: Can I install VIPM on Windows Vista We appreciate your feedback. Let us know if you experience any other issues. Thank you, -Jim
  8. When you select Edit>>Copy Package Names or Edit>>Copy All Columns VIPM will copy the package list information to the clipboard as a tab delimited string, which can be pasted into Excel (or anywhere, for that matter). For example, let's create an excel spreadsheet containing all the info of the installed OpenG packages. 1) Open VIPM's main UI and set the Package Show Filter listbox to "Installed" and type "openg" into the Quick Search textbox (as shown below). 2) Select Edit>>Copy All Columns in the VIPM menu to copy the entire package list to the clipboard. 3) Open Excel, select the first cell (A1) and then select Edit>>Paste in the Excel menu to paste the data into the worksheet.
  9. Hi Chris, This has been fixed in VIPM 1.1. Thanks for your patience and feedback. -Jim PS - I split this thread from original topic, since the tip is now working.
  10. I wanted to give you an update: The two bugs that I mentioned in my last post have been resolved in the official release of VIPM 1.1. See here for more info. Thanks, -Jim
  11. Yes, attributes are achieved by placing a cluster named "#attributes" as the first cluster element of the xml element cluster. Example LabVIEW Data Structure: EasyXML output: <my_element my_attribute_1="value 1" my_attribute_2="value 2"/>
  12. With JKI's EasyXML VIs, you can create and parse any XML data type, including those defined by you, your co-workers, other companies, or industry standards bodies (like ATML, XDF, Open Office XML, etc.). And, you don't have to understand everything there is to know about XML or XML parsers. We've made creating and parsing XML so easy that anyone can do it! With LabVIEW's built-in XML functions, you can only create XML data types that conform to the LabVIEW's XML data schema, which is defined by NI in this schema file: vi.libUtilityLVXMLSchema.xsd Or, think of it this way... JKI's EasyXML VIs: convert specific LabVIEW data types to and from any XML data type. LabVIEW's built-in XML functions: convert any LabVIEW type to and from a specific XML data type. Let's look at a simple example, where the following cluster is converted to XML using both NI's functions and EasyXML: XML data generated by LabVIEW's built-in XML functions: <Cluster> <Name>My XML Data</Name> <NumElts>2</NumElts> <DBL> <Name>My Number</Name> <Val>1.23000</Val> </DBL> <Boolean> <Name>My Boolean</Name> <Val>1</Val> </Boolean> </Cluster> XML data generated by JKI's EasyXML VIs: <My_XML_Data> <My_Number>1.23</My_Number> <My_Boolean>TRUE</My_Boolean> </My_XML_Data> As you can see, the EasyXML output is much more compact and allows you to define your own XML schema.
  13. Yes, you will need to install the 8.2.1 run-time engine in order to run VIPM 1.1. This can co-exist with LabVIEW 8.5 and the LabVIEW 8.5 run-time engine -- no problem. Please see the, Which LabVIEW Run-Time Engine do I need?, FAQ entry for more details and links to download the LabVIEW run-time engine. Thanks, -Jim
  14. Hi Brett, That's great news. I'm happy that you've gotten everything working, finally. Thanks, -Jim
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. Hi Chris, You beat us to the punch We will be announcing the release candidate today. Thanks, -Jim
  21. Hi Vix, Have you contacted NI support about this? I am pretty certain that it's an issue with LabVIEW. Thanks, -Jim
  22. 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
  23. 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
  24. 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
  25. 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
  • Create New...

Important Information

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