Jump to content

Search the Community

Showing results for tags 'linux'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Special Interest Boards
    • Professional User Interface Design in LabVIEW
  • VI Package Manager (VIPM)
    • VI Package Manager (VIPM)
  • 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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 9 results

  1. 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
  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. 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-15.0.0.1.noarch.rpm Yields an error as: "error: Failed dependencies: nisvcloc < 18.1.0 is obsoleted by (installed) ni-service-locator-19.0.0.49153-0+f1.x86_64" 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.
  4. 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?
  5. 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!
  6. This is covered in part in various places but I thought it might be useful to have it in one. I've got VIPM running on CentOS 8 but you have to jump through some hoops due to 64 bit, wayland and rpm signing! 1. Install support for the 32 bit RTE on 64 bit by installing the following packages: glibc.i686 libstdc++.i686 libXinerama.i686 libGL.so.1 2. To install the run time engine - you need to remove the digest checks since these have got more strict. In the run time engine folder edit INSTALL so the line that starts RPMOPT includes --nodigest at the end of the string. 3. Now follow the standard install instructions. 4. Before running VIPM run the command "xhost si:localuser:root" to allow the root user to launch a window process. I believe this is due to wayland. Hope that helps someone!
  7. 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.
  8. From the VIPM 2017 release notes: The only solution to this is to upgrade to VIPM 2017 if you want to install any packages built in that version. The problem here is that VIPM 2017 does not exist for Mac or Linux. In fact, version 2014 is the latest available download for those platforms. This means that any new package built with Windows cannot be installed on any non-Windows systems, effectively eliminating VIPM support for Mac and Linux. If you use VIPM on Mac or Linux, you may want to hold off on upgrading to LabVIEW 2017 until this gets resolved.
  9. It looks like VIPM 2017 is included with LabVIEW 2017, but it is not yet available for download on https://vipm.jki.net/download. This would normally be fine, except I noticed in the release notes that packages built with VIPM 2017 cannot be installed with older versions. This is a potential problem because anybody who has installed LabVIEW 2017 cannot currently distribute their newly built packages to people who are still using older versions of LabVIEW, since they have no way of getting their hands on VIPM 2017. Also, can anyone confirm that there will be Mac and Linux versions of VIPM 2017? If not, that will be a big problem for those of us who build packages on Windows then need to install them on other OSs.
×
×
  • Create New...

Important Information

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