Jim Kring

Yes, that’s the general idea. Please let me know how it goes. BTW, we’re working on updated documentation here (and it’s far from complete) as there are a lot of new features in the works. https://docs.vipm.io/package-building/vi-packages-build-templates/ BTW: the documentation is in a public GitHub repository, so you can suggest edits by clicking on the little edit icon ✍️ -Jim

Done. 👉 vipm.io/package/jki_lib_vipm_api/

OK, I was able to track down the fixed VIPM API package here: VIPM API 2022.0.3.80 >> jki_lib_vipm_api-2020.0.3.80.vip @sbasavaraj can you please try this and let me know if it works for you?

I agree with your points an am very friendly to this recommendation. Would you be willing to collaborate on this effort? It would require writing unit tests, verifying the upgrade process, etc. Update: There's a pull request where @jyoung8711 did just this. I think we should take this step foward.

hi @sbasavaraj. I'll look into it. @Joerg Hampel to you recall where this left off? I've created an issue to track it, either way: https://github.com/vipm-io/vipm-desktop-issues/issues/14 We've been working on a real command-line interface, so I'm not sure if we actually updated the VI-based API.

Hi @Vishal. Which version of VIPM are you running? Upgrading to the latest VIPM 2022 has fixed this for some people.

Hi @adamarbor, OK, that definitely looks like a bug (and we may have fixed it -- or, it'll be fixed soon). What's the build number of VIPM you're running? -Jim

Hi @adamarbor, Thanks for giving VIPM 2022 on Linux a try. It's great you've gotten it to start up on Ubuntu (and give some errors) since that can be tricky with alien First, can you share which build number of VIPM 2022 you're running? Next, we've been putting some docs together on ubuntu here: https://docs.vipm.io/linux/ubuntu/ That doc is far from being super helpful at this point, so I'll share some info here (and we'll be updating those docs along the way). A.) Running VIPM as a root user. I noticed in your VIPM error log that it couldn't find the LabVIEW config file for the root user (shown below). /root/natinst/.config/LabVIEW-2022/labview.conf This means that VIPM was running as root and you have not (nor should you) run LabVIEW as root (which would create/save a LabVIEW config file the root user). Tricking VIPM-running-as-root to use your default user's LabVIEW config file To run VIPM as "root" and LabVIEW as "adam" you can create symbolic link at "/root/natinst/.config" (where VIPM is looking) that points to the "adam" user's natinst config folder (~adam/natinst/.config). Here is an example shell command to create such a link: sudo ln -s ~adam/natinst/.config /root/natinst/.config B.) Running VIPM as a normal (non-root) user Note that you may not want to run VIPM as root, but rather as your default "adam" user. However, running VIPM as a normal user will require you make various VIPM files and folders writeable to normal users. Files to Make Writeable to Normal Users (if running VIPM as a normal, non-root user) Here are a list of files and folders you will want to make writeable to normal users: The VIPM application folder and files: /usr/local/jki/VIPM The following folder and files here: /etc/JKI The LabVIEW folder and files: /usr/local/natinst/LabVIEW-2022-64 Also, keep in mind that when VIPM launches LabVIEW, if VIPM is running as root then it'll launch LabVIEW as root. You probably don't want to run LabVIEW or VIPM as root. We're working on a fix that will allow running VIPM as root (e.g via a "sudo" command) but have LabVIEW get launched by VIPM as the user who launched VIPM with the sudo command -- but, that's not implemented yet. I hope this is helpful to getting you up and running. Let us know how it goes...

Hi Joerg, Yep, this VI exists in several different locations... 🤪 Please go ahead and up-save to LV 2016 (or 2017) and submit a PR, if that works OK for you. We'll get a new build out.

Can you upgrade to VIPM 2022? https://www.vipm.io/desktop/versions/

Hi Joerg, Those notes are great! Question: Are you running LabVIEW Professional Edition or the Full Edition on Mac? - I'm not sure about vi.lib/wsapi. It might be a good idea to not rely on that for Escape HTTP URL.vi. If I recall correctly, such a VI has or does exist in several different locations. - You may be able to copy vi.lib/Platform/fileVersionInfo.llb over from a Windows machine.

See also: https://support.vipm.io/hc/en-us/articles/360045406692-Disabling-VIPM-service-System-Tray-startup-when-LabVIEW-starts-up

Also, please let us know which version of macOS you’re using. Thanks!

Thanks for posting these issues. There’s a good KB entry on how to configure permissions on Mac. I suspect that the error 8 and error 10 will be resolved once the permissions are adjusted, and that will help the downstream functionality to work. Configure VIPM to Download LabVIEW Add-Ons for macOS

You should be able to change this from the right click menu of the system tray icon. You can also disable that completely in the VIPM options dialog. Let us know if that works for you, or if it’s still misbehaving or unintuitive.

@drjdpowell might have other good recommendations.

I might try an approach where you first get all object items as JSON strings. Since they are all the same type (having three x, y coordinates), you can then iterate over the JSON Items (array of strings) and convert each of them to LabVIEW types "From JSONtext". Does this approach make sense?

There is a new build for Linux available: vipm-2022.0.0.2355-beta-linux.zip

Thanks for reporting this issue. Right now, the description on the website is taken directly from the package's spec file and the <nothing> string is getting removed because the website has to strip HTML tags from the description. We're considering good solutions, which might be to just let users manually edit the description on the website (and possibly add a flag that prevents it from auto-updating when new packages are published). Regards, -Jim

It looks like it could be a permissions issue. This article may help: https://support.vipm.io/hc/en-us/articles/360055884411-File-Permission-Errors-running-VIPM-on-macOS -Jim

Hi @RomainToro, Is it correct to assume you do have LabVIEW 2015 installed on your computer? Most likely, one of the VIs (or other LabVIEW files) in your package source folder got saved in LabVIEW 2020. In such cases, VIPM is trying to be "smart" and using LabVIEW 2020 to build the package (but it's not informing you about what it's doing). The solution is probably to try opening your source files in LabVIEW 2015 to verify that all of them are saved in 2015. Thanks for letting me know. -Jim

Is it just this package that is causing issues? Are you able to download other packages?

Hi @cmal, @ensegre, We have just released a beta of VIPM 2022 for Linux and Mac which is a 64-bit app that uses the LabVIEW 2019 64-bit Runtime Engine. It should work well with LabVIEW 2022 and earlier. 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

Hi All, We have just released a beta of VIPM 2022 for Linux (and Mac). This is a 64-bit application (it uses the LabVIEW 2019 64-bit Runtime Engine) which greatly simplifies the installation process (since it doesn't require any 32-bit support libraries). 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

Hi @Marco Pignati, We have just released a beta of VIPM 2022 for Linux (and Mac). 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