Lancer un executable Labview 2011 dans Ubuntu 11.10

bonjour ,
j'ai installé labview (2011) dans Ubuntu 11.10 , et aussi j'ai installer le Runtime Engine assicié a cette version.
j'ai créer un programme test , mais lorsque je le lance , j'obtiens le message d'erreur suivant :
root@alaa-VirtualBox:/usr/local/natinst/LabVIEW-2011/project# ./Exe\ Test\ LV
Internal Warning 0x9120BBD8 : "CPUInformation.cpp", line 408
LabVIEW version 11.0
For assistance in resolving this problem, please contact National Instruments Support.
Abandon
svp ,comment je peux résoudre ça
merci d'avance ;

Bonjour devlopperKimo,
tout d'abord, merci d'utiliser le forum National instruments.
Malheureusement National Instruments ne supporte pas Ubuntu, ce qui signifie que le bon fonctionnement de LabVIEW n'est pas assuré.
Est-ce que votre LabVIEW est installé directement sur Ubuntu, je vois le mot clé VirtualBox est-ce que ça a un quelconque rapport avec le logiciel de virtualisation d'oracle?
Cordialement,
Audrey_P
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

Similar Messages

Lancer un executable dans une fenêtre de mon VI

Bonjour,
Je souhaite lancer un executable dans mon VI, comme s'il faisait parti de mon code (pas à l'exterieur)
Pour simplifier les choses, mon programme fera la liste de tous les executables disponibles dans un repertoire défini puis les proposera dans une boite à onglet
Ces executables sont des SFP de ressource
Ainsi je me retrouve avec un applicatif qui contient tous les SFP que j'ai de disponible (je ne pense pas en avoir plus de 10 sur un banc de test)
Pour la gestion de la boite à onglet j'ai trouvé et ca marche bien
Il ne me reste plus qu'a lancer les executables dans les différentes pages et là, je ne vois pas comment faire
je sais que l'on peux lancer des executables à côté, mais cela ne m'interesse pas, je les veux dedans
est-ce faisable ?
D'avance merci
Cordialement
Résolu !
Accéder à la solution.

Hello,
Attention, cette méthode était valable avant, et sur Windows XP (ou antérieur) :
- http://digital.ni.com/public.nsf/allkb/8545726A00272EB0862571DA005B896C?OpenDocument
Pour les raisons citées, désormais on utilise plutôt les bibliothèques empaquetées. Elles sont compilées, donc pas de risque d'avoir de fuite de code :-)
Un très bon début avec cette architecture :
- https://decibel.ni.com/content/docs/DOC-19176
Alternative moins crédible : appeler les exe par la fonction "System Exec", et jouer avec les fonctions Windows (au fond de user32.dll) pour que la fenêtre des exe soit une fenêtre enfant du VI appelant...
A+
--Eric
Eric M. - Application Engineering Specialist
Certified LabVIEW Architect
Certified LabWindows™/CVI Developer

Labview 2011 file layout in executable

I am working on upgrading my projects from v8.6 to 2011. one thing i noticed was that the file layout in the built executable has been changed to treat the executable itself as the root directory of the code sources.
To better address my problem, i would like to present an example as below:
I have two projects, A and B, where B is built on top of A. Their paths are:
C:\Workspace\ProjectA\source\Always_Included1.vi ...
C:\Workspace\ProjectB\source\Always_Included2.vi ...
in the built executable(ie. Application.exe) i found that all VIs were located under such as:
Application.exe\Workspace\ProjectA\source\Always_Included1.vi ...
Application.exe\Workspace\ProjectB\source\Always_Included2.vi ...
Since the "Workspace" is just a variable name for one of my workspaces, I am wondering if it's possible to make the built executable to start with one level deeper, such as:
Application.exe\ProjectA\source\Always_Included1.vi ...
Application.exe\ProjectB\source\Always_Included2.vi...
*notice that the "Workspace" has been omitted.
Thank you.
LabVIEW 2011 newbie >.<
Certified LabVIEW Developer

I don't think there's a way to really control this, as this is something which is done automatically by the application builder.
A couple of options I can think of:
Place the top level VI in a level above ProjectA and Project B. This might cause the EXE to consider that as the main folder and start from there.
Check the 8.x check box in the Advanced page of the build settings. This will cause the build to be flat instead of a hierarchy, but I wouldn't recommend that, as that's basically a flag for backward compatibility.
The real question is what's your actual problem? Most people don't care about the actual location of the files inside the executable. If you do need access to a specific file, using relative paths is generally enough, as they stay the same inside the EXE. Another option which people use to control this is to direct some VIs to be saved outside the EXE (the build spec allows you to do that), but that's usually for specific use cases, such as calling plugins.
Try to take over the world!

