Problem labview & perl

We work NT platform (labview v.5.1). Our purpose is to start a vi's file "via
website" (with script in perl lenguage). The instruction is:
"Win32:rocess::Create($ProcessObj,"C:/soft/natinst/labview/labview.exe","C:/soft/natinst/labview/labview.exe
uveis/gf_prova.vi",0,NORMAL_PRIORITY_CLASS,".")|| die ErrorReport();"
With this, the server start the labview program, but no the vi file.
We repeat the experience with the notepad program and the instruction go
ok.
The other solution is use the next instrution: "exec ('C:/soft/natinst/labview/labview.exe
uveis/gf_prova.vi');",
but then, the vi executes in the background (the front panel not appears
in the monitor, because the vi is running, and then i can't kill the process...
Ctrl-A
lt-Del).
I think that the problem resides in the definition labview process.
I have explained it good (???).
I don't know if someone has work in similar themes. I will be grateful for
some suggestion or comment.
Thanks,
Santi

Instead of using VISA try using just the 488 or 488.2 vi's to communicate
with the HP. Verify you can read/write using the GPIB vi's. The logging
system I built uses just the 488.2 vi's and works fine. I found the 34970A
sample vi drivers didn't always works correctly.
"koutatelazzo" wrote in message
news:384788001.985023910852.JavaMail.root@web572-mc...
> Hi all !
>
> I'm a total novice in Labview, but I have to control a HP 34970A with a
> 20-port MUX to read VDC signal from two dp-cell, a mass flow meter and a
> thermocouple. I own a GPIB card (PCII) and I use Labview 5.1 on win95.
>
> The problem is this:
> the VISA initialization VI finds the HP, and correctly identifies it (with
> the correct GPIB port). But, when I try to read or write (with
the VISA
> read-write VI) or when I use the HP drivers (found on the National
> Instrument site), I obtain an error, which explanation sounds like "VISA
> hasn't sufficient information on instrument location". This thing happens
> even also when I send a simple request (as the IDN request), via the VISA
> read-write VI.
>
> Is it a driver problem, a HP problem or a GPIB problem ? I think it is a
> driver problem (the GPIB software identifies the Hp). How can I fix it ? I
> have downloaded the Labview driver of the HP, but I've noticed there are
> also the LabWindows drivers....
>
> Thanks for any advice ! I hope I have explained well the problem...
>
> Regards,
>
> Tetrazzo
>
>
> ______________________________________________
> FREE Personalized Email at Mail.com
> Sign up at http://www.mail.com/?sr=signup
>
> --
> Posted from 131.175.67.92 by way of rmx308-mta.mail.com [165.251.48.43]
> via Mailgate.ORG Server - http://www.Mailgate.ORG

Similar Messages

Facing Problem in Perl Script

Hi ,
I m facing one problem in perl script.
Oracle Database 10g.
DBD::Oracle::db selectall_arrayref failed: handle 2 is owned by thread 225ffc not c
urrent thread 1c4f8ac (handles can't be shared between threads and your driver may
need a CLONE method added) at c:\perl\update_card_numbers_oracle.pl line 258, <STDI
N> line 1.
Thx in advance....

There are forums here at OTN for Perl related issues ... this isn't it.
Return to the list of all forums and find the one where your inquiry belongs.

Xnet problems labview 8.6.1

Existing Labview code on clients sytems 8.6.1 so have to work with this.
Using CAN 2 PCMCIA card for original program development using API Channels was no problem and client ECU could be read without fail over long periods (24 hours plus).
PCI card dual channel had to be used for client deployment which required the installation of XNET to support this card. Version used was 1.5 because after this xnet no longer supports Labview 8.6.1.
Can drivers loaded version 2.7.3 (last support for 8.6.1)
When the originally developed program was run with PCI card and XNET problems occurred with the CAN link failing after about 10 minutes. Error message summerised was insufficient sampling time or/and too much data specified. Sample rate is 1ms (client ECU has new data available every 20ms so 1ms should be well within limits?)
From what I gather the PCI card buffers are not read fast enough, fill up to limit then just crash........
So after lots of messing around and reading forum it seems that Frames are the way forward for the versions of drivers/software I am using.
Ok, that's the background, so what do I want to know?
1) Using MAX have created .ncd file for Channels, is it possible to use this for Frames? Found the XNET Database Editor and see you can develop
    clusters?
