Hi, I'm a new Arch user having migrated from Ubuntu a few weeks ago. I've been stuck for several days trying to get the National Instruments Labview runtime engine installed. It is an easy process on Ubuntu so it must be possible with Arch. I'd prefer not to operate outside of pacman (ie. installing with rpm or dpkg) based on what I've read in the forums.
Labview Runtime Engine 86
Download Zip: https://urlcod.com/2vKwe5
The Labview runtime engine is a free download from National Instruments and allows programs that are generated by the Labview developer package (expensive) to be run on any box without having the licensed Labview software installed. This is handled with two .rpm files that one downloads from the NI website after registering there. You must download the .rpm files appropriate for the version of Labview that generated your executable. (Note that executables generated by Windows Labview and Linux Labview are not interchangeable) For reference, those files can be found here:
and rebuilt lvtest from scratch, but I still can't get my Labview applications to run. For clarification: these separate application files are what I was referring to as "executables" since that is how they are identified in the file manager. They are not part of the .rpm files I'm trying to install. These custom-made executables are built on another box that has Labview's full developer software package. They will run on another computer without the licensed Labview software provided the two .rpm files are installed correctly. The .rpm files generate the (free) runtime engine. So when I set this up with alien -> .deb -> dpkg on Ubuntu, a simple double-click on the application/executable file starts the Labview runtime engine and all is well.
OK, I'm making progress. I took a look at the successful runtime engine install on the Ubuntu box. I found that dpkg copied the alien-converted rpm packages to /usr/local/lib/ with root privileges. The only way I can launch an application (foo) generated by Labview's developer software (on a different computer that I don't have access to) is to double-click on the foo icon. According to the icon properties, this tells Ubuntu to "execute". I have no idea how to run it from the terminal, including just typing foo. And yes, the permissions are executable.
Ka-ching! Well solved Xyne. Your first suggestion did the trick. The Labview runtime engine is now functioning here on Arch. From the runtime GUI I can open foo and it runs perfectly. The export LD_LIBRARY_PATH stuff is also necessary before running foo.
where foo is the Labview application built previously on another machine. I was expecting that typing foo at the terminal would open the runtime engine AND foo. But it only opens the former and stops there, waiting for me to specify an application/executable. It appears to be ignoring foo even though it was explicitly installed by PKGBUILD. So I'm essentially using foo to only open the RTE -- from there I must open foo from the menu. Why is that?
That's essentially what's happening. Since I can't find any script in the package of .rpm files, the only way I know how to get the runtime engine (RTE) going is by launching the pre-built application foo. This starts the RTE, but it is not aware of foo so it halts and asks me to open any file of my choice via the GUI. So I click through the directories until I get to foo. It's not the clean solution I was hoping for (i.e. what happens with the RTE on Ubuntu as described in earlier posts) but it is a solution.
For the sake of completeness, here is the detailed procedure for installing the LabVIEW runtime engine (RTE) on Arch, relying entirely on pacman. This assumes you have an application `foo' that was built by the premium version of Labview with the developer package. You must know the exact version of Labview/Linux that produced foo. Download the corresponding two .rpm files that will generate the RTE after registering on the NI website. Extract the various libraries from the .rpm files first (independent of PKGBUILD) to see how things are named. You'll need that information to edit the following PKGBUILD for your specific version of the RTE. Then put just the two .rpm files in the same directory as the PKGBUILD file.
ActiView is the acquisition program for the ActiveTwo system. It is an open source program written in LabVIEW. The National Instruments runtime engine is needed for being able to run LabVIEW executables without having LabVIEW installed on your PC. You need the LabVIEW runtime engine when you want to run the ActiView executable without having LabVIEW installed on your PC. The ActiView window is resizable. The minimum window size of ActiView is 1200x650 pixels. If your monitor has a lower resolution than the selected ActiView, then you will only see a plain gray screen. When you want to go to the source code of ActiView, go to the about tab and then click on the red square. (you need to have LabVIEW installed for viewing/editing the source code) All BioSemi downloads contain both a executable (LabView RunTimeEngine required) and the LabView VI with sourcecode (LabView Full or Community required)
LabVIEW includes a compiler that produces native code for the CPU platform. The graphical code is converted into Dataflow Intermediate Representation, and then translated into chunks of executable machine code by a compiler based on LLVM. Run-time engine calls these chunks, allowing better performance. The LabVIEW syntax is strictly enforced during the editing process and compiled into the executable machine code when requested to run or upon saving. In the latter case, the executable and the source code are merged into a single binary file. The execution is controlled by LabVIEW run-time engine, which contains some pre-compiled code to perform common tasks that are defined by the G language. The run-time engine governs execution flow, and provides a consistent interface to various operating systems, graphic systems and hardware components. The use of run-time environment makes the source code files portable across supported platforms. LabVIEW programs are slower than equivalent compiled C code, though like in other languages, program optimization often allows to mitigate issues with execution speed.[10]
LabVIEW has a direct node with modeFRONTIER, a multidisciplinary and multi-objective optimization and design environment, written to allow coupling to almost any computer-aided engineering tool. Both can be part of the same process workflow description, and can be virtually driven by the optimization technologies available in modeFRONTIER.
Yes, you can view the LINX source in the LabVIEW MakerHub GitHub Repository. Additional resources used for LINX support on BeagleBone Black and Raspberry Pi are located in the meta-labview and lvrt-deb-pkg repositories.
To restart the LabVIEW run-time you can right-click the target in the LabVIEW project and got to UtilitiesReboot; despite the name this will only restart the LabVIEW run-time and will not reboot the target. If you SSH into the target you can also run sudo systemctl stop labview.service to stop the LabVIEW run-time and sudo systemctl start labview.service to start the LabVIEW run-time.
A chroot is a Linux construct that allows a process (like the LabVIEW run-time engine) to run as if an arbitrary directory is the root directory. The way that we use a chroot with the LabVIEW run-time engine is to act as if LV was running within a very lightweight virtual machine. There are 2 reasons that LabVIEW runs within a chroot on the BBB/RPi2: 1. Using a chroot we can make one installer which will run on several different Linux distributions and devices since the chroot contains its own set of system libraries and other operating system files. 2. The LabVIEW run-time engine is compiled with options that make it incompatible with the system libraries that are included in the default operating system images used with the BBB and RPi2/3, so the chroot allows us to include a set of system libraries for LabVIEW to use that are compiled with options that are compatible.
Yes, just SSH into the target BBB or RPi2 and run sudo schroot -c lv -r and this will create a new shell within the chroot. From here you can examine the file system and run other commands in the same environment that the LabVIEW run-time engine is running in. When you are finished, you can run exit to return to the normal shell.
I must be dumb. I downloaded all the files into a folder called nanov2. and unzipped the one called nanoVNA_V2Plus-0.10.zip. It created new folder called NanoVNA_V2Plus-0.10 in which there are 4 files. I ran the file V2P4_Test_R0.exe and it just came up with an error message immediately about nor being able to find LAbview Runtime_engine. Teh files with numbers on seem to be unused and unchanged! What am I doing wrong? regards Mike
So, must I understand that, apart from the software (the various zip files), I must install some other software (such "LABview runtime engine")?I've installed both variants of Joe's software:* The first one, not including NI-VISA* The 2nd one, including itBut neither worked. Both showed 10 error dialogs at start-up complaining about missing procedures/libraries... Then, when trying to connect to the nanoVNA, the first one didn't allow me to select a COM port, whereas the other allowed me, but the Link button did nothing.Thanks & regards.
The files are a spanned ZIP containing the runtime engine as well as NI-VISA. There should be no need to rename files or to download other files. I use 7-ZIP.The software that is included with this spanned ZIP is fairly old. I ended up moving to a common code base and porting it over to the original hardware. There are now two branches, one for the V2 Plus, the other for the original hardware. Once you have the runtime and VISA installed, there is no need to reinstall them. Just download the software for your hardware and copy it to where ever you like. I strongly suggest reading the manual before you waste too much time trying to use it. It's nothing I would suggest a beginner attempt to use, rather stay with one of the many supported programs available.This short video shows some of the latest changes. =scZ3kZ4Q2sQ 2ff7e9595c