Leaderboard

Some advanced users are asking for support to install VIPM for Windows onto a Docker container. This would allow creating fully automated build processes that spin up virtual machines that have LabVIEW and VIPM installed on them, so that VI Packages can be created automatically.

I'd love to see these three License-related improvements to VIPM: 1) First, a main window column showing the package license, so it becomes very easy to see whether a package is open source, freeware, proprietary/custom, or something else. It'd be nice if the column title could be clicked to sort sort packages by license type: 2) To complement this, a change to the filter box with options to filter by license type, or maybe a second filtering box for this specific purpose. This would further help those searching for packages to focus on finding one they can afford and actually u

I think I see what you're saying -- if an older version of the package is published in a repository, but the installed/latest (i.e. displayed) version is not published, it would be helpful to know that it's a development version that's not yet "officially" published to the repo. This is different, perhaps, than a package where no versions are published. Idea: Maybe VIPM should display "Local" as the Repository name if no versions of the package are published. This deserves some more thought, for sure. I'm glad you have a workable solution, for now. Thanks for sharing these ideas.

Currently at our company we are building internal toolkits which we use for projects, but do not put it to LVTN. Toolkits are published via OneDrive, everyone has mapped same local folder as repository in VI Package Manager. Different toolkits are handled by different developers. And sometimes there is a situation, when new version of toolkit is built, installed locally and tested, but it is not published to our local repository. It would be nice (I understand that on the other hand it is not such a common case) to have it in such a way, that: - developer installs new version of

Just the idea - not sure whether it is possible to implement. There are some packages, which are used as dependencies in other packages. And, we can find dependencies of the packages by sending package to configuration; but we can not find packages which are dependent on some particular packages. If we could do something like right click on the package in the list -> Find dependent packages, and it would show us list of packages (ideally even not installed) which use that package as dependency, that could be sometimes useful. Now, for example, we use some package as dependenc

Hi, I would like to ask for a help with the following issue: I am trying to distribute VIP file with some dependencies, which are not published on VIPM. Hence, I added them to VIPC and would like to distribute this VIPC with VIP file. Is this somehow possible?

Howdy V, I have not previously done exactly what you are asking, but have done some similar tasks. We use VIPM Pro and a local repository to distribute packages not found in the public repositories; not only our internally developed packages. First, using VI Package Builder's Destinations and Source File Settings pages you can easily include the file and specify where it is installed. Second, using the Custom Actions you can specify a VI to run Before or After the package install. Use the Generate VI button to create a template VI and save into your package project; I create a C

I do not know what I am doing wrong: I have an account on https://www.vipm.io/ where I can log in. I have VIPM installed and it was just recently automatically updated. I am able to install i2 JSON for 2018-64 I am not able to log in for "community" or "free" status. When I choose in the new window "Use existing JKI account" I get an error message, when using the account data for www.vipm.io. I also get an error when choosing "Sing up for a new JKI account". When pressing "Forgot your password?" an new tab in the browser opens where I can write my mail address and it tells

Hi, I am having an issue with functions palette I generate in VIPM. The palette is generated and behaves correctly in LabVIEW, however, when I click "show in palettes" in VIPM after installing toolkit, instead of my functions palette, Agilent 34401 palette is displayed. Any idea what might be wrong?

John, check out "Test Runner Pre-build action.vi" in the 1.0 release. I'm not sure what the current version is on LVTN, but you can find 1.0 on GitHub: https://github.com/JKISoftware/Caraya/tree/release/1.0.0/src The first snippet below is the Pre-Build action itself, the second is the actual guts of where the test gets invoked. Let me know if that doesn't get you started in the right direction or you have more questions.

Hi guys, I've written this small wrapper for Run Tests Programmatically which I can just drop in any of our projects, it will find the uni tests in the folder structure and run them. It works perfectly except there is no way to change the result format of the test results. This wrapper also drops the results into the repo so they will be part of the commit/pull request and easy for the reviewer to see. The text result format would be easier to see in Azure DevOps than XML. Is there a way to change the result format for this vi (other than hack it with vi server)? It seems to be

Here was last answer from IT which solved my problem : Maybe our problem is not AV itself but something else… I just put this machine xx.xx.xx.xx under a policy that has only AV enabled.

For keeping track of used packages for our projects we'd like to put a list of used packages to our measuring data. That way we could later on see if a specific problem we encounter with our measurements might be due to the used packages. Is there an easy way for this? The best way I can think of right now is saving the names of installed packages out of VIPMs program data folder.

Thanks, that worked.