Cannot execute a library created with Labview 2011 in visual C++

I created a very simple DLL in Labview 2011, then, I try to call this DLL from a Visual C++ 2005 application.
I have tried to load the DLL at compilation time with the .LIB and .H files, and also dynamically with AfxLoadLibrary.
When I try to call the library function, it works fine, but the second time i call the library freezes the app.
all the library does is to show a simple dialog box and that's it, no params, no returns, no nothing,
but it freezes the app, why the VI works in Labview, but in DLL doesn't?

Hi Alveru,
What might be happening is that the process never ends and when you try to re call it, it fails and that it is why your app freezes, what you can do to probe is that is what is happening is to test your DLL directlly in LabVIEW with the Call Library Function Node so you can import the DLL and test it. If it also freezes or not work as expected the problem is with the DLL.
The proceses are automatically closed by LabVIEW at the moment the VI stops running; however, when you deploy the vi, you need to close them manually.
Try this out!!
Regards,
Luis Fernando
National Instruments Cono Sur
Ingeniería de Campo y Consultoría
http://chile.ni.com/

How to start an 8.2 app in LabVIEW 2011

This has been a problem that I've been trying to deal with for the past week to no avail.
In short:
The 8.2s which worked on an XP machine were openned on a Windows 8 with LabVIEW 2011, made into an executable, put back on to the Windows XP to see if it will still all worked, and it does not.
In detail:
I had a ready made, working application made in LabVIEW 8.2. The goal is to update all old software to the new LabVIEW 2011, but to still make it work. The problem is, after making it run in edit mode for at least a little bit (after debugging common errors with openning in a newer version), after making an executable and putting it on the machine it used to run on, it won't run. The program will not communicate with the machine and will give the following errors which are, my eyes, things that should not be happening after working in edit mode.
Two error codes received:
1) One or more Configuration File(s) are not available. Please Check the Hardware configuration!
2) {
Error 7 occured at Openfile+.vi: Open file
Possible reason(s):
LabVIEW: File not found. The file might have been mover or deleted, or the file path might be incorrectly formatted for the operating system.
For example, use\ as path separators on Windows, : on Mac OS X, and / on Linus. Verify tht the path is correct using the command prompt or file explorer.
=========================================
NI-488: Non-existent board.
Please, if anyone has had the same or a similar issue and can give any sort of feedback or thoughts, I would greatly appreciate it. Thank you!
-Hub25

Bob_Schor wrote:
There are a number of issues here. First, LabVIEW 8.2 cannot be installed on Windows 7 (to say nothing of Windows 8), and LabVIEW 2011 cannot be installed on Windows XP. I'm not sure whether executables can be built across Windows 7/XP boundaries, but I'm pretty sure that, at a minimum, you'd need to install the LabVIEW 2011 Run Time Engine on the Windows XP system (and I don't know if this is possible).
After next April, Windows XP "turns into a pumpkin" as Microsoft drops support for it. A good time to migrate to Windows 7!
You can install LabVIEW 8.2 on a Windows 7 computer. I have that right now specifically for converting old code. And I am sure LabVIEW 2011 can go on XP as well.
I'm guessing the main issue is the lack of the 2011 Run-Time Engine on the XP machine. But I would also advise moving away from the OpenFile+.vi since that is a really old VI and the newer LabVIEW file I/O primitives are so much better anyways.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Install labview 6.1 (or compatible) run-time engine with labview 2011

I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
Solved!
Go to Solution.

Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

LabVIEW 2011 to 7.1 VI

Hello,
I need a conversion of my VI to the 7.1 version.
Thank you
Attachments:
correlation.vi ‏19 KB