2) Using the Examples file tried XNET read vi and although it seems to allow me to select a frame it does not recognise my installed PCMCIA CAN
    interface, Why?    Looking in MAX the card is there and tests fine..............
3) Tried a CAN Example and that quite happily found my CAN PCMCIA card and also obtained data from Clients ECU, Why?
Summay
Without going through the pain of what Labview/Drivers no longer supports etc I just want to know what I need to concentrate on?
I think one conclusion is that I need to use frames, channels cannot cope?
XNET vi's are limited with legacy CAN and perhaps Labview 8.6.1 so do not use there vi's??
Stick with legacy CAN vi's using Frames and 'chunk' the frames using std LV code?
Appreciate comments on best route to go. In fairness the XNET stuff looks good but I get the feeling its not applicable to the version of Labview I am using?
Jack
Labview Version 8.5
Labview Version 8.6
Labview Version 2013

Hi Jack,
I hope you are well. In response to your questions please see below (If you are still having issues).
1)      The .ncd file is used for configuration information about CAN messages such as frames and channels.
Further information can be found here:
http://digital.ni.com/public.nsf/allkb/FCC9622168F856B486256CA2005C981B
You can use the NI Database editor if you need to store information about the frames and signals on the network. It is possible to use a CAN network without using the Database Editor, but highly recommended.
2 & 3) To use a XNET example, you will have to be using an XNET supported card (shown in the XNET Readme file). The PCMCIA CAN interface sits on the CAN driver level so relies on the CAN driver.
Further information can be found here:
http://www.ni.com/white-paper/9727/en/
http://www.ni.com/white-paper/2732/en/#toc9
I look forward to hearing from you.
Kind Regards,
Aidan H
Applications Engineer
National Instruments UK & Ireland

Problem with perl Net::Telnet::Cisco for Solaris 10 SPARC

