Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. If you can install VIPM, you can install the OpenG Packages from a local source (i.e. portable hard drive / flash drive). You still have to download the OpenG VIs from sourceforge yourself, using this link, but once you get them all on disk, VIPM can import them and install them on a machine not connected to the internet. I know because its how I operate. You'll also want to look for release notices on the VIPM or OpenG pages to know when new or new versions of packages have been released. Chris
  2. If I don't want to upgrade to 8.2.1 can I test VI's written in 8.2 from withing 8.5? I know its a strange question, but I'm not entirely sure what VI Tester would do. My first gut answer would be yes since I don't believe that VI Tester would actually try to save or modify my VI while testing it. What do you guys think? Is this a crazy idea?
  3. Your workaround works. When I did this I was able to interact with the blank project correctly. I think I've done what you asked here, to no avail. The same exec.cpp error popped up. BTW, I did a quick search on NI's site as well as LAVA and didn't find this particular error mentioned anywhere. I know these errors are EXTREMELY difficult to diagnose, so thanks for trying. I'm not opposed to upgrading to 8.2.1, if you think that will solve my problems, I just haven't yet.
  4. I got VI Tester downloaded, but I'm having an issue. I've attached two screenshots with my error. When I first start VI Tester I get a message saying that it needs to mass compile itself, which I let it do. At the end of that I get the following screenshot. I thought I would mass compile the directory myself, to see if that would help, and it did. So now I can run VI Tester. When I make a "new" test project / lvclass the project window for that class won't come to the front, so I have to quit LabVIEW to get it to close. Now since there is a sample test in the test class, I thought I would run it through the VI Tester just to give it a shot. Same internal error as before. . For the record, VI Tester installs and works fine in LabVIEW 8.5 and 8.6. I seem to remember quite a few bugs related to lvclasses in 8.2 that were fixed in 8.2.1, but I thought I would post this message to see if others were having trouble before I tried to upgrade my system. System setup: LabVIEW 8.2 (no 8.2.1 patch installed) Windows XP SP2
  5. JKI, Thanks for the work on VI Tester! I would like to try it, but I don't have LabVIEW installed on a machine that is connected to the Internet. Could you provide a link in your pinned / locked topic for downloading VI Tester to disk to install on another machine? BTW, I didn't see any system requirements. At this point I'm assuming LabVIEW 8.2 is a minimum requirement, but I'm sure others would like to know operating system requirements that might, or might not come into play. Thanks, Chris Davis
  6. Is there another way to post this video? I can't see flash based content at work and would like to be able to view this video.
  7. Jim, I've been doing just that. I also thought I would try out your tutorial above and I've almost got it the way I want it. I am having trouble with, as you have guessed, creating the mnu file correctly. I seem to have it setup just perfectly for the functions palette, but whenever I try to get the controls palette to show up with the same mnu file I run into snags. I'm thinking maybe I need to distribute two mnu files both of which sync to the org\palette mention above. One of these proposed mnu files would handle putting controls on the controls palette and the other would handle putting functions on the functions palette. I just thought I would ask if I'm missing something before I go down this path. I think I'm going to keep the method you've "tutorialized" (pardon the coined phrase) above because the group likes it. And, it seems fairly straight-forward to implement. Thanks!
  8. Actually, I was going to be content with putting all of my work under the User Library, but now that you've shown me another way, I will be checking this tutorial out. To clarify, currently I navigate to User Libraries, then I have a subpalette there with my org name, then under that several subpalettes that contain my reuse VIs, as seen below. I did it this way because no tutorial existed on how to do it another way. If I want to continue doing my reuse library this way, what parts of your tutorial would have to change? BTW, thanks for producing this quick tutorial, I'm going to discuss this idea with my other users to see if it will help out.
  9. Jim et al, I've got several reuse library VIs that I would like to package into several (15ish) VIPM 2 packages. VIPM 2 has made it mucho easy to put together nice looking palette's. Now I want to make a palette of all my various packages and make the installed items look the same in all installed computers, in much the same way that OpenG does with its packages. Any advice? Thanks
  10. take a look at this OpenG page, it should help you find the EasyXML examples. As for the documentation, mine shows up when I click on detailed help, so I can't be of much help there...
  11. Thanks guys, I guess I'm out on the leading/bleeding edge...
  12. Today I tried to run my install of VIPM 1.1 Beta 2 (Build 622) and it had expired. A dialog presented itself asking if I wanted to begin using the community edition or continue to use the professional edition. When I selected community edition, I was unable to continue, the dialog kept appearing on two different machines that I've installed VIPM on. I decided to go to the download link to make sure I had the most current version. It seems that there is an unannounced release candidate 1 version out now (build 623), which I didn't have. I'll try installing it now and see if it helps. FYI, When I install it, it gives me 60 more days of activity. Keep up the good work, just wanted to let you know about the error with the community edition dialog.
  13. EMG, As far as I know VIPM was never built with anything less than LabVIEW 8.0.1. Jim can correct me if I'm wrong. You might have used OpenG Commander at some point in the past, which was not a compiled LabVIEW exe and worked within the LabVIEW environment to download and install OpenG packages. As for an older version of VIPM, I'm sure that JKI has them somewhere, but I don't know exactly where. If you don't want to install the runtime, I'm afraid you are out of luck, it is a requirement of VIPM. Chris
  14. Sure, VIPM works with LabVIEW 7.1. VIPM is an LabVIEW executable written in LabVIEW 8.2.1 and needs the 8.2.1 runtime engine to operate. You can download it from National Instruments for free. (windows version here) Enjoy VIPM! Chris
  15. Thanks for trying to help, I'll just have to stick to downloading the packages from sourceforge directly, or someother method to try and get new packages as they are released. Chris
  • Create New...

Important Information

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