Hi there,
Can I please get some assistance on the following issue?
I have one application (let's call it A), which was built on LabVIEW 7.1. Unfortunately I don't have 'VI' for it, I only have an executable file (.exe). The main purpose of this application is to read the BIN data.
I have one more application (let's call it B), which was originally built in LabVIEW 7.1. I have a VI for it. This application creates some data files which is in a BIN format. I recently made some changes in this application using LabVIEW 2011 SP1.
Now, when I try to read the BIN files (created by Application B), it doesn't show / read anything in Application A meaning it is not compatible.
I remember when I had this problem earlier, I asked that person (who initially built Application B) to modify the code for me and make an executable (.exe) for application B, so in this way I was able to use it and read the BIN data in Application A.
However, I am still keep modifying the code in Application B, so I would like to run everything smoothly on my end without bothering that person to update the code and make executable for me.
Is there a way around this problem since I would like to modify the code on LabVIEW 2011 SP1 for future updates? What are my options here?
I will be waiting for someone's help on it.
Thanks!!!

LabVIEW 2011 WSN Module?

I just received a NI WSN Starter Kit and it came with LabVIEW 2010 evaluation disks and the WSN Module Pioneer 2010. On my work laptop I have recently removed LV 2010 to upgrade to 2011. The WSN Module won't install without LabVIEW 2010...
Is there a walk-around or a new version of the WSN Module for LabVIEW 2011? Or do I have to install LabVIEW 2010 again?
Thanks.

Hello GrigS,
This is Andrew Brown, an Applications Engineer from National Instruments. There is a newer version of the NI-WSN driver (1.3) that is compatible with LabVIEW 2011. You do not need to install LabVIEW 2010 again.The download page for the driver is:
NI-WSN 1.3 - NI Wireless Sensor Networks - Windows 7/Vista/XP x86
Please note the installation instructions on the page are:
Installation Instructions
Perform the following steps to install NI-WSN 1.3.0:
Install LabVIEW
Install LabVIEW Real-Time Module (required for NI 9792 and NI 9795 support)
Install NI-RIO Driver Software 4.0 or later (required for NI 9795 support)
Download and run the self-extracting executable NIWSN130.exe. This will install NI-WSN 1.3.0 and all necessary driver files.
Regards,
Andrew Brown
Applications Engineer
National Instruments

Labview 2012 Runtime Ubuntu

Hello. I am trying to distribute a compiled labview program on Ubuntu linux machines. However, I can't seem to get the Labview Run Time Enviroment to install on Ubuntu in order to run the executable. Has anyone managed to do this? I have tried using Alien to convert the .rpm into a .deb. However, whenever I do this I get a weird Alien error that I can't seem to debug:
Error executing "rpm -qpi 'labview-2012-rte-12.0.0-1.i386.rpm'": at /usr/share/perl5/Alien/Package.pm line 489.
I would appreciate any help.

This configuration is not officially supported by NI, but this forum post may be helpful to you:
http://forums.ni.com/t5/LabVIEW/LbVIEW2012-Linux-Ubuntu-12-Installation/m-p/2304470
Applications Engineer
National Instruments

LabVIEW 2011 compiled application icon missing

Previously when I built an application the VI Icon would appear in the top right corner exactly the same in the compiled executable as it did in the VI.
Since upgrading to LabVIEW 2011SP1 all I get is a blank/question mark, icon missing indicator.
This happens for all of my compiled applications regardless of what icon I specify, even if I leave it as the default.
VI icon looks like this Application icon looks like this.
Just to be extra clear, there is no problem with how the exe icon appears in windows explorer and shortcuts.
I am ONLY talking about how the front panel icon in the top right corner appears.
The application works, it just looks ugly/unprofessional.
Is this a bug? Do I have something configured incorrectly? Is there a workaround? Has anyone else noticed this?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I tried building on another computer. It works properly.
My usual development machine is running Windows XP SP3.
The other computer I just tried a build on is running Windows 7 and that works fine.
I'm trying a repair of the XP installation now (I'll get back to you in a couple of hours!).
One other possible difference is that on the XP machine I installed the LabVIEW 2011 SP1 f1 patch.
Now I can't remember if I uninstalled it again afterwards. How can you tell if the patch has been applied or not?
I can't remember if I did it on the Windows 7 machine too???
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Utilisation d'une camera Gig E via swich sous Labview 2011

Bonjour,
J’ai besoin d'acquérir des photos grâce a une camera Baumer Gig E sous labview.
J’ai plusieurs composant connecter a mon ordinateur en Ethernet (Carte DAC, Camera, Moteur...) et j'utilise donc un Switch.
Problème: la camera n'est pas reconnue a travers le Switch, Pourquoi? (elle fonctionne très bien lorsque elle est directement relier a l'ordinateur).
Merci de votre aide.
P.S j'utilise labview 2011 avec vision acquisition et vision développement

Bonjour,
Tout d'abord, je vous confirme bien que c'est faisable, c'est même spécifié dans une de nos documentations.
Je ne sais pas quels sont vos réglagles mais votre switch supporte-t'il les jumbo frames ?
Voyez-vous toujours vos autres périphériques ?
Quand vous parlez de non reconnaissance, est-ce dans MAX ou directement dans LabVIEW ?
Cordialement,
Mathieu P. | Certified LabVIEW Associate Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

