Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Kring

  1. NI returned CAR# 148158 for this issue. I'll let you all know when the status changes.
  2. FYI - I've submitted this bug to NI. I'll keep you all posted with any information I get back from them.
  3. Hi Richard, Sorry for the trouble and thanks for your patience. The "error 7 occurred at get file size" is actually a false error message. It's a downstream error that is masking the real error. The error you're encountering is due to the fact that VIPM is having trouble executing a "script VIs" inside the package. In order for VIPM to be able to execute script VIs, you should make sure to set up your VI Server permissions. Please read this FAQ entry and see if configuring VI Server correctly helps with your problem: http://forums.jkisoft.com/index.php?showtopic=232 Please report back and let me know if this helps. Thanks, -Jim
  4. Hi Jim, I'm glad to hear that you're out there spreading the JKI State Machine love Hopefully some day (soon?) the Event Structure will be usable in the base version of LabVIEW. Regarding Macros, my general rule is that whenever I have a sequence of steps that I need to use in more than on place, I create a macro. That's unless I know that I'll eventually use it in more than one place -- in that case I'll make it a macro pro-actively. Thanks, -Jim K
  5. I have no idea why this is happening, but I think it might have something to do with the fact that the VIs are members of classes and need to be saved (recompiled) in the newer version of LabVIEW. I've seen this issue, too, but I don't have the exact steps to reproduce.
  6. Hi Chris, There shouldn't be any problem running tests in 8.5 that were created in 8.2. No, VI Tester isn't going to try to save any of your VIs.
  7. Thanks for the ping on this topic, Ben. I'll try to get the JKI Team to put out some JKI Software Blog articles on tips, tricks, and design patterns for the JKI State Machine.
  8. Hi Martin, You should take a look at these posts on the NI forums: http://forums.ni.com/ni/board/message?boar...ssage.id=369135 http://forums.ni.com/ni/board/message?boar...ssage.id=202130 It might provide some insight. Also, this is an issue that NI's tech support can help you with, since it's an issue with LabVIEW executable applications running in the run-time environment -- it's not a VIPM issue, per se. Thanks, -Jim
  9. Hi Glen, Yes, I think this is a permissions issue and will be very tough to diagnose over the forums. Please, send us your email and phone number via our contact form and I'll follow-up with you, off-line. Thanks, -Jim
  10. Hello Heiko, You should be able to open the VIPC in the VI Package Configuration Editor, change it's LabVIEW version to "9.0", and then Apply it. Let me know if this works for you. It should, since I did this myself yesterday Thanks, -Jim
  11. Hi Glen, Sorry about the slow responses. As you might imagine, this is a tricky issue and tough for us to diagnose remotely. Yes, if you're running VIPM as the root user and VIPM launches LabVIEW, then LabVIEW will be running as the root user. Thanks, -Jim
  12. Hi There, Sorry to hear you're having troubles. I have a few questions that might help us figure out what's wrong: Which TCP-IP port is LabVIEW configured to use for VI Server? If VIPM is not already running when you launch LabVIEW 8.0, does LabVIEW show the "VI server port already in use" error message after it is launched? Based on your answers, I might have some follow-up questions. Hopefully, we can get you up and running Thanks, -Jim
  13. That's great! I'm looking forward to your next article. Let us know if you have any related questions. Thanks,
  14. Ben, I see that you've spent some time unit testing in LabVIEW We're very happy to hear that you like VI Tester and we're excited to hear your ongoing feedback -- keep it coming. Thanks! -Jim
  15. There's a very interesting discussion happening on LAVA, regarding testing of private class VIs: http://forums.lavag.org/Testing-private-cl...vis-t13052.html I'm going to close this thread, to encourage people to respond on LAVA.
  16. Hi Chris, We're excited to hear your feedback on VI Tester, once you've had a chance to give it a try. I've emailed you information about how to get VI Tester onto your off-line computer. Thanks for the feedback about the missing system requirements. I've created a new System Requirements page and put links to it in a few places. Yes, it's LV 8.2 or greater (good guess!). Thanks, -Jim
  17. Hi Tim, I'm sorry about that. It's a known issue: Known Issue (Case 5244): Can't parse array of time stamps I'll take a look at how the fix is coming and get back to you with any work-arounds or other information. Thanks, -Jim
  18. Hi Glen, Sorry for the trouble. I hope that the information on the known issue report was sufficient to help you work around this. Please let us know if you need further help. Thanks, -Jim
  19. Hi Ton, I have added this to the known issues: Known Issue (Case 6782): VIPM installer on Linux can alter home and tmp permissions Thanks,
  20. This has been added to the known issues: Known Issue (Case 3021): Installation bug on Mac when HD name that is not default ("Macintosh HD") Thanks,
  21. Hi Ton, I just heard a similar story from another Linux user who said the following: Thanks, -Jim
  22. Hi Francis, Thanks for sharing your installation experience with us -- hopefully it will help anyone else who encounters something similar. I'm happy to hear that you're up and running, now. Yes, sometimes there are tricky installer/OS issues that require installing LabVIEW and/or the RTE from oldest to newest. Sometimes older versions can "step on the toes" of newer versions. We look forward to hearing more about your successes (and any issues you might have) in using VIPM. Thank you, -Jim
  23. Hi TiTou, Happy New Year and thanks for the bug report. What seems to be happening is that the sort algorithm is case sensitive. We did a bit of optimizing of the sorting algorithms in the past, but it appears that a bug slipped past! I have filed a bug: Known Issue (Case 6624): Column sorting in package lists should be case insensitive Thanks, -Jim
  24. Sure. Anything to help my favorite VIPM user. PS - Did I mention that I use VIPM a lot and need this feature working?
  • Create New...

Important Information

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