Jim Kring
-
Posts
2,200 -
Joined
-
Last visited
-
Days Won
105
Posts posted by Jim Kring
-
-
On 11/12/2021 at 2:46 AM, ricardoszf said:
Hi Jim,
Following your directions, I copied all the folders and files listed in the C:\ProgramData\JKI\VIPM\databases\LV 21.0\mb_master\files-installed.
Now, I can use the Plasmionique Modbus Master Package in LabVIEW 2021 running in Linux Opensuse Leap 15.2.
Thank you very much for your guidance.
I hope that JKI can release an updated VIPM for Linux.
We are trying to work with LabVIEW and Linux in order to benefit from the reliability of both.
Best Regards,
Ricardo
Hi @ricardoszf,
We have just released a beta of VIPM 2022 for Linux.
There is an announcement and download link here:
Please post in the VIPM 2022 for Mac and Linux beta forum and let us know how it works for you.
-Jim
-
Note: Official releases of VIPM 2022 for Windows and Linux are available here 👉 vipm.io/desktop
What's New in VIPM 2022 for MacOS and Linux- VIPM is now built as a 64-bit application, which greatly simplifies installation on 64-bit Linux and improves compatibility with newer versions of MacOS that dropped support for 32-bit apps.
- LabVIEW 2022 (and earlier) support on MacOS and Linux, which the community has been increasingly requesting.
Screenshot of VIPM 2022 beta running on Ubuntu 22.04.1 LTS 64-bit
Download VIPM 2022 beta for Mac and Linux
- macOS: vipm-2022-beta-macos.zip
- Linux: vipm-2022-beta-linux.zip
Requirements
- LabVIEW 2019 Runtime Engine (RTE) - Note: If you have LV2019 or greater installed, then you probably already have the LV2019 RTE
- 64-bit Operating System
Installation (Mac)
- Unzip download and copy "VI Package Manager.app" to your Applications folder
Installation (Linux)
- Unzip contents of the download into the /user/local/JKI/VIPM/ folder
-
Ensure that the user account that will run VIPM has write permissions to the following folders:
- /etc/JKI (you may need to create this first as sudo and then give write permissions)
- /user/local/JKI/
- /user/local/JKI/VIPM/
-
For installing packages with VIPM, you will need write permissions to various folders under the LabVIEW installation folder, such as:
- /usr/local/natinst/LabVIEW-2020-64/
- /usr/local/natinst/LabVIEW-2021-64/
Troubleshooting
VIPM's error logs may be found here (in the "error" folder inside the folder where you are running VIPM):
- /user/local/JKI/VIPM/error
-
Hey Kevin,
This is an interesting use case. Does your package contain items for both LabVIEW and Test Stand within the same package?
-Jim
-
Sorry for the trouble. It looks like the older installers is having problems.
You might try upgrading to a newer version of VIPM.
https://www.vipm.io/desktop/versions/
You can also download the Random Number Within Range.vi directly here:
-
Hi @TimS-Bench. You can used both the Free (Commercial) and Community Edition in order to download and install the BLE Toolkit for Labview. No problem.
-
Hi @plasmapper, The packages should be all published now. Please let us know if there's anything not showing up in VIPM or if you need additional support.
-
Hi @plasmapper,
thanks for publishing your packages.
we have been working through some technical challenges lately with a cloud service provider and our workflow.
you’re doing everything right on your end of things and we just need to fix a few things on our end. I’ll work to make sure your packages go through and get them associated with your user account.
Jim
-
I'm wondering if it would make sense for your build tools to check and set the appropriate keys in VIPM's settings file?
C:\ProgramData\JKI\VIPM\Settings.ini
[General] check for updates on startup?="FALSE" Check new ver. of App. on startup?="FALSE"
You could check these and set them, prior to launching VIPM (when you detect that VIPM is not already running).
Something like this:
-
The "quiet?" argument is only exposed on some of the VIPM API calls -- it probably needs to be exposed on more/all of them.
Let me know if you need help solving your specific use case. We're working on improvements to the API and CLI...
-
It looks like you may be on an M1 (ARM) Mac. If so, LabVIEW and VIPM are not yet supported. NI aid working on this, but it probably won’t be ready until 2023.
-
@Joerg Hampel great ideas!
One question that came to mind is about which API a method is being called and whether it’s being called with the quiet/silent argument was set to TRUE.
The intended behavior is that the quiet/silent argument will suppress all dialogs. However, it’s totally possible that some of these dialogs may have slipped through the cracks — that would be a bug.
Thanks,
Jim
-
Hi Francois. We're doing some testing of a VIPM 2022 beta candidate. This may be fixed, and it would be great if you could confirm.
I'll ping you off-line...
-
Fantastic! 🏆
-
Can you take a look at these Knowledge Base articles on how to resolve this issue, and let us know if that helps?
-
Hi @Patrick. I think we've seen this issue show up for icons that have a lot of transparent elements and no frame on them. If you fiddle with the icon in the icon editor, sometimes whatever part of LabVIEW that's drawing the icons will "wake up" (for lack of a better term). LMK if you're able to make that work...
-
1
-
-
I forgot to add:
If you find any bugs with VIPM, we have a public issue tracker here:
https://github.com/vipm-io/vipm-desktop-issues -
Hi There. Thanks a bunch for reporting this issue and how you worked around it. I had some additional questions, so that our team can try to reproduce the issue.
When you say you "clicked VIPM > Uninstall for LV 2021" can you describe a more about how you got to this action? For example: is this option/action within LabVIEW (Tools Menu), NI Package Manager (LabVIEW / VIPM uninstallation), VIPM (option in the VIPM Main window), Windows Add/Remove Programs, etc.?
Also, if you have any screenshots, that would help, too.
-
1 hour ago, Samuel said:
Hi Jim,
Great, that works like a charm! Thank you very much!
Fantastic! Glad it worked for you.
-
Hi Samuel,
You're right that LabVIEW will automatically add anything it finds in instr.lib into the Instrument Drivers palette.
Note that if you name your installation target folder with an underscore at the beginning of the folder name (e.g. "_My Instrument") then LabVIEW will not automatically add it to the palette. That might be the best work-around if you need your VIs installed under instr.lib
Hope that helps. Let me know...
-
Hi Arly,
One thing you might look at is to be sure that you don't have a "/" characters both (a) at the end of your `base URL` and (b) the beginnings of your `path` inputs of your GET/PUT/POST method calls. Another thing to look at is that you have the right headers configured.
Here's an example: JSONPlaceholder Example.vi
-
OK, I'm glad you found a solution. I hope the JSON tool works well for you on your project.
-
It looks like VIPM is not connecting to the Internet successfully.
Can you look in the Settings and experiment with the proxy settings?
-
Hi @JosephK.
Can you try opening VIPM and updating its package database by clicking the Refresh button?
Then you should be able to find and install the missing JKI Serialization and JKI Unicode packages.
-
I’m glad that worked for you @Alexei k!
VIPM on Linux problem
in VI Package Manager (VIPM)
Posted
Hi @tizchangal and @Angel Guo,
We have just released a beta of VIPM 2022 for Linux.
There is an announcement and download link here:
Please post in the VIPM 2022 for Mac and Linux beta forum and let us know how it works for you.
-Jim