Labview 2011 NI Report and error 7

I know this topic has been cover in this forum many times, but I just can’t get it working.
Recently, we have updated our labview from 8.2 (Window XP) to 2011 sp1 (Window 7), and of course, NI report stops working.
In our software, we have a project that eventually gets compile into a DLL (Not AN .EXE, THIS IS NOT AN EXECUTABLE). In this DLL, we modify an excel spread sheet. As a result, we need the NI report tool kit.
Now I know that you would have to manually include the two folders (NIReport and LVclass)in your project in order for this to work in labview 2011, which I did by following the link below.
http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument
I made sure that the two folders were “Always Included”, and not using the labview 8.x file layout. After the compiling has been complete, one DLL was created (with 4 other files, which is good because I only want one DLL). I assumed that the NI report tool kit is included in the build since I selected “Always included”.
After that I ran my main top level vi. The main top level vi tried to access the DLL, and I got error 7,
Get LV Class Default Value.vi<APPEND>
<b>Complete call chain:</b>
Get LV Class Default Value.vi
Test.vi
<b>LabVIEW attempted to load the class at this path:</b>
C:\BUILD PATH\DLL NAME.dll\1abvi3w\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass
Now I assume this might be caused by two reasons. The path is incorrect or the tool kit wasn’t included.
I have been working on and off with this problem for weeks and still can’t get it working. I am guessing the path is incorrect, but I have manually changed the path to something different but got no luck. Any suggestions?
Solved!
Go to Solution.

Hi,
Thanks for the reply.
The reason I didn't select "use Labview 8.x file layout" is because it will also create 10 extra support folders (I think this is due to name conflicts in the DLL directory) after compiling the project. This is not an acceptable solution for my customer since no one would want a DLL that comes with so many extra files.
And yes, I am aware of the file layout after Labview 2009. However, the path to NI_Excel.lvclass (C:\BUILD PATH\DLL NAME.dll\1abvi3w\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass) was provided by “Excel class path.vi” (vi.lib\Utility\NIReport.llb\Excel class path.vi). In “excel class path.vi” it checks to see if the application is using the 8.x layout or not.
I switched to “use Labview 8.x file layout” just for testing reasons but it still doesn’t work. The file path for NI_Excel.lvclass is now C:\BUILD PATH\DLL NAME.dll\Excel\NI_Excel.lvclass (provided by “Excel class path.vi”). I also hard coded the path to C:\BUILD PATH\DLL NAME.dll\NI_Excel.lvclass and that doesn’t work too.
I have created a simple project to demonstrate my problem. Copy the attached folder to your desktop and you will see a folder named “Excel”. Open the “excel Test” project and build the DLL, check the build path and make sure it’s building to “Desktop\excel\Exceltest”. After that go to the DLL TEST folder (\Desktop\excel\DLL TEST) and run DLL test.vi. Make sure the path to the DLL (on the block diagram) is correct and run the vi. You should see the error I am talking about.
Thanks,
Attachments:
excel.zip ‏19 KB

Which LabVIEW 2011 system to buy?

I am looking to buy LabVIEW 2011 but don't know which level to buy. I am just getting it to run a program, that was already written, that corresponds with an Instron Stress Machine. If you need to see the program to tell the minimum version of 2011 it will run on, I can attach it to a post.
Thanks for your help,
Will Huntley

Will,
executing existing (compiled) code requires the RunTime Engine (RTE) which is free of charge.
But you will not get it to execute the code if it is still in VI form.
So you have two options:
a) get the finished code in the form of an executable (EXE). This requires the application builder for the person creating the EXE for you.
b) get a development version of LV in order to execute the VI form.
It seems that you are looking for option b) currently and you are correct that there are three different setups available. In order to compare those, please look there. Please see the green LED comparison table.
So as a short summary:
- You will be able to execute existing LV VI's using the Base Development Package even if the code includes certain components not part of this package (e.g. event structure/scripting). Note: You will probably not be able to run code using functions from LV modules/toolkits though (e.g. MathScript RT).
- You will not be able to modify certain components of the code if they are not part of the selected package. E.g. LV 2011 Base Development Package won't let you modify content of event structures (if included in the code).
- The application will possibly require more than just LV to run (driver, toolkits, ...). Many drivers are available for free, but there are also drivers/components requiring license costs.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Labview 2011 on Win7, OS causing serial loopback message corruption when clicking on top of windows?