hi all,
I have problem with installing this modules : Net::Telnet::Cisco,TermReadKey-2.30.tar.gz.
I'm trying to install this packages Net-Telnet-Cisco-1.10.tar.gz, and the it notifies me that I need to install before the TermReadkey, I get it from www.CPAN.org -TermReadKey-2.30.tar.gz
and look what I have when I run : "make test" or even "make install"
cc -c -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -xarch=v8 -D_TS_ERRNO -xO3 -xspace -xildoff -DVERSION=\"2.30\" -DXS_VERSION=\"2.30\" -KPIC "-I/usr/perl5/5.8.4/lib/sun4-solaris-64int/CORE" ReadKey.c
sh: cc: not found
*** Error code 1
make: Fatal error: Command failed for target `ReadKey.o'
Please can some one help me. it 's very urgent
thank you in advance

Vipul_Ramani wrote:
only thing you are missing CC does not your current PATH
ADD it again
using export PATH=$PATH:/usr/ucb and try ... do it No, please don't. There is no compiler in /usr/ucb, and it is probably a very good idea to compile without /usr/ucb in your path. /usr/ucb/cc is only a wrapper to extend a very old SunOS compatibility environment onto an existing compiler.
If you don't have the current Sun compiler suite on your machine (go ahead and download it, it's free), then you can use gcc by invoking "perlgcc" instead of "perl" on the module's makefile.
Darren

RS232 problem: LabVIEW not transmitting \03 (ETX) or (sometimes) last byte

Hi there,
I've coded small VIs to communicate with RS232 devices
since LabVIEW v3.x. I'm now trying to write a VI to
talk to an esoteric photon detector. Using a serial
line sniffer, I have verified the serial line setting s
and can communicate with the device using some
simple C programs. However, using LabVIEW, I cannot
get the \03 (ETX) character to be transmitted
properly. The first instance of the ETX character
in a string will always disappear while any others will be transmitted. I've used labview v6.0.2 on
both Windows and Linux and can reproduce the problem.
I think its a serial lne setting but can't for the
life of me find it...
What am I missing?
-Ed

Attached is a VI in LabVIEW 6i that can transmits the \03 character through VISA. This can be verified by running NI-Spy. Hope this helps.
Randy Solomonson
Application Engineer
National Instruments
Attachments:
03.vi ‏14 KB

Character encoding problems in Perl debugger on OS X 10.6

My debugger isn't working like I would expect it to, coming from a linux environment. I've never used a debugger session on this machine, so it's not something that worked then stopped. It's an early 2008 MacBook Pro, running Snow Leopard, 10.6.8.
If I have a debugger session open, launched via "perl -de 1", I can't use the up and down arrow keys to cycle through my history or Control+A or Control+E to get to the beginning and end of the line.
These are the characters I get if I hit up, right, down, left:
^[[A ^[[C ^[[B ^[[D
If I hit Control+A or Control+E
^A and ^E
In Terminal preferences
I currently have my terminal declaration set to xterm-color, and my encodings are the defaults.
It's happening with both an external keyboard, and the laptop keyboard.
Has anyone run into this before, and have any advice on what settings I could tweak to make it work as I would expect?
Thanks.

Thanks for the help.
My initial install via a root CPAN shell was not successful. I was running into errors. I tried installing YAML, which had some dependencies, and those dependencies had other ones. It was a mess.
I did some searching online for *those* problems and the consensus seemed to be to install XCode. I was able to download it free from Apple, after signing up to be a developer (free signup).
I was then able to install Term::ReadLine::Perl.
In case anyone else runs into the problem. Someone on PerlMonks also suggested installing "Term::ReadKey"and "Term::ReadLine::Gnu" in addition to "Term::ReadLine::Perl"

Problems with perl 5.8

Hi everyone.
I'm running Solaris 8 in a dual p III 450Mhz box with 512 Mb RAM. I started to download every perl module I need to do my research, but after installing some modules I got this:
perl -MCPAN -e shell
Out of memory!
Callback called exit.
BEGIN failed--compilation aborted.
What is the meaning of that?. What memory is perl talking about?. I did a "top" and I found the box with 422 MB RAM free and an uptime 0.02.
What should be the problem?.
Thanks alot.

I have tried modifying the path and environment
variables without success. I have heard from some
classmates that these perl problems have been encountered and solved before. Have changed path on system/user level or on command prompt.
- Virag Sharma
http://viragsharma.blogspot.com
http://virag.sharma.googlepages.com

LLB file problem (Labview 2013)

I have made labview project that builds a LLB file.
It contains my "test VIs"(auto-populating dir) and all Dependencies(user.lib, vi.lib....)
Building the LLB file goes fine.
But when i try to run the "test VIs" in the LLB file using an .Exe that uses "open VI reference -> invoke node "Run VI" i get a broken arrow and error 2002200....
Opening the "test VIs" in the LLB with Labview, the path for some of the sub VIs do not point to the LLB. It still points to the original VI (in user.lib, vi.lib....) causing the "test VI" to not be executable . ("test VIs" where all sub VIs points to LLB woks)
what am i doing wrong/how do i fix this?
/J

After some investigation.
Using Projec Explorer building a "Source Distribution" LLB Then calling my "test VIs" in the LLB file using an .Exe that uses
"open VI reference -> invoke node "Run VI" i get a broken arrow and message "VI has an error of type 2002200. The full development version of LabVIEW is required to fix problem"
The functions are in "Programming->File I/O-> Configuration file VIs" menu
(Directory C:\Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\Utility\config.llb\)
Below VIs generates the error
Get Key Names.vi
write key.vi
Remove Key.vi
Remove section.vi
Read key.vi (boolean)
Read key.vi (Double)
Read key.vi (I32)
Read key.vi (path)
But these works in llb
Open config data.vi
Get section names.vi
Read Key.vi (string)
Close config data.vi
I cant find any reason why some works and some dont.
is there someone how knows how to fix this?
/J

Problem Labview receiving data continuously

hello...
i'm final year student in one of the university in Malaysia. In my final project, im doing the RS232 Interface Wireless Receiver. In this project,i have been having the some difficulties, i dunno how to received the data continuously. which means, Example: If i send word "HELLO", i will also received "HELLO". But the problem is..i want the HELLO word is received continuously.
Send: HELLO
Received: HELLO
                 HELLO
                 HELLO
                 HELLO
                 .....many times....
So, can sumbody help me...i really need ur help regarding on this..thanx...

duplicate post
CLA | LabVIEW 7.1... 2013
www.renishaw.com

Probleme LabVIEW - module DSC / OPC

Bonjour,
j'utilise LabVIEW 2010 avec son module DSC.
Et je souhaite accéder à des variables OPC en Lecture et Ecriture depuis une application labVIEW.
Le serveur OPC que j'utilise fonctionne correctement (j'ai également fait le test avec le serveur de NI, mais le resultat est identique). Je peux lire et ecrire des variables avec 'OPC Quick Client'
J'ai configuré la connexion DCOM avec une "identité" : 'Utilisateur interactif'
Cependant depuis le projet LabVIEW, la creation des variables partagees ne fonctionne pas (Create Bound Variables) (cf. piece jointe)
J'ai suivi la note : Connect to Any PLC using OPC (lien : http://zone.ni.com/devzone/cda/tut/p/id/7450)
? Est-ce que quelqu'un a deja rencontré ce probleme et surtout trouvé une solution ?!?!?!???
Dans l'attente et en vous remerciant d'avance pour votre aide
<Nicolas>
Attachments:
CreateBoundVariables.JPG ‏40 KB

Hello,
J’ai trouvé une solution mais est-ce la bonne ?!? en tout cas, elle fonctionne.
J’ai préalablement ‘configuré’ le gestionnaire de système distribué (accessible à partir du menu : Tools \ Distributed System Manager) :
- Je crée/J'ajoute un nouveau Processus à "Mes systèmes \ local Host \" , nommé OPC (avec les paramètres par défaut)
- J’ajoute à ce processus un serveur d’E/S
- Je configure ce serveur pour qu’il accède à mon serveur OPC avec les paramètres qui vont bien.
- Et j’accède aux Items …
( Ce processus apparaît également sur les éléments du réseau )
- J’enregistre tout ça... je ferme ... et je reviens au projet
Donc ensuite, depuis le projet, je suis la procédure Connect to Any PLC using OPC
(lien : http://zone.ni.com/devzone/cda/tut/p/id/7450
Il faut alors juste préciser dans la fenêtre de configuration "Create Bound Variables" :
Browse source = Network Items
Et ensuite je peux sélectionner des variables partagées, (des items de mon serveur OPC) en naviguant dans son arborescence.
La note de Thomas B. décrite ci dessus fonctionne très bien, mais nécessite également (dans mon cas) la configuration du gestionnaire de système distribué.
<NBA>

Problem: Labview 5.1 & HP 34970A via GPIB

Hi all !
I'm a total novice in Labview, but I have to control a HP 34970A with a
20-port MUX to read VDC signal from two dp-cell, a mass flow meter and a
thermocouple. I own a GPIB card (PCII) and I use Labview 5.1 on win95.
The problem is this:
the VISA initialization VI finds the HP, and correctly identifies it (with
the correct GPIB port). But, when I try to read or write (with the VISA
read-write VI) or when I use the HP drivers (found on the National
Instrument site), I obtain an error, which explanation sounds like "VISA
hasn't sufficient information on instrument location". This thing happens
even also when I send a simple request (as the IDN request), via the VISA
read-write VI.
Is it a driver probl
em, a HP problem or a GPIB problem ? I think it is a
driver problem (the GPIB software identifies the Hp). How can I fix it ? I
have downloaded the Labview driver of the HP, but I've noticed there are
also the LabWindows drivers....
Thanks for any advice ! I hope I have explained well the problem...
Regards,
Tetrazzo
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
Posted from 131.175.67.92 by way of rmx308-mta.mail.com [165.251.48.43]
via Mailgate.ORG Server - http://www.Mailgate.ORG

Instead of using VISA try using just the 488 or 488.2 vi's to communicate
with the HP. Verify you can read/write using the GPIB vi's. The logging
system I built uses just the 488.2 vi's and works fine. I found the 34970A
sample vi drivers didn't always works correctly.
"koutatelazzo" wrote in message
news:384788001.985023910852.JavaMail.root@web572-mc...
> Hi all !
>
> I'm a total novice in Labview, but I have to control a HP 34970A with a
> 20-port MUX to read VDC signal from two dp-cell, a mass flow meter and a
> thermocouple. I own a GPIB card (PCII) and I use Labview 5.1 on win95.
>
> The problem is this:
> the VISA initialization VI finds the HP, and correctly identifies it (with
> the correct GPIB port). But, when I try to read or write (with
the VISA
> read-write VI) or when I use the HP drivers (found on the National
> Instrument site), I obtain an error, which explanation sounds like "VISA
> hasn't sufficient information on instrument location". This thing happens
> even also when I send a simple request (as the IDN request), via the VISA
> read-write VI.
>
> Is it a driver problem, a HP problem or a GPIB problem ? I think it is a
> driver problem (the GPIB software identifies the Hp). How can I fix it ? I
> have downloaded the Labview driver of the HP, but I've noticed there are
> also the LabWindows drivers....
>
> Thanks for any advice ! I hope I have explained well the problem...
>
> Regards,
>
> Tetrazzo
>
>
> ______________________________________________
> FREE Personalized Email at Mail.com
> Sign up at http://www.mail.com/?sr=signup
>
> --
> Posted from 131.175.67.92 by way of rmx308-mta.mail.com [165.251.48.43]
> via Mailgate.ORG Server - http://www.Mailgate.ORG

Application Build problem Labview 8.5.1

Having a problem creating an Installer with 8.5.1. When being built a menu appears asking for
"NI Labview 8.2.1" distribution. Needs to copy a component installed or updated by the distribution to continue building the installer.
Despite trying all of the Disks I have, First quarter DVD, and all of the second quarter CD's it does not recognise any of them. When the CD's or DVD is inserted it shows a nidist.id file which I select (because it says that's what it requires) but them it gives a message stating that
"You cannot choose this folder name; a file of that name exists"
I have tried this build on 2 different machines and get the same response, anyone got any ideas on this or is it a no brainer in 8.5.1?
One last thing if this lot cannot be got to work, the additional files required are:-
Ni Labview Runtime Engine 8.5.1
NI Measurement & Automation Explorer 4.5
NI PXI Config Support for Windows
NI DAQmx 8.7 (unsure if this is included in MAX?)
NI Visa Runtime 4.4
Does anyone know if I just downloaded these from NI website and installed on the computer that will run the final .EXE file it will work?
Labview Version 8.5
Labview Version 8.6
Labview Version 2013

Hello Jack1,
I have been looking into your posts. There are two immediate actions you could try to help. I have identified that you are having issues with the computer recognizing that you have inserted the CD it has requested. Also, you are having trouble with repeatedly being asked to change back and forth through disks, at every attempt to build the installer. As you may need to try this more than once, it may be helpful to you to create a folder for each CD or DVD, and copy and paste the contents of the individiual disks. This software will be recognized, even if copied on to your hard disk.
When you click 'Build', to begin building your installer with your necessary additional resources, you will be asked to insert the last set of CDs or DVDs you have used. However, at the prompt you can click on the 'Folder' icon and browse the folder where you have saved the individual disk contents. The error you were receiving in your first post, "You cannot choose this folder name; a file of that name exists", implies that you were most like click on the *.id file and selecting ok. I have avoided this on my machine by opening the folder with the disk contents, not selecting any files, and the click the 'Current Folder' button. After you have selected it, ensure that you have ticked the box next to 'Cache components from this distribution.' Whether you use the CD, or folders containing the disk contents, this options creates a local copy of the requested files to a cache directory, therefore no requiring the user to input disks, or point to file locations in the future. If you have a repeated patter of building applications and installers, this will quicked your process, and eventually allow to delete the disk contents you have copied to your hard disk.
The disks from your previous installations are requested primarily because of your selection to include NI-DAQmx as an Additional Resource. As this is the main driver, shared components are recognized by the Application Builder. I, therefore, can recommend that you try building the installer with the above steps on your laptop, which your mentioned is a fresh installation.
When you have had a moment to try this, please post back to see if I can answer any further questions on this topic, or know that it has worked.
Regards,
Message Edited by gt3000 on 11-03-2008 03:26 PM
George T.
Applications Engineering Specialist
National Instruments UK and Ireland

PROBLEMA LABVIEW

Hola todos, tego un programa realizado en labview que envia caracteres por el puerto serie. Mi problema es que no me detecta los puertos COM virtuales que tengo. El programa anda bien en otras computadoras pero nosé porqué ami no me deceta ningun puerto. Podria ser algun problema de que me faltan instalados algun tipo de drivers de labview o algo por el estilo como alguna configuracion o algo? Adjunto el programa
Attachments:
Nueva logica.vi ‏62 KB

duplicate post
You are already being helped in your other post. Please be patient. This is a forum of volunteers.

Problems installing perl-goo-canvas

I want to install shutter, however, it failed because it can't build perl-goo-canvas, so when i try to install perl-goo-canvas, i meet the following problem:
==> Building and installing package
==> Making package: perl-goo-canvas 0.06-2 (Sat Jun 23 12:12:29 CST 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Downloading Goo-Canvas-0.06.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 103k 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 30 103k 30 32768 0 0 19030 0 0:00:05 0:00:01 0:00:04 100 103k 100 103k 0 0 51069 0 0:00:02 0:00:02 --:--:-- 181k
==> Validating source files with md5sums...
Goo-Canvas-0.06.tar.gz ... Passed
==> Extracting Sources...
-> Extracting Goo-Canvas-0.06.tar.gz with bsdtar
==> Starting build()...
Perl API version v5.16.0 of Cairo does not match v5.14.0 at /usr/lib/perl5/core_perl/DynaLoader.pm line 213.
Compilation failed in require at (eval 8) line 1.
BEGIN failed--compilation aborted at (eval 8) line 1.
Checking if your kit is complete...
Looks good
Warning: Guessing NAME [Goo-Canvas] from current directory name.
Can't locate object method postamble_clean via package Glib::MakeHelper (perhaps you forgot to load Glib::MakeHelper?) at Makefile.PL line 153.
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build perl-goo-canvas.
can anyone help me solve this problem ? thank you!

Thanks much!! Once I saw that it was part of the base-devel meta package I realized I must never have installed that (could have sworn I had, but apparently not so much), fixed all my issues. MUCHAS GRACIAS!!

Problema : LabView´s Memory Corrupted

During a temperature measurement session, I got the the following message and my application stopped:
"An exception occured within the external code
called by a Call Library Node. This may have corrupted
Lab View´s memory. You should save any work to
a new location and restart LabView. VI "xyz.vi" was
stopped at node 0x2380 of subVI "AI Single Scan (single-point waveform).vi"
Why did it happen? How can I fix this problem?

It sounds like something strange happened in a NI-DAQ VI. If you keep getting the error I would suggest re-installing NI-DAQ and if that does not help re-install both LabVIEW and NI-DAQ.

Problem labview & perl

Similar Messages

Maybe you are looking for