Building a VI package can take quite a while. For our Release Automation Tools, it takes about 20 minutes. Even though we build our packages on the build server now, it would be great to be able to feed back the progress of the build process to the CI system. As an example, the NI Application Builder API offers "progress bar" events, which you can register for and then show the progress details as you see fit: The VI Package Builder shows at least a few pieces of progress information in its status bar. Maybe these could be "routed" back to the VIPM API?

The trouble has been solved by IT. it was due to antivirus "cybereason" which was blocking .net for VIPM 2020. Thanks for your advices.

Hi @Jim Kring That worked😃. I had already gotten around the issue by uninstalling VIPM from Programs and Featuresafter having uninstalled it from NIPM.But then as soon as VIPM was reinstalled and updated again from its automatic update feature the issue in NIPM was back. As I suspected...The folder you sent was accepted as a source though so with that it is possible to do a repair without everything halting on the VIPM error. PS. NIPM is really terrible (compared to VIPM e.g.); From NIPM you cannot even repair VIPM without having to repair almost every component there is of Lab

Some packages (specifically if using NI License Manager API) require VIPM and LabVIEW to be started as administrator. It'd be great if there would be a "requires admin rights" flag for the package.

Hello @Jim Kring, thank you for the provided files for unpack/repack the package. I've tried to implement post-build action, but seems that there are 2 issues. 1. Seems, that post-build action is not executed. I've put breakpoint to post-build action VI - and nothing happened during the build, VI was not executed. Also, spec file was not modified. Could it be the bug, and post-build action is disabled for Community edition (the same situation as with flags?). 2. I've prepared VI in order to modify package manually (as post-build action was not called). When I

Thank you @Jim Kring, now it is clear.

I'm not sure whether this place is proper for this idea, but as vipm.io directly relates to VIPM itself, let me write it here. The point is that now toolkit could contain some links in the description. It would be nice to open them in new tab, and not in the current. This is small detail, but it actually makes users leave vipm.io while browsing some toolkit's homepage, or something. Of course, there are many ways of how to open link in new tab, but I guess it would be nicer that this would be the default action on simple left-click.

There has been some problems with the whole installation. Therefor I tried to do an update. There was updates but when I tried do install it the installer said "Another installation is in progress. You must complete...". I checked running processes. Restarted computer. Nothing helped. What can I do?

I've tried it and it works as expected - so it is possible to browse external links without leaving vipm.io. Thank you for this change!

Thank you, Jim. I'll put it through its paces and let you know if I find anything noteworthy.

I believe that is what I was looking for. https://github.com/JKISoftware/Caraya/issues/112 It is coming in 1.2

Since there does not seem to be any actual security issue it could be just a waiting game. I think my IT department might be able to submit the executable for reevaluation or as a false positive, I will see if I can get it fixed that way. Thanks for the help.

I understand and I don't mind helping improve great products like yours. When I started the day yesterday, I opened LV2020 to work on one project. Upon completion, I closed LV2020. A few hours later, I had to work on another project that used LV2019. That's when VIPM opened and I closed immediately closed it. Finished my work in LV2019 and closed it. Later I had to open it again and VIPM opened along with it again. This morning during our initial messages. I opened LV2019 to make sure I was correct in my replies. I then close it and opened LV2020. That's when I noticed no VIP

It appears that in the localizer tool kit the boolean tags are reversed. That is when setting Label.False text it changes the true text for the boolean. { "Key": "Front Disengaged.False", "Phrases": [ "FRONT DISENGAGED", "frente desenganchado", "" ] }, give this result:

Thank you @Jim Kring for the KB and for the suggested workarounds. We were considering the option of adding toolkit directly to source, but then decided simply to get rid of it completely since we've used it just as simple DVR-based lookup table. Moving to Tree Map was not possible, because it supports LabVIEW 2019 and later, but our project is done in LabVIEW 2015...

Hi again, Ivan. I went ahead and created a new Knowledge Base entry for this issue, since many others have experienced this error message: Error 1357 during a package build (File Already Exists) Let me know if that makes sense and/or if I missed anything (other possible workarounds or made any misstatements in the recommended workarounds).

Hi Again. Update: To make this easier for you and other users, we've updated the package details page with a "Download Package" button, as shown below. Please let me know how that works for you, and thanks again for the great question/feedback!

We've implemented the following solution. One Drive is mapped to the same location on all PCs (Public Documents), and we have shared one folder as repository folder. So we could publish packages to that location from any PC, and scan it as VIPM repository. Thank you for your help, Sincerely, Ivan.

