LabVIEW Runtime 7.0 Linux and Mozilla

I have successfuly instaled runtime plugin into Mozilla under linux. I copied plugin into mozilla plugins directory.
When I connect to any page with LV Remote Panel, the plugin loads the page, but after 100% it doesn't work. It just display gray rectangle, or the Remote Panel on incorect position. Does somebody has the same problem? Do you have any working example of Remote Panel web page which I can use for testing?
Thanks
Ondra

Hello Ondra,
Thank you for contacting National Instruments.
What version of LabVIEW are you running? To use the Run Time Engine (RTE) 7.0, you must be running LabVIEW 7.0.
If you are running 6.1 or earlier, you must install the corresponding RTE. To view LabVIEW 6.1 front panels in Mozilla, further steps will be necessary. Please follow the link below for instructions.
http://digital.ni.com/public.nsf/websearch/93D8AD6F55D6F91486256BE6006FB868?OpenDocument
Let me know if this does not solve your problem.
Sean C.
Applications Engineer
National Instruments

Similar Messages

Java(TM) Plug-in 1.4.2_03 under Mandrake/Linux and Mozilla

I'm having problems getting applets to load/run using Mandrake/Linux 9.2 and Mozilla 1.6. Apparently the classes are failing to load.
about:plugins in Mozilla shows that it has the Java plugin loaded, but when I try to test it using one of the sample applets at http://java.sun.com/applets/jdk/1.4/demo/applets/Clock/example1.html, I get the errors shown below in the Java Console.
I have a link in my plugins directory linking to:
lrwxrwxrwx 1 tim tim 67 Jan 17 22:33 libjavaplugin_oji.so -> /usr/java/j2re1.4.2_03/plugin/i386/ns610-gcc32/libjavaplugin_oji.so*
I PRESUME I've got some sort of configuration error, but I'm unsure where to begin to look - any help will be greatly appreciated!
Tim
Java Console Error Message Log
Java(TM) Plug-in: Version 1.4.2_03
Using JRE version 1.4.2_03 Java HotSpot(TM) Client VM
User home directory = /home/tim
<snipped "help" reference message from console>
Stopping applet ...
Joining applet thread ...
Destroying applet ...
Disposing applet ...
Quiting applet ...
Joined applet thread ...
Finding information ...
Releasing classloader: sun.plugin.ClassLoaderInfo@110278e, refcount=0
Caching classloader: sun.plugin.ClassLoaderInfo@110278e
Current classloader cache size: 3
Done ...
setWindow: call before applet exists:16956179
Referencing classloader: sun.plugin.ClassLoaderInfo@110278e, refcount=1
setWindow: call before applet exists:16956179
setWindow: call before applet exists:16956179
Loading applet ...
Initializing applet ...
Starting applet ...
Connecting http://java.sun.com/applets/jdk/1.4/demo/applets/Clock/Clock.class with no proxy
Connecting http://java.sun.com/applets/jdk/1.4/demo/applets/Clock/Clock.class with cookie " "
Connecting http://java.sun.com/notfound.jsp?requrl=/applets/jdk/1.4/demo/applets/Clock/Clock.class&refurl=UserTypedURL with no proxy
Connecting http://java.sun.com/notfound.jsp?requrl=/applets/jdk/1.4/demo/applets/Clock/Clock.class&refurl=UserTypedURL with cookie " "
Connecting http://java.sun.com/applets/jdk/1.4/demo/applets/Clock/Clock/class.class with no proxy
Connecting http://java.sun.com/applets/jdk/1.4/demo/applets/Clock/Clock/class.class with cookie " "
Connecting http://java.sun.com/notfound.jsp?requrl=/applets/jdk/1.4/demo/applets/Clock/Clock/class.class&refurl=UserTypedURL with no proxy
Connecting http://java.sun.com/notfound.jsp?requrl=/applets/jdk/1.4/demo/applets/Clock/Clock/class.class&refurl=UserTypedURL with cookie " "
load: class Clock.class not found.
java.lang.ClassNotFoundException: Clock.class
     at sun.applet.AppletClassLoader.findClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.applet.AppletClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.applet.AppletClassLoader.loadCode(Unknown Source)
     at sun.applet.AppletPanel.createApplet(Unknown Source)
     at sun.plugin.AppletViewer.createApplet(Unknown Source)
     at sun.applet.AppletPanel.runLoader(Unknown Source)
     at sun.applet.AppletPanel.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Caused by: java.io.FileNotFoundException: http://java.sun.com/notfound.jsp?requrl=/applets/jdk/1.4/demo/applets/Clock/Clock/class.class&refurl=UserTypedURL
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
     at sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
     at sun.plugin.net.protocol.http.HttpUtils.followRedirects(Unknown Source)
     at sun.plugin.cache.CachedFileLoader.download(Unknown Source)
     at sun.plugin.cache.CachedFileLoader.load(Unknown Source)
     at sun.plugin.cache.FileCache.get(Unknown Source)
     at sun.plugin.net.protocol.http.HttpURLConnection.connectWithCache(Unknown Source)
     at sun.plugin.net.protocol.http.HttpURLConnection.connect(Unknown Source)
     at sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
     at java.net.HttpURLConnection.getResponseCode(Unknown Source)
     at sun.applet.AppletClassLoader.getBytes(Unknown Source)
     at sun.applet.AppletClassLoader.access$100(Unknown Source)
     at sun.applet.AppletClassLoader$1.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     ... 10 more