I'm wondering if anyone else has seen problems like this.
I've been tearing my hair out over debugging some code. I have a ftont panel, I'm using some LEDs to send messages through the NI RS232 cable I bought, and have connected with a connector in a loopback fashion.
I've been trying to read the incoming messages from loopback...and based on those, changing indicators and controls on the front panel.
I could not figure why values were changing at strange times....like T's were turning to F's (I'm working with the serial data as boolean arrays).
Well, I was simplifying code, and mostly running right...but every once in awhile, it appeared that my front panel indictors, especially the values I'm changing based on the loopback serial messages would *BLINK*.
I happened to be looking at the Probe Watch window...and I saw where my probes were correctly showing on a couple spots (a left and right indicator) TTTTTTTF and TTTTTTTF......these appear at times to change T's to F's and vice versa.
I then started clicking around...and found this is almost always caused, when I click the mouse on the top of the window...the part that you usually click and drag to move a window around the Windows desktop!!!!!!!!!!!!
I can see this happen when I click on ANY window on the Windows OS desktop!!!!!!
It appears that the OS is messing with me..............?
I'm using Labview 2011, 32-bit on Win7....I believe the OS is 64 bit.
Has anyone seen behavior like this before?
Thanks in advance,
cayenne

Matthew Kelton wrote:
When you are probing, are you looking at the actual spot where you are getting your serial data, or are you looking at it after you've done some processing? I would look at the actual raw data and use a serial port capture utility (there are several free ones on the internet) which will confirm your data is coming in correctly.
What is your CPU running at? If it is pegged at 100%, something has to give.
Is your entire VI running in the UI execution system? If you post your test code, it sounds like it would be easy enough for someone to do a loopback test of their own to confirm similar behavior.
Thanks for the reply. No, CPU isn't being hardly used at all...this is a new lenovo laptop.....high end Dell U2711 monitor...
Task Mgr while Front Panel running:
I'm looking after I've done some processing....
I'm new to working with serial port stuff....I don't have a serial port capture device...?
Thing is...when I run this in debug with breakpoints and stepping through...I don't see this happening. But when running at full speed, and especially when I click on any of the open windows on my desktop, along the top margin where you would click and drag a window around...I can see the serial data in the probe jump...and all data going through the serial port and being displayed on the front panel changing values...
On my VI, I'm actually constructing the byte string...sending it through the serial loopback, and receiving it and acting on it. I can see the data going in is the same as is coming out...it just seems to quickly corrupt and then come back again...like maybe it is getting interrupted by the Win7 OS....?
I can't really post the whole code here...proprietary stuff...that's why in the past, I was posting a separate, simpler vi with only the parts I was having problems with....
I think I have full support with NI...I wonder if I could send them the code to look at, with more confidentiality...?
But again, I can make the problems happen, when it and the probe window is open, in real time...by clicking on windows.
Also, this tends to explain problems I saw earlier...when running slow, all was well , when debugging with break points and stepping through. But at full speed, unexplained...things would start resetting without explanation...and without regularity.
C
I"m not sure what you are asking with "Is your entire VI running in the UI execution system?"....I have the one vi running, and only that vi is running.....

Error -1074397038 occurred at IMAQ Start.vi for 64bit Labview 2011 SP1, Win7

Hello,
I am using a MC1362 camera from Mikrotron with a PCIe1433 framegrabber. I was using it with windows XP, 32 bit, labview 2010 SP1 32 bit, it was working perfectly fine. I just switch to windows 7 with labview 2011 SP1 64bit, and it is not working anymore with my custom routine in labview, though it works with MAX and camera file generator and I use the same camera file.
When I run my routine, I have this error message:
Error -1074397038 occurred at IMAQ Start.vi
Possible reason(s):
NI-IMAQ: The requested serial termination string was not found in the returned buffer.
Then, If I try to run the camera with MAX, it doesn't work anymore, I have to reboot the camera, and put it in the right mode with the Mikrotron control tool to obtain an image.
I have seen similar issue on a Basler camera on the forum, and it has been solved by using a camera file to set the different parameters. There is no camera file complete to set all the parameters of the camera, so I had to program them in serial to drive the camera with my Labview routine.
Could you help me to solve this issue please?
Thanks
Bests
David Dulin

This forum post is already handled --> SR 1154262.
Kind regards,
Corné Westeneng
Applications Engineer
NI-Netherlands

Lancer un executable Labview 2011 dans Ubuntu 11.10

Similar Messages

Maybe you are looking for