LL and change the first occurance of:
NORPM=
to
NORPM=y
the install script should work for you.
David Duffey
resulting executable which will be made up of the VI that uses
VI server.
But your question is a little bit vague. What exactly is your goal
after "launching LabVIEW." You said that you want "an application to
launch LabVIEW." Which application? Do you have the source code?
Wh
ect sounds interesting, let us know more about it and it's
requirements!
David Duffey
going on.
--
David Duffey
National Instruments
Yes, LabVIEW 6i works on the 2.4 kernel.
I am currently runing the Debian testing distribution with the 2.6
kernel and was able to at least run LabVIEW 6i. Don't use 2.6 though,
IIRC there are some new threading issues that affect LabVIEW 7.0 and
earlier with the new threads in 2.6.
As far as I
I'm not sure what you mean with "before being concatenated with the
rest of the pointer".
An x86 machine is little endian. So the CPU expects the bytes to be
in reverse order. If a function in your dll expects an int32, it will
want the bytes in reverse order.
So, when LabVIEW makes calls to na
Hi Jason,
Ideally you'll want to use the exact same version of g++ that was used
to compile LabVIEW. For 7.0 on Linux, this was g++-3.1 (so I've been
told). I used g++-3.0 (which happened to be on my machine) and it
worked okay. This is because exceptions are compiler specific, and
the ABI has
I didn't make it clear, if you used the modified linker line, you
should be able to use any version of gcc.
-Duffey
In your "false" case you need to fill in the {0,0} missing elements.
The only way that you hit the false case is if you come across a time
stamp that is larger that the current interval. So, what you should
do is put a loop in the false case that add the correct number of
elements to "catch up" to
Unfortunetly, I don't know how to script in a password for ssh. SSH
closes the stdin and re-opens the tty that you are logged in at. This
is actually a security feature. As well as a way to send stdin to
remote programs (otherwise your password would get in the way.)
If you don't need to ssh to
Hey JP,
Does your problem stem from the fact that you have no way to enter
your password?
If so, you could setup a public/private key and use the
authorized_keys file so that ssh never prompts for a password.
Everything should work after that.
You could also use an agent so that you only have to
Hi JP,
Yes you can use g++ to build shared libraries that labview can use.
You'll want to give your C++ library a C interface. This is really
common practice. You can do this by simply declaring functions as
'extern "C"'. Here is a link with more information:
http://www.parashift.com/c++-faq-l
Hi Martin,
Oops, I didn't expect for the property node to give an error when used
in a sub-panel, but it makes sense.
I only meant for the property node to be used when you are doing your
editing. This allows you to run the VI, and the property node will
line things up for you exactly. Then you
The top-left corner of the subPanel uses the same coords as the
top-left corner of your saved sub VI. Also the "subPanel document
size" will be the same size as your running VI. I.E. the sub VI's
should have the same placement / appearance as "regular" VIs, or
exsiting in a subPanel.
If you want
I found a defora core 1 release and verified your problem (on LabVIEW
7.0). It's because the fedora kernel uses native posix threads
instead of pthreads. This changes the behavior of signals.
If you recompile your kernel and use pthreads the problem should go
away. (Although I have not done thi
You should be able to use the TCP vis without being root. This is
most likely a security / firewall(on your localhost) setting that is
hosing your networking.
You can use "telnet" and "netcat" (nc) programs to help debug what is
going on. Make sure you are using ports over 1024, as traditionally
I know of several people using LabVIEW on embedded linux devices, as
well as RT linux.
LabVIEW actually doesn't depend on much. It requires the correct
version of libc (along with libm and libdl), and libpthread.
It also depends on X (libX11, libXext). It requires an X server to
display to, bu
Are you sure that your are running LabVIEW 7.1 on RedHat, and not 7.0?
I don't have a mac to test with, but have you narrowed down the area
in loss of performance? Do you think it is in your G code, or the
overhead of using a CIN?
Do you think you could create a small demo VI that demonstrates t
Ah, a weirdness with sftp. I ran a test like this on my machine:
# begin typing
mkfifo /tmp/test
ftp < /tmp/test
cat > /tmp/test
open ftp.ni.com
cd /incoming
ls
^D
# end typing ^D, is control, D of course
You should see the results as you type the commands to cat (cat keeps
the pipe open, until
Hi David,
I'm glad that you got expect working under LabVIEW 6.1
Under LabVIEW 7, you could also be use the "Open System Command Pipe"
VI found in the Communications -> Pipes palette which would give file
descriptors that you can read and write to with the pipe VIs.
This would give you a purely
20 matches
Mail list logo