Exception: java.lang.ClassNotFoundException: Clock.class

To determine if your browser can view applets, try
viewing the "Cubic" applet on the following page..
http://java.sun.com/docs/books/tutorial/2d/display/Cubi
.html
You will notice that you can manipulate the pattern of
the applet by dragging the colored squares. Thanks for the pointer - it does, indeed, work as expected.
It's a bummer that the "sample applets" are screwy, as that seems like a good place to go to confirm that you have everything configured right (well, it DID seem like a good place to go - it seems quite a bit less good now).
Thanks for the help,
Tim

Installing of LabVIEW runtime is cause of InTouch can't find its licenses

Hello All.
I need to run executable built with LabVIEW from Wonderware InTouch 2012 runtime. But If I install LabVIEW runtime to the target PC, InTouch runtime can't find its licenses and run in Demo mode only. When I uninstall LabVIEW runtime InTouch can find licenses again and operates in normal mode. Licences for InTouch consists of files on the hard drive and software protection dongle of unknown type, connected to USB port. I have tried LabVIEW runtime versions 2012, 2012f3 and 2013, installed from standalone distributions or with distribution of application built with LabVIEW, no differences. What can be cause of conflict? What can I try to do to run InTouch runtime and LabVIEW application simultaneously?
Target OS: Windows 7 Ultimate 64-bit MUI
Host OS: Windows XP Professional 32-bit Russian

Tortu wrote:
Have you verified if this behavior is present in other computers?
No, I have only 2 PCs for tests, both new and identical in hardware and software. I'm sure I will get same result on both.
Have you tried changing the port at which you connect the USB key?
Yes.
Did you restart the computer after installing the LabVIEW RTE?
Yes.
Have you tried installing the LabVIEW RTE before installing the Wonderware software?
Yes.
Can you access other USB keys when you have the LabVIEW RTE install or does all USB communications fail?
I have another software protection dongle for InTouch. I've tried it, it doesn't work too. USB in general is working (HID, USB flash drives, USB HDD).
Have you received any troubleshooting steps from Wonderware? Please let us know.
Wonderware support engineers sent me test license file which not require USB dongle. With this license file InTouch operates in normal mode when LVRT is installed. But it is impossible to use such license in production.

Several question s about runtime Engine, application builder and labview player

I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferry

ferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png ‏24 KB

LabVIEW for Linux and hardware registers

Hi all,
I'm considering using LabVIEW for Linux in an upcoming project based around
PC/104. As the only way to communicate to the PC/104 module inputs is via
hardware addressing, I need to know whether it is possible to directly
address hardware in LabVIEW for Linux. If not can you suggest a way of doing
this? Also does LabVIEW for Linux and say RedHat make for a more stable
system than LabVIEW for Windows and Windows 2000/XP?
Thanks in advance.
Regards,
Shane Broadbent
- remove the 'nospam' to reply by e-mail

Hi Shane.
I know that you can address hardware in Labview for Linux: I do it with an NI6071e,k 6602 and 6503. I don't know specifically about the PC/104, but I imagine it can also be done.
Generally you can talk to the hardware registers using code interface nodes (CINs) in Labview. In the CIN you just use a 'write()' command. I don't think there's anything more to it than that. Creating the CINs is no trouble at all.
Don't know about stability of Labview with Linux compared to windows, all though others tell me stability is pretty much the same.
hope this helps and good luck!

Runtime.exec(), linux and redirection

Hi all,
I need to exec an external command from java under linux, and have both the stderr and stdout of the command redirected to the
stdout, so that I can capture them and keep them in synch in the java app. I've tried many combination, but I'm unable to make
this work: only the standard output shows up. Note that I can make this work under windows.
A java code example and a small C example to simulate the program to be invoked follows. Running the java program should show both the "messsage" and the "error" lines, but it shows only the "message" ones.
Note that removing the apparently redoundant ">&1" doesn't solve the problem. I got a suggestion to modify the exec invocation into
String[] cmd = { "/bin/sh", "-c", "./test1 >&1 2>&1" };
Process p = Runtime.getRuntime().exec(cmd); but that didn't work eiter.
Can anyone tell me where I'm wrong?
Roberto
======================= class test.java ================================================
import java.io.*;
public class test {
public static void main(String args[]) {
    new test();
public test() {
    try {
      Process p = Runtime.getRuntime().exec("/bin/sh -c ./test1 >&1 2>&1")
      InputStream inStr = p.getInputStream();
      BufferedReader inBr = new BufferedReader(new InputStreamReader(inStr));
      String line;
      while((line = inBr.readLine()) != null) {
        System.out.println("line = "+line);
      try {
        p.waitFor();
      } catch(InterruptedException ex) {}
      System.out.println("process terminated with code = "+p.exitValue());
      inBr.close();
    }catch(IOException ex) {
      System.out.println("IOException : "+ex.getMessage ());
}======================= end of class test.java ================================================
======================= test1 program ================================================
#include <stdio.h>
int main(int argc, char **argv) {
int i;
for(i=0; i<100; i++) {
    fprintf(stdout, "message %d\n", i);
    fprintf(stderr, "error %d\n", i);
}======================= end of test1 program ================================================

Redirection dosen't work with Runtime.exec(), it really dosen't have sense. Do the foolowing:
String[] cmd = { "/bin/sh", "-c", "./test1" };
Process p = Runtime.getRuntime().exec(cmd);
OutputStream out = p.getOutputStream();
//now wrte out to the file, formating as you want
What is doene obove is execute your command, without redirection, and the obtaininh the output stream of the created process. This is "the place" where the process will write everithig it'll would write in the console if executed there.
The handle the OutputStream as any other OutputStream, and write it to the HD or do whtever you want.
Abraham.

LabView runtime and VMware

I don't think LabView runtime is compatible with Windows 2000 server so I tried to install VMware with XP as host. Has anyone been successful with this setup? I have tried but the USB board was not being recognized in the guest system.
Alternatively we could upgrade the WinServer2000 to 2003 I suppose. Any suggestion on this would be appreciated as well.
Thanks
jp lande
UCHSC
why google it when you can LookItUp.us?

Yes, we tried to install LV runtime on the 2000 server, but no luck. Installation program would not complete.
The reason for using the server OS is that we currently have two rackmounted Dell 2650 computers in a rack where we have all other instruments. We could install XP on one of them but then we would loose the benefits of using the redundancy diskdrive that we currently have now. Right now we are using a Dell Optiplex with XP Pro to run the LabView program, but the diskdrive on the desktop actually crashed over the last weekend after only 3 months of running, another reason we would like to keep the redundancy diskdrives...
Thanks!
jp

Complete newbie: Linux, and writing drivers...

I have spent a bit of time searching this forum, and reading over a
good deal of older posts to get an idea of things. I am
completely new to LabView --- I have not even used it yet --- but am
looking to get to know it better in the near future.
My first questions relate to LabView on Linux. I have read a few
posts about the differences between the Linux and Windows versions, but
these were fairly old. Is the Linux version still lacking
compared to the Windows one, or are the differences fairly small
now? In addition, there are a few pages which state that Debian
is a supported distrobution, but the FAQ does not list it: is that a
simple oversight? My work system runs Ubuntu (a Debian-based
distro), and I would like to stick with that if possible, but if I
would be better off using the Windows version I can access a Windows
system.
I have also been looking into writing LabView drivers for accessing
dedicated hardware. Most of what I have seen and read so far
relates to drivers written in LabView, however, I have read a little
about then being written in several other languages. Is there
anywhere I would be able to get the source for any drivers written in
C, so I can see what exactly is involved in writing one. I find
it a lot easier to understand these kinds of things by looking
at examples, rather than explanations (with is the bulk of what I have
found so far). If I can see examples written for both Windows and
Linux, that would be even better --- that way I could understand the
differences between drivers for these two operating systems.

A couple of things to clear up (or muddy up!). LabVIEW "compiles" its code the first time you run it after loading or changing code. It doesn't, at this point, create a file that can be executed on another computer without the development package. To do that you need to purchase the Professional Development package, or one of the lower versions and the Application builder toolkit. This toolkit creates an installation package that includes a ".exe" file. To run it you will need to install the LabVIEW runtime engine on the target machine. This can be done by the installation package created by the application builder, if so configured. The runtime engine is a fairly big package in version 7.1, and this causes a lot of comments by the VB and VC++/.NET folks, but the truth is they also have a runtime engine requirement, theirs is just automatically installed as part of Windows.
Instrument drivers, for standalone instruments (GPIB, serial, etc.), usually do include the source. In the current (this does not apply to IVI drivers, they are a whole different category) method of writing these types of drivers, calls are made to some LabVIEW resources that use what are called VISA functions. VISA is a technology that provides a level of abstraction between us and the actual hardware port (GPIB, serial, etc.) Most of these standalone instruments are setup, programmed, read, using commands that consist of ascii strings. So drivers in this case are functions that convert settings for instance into the appropriate string of commands, i.e. "RB 3000000HZ;VB 1000000HZ;VAVG OFF;VBR 0.300000;" sets the resolution bandwidth, video bandwith, video averaging and video bandwidth resolution on a HP859x series spectrum analyzer.
For the National Instruments cards LabVIEW comes with a bunch of tools to make talking to them easier, it still being at a relatively high level of abstraction, where a settings, etc. are passed to and from some built in function. The problem comes with boards from other vendors. There you are at the mercy of drivers they supply, as obviously National Instruments is not going to devote their development resources to drivers for hardware from competitors. The drivers from the other vendors range in quality from pretty good to what looks like it was written by the new hire engineer that had a copy of LabVIEW dropped on their desk and were told "we need some LabVIEW drivers for the biphase framistat by next Friday!".
P.M.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

CIN (Code interface node) LabVIEW runtime engine dependency

Hello:
Am I correct that the old style CIN (code interface node) is not dependent on what version of LabVIEW runtime engine is being used?
However if I create a dll from say LabVIEW 8.2 I must then alway have LabVIEW runtime 8.2 installed on any newer machine with newer version of LabVIEW?
Thank You!

GE Osmonics wrote:
Hello:
What I have are old CIN (no source) that work in LabVIEW7.1 but will not work in LabVIEW 2010 (link error, object code not loaded).
What I thought I could do is generate dll from the vi's that contain the CIN using LabVIEW 7.1 with application builder.
I could use the Call Library Function from LabVIEW 2010 to load the 7.1 generated dll to effectively do what the old CIN accomplished
provided I installed the LabVIEW 7.1 runtime engine on my LabVIEW 2010 machine
Thanks for the input
If the CIN resource doesn't load you most likely changed the LabVIEW platform. LabVIEW for Windows 32 Bit and LabVIEW for Windows 64 Bit are different platforms. Just as LabVIEW for Windows and LabVIEW for Macintosh or Linux. A 32 Bit DLL, which a CIN is internally can't be executed in a 64 Bit environment at all.
Your solution fails for more than one reason here. LabVIEW will try to load and link a LabVIEW DLL into its actual runtime environment to avoid interprocess communication latency which would be inavoidable if the DLL is started in a seperate runtime engine, which is in fact a new process. If your issue is 32 bit to 64 Bit you won't be able to link the 7.1 32 Bit DLL into your LabVIEW 64 Bit application through the Call Library Node at all.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Labview runtime engine [SOLVED]

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.
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:
http://joule.ni.com/nidu/cds/view/p/id/1103/lang/en
For Ubuntu, I converted the .rpm files to .deb using alien and installed them with dpkg. The Labview executables can then be run by opening them in the file manager. As a first step in Arch, I unbundled the .rpm files using rpmextract and found that they are just a bunch of library files placed in usr sub-directories. I then wrote the following naive PKGBUILD followed by makepkg -s.
pkgname=lvtest
pkgver=1
pkgrel=1
arch=('i686' 'x86_64')
license=('GPL')
makedepends=('rpmextract')
source=("labview86-rte-8.6.0-1.i386.rpm"
"labview-rte-aal-1.1-1.i386.rpm")
md5sums=('37b43da794fd9c61d0c5e3c9cfa56628'
'a2110e5b5677351095bd93e5b1aa5bea')
build() {
cd ${srcdir}
rpmextract.sh labview-rte-aal-1.1-1.i386.rpm
rpmextract.sh labview86-rte-8.6.0-1.i386.rpm
cp -ra ${srcdir}/usr $pkgdir/
This generates a pkg.tar.xz that I install with pacman -U. My problem is that the Labview executables are not being recognized, ie. I don't know how to open them. I suspect this has something to do with permissions or perhaps linking that I sometimes see in other PKGBUILD files, but I don't know how to proceed. I am brand new at this, but have spent a lot of time searching the wiki and forums looking for hints and guidance.
Last edited by sportscliche (2011-01-02 23:58:49)

Thanks for the fast reply! Output of pacman -Ql lvtest follows:
lvtest /usr/
lvtest /usr/local/
lvtest /usr/local/lib/
lvtest /usr/local/lib/LabVIEW-8.6/
lvtest /usr/local/lib/LabVIEW-8.6/.data/
lvtest /usr/local/lib/LabVIEW-8.6/.data/Analysis-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/IAK_SHARED-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/LV_RemotePanelConnection.lic
lvtest /usr/local/lib/LabVIEW-8.6/.data/LabVIEW Simulation Module-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/LabVIEW-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/Measure-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/NI-488-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/NI-Reports-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/VISA-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/English/
lvtest /usr/local/lib/LabVIEW-8.6/English/lvapp.rsc
lvtest /usr/local/lib/LabVIEW-8.6/English/vidialogs.rsc
lvtest /usr/local/lib/LabVIEW-8.6/LV86NPlugin.so
lvtest /usr/local/lib/LabVIEW-8.6/copyright.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/Analysis-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/IAK_SHARED-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/LabVIEW Simulation Module-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/LabVIEW-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/Measure-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/NI-Reports-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/libappweb.so
lvtest /usr/local/lib/LabVIEW-8.6/libappweb.so.2
lvtest /usr/local/lib/LabVIEW-8.6/libappweb.so.2.3.0
lvtest /usr/local/lib/LabVIEW-8.6/liblkdynam.so
lvtest /usr/local/lib/LabVIEW-8.6/liblkdynam.so.5
lvtest /usr/local/lib/LabVIEW-8.6/liblkdynam.so.5.0.0
lvtest /usr/local/lib/LabVIEW-8.6/liblkrealt.so
lvtest /usr/local/lib/LabVIEW-8.6/liblkrealt.so.5
lvtest /usr/local/lib/LabVIEW-8.6/liblkrealt.so.5.0.0
lvtest /usr/local/lib/LabVIEW-8.6/liblksec.so
lvtest /usr/local/lib/LabVIEW-8.6/liblksec.so.5
lvtest /usr/local/lib/LabVIEW-8.6/liblksec.so.5.0.0
lvtest /usr/local/lib/LabVIEW-8.6/liblksock.so
lvtest /usr/local/lib/LabVIEW-8.6/liblksock.so.5
lvtest /usr/local/lib/LabVIEW-8.6/liblksock.so.5.0.0
lvtest /usr/local/lib/LabVIEW-8.6/liblvrt.so.8.6.0
lvtest /usr/local/lib/LabVIEW-8.6/liblvrtdark.so.8.6.0
lvtest /usr/local/lib/LabVIEW-8.6/libnids.so
lvtest /usr/local/lib/LabVIEW-8.6/libnids.so.4
lvtest /usr/local/lib/LabVIEW-8.6/libnids.so.4.5.4
lvtest /usr/local/lib/LabVIEW-8.6/libnitaglv.so
lvtest /usr/local/lib/LabVIEW-8.6/libnitaglv.so.1
lvtest /usr/local/lib/LabVIEW-8.6/libnitaglv.so.1.5.0
lvtest /usr/local/lib/LabVIEW-8.6/libniwebsrv.so.1.0.0
lvtest /usr/local/lib/LabVIEW-8.6/libnixerces.so
lvtest /usr/local/lib/LabVIEW-8.6/libnixerces.so.2
lvtest /usr/local/lib/LabVIEW-8.6/libnixerces.so.2.7.0
lvtest /usr/local/lib/LabVIEW-8.6/linux/
lvtest /usr/local/lib/LabVIEW-8.6/linux/README.libs
lvtest /usr/local/lib/LabVIEW-8.6/linux/libstdc++.so.5
lvtest /usr/local/lib/LabVIEW-8.6/linux/libstdc++.so.5.0.3
lvtest /usr/local/lib/LabVIEW-8.6/lvanlys.so
lvtest /usr/local/lib/LabVIEW-8.6/lvdark
lvtest /usr/local/lib/LabVIEW-8.6/models/
lvtest /usr/local/lib/LabVIEW-8.6/models/arrow.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/attank.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/bowvalve.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/box_inc.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/box_incp.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/boxshadow.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/frame_i.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/frame_o.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/gauge_f.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/inc.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/knob_d.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/knob_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/knob_t.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/meter_f.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/meter_g.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/meter_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pb_d.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pb_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pb_l.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pro_bar.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pro_bar_in.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/rectvalve.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/rocker.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/rockerl.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/rockerr.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/slided.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/slideh.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/slider_b.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/slider_d.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/slider_f.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/slider_t.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/slidet.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/squreled.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/tab.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/tank.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/tb_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/tb_h_in.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/therm_e.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/therm_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/toggle_b.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/toggle_s.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/toggle_su.ptc
lvtest /usr/local/lib/LabVIEW-8.6/nids.so
lvtest /usr/local/lib/LabVIEW-8.6/niwebsrv.so
lvtest /usr/local/lib/LabVIEW-8.6/patchlib/
lvtest /usr/local/lib/LabVIEW-8.6/rtapp.rsc
lvtest /usr/local/lib/LabVIEW-8.6/webserver/
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/liblvauthmodule.so.1.0.0
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/liblvrfpmodule.so.1.0.0
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/liblvsnapshotmodule.so.1.0.0
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/lvauthmodule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/lvrfpmodule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/lvsnapshotmodule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/logs/
lvtest /usr/local/lib/LabVIEW-8.6/webserver/logs/access.log
lvtest /usr/local/lib/LabVIEW-8.6/webserver/logs/error.log
lvtest /usr/local/lib/LabVIEW-8.6/webserver/mime.types
lvtest /usr/local/lib/LabVIEW-8.6/webserver/modules/
lvtest /usr/local/lib/LabVIEW-8.6/webserver/modules/libcopyModule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/modules/libdirModule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/modules/libespModule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/niwebserver.conf.defaults
lvtest /usr/local/lib/libguide.so
lvtest /usr/local/lib/libmkl.so
lvtest /usr/local/lib/libmkl_def.so
lvtest /usr/local/lib/libmkl_lapack64.so
lvtest /usr/local/lib/libmkl_p3.so
lvtest /usr/local/lib/libmkl_p4.so
lvtest /usr/local/lib/libmkl_p4p.so

Failure to build LabVIEW application on Linux using "Shared library"

In order to create a LabVIEW application on linux without an X display, I complied the LabVIEW VI using the Linux Shared Library. I did this by right clicking on Build Specification and selecting New >> Shared Library, and in the Advanced section, checking the box labeled Use embedded version of run-time engine. At the end of the build process, a message came up informing that the build was unsuccessful, with the following message:
"Error 127 occurred at System Exec: sh: gcc: command not found
The error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an error code to the error code input."
I had no compling the LabVIEW VI in the normal fashion, so am confused about what the problem is.
Solved!
Go to Solution.

Hi Julian,
gcc is a C and C++ compiler on Linux. An easy way to check if it is installed is to open a terminal and type "gcc", if the command is recognized then the package is already installed and the problem must lie elsewhere. If this distrobution of Linux has a package manager included then it should be displayed in there as well. If not then it could point to it being not installed or some dependency is missing making it not accessible from the command line. Here is a link that should hopefully step you through installing gcc with Redhat: http://www.cyberciti.biz/faq/centos-linux-install-gcc-c-c-compiler/ .
Justin D
Applications Engineer
National Instruments
http://www.ni.com/support/

Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC

I have a dll built using LabVIEW 6i. I am calling the dll from a VC++ application. When the application loads I get an error pop-up 'cannot find LabVIEW runtime'. If I change the VC++ code to dynamically load MFC (using the loadlibrary function) or dynamically load the LabVIEW dll I created then the problem goes away. Only when both are loaded statically do I get the error message.
The target machine is running Win2K pro and has the LabVIEW runtime installed.
I do not want do dynamic loads as I need to call the dll from a legacy application. Are there any options to change the way LV links to MFC or to force the dll to find the LV runtime?
Alan Widmer

Ben,
I have attached a ZIP of the files required to test a DLL from an MFC application. Or you can build the same application by following the instructions below. I used the numtest dll that you previously sent to me so there is no 'magic' in the LabVIEW or dll.
In VC++ select NEW. Pick the MFC AppWizard (MFC) to build an MFC application. In the wizard select
Project Name: MFCNumtest
Single Document
No database support
No Compound document support
Support for ActiveX
Default settings on the Features page
MFC Standard
MFC as a shared DLL
From the ResourceView of the project explorer, add an item Test to the IDR_MAINFRAME menu then add an item Go as a submenu item (with an ID of ID_TEST_GO)
Right click the new menu item and run the Class
Wizard. Click Add Function.. button to make a function OnTestGo()
Open MainFrm.cpp and scroll to the end of the file to see the skeleton for the OnTestGo function. In this function add a call to the LabVIEW dll. You will also need to add a reference to the .lib file and the usual extcode.h.
When you run the app you will see a window with the Test menu item. Select it and click Go to run the call to LabVIEW.
This all works great. If you now go to Project | Settings and on the general tab change the Microsoft Foundation Classes: item from 'Use MFC in a shared DLL' to 'Use MFC in a static library' rebuild ALL files in the project and run the app you get the error message:
System error 998 while loading the LabVIEW Run-Time Engine (C:\Program Files\National Instruments\shared\LabVIEW Run-Time\6.0\\lvrt.dll).
numtest requires a version 6.0 (or compatible) LabVIEW Run-Time Engine. Please contact the vendor of numtest to correct this problem.
I apologies for my slow response, g
ot distracted by some other issues.
Thanks for your help,
Alan Widmer.
Attachments:
mfcnumtest.zip ‏44 KB

Web Start doesn't leave the gate on Linux and Mac

I am evaluating Java Web Start to decide whether to recommend it as part of a government grant proposal. My initial impression of Web Start has been a sorry one. When I go to
http://java.sun.com/products/javawebstart/demos.html
and click on one of the demos, I am redirected to the page
http://java.sun.com/products/javawebstart/needdownload.html
which tells me that I need to download Java Web Start ("a one-time process"). Fine, I click on the download link, and instead of a download, what I get is a bug-report page:
http://java.sun.com/webapps/bugreport
I have seen this behavior on both Linux and Mac OS X. (My Windows machine already had Web Start installed from several months ago; I don't know if this reflects a superior Windows support relative to Linux or Mac OS X support, or a better download software several months ago.)
This is a terrible first impression for one's software. Given these beginnings, any sane developer would run away as fast as possible from the Web Start technology. Clearly a lot of work has gone into Web Start, and to see squandered like this is surprising.
Our software's user base (research biologists) has large Macintosh and Linux constituencies. My experience with Web Start suggests that Web Start would be a disastrous choice for us. I hope there is a simple way around these obstacles.
Any suggestions would be much appreciated.
Thanks,
GFBerriz

I haven't tested JWS before JRE 1.4 so I can't recommend you anything if you require JRE 1.3 or before, but if you can install JRE 1.4, specially JRE 1.4.2 or after, JWS works very good on Linux and Windows. In both platforms I use deploy applications using JWS and they all work very good. I have no experience on Mac OS X.
Both platforms obviously require Java preinstalled. Also there is some ways to install Java automatically, this is something that must be done by an administrator as every other software that requieres installation and configuration on every PC. After that step, everything is very simple.
On Linux if you click on a .jnlp file for the first time, at least mozilla ask if you want to save the file or open it, you can select the javaws executable inside your java installation as the program to open this file, mark that that's the action you always want to do with that kind of files, and that's all. Also you can manually register .jnlp files and application/x-java-jnlp-file mime tipe as handled by javaws as the last part of the java installation and this first step will not be necesary.
On Windows the installer automatically register itself as insterested in handling jnlp files, so the previous step for linux is not required.
Hope this helps.
rivas.

LabVIEW Runtime engine on Windows Embedded Standard 7 P 32/64 bit?

Did anyone ever try to install and run LabVIEW Runtime engine (2011 or later) on Windows Embedded Standard 7 P 32/64 bit?
I am trying to figure out if this will work, for example on a Beckhoff CX5120 embedded PC. I will need to have some simple TCP/IP communication in order to exchange information with another PC, but nothing else, i.e. drivers, etc...
I hope someone tried to do this already. I just don't have the right hardware right now to check it out.
Solved!
Go to Solution.

As NI sells touch panels with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume they've used the RTE on WES7.
But yes, it's been done.

How To Handle Labview Runtime Error in Teststand

Hi,
I am working NI-CAN device to transfer CAN frames through the VI's using TestStand. Before transmission took place, we need to choose for the port, in case if the port is selected wrong, Labview take it as a runtime error and handles accordingly while teststand keeps on running i.e. if I have 7 steps that are calling that VI, the runtime error from the labview will appear that many times also. Is there any way to handle labview runtime errors directly through TestStand. I have a sequence that will take care of the Runtime Errors in my sequence file.
Please help me soon.
Thanks in Advance,
Vivek

Hi Vivek,
If the LabVIEW VI is handling the error, then what you probably want to do is make the VI have an Error Out output terminal. You'd have to wire the appropriate error out wires to the terminal of course.
This way, when you call the VI from TestStand, you can check the value of the Error Out and decide in TestStand how to handle it (skip the remaining steps, popup a message, etc).
Jervin Justin
NI TestStand Product Manager

LabVIEW Runtime 7.0 Linux and Mozilla

Similar Messages

Maybe you are looking for