Jump to content

Jim Kring

JKI Team
  • Content Count

    1,495
  • Joined

  • Last visited

  • Days Won

    28

Everything posted by Jim Kring

  1. You may need to do some googling and research to figure out how to run 32 bit applications on your linux installation. there’s a discussion thread here with some tips: https://stackoverflow.com/questions/23182765/how-to-install-ia32-libs-in-ubuntu-14-04-lts-trusty-tahr Specifically, it talks about how to add another package repository for apt yet to find the missing package. Please keep in mind that I’m not sure exactly if this is the best solution for you, so please be sure to do some research.
  2. Some googling shows that this error can occur when you're running 64-bit and in order to run 32-bit executables, you'll need to install the ia32-libs package (and make sure you have multi-architecture support enabled). You can try installing the ia32-libs package using the following command: apt-get ia32-libs Some googling will help you figure out all the details for your platform. Disclaimer: I'm not a Linux expert, but I sometimes play one on TV.
  3. You might try creating a JKI folder here, and ensuring that your user account (or all user accounts if you wish) has write access to it.
  4. @tomlawton oops, you're right. I just tried installing on a clean Mac and I get the following: I typed in my password and then VIPM launched just fine (and on subsequent launches without typing in my password). Question: Is your user account an admin account?
  5. thanks for posting that. It looks like you are in the right folder, the permissions are correct on the vipm file, and you tried to execute it. I'm no Linux expert, but that looks like it should work. What happens if you type the following? ls -al /usr/local/JKI/VIPM/vipm This should output something that looks like: -rwxr-xr-x. 1 root root 35218160 Mar 8 21:22 vipm
  6. @tomlawton can you please send your VIPM troubleshooting file to support@jki.net (please don't post it here)?
  7. You need to run the executable: sudo /user/local/JKI/VIPM/vipm or change directories into the VIPM folder first and then run the executable cd /user/local/JKI/VIPM sudo ./vipm The directions could be a little more clear. Does that work for you?
  8. @tomlawton Thanks for reporting this. Yes, it looks like a permissions issue. I'll see if I can find some info about which files to check...
  9. The latest official release is available for download and installation with VIPM. That said, we do have pre-release versions of JKI State Machine that you can download, try out, and provide us with feedback. Check out the JKI State Machine Releases page on our GitHub.
  10. Yes and no. Yes, it's possible. You will need to write to the http request header a "Authorization: Negotiate [token]" instead of "Authorization: Basic" (for basic password authentication). However (this is the "no" part), you probably will need to implement the security token handshaking protocol yourself -- I don't see (via googling) that anyone has done that. See here for a high level overview. There's a more detailed, technical explanation of the process here.
  11. Hi Fab, Chris. You probably already saw the announcements: VIPM 2017 for Mac and Linux have been released. Hopefully, there’s no reason for anyone not to upgrade.
  12. We're pleased to announce the release of VI Package Manager 2017 for Linux! Our team has worked hard to address several issues that were making Linux support difficult. Click here for more details.
  13. Good catch @wyzromek! We've fixed this issue (I hope) and released a new version. Also, we added support for In Place Element Structure cluster (un)bundlers, while we were at it.
  14. We're pleased to announce the release of VI Package Manager 2017 for Mac! Our team has worked hard to address several issues that were making Mac support difficult. Click here for more details.
  15. A very simple LabVIEW toolkit for localizing VI front panels, based on a dictionary translation file. This toolkit makes use of the "Language for non-Unicode programs" setting in Windows (located in the "Region and Language" settings). The toolkit uses a JSON dictionary file (can be in Unicode format) to store phrases in several different languages. The toolkit will translate from the default language (typically English) to the target language specified as the "Language for non-Unicode programs" in Windows. It does all this by making calls into the Windows API to translate the Unicode 16-bit characters from the dictionary into 8-bit non-unicode characters that can be displayed by non-Unicode program (assuming the "Language for non-Unicode programs" has been properly set in Windows). In this way, LabVIEW developers have a simple way to localize their applications, even though LabVIEW does not support Unicode, out-of-the-box. JKI Simple Localization Homepage Get JKI Simple Localization
  16. Get the JKI State Machine Editor (just check VIPM for package updates) Version 2013.4.0.186 This new release adds a right-click option called "Find Data Accessors" to Bundle by Name and Unbundle by Name nodes in a JKI State Machine. Using this feature will open a dialog showing all the frames of the JKI State Machine that access the data, as shown below:
  17. Hi Ben. Thanks for your help trailblazing with VIPM on the Mac! I don't have any experience with High Sierra -- I'm still on Sierra (10.12.x). Are you using VIPM Pro or Community Edition? That might be the issue. I just did a test and I can successfully build a package on Sierra using an internal test build of VIPM 2017f1 for Mac (yes, we're working on it). The package does have VIs in it and they get installed into the correct location. However, for some reason the installed package doesn't show the VIs in the palette correctly. It looks like it's a problem with the MNU files that get created.
  18. Hi All, There have been reports of issues downloading OpenG packages using VIPM, due to an outage at SourceForge.net (get status updates here). In the meantime, you can install all the latest OpenG Toolkit packages using this VI Package Configuration file: OpenG Toolkit - 2018-02-28.vipc
  19. You're welcome @Ben Stern. I think this is an interesting technical area and it would be nice if we were able to get the VIPM API working on Mac. I've created a case in our issue tracker for this: #17827. As always, we can't commit to a timeline for a fix, but wanted to let you know that it's in our tracking system.
  20. OK, I was able to call a built *.app on Mac from the command line with arguments (you actually have to execute the *.app/Contents/MacOS/Application file inside the bundle). So, it would seem that it should in theory be possible for the VIPM API to work on Mac. However, this would take some development effort on the VIPM side of things (not just on the VIPM API library).
  21. Hi @Ben Stern. That's an interesting question, and I can see how it would be very useful to have the VIPM API working on Mac. It's not currently possible (meaning, the VIPM API won't work on Mac). I don't have much experience calling built LabVIEW apps on the Mac from the command line with arguments. Do you know if it's even possible? On Mac, Applications that run in Finder are a little bit different than command-line executables (but, keep in mind that I'm not a Mac expert). I'm thinking there's probably a way to make this all work, since it's only software...
  22. I’ve created an issue in github for tracking the fix for this: https://github.com/JKISoftware/JKI-VI-Tester/issues/12
  23. Hi Norm (@Viper). Great question and you're not the first one to want this feature -- I'd like it, too. No, right now that's the only way to do it -- by unbundling and building a cluster of data yourself. EasyXML doesn't look at the data inside of classes, unfortunately.
  24. That's great that you can see the packages, now. Can you describe what you mean by a "MacOS JKI VI Tester" package? I'm assuming this might be the special Mac-compatible package I shared with you yesterday. We didn't actually make that available to the public inside VIPM -- my guess is that it says "unreleased" in the repository information.
×
×
  • Create New...

Important Information

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