Hi @James@Work. Thanks for posting about your experience with this. I'm sorry that JKI Design Palette was interfering with QuickDrop. Thanks for the good suggestion on including better documentation/instructions for how to work around this and for uninstalling it. I'm glad to hear it's working for you now.

Thanks Jim. That was exactly what I was looking for.

I was surprised to hear in the state machine course the best practice of adding states at the front of the state queue. I've always added them at the back under the theory that I'm "queuing up" states to be run, but I don't want to hijak the order of exectution if there's already seme states enqueued. The only time I add to the front is in an interrupt type situation. Can someone explain why adding to the front would be considered best practice?

Suppose you have an architecture where states calls sub states to do the details of the action then you have to queue to the front. Example of a motor stage with a break: Top level commands queued are 1) Move_To_Pos >> A 2) Move_To_Pos >> B where state Move_To_Pos (PosArg) issues the actual string of commands or states: Break >> Off Goto >> PosArg Break >> On The initial queue after 1), 2) are queued will be: (Front) Move_To_Pos >> A; Move_To_Pos >> B (tail) which if you use add to front of queue g

I am having trouble installing VIPackage Manager 2020. I keep getting the following error: Any help would be appreciated.

A little more info I found when playing around: I located .mnu file responsible for my palette in LabVIEW directory and deleted it. Now, as expected, show in palettes does not work. Also, my palette disappeared from LabVIEW funtions palette. When I restore .mnu file, palette is available once more, however, show in palettes displays Agilent 34401 palette after clicking again.

Similar issue, im not able to activate this via email. I send out the email request and never receive an Activation code. Is there an alternate method of activation available? Fixed now, looks like my account was not setup to receive emails from JKI

Hi Everyone @Mads Toppe, @szymsciupak, @wolfkil, This is a known issue that affects some people behind corporate firewalls. In VIPM 2020.1 (still in beta), you will be able to download packages without a sign-in and hopefully this will resolve the pain point. Thanks for your patience. -Jim

Hi Thomas, Actually, we use some 32-bit shared libraries, including OS libraries and also some 3rd party libraries, like the OpenG Zip Tools. For the MacOS beta, VIPM migrated to using command line zip/unzip tools and dropped a couple minor usability features that maybe nobody will notice (like extracting lvlib/lvclass icons from the XML file, which requires zlib deflation). However, for MacOS, we figured it was better to have things mostly working OK in 64-bit than not at all. For Windows, we wouldn't want to lose any functionality. I hear you about the memory limit issue. I hope

Hello, I have exactly the same problem. When trying to sign in or create new account, I get the message as in the screenshot attached.

I don't see the way to "ignore dependency". Still looking through help.

Curious if there is any plan to ad LV2020 support?

Hello LV Gurus, I am creating a simple GUI to control a web (specifically RESTful web server) based DLI Web Power Switch Pro I have three problems: What is the "Base URL" Is it just the IP + port (e.g. http://192.168.0.100:80) or the whole URI including the path to the web server (e.g. http://192.168.0.100/restapi/relay/outlets/0/state/) Where and how do I insert the cross-site forgery ignore in the header (e.g. X-CSRF:x) with your REST API? The Default Header list does not include X-CSRF. Do you support Basic and/or Digest authentication? I get "Unauthorized" error

We just released a new build with 2020 support https://www.vipm.io/package/jki_design_palette/

Hello All! I'm working on integrating the Caraya test framework into our CI process. As of now, we are using a Jenkins server to manage our builds, but I'm looking to add our Caraya unit tests to that equation. I'm relatively new to the CI world, but have a good amount of experience using Carayas built in test reporting functionality (the text report version). Ideally, upon unit test failure I would like to have the full report sent to the user via email showing them which unit tests did not pass. I know some of this is handled on the Jenkins side, but I'm more so curious abou

Is this going to be in the next VIPM version?

Hey Ruslan, Thanks - I was able to take that dialog window out of my project pretty easily. Not sure what version of LabVIEW you're using, so I saved it back for 2013 just in case. The one dialog window is effectively two clusters stacked on top of each other. First I make the selection cluster visible, then when a user selects which option they want, I hide that cluster and the Name and Apply buttons are visible beneath it. Happy to answer any questions you've got on it. -Nate Add New Specification.vi

Hi guys, Just wondered if there's any way (using VIPM File Handler) to Refresh a VIPC to reference latest versions of listed packages (assuming they're already installed in VI package library) ?. Alternatively, any plans to add the ability to Add Packages to VIPC by package name rather than scanning a Project ? BR. Chris