Jim Kring
-
Posts
2,200 -
Joined
-
Last visited
-
Days Won
105
Posts posted by Jim Kring
-
-
@ThomasT Thank you for reporting this issue. It should be fixed now -- please let us know. Thanks!
-
1
-
-
Hi @Simon Klein
Thanks for publishing LV ArgParse. It's really well put together. I have some questions and observations based on my first use:
It seems that the Output text from Setup (using the example VI) always returns the help text.
This is also true for when I pass only "-v" or "-h" as the Arguments. I'm not sure how -v or -h are intended to be processed and returned to the user, in this case.
-
Hi Oli. I'm glad that worked for you and you colleague. That's a great idea to have the installer check the permissions in the cache folder! I'll pass that idea along to the team.
Cheers!
-
The most likely culprit is that this package got installed when VIPM was running with administrator privileges.
please see this doc and let us know if that fixes it for you.
-
Hi Oli,
Can you try this latest build -> VIPM 23.3.2530
Also, please check you "C:\ProgramData\JKI\VIPM\error" folder for logsThanks for testing and providing additional info, and we'll go from there...
-
OK, that's good news. I'm not sure what "broke" and is preventing VIPM from exiting/launching LabVIEW. I think that NI has added some new "security" features that may be causing this.
-
1
-
-
Quote
When I click verify in Options/LabVIEW, I get the prompt that VIPM will restart LabVIEW and to save VIs. I then get the window that VIPM is waiting for LabVIEW to close. After about 30 seconds, it reopens the prompt that it will restart LabVIEW. It's an endless loop unless I cancel. (Firewall and other settings attached)
After you get the window that VIPM is waiting for LabVIEW to close, what happens? Does LabVIEW close? If you close LabVIEW yourself, manually, does it reopen LabVIEW automatically? If not, can you try opening LabVIEW manually and see if VIPM can reconnect and verify the connection?
-
1
-
-
The error message is showing that it can't reach http://download.ni.com/evaluation/labview/lvtn/vipm/packages/data_ahead_gmbh_lib_xlr8/data_ahead_gmbh_lib_xlr8-2023.4.0.2.spec
I can download this file with my browser, just fine.
It's odd that it's only this one package that shows an error, since I'm sure other packages are hosted on download.ni.com
Additionally, this error is unrelated to VIPM connecting to LabVIEW (other than both of these "features" of VIPM are using TCP-IP).
Sure, LMK if the VIPM upgrade helps and we'll go from there...
-
1
-
-
Also, you can send your troubleshooting file to us at support.vipm.io -> submit a request
You may also see something in the `/ProgramData/JKI/VIPM/error` folder that you can open and review/sanitize then copy+paste here.
-
1
-
-
Hi @JW-JnJ. Can you try upgrading to version 23.3.2523 here -> https://www.vipm.io/desktop/
Please let me know if that fixes the issue or if it persists.
-
1
-
-
Security feature 🤷♂️
-
In your initial post, I just now noticed that the `LabVIEWCommunity.app` bundle was the target/argument of the `chmod` command.
I would have probably targeted the whole LabVIEW folder:sudo chmod -R ugo+rw /Applications/National\ Instruments/LabVIEW\ 2023\ 64-bit/ -
2 minutes ago, Gary Johnson said:
Hi Jim,
I'm retired but still at it 🙂
The file is there now, and the pkg install works, after I made user.lib RW for Everyone, manually. Also had to do that for menus/Categories.
-Gary
Oh, good! You'll probably want to do that for various other sub-folders of LabVIEW, too (vi.lib, resource, project, help, etc.)
-
Hi Gary! 🙇♂️
It may take a few tries, but we should be able to get this all sorted soon.
Question, if you look in this folder, what do you see?
/Applications/National Instruments/LabVIEW 2023 64-bit/user.lib/_OpenG.lib/boolean/Does that folder exist?
Is there an LLB named `boolean.llb` in there?
Or, is there a folder named "boolean.llb"? Anything in it?Thanks for letting us know and for your patience with this, as it takes a bit of work to support Mac (and Arm) but we're trying
-
OK, we've repackaged the Advanced Plotting Toolkit as a new build (1.1.0.136) that is compatible with all Windows OS versions.
@Mattias Sjöberg, thank you for testing and confirming the issue was still present with the older package in the latest VIPM release.Please let me know if the new 1.1.0.136 release works for you.
-
Would you check to see if, by chance, the new build of VIPM 2023.3 (build 2523) resolves this issue (available here)?
If not, we we can work to re-release a new version of the package with adjusted meta-data, to allow it to be installed on any version of Windows.
-
You can download it here:
vipm-2023.3.1.2362-rc1-linux.zip
Note that this requires the LabVIEW 2020 or greater runtime engine. If you have LabVIEW 2020 or greater installed, you should be OK. -
Hi @tomlawton67. MacOS did a bunch of stuff to tighten up security in recent releases. It's taking a while to keep up with it all. It makes me wonder if it's an issue related to temp file security...
-
8 hours ago, Bakur said:
Hey Jim,
I'm having issue with vipm 2022 on CentOS7. I'm trying to install g-cli package from https://github.com/JamesMc86/G-CLI and it fails when opening .vip file due to not valid format.
I'm pretty sure it's not the fault of the file as it gets open without issues on Windows and vipm 2017 on CentOS7. Do you have any advise?I think we've figured it out -- the issue is that some packages (like G-CLI) have Extended ASCII characters and are not being read correctly in Linux and Mac. We've found a solution and should have a beta build of VIPM 2023 Q3 for Linux available soon for you to help test, if you're interested.
An issue was created here:
https://github.com/vipm-io/vipm-desktop-issues/issues/30-
1
-
-
Thanks @Bakur. I'll take a look...
-
There is an official release of vipm 2022 for linux, here, with fixes for working with labview 2023 q3 --> vipm.io/desktop/versions
-
I'm not sure about that one. You might need to contact NI or post in the NI forums, since this uses the NI third-party licensing and activation toolkit.
-
Hi @Dmytro
It appears the issue is that the publisher marked the OS Compatibility in a way that prevents it from being installed on Windows 10/11.
-
That’s great! 🥳
Fine grained control of package dependencies
in VI Package Manager (VIPM)
Posted
Hi Andrea,
The aim is for dragon.vipm.io to support this. Parts of it, under the hood, do already support it, but it's not yet exposed in the Package Dependencies UI.
-Jim