Jump to content

Search the Community

Showing results for tags 'vipm'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Special Interest Boards
    • Developing LabVIEW Tools and Add-ons
    • Professional User Interface Design in LabVIEW
  • VI Package Manager (VIPM)
    • VI Package Manager (VIPM)
    • Dragon Beta
  • JKI Tools
    • JKI Flat UI Controls
    • JKI Design Palette
    • JKI State Machine
    • JKI State Machine Objects (SMO)
    • Caraya Unit Tester
    • VI Tester
    • JKI JSON
    • HTTP REST Client
    • JKI Simple Localization
    • EasyXML Toolkit
  • Legacy Tools
    • Legacy Tools
  • VIPM Community Add-ons for LabVIEW
    • JSONtext by JDP Science

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 25 results

  1. Hi, my name is Francesco. I'm Italian and i don't speak good english. I have a problem with the installation relatives VIPM in linux I follow the instruction but appear this message when i launch the command: sudo ./vipm Can't find library liblvrt.so.15.0 Make sure this library is installed in your LD_LIBRARY_PATH search path, or in /usr/lib To download the LabVIEW Runtime engine, go to http://www.ni.com/rteFinder?dest=lvrte&version=15.0&platform=Linux&lang=en How can i resolve this? Thank you so much and sorry for my english!
  2. Hi, I have LabVIEW Linux 2020.0.1 64-bit on Linux Mint 20.1. I installed VIPM 2017.0.0f1 according to the instructions with no problem, but when I want to verify the connection, I have this error in the log file : Could not connect to LabVIEW 2020 (64-bit) on TCP/IP port 3369, because LabVIEW 2020 is already running and using that port. Please close LabVIEW 2020 and try again. I tested every solution on VIPM website and forums but doesn't work. Full log file content: =========== START of VIPM 2017.0.0 (build 2018) Error Message =========== An internal VIPM 2017.0.0 (build 2018) Error has occured on: Tuesday May 11, 2021 at 04:50:44 PM = Automated Message Start = Error 42 occurred at F245EB04A0A76ECF8E676534A0E5DC7A Possible reason(s): Could not connect to LabVIEW 2020 (64-bit) on TCP/IP port 3369, because LabVIEW 2020 is already running and using that port. Please close LabVIEW 2020 and try again. Complete call chain: F245EB04A0A76ECF8E676534A0E5DC7A VIPM Configure LV Port.vi Options.lvlib:VIPM Options Window.vi VIPM Main Window.vi = Automated Message End = = User Defined Message Start = Testing the LV connection from the test connection dialog. = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> Options.lvlib:VIPM Options Window.vi-> VIPM Configure LV Port.v = Error Handler Call Chain End = =========== END of VIPM 2017.0.0 (build 2018) Error Message ===========
  3. Hi, I have two packages A and B. B is dependent on A version>= in dependencies). I successfully built Package A but then while building Package B I got this error. """" There was a problem building Package B. Error Details: Code: 1 Source: (No Package Info found for "packageA-") 96FD42B2A6437B734EC63B98E9EED24B in OGPM Class.lvlib:46D46467862C6022A7CA939401F1D0E3->VIPB.lvclass:DDA0A855BDB08E9AC01A4A891080E62F->BBD7971411AADF3E949AD5D04F9B412C->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi """" Kindly help me with the above issue. I have tried building the packages multiple times but couldn't solve this issue.
  4. 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 me that an email was sent. However, I nether get the mail, nor is it gone to my spam folder. What can I do to solve this. I rely in my largest project on the OpenG lib and the MGI lib, which was not a problem to install in previous time. Best regards Wolfgang Kilian
  5. Considering the tools developer having multiple binaries (such as PPLs, Shared Libraries) built for different systems ranging from various LabVIEW versions, bitness (32 and/or 64) & OS. A single Package may contain all the required resources to support multiple platforms. But when being installed, only the platform dependent resources actually get installed leaving other resources untouched. A great example for this kind of package is JKI Design Palette. It supports LabVIEW versions from 2015 and beyond, even includes support for both 32 & 64 Bit versions. Tried to replicate it with my package building, but to no avail. While digging deeper I came across the following detail and came know - this is actually possible with the VIPM package building process, But I couldn't find myself how to configure the VI Package Builder to do this. It would be really helpful if there any documentation available to carry out this process with VIPM Package Builder. Also check this post for PPL forward compatibility reference,
  6. I am trying to run VIPM on openSUSE Linux. On a fresh install of openSUSE, I installed the LV 2015 run-time and the 32-bit libraries below. I copied the JKI VIPM folder to /usr/local/JKI/VIPM sudo zypper install libXinerama-devel-32bit libX11-6-32bit libXext6-32bit Mesa-libGL-devel-32bit This allowed me to successfully run a 32-bit test application provided to me by NI support however I cannot run VIPM. jonathan@DESKTOP-L5EF9SK:/usr/local/JKI/VIPM> su Password: DESKTOP-L5EF9SK:/usr/local/JKI/VIPM # whoami root DESKTOP-L5EF9SK:/usr/local/JKI/VIPM # ll total 34508 drwxr-xr-x 1 root root 8294 Jul 1 12:44 help drwxr-xr-x 1 root root 10 Jul 1 12:44 icons -rw-r--r-- 1 root root 102497 Jul 1 12:44 License_Agreement.pdf drwxr-xr-x 1 root root 268 Jul 1 12:44 support -rw-r--r-- 1 root root 13 Jul 1 12:44 version -rwxr-xr-x 1 root root 35218160 Jul 1 12:44 vipm -rw-r--r-- 1 root root 36 Jul 1 12:44 vipm.conf DESKTOP-L5EF9SK:/usr/local/JKI/VIPM # ./vipm No protocol specified No protocol specified Fatal Internal Error 0x90FFFA4E : "AppEntryPoint.cpp", line 86 LabVIEW version 15.0.1f10 You will lose any unsaved work. For assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments. Aborted (core dumped) DESKTOP-L5EF9SK:/usr/local/JKI/VIPM # An internet search of the error code 0x90FFFA4E brings up this. What do I need to do next? The 32-bit LV 2015 Linux test application is attached in case it helps someone debug. I have been through a few road blocks just to get to this point. build.zip
  7. The customer installed LabVIEW 2020 SP1 When trying to use the LabVIEW Application Builder to create an installer it asks for the VI Package Manager Runtime Engine installer. After using the installer provided in this KB article (vipm-runtime-engine-19.1.3-windows.zip), it is now showing the following error: "The media you have provided is a different version of the requested media." The installed version of the VI Package Manager is 20.3.2540. Can you please provide the installer for the Runtime Engine
  8. 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 the toolkit; - VIPM detects that actually such a toolkit (based on name and version) has been previously installed from a locally configured (custom) repository; - if so, VIPM checks that this toolkit has not yet been published to that local repository; - it will display some icon similar to those which are in "VIPM Legend" list. In that case, developer would see that he has some toolkit which is not published - so either he will publish it, or leave it as it is. Also there could be warning similar to the one which is shown when VIPM is opened, and there are updates for the toolkit. And, when toolkit is published - icon is set as usually.
  9. 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?
  10. 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?
  11. The problem is with loading the LV2015 run-time supplied with vipm-17.0.2018-linux, which I tried to install on LV2019 Full for RedHat Enterprise Linux 8. There are verification errors, easily dealt with running "sudo rpm -i --nodigest labview-2015-rte-15.0.1-11.x86_64.rpm", and Most of the the other items (eg. nicurli) which refuse to install because the version 2019 .so libraries are newer can have appropriate soft links added. However, there is a basic architectural problem with nisvcloc. Trying an install ( as the script would, except it needs "--nodigest" ) as: rpm -i --nodigest nisvcloc- Yields an error as: "error: Failed dependencies: nisvcloc < 18.1.0 is obsoleted by (installed) ni-service-locator-" WIth "rpm -ql nisvcloc-15.0.0-1.noarch.rpm" , the files are: /usr/local/natinst/nisvcloc /usr/local/natinst/nisvcloc/bin /usr/local/natinst/nisvcloc/bin/nisvcloc /usr/local/natinst/nisvcloc/bin/nisvcloc32 /usr/local/natinst/nisvcloc/bin/nisvcloc64 /usr/local/natinst/nisvcloc/etc /usr/local/natinst/nisvcloc/init.d /usr/local/natinst/nisvcloc/init.d/nisvcloc Since the new ni-service-locator is a daemon under systemd, a simple soft link or manually adding the directories/files are not options. The daemon executable is /usr/sbin/nisvcloc. There isn't any directory structure as shown above for the nisvcloc rpm file at all. IS there a workaround to install VIPM 2017 on RHEL 8 ? Or do I need to wait for a new release to support LabVIEW 2019 Full for Linux ? Thanks to all for your time in reading my post.
  12. 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.
  13. Hi, I am trying to instal LINX for LabVIEW 2013 and I encountered a problem (see attachment). I am using Win 10 and VIPM 2019. TCP/IP port is 3363 and is checked. Under Win XP and earlier version of VIPM it was working. Any help is welcome. Thx.
  14. I have a *.lvlib file which has some VIs and non LabVIEW file.(say *.txt). Now I have the package built. (No much of configurations in the VIPB). After the installation of the package, the lvlib file is corrupted and the says the TXT file is missing but the file is present in the folder location. Looks like the lvlib file still points to the file in the temporary location which was created during package build process. I have attached a sample library with this thread. Thank in advance for any help on this. Regards, Bhaghyaraj. Sample Package.zip
  15. I tried installing the new VIPM2017 for Linux in a clean Fedora 27 virtual machine just to give it a try but I can't get it to do anything. I followed the two basic steps: 1) install LVRTE 2015SP1 which installs without any problems or errors 2) copy JKI folder to /usr/local as described in the instruction.txt When launching vipm I just get the blunt error: No such file or directory as shown below sudo ./vipm sudo: unable to execute ./vipm: No such file or directory What could be the problem and how could it be resolved?
  16. Hi, I work for Texas instruments and we heavily use VIPM for Package deployment to 1000 + users. Recently we upgraded the VIPM to 2019 and of late (Probably last 8-10 months), we are seeing users reporting VIPM throws this error intemittently and have to retry couple of times to get through the package installation. The error says " There was an error accessing the following repositories 1. LabVIEW Tools Network 2. VI Package network 3. OpenG mirrors list" We know this error is coming because we use OpenG packages as reusables. Any suggestions to get this fixed.
  17. I work for a company that is very tight with what we can and can't install. It's really a huge pain in the behind. I am always looking to improve what we are doing and trying to make things more automatic and simplified for our developers. If I download VIPM and develop something, for another to use it they all have to have VIPM and the same packages is that correct? How do companies that manage to successfully use VIPM handle the installation and propagation of packages to all their developers? We typically don't build applications but are always reusing old projects and code to speed up the development process. Thanks for any pointers. -- Kellen
  18. Hello, I have a pro license for VIPM 2018 and LabVIEW 2019 installed a newer version by accident. Can someone help me out and send me a VIPM 2018f2 release as a .zip file? Why isn't there a possibility to download older releases on the JKI website? I wrote to the JKI request 3 times and I have the feeling they don't want to help me. Cheers Gregor
  19. Hi all, I am using VIPM 2018. I am unable to open a VIPB file in my PC. I have attached the error that I see when I open the VIPB file. I am able to open the file in another PC which is having the same version on VIPM. Could anyone help me in understanding and solving this issue? Thanks, Bhargavi.
  20. Hi all, I am not able to install VIPM in my PC. The error is as attached below. Please suggest me how to overcome this error and complete my installation. I have tried to install the VIPM from the LabVIEW Installer.
  21. I need some help to remove this program, for proper installation, but I´ve been trying all day and this message keeps poping out , "there is a problem with this windows installer package. A program riquired for this install to complete could not be run. Contact your support personnel or package vendor". The problem is, i have not uninstalled properly. i have deleted files, so it is not removing from my control panel. please tell me how to uninstall or reinstall the VIPM
  22. It would be great if there is a preview window along with the description editor. Right now, after formatting the description with various tags (like bold/italics etc.,) I would need to build the package in order to see the formatting. If there is a preview pane along with the description, it would easy to see the final formatting. Thanks, Ajay.
  23. Hi, Please help... I am trying to create a .vip that will install my LabVIEW project as a LabVIEW project template (note: I have done this process a few time before with no issues) I have my project that I want to make into a template, everything works perfectly. I configure the .vipb, I build and install the .vip. I check the destination to see if my files have installed to the correct location, they have. Here's where the problem kicks in...... I open my LabVIEW project that has installed in the destination, and notice that the .png files in my project some are missing and some are saying missing. In my project I have .png files in various .lvlibs. The first .lvlib in the project has the .png's showing, however showing as missing and the expected location is saying C:\ which is incorrect, it should be in the location where my .lvlib is in the destination. The other .lvlib's don't even show the .pngs in the LabVIEW project explorer. Now checking on disk all the png's are there and in the correct location. In summary it looks as if as part of the vip install it is removing the link the .lvproj has to my .png files VI Package Manager Version : 2018.0.0f1 Jul 21 2018 LabVIEW Version : 2016 (32 bit) OS : Windows 10 Pro Version 1803 Any help is greatly appreciated Thanks in advance. Kev
  24. Hi, I see an option in VIPM to disable the automatic VIPM update, please see the snippet attached. Is there way to disable this programmatically. Is the value configured in this is stored any ini key?
  25. 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.
  • Create New...

Important Information

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