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!

Similar Messages

Please convert Labview 2011 file to Labview 7.0

Please convert Labview 2011 file to Labview 7.0. Thanks alot!
Attachments:
FreqResponse.vi ‏104 KB

attached
You will need to replace the front-panel graph. Downconversion sometimes corrupts graphs.
Attachments:
FreqResponse.vi ‏299 KB

LabVIEW 2011 file selection fails to fill in the file name into the "File name:" field

In LV2011 I am selecting a text file while my code is running. The "file name:" field is not populated with the selected file name.
This is inconvenient, especially if I want to modify a file name by one or some few characters.
How do i make LV 2011 behave like the previous versions?
Scientia est potentia!
Attachments:
File name is not filled in.PNG ‏72 KB

Thank you fot your reply it causd me to find the problem.
I figured it out while I was trying to extract the applicable section of my code to send it to you.
I had an asterisc wired to the "default name" input of the "File dialog" VI.
Now I am not wiring anything to the "default name" input of the "File dialog" VI and it works just fine.
I am sorry for your lost time.
Scientia est potentia!
Attachments:
Corrected code.PNG ‏10 KB

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

Transfring from CSV file to LabVIEW 2011 and view it in XY Graph

Hi, I would like to seek for your assistance in my project.
I have an excel file which is in CSV format and intend to transfer it into LabVIEW 2011.
I want to create a storage to store all the excel file for viewing purpose and in the mean while I want to view it in graph form.
Hope to that you will be able to help me with this. Thank you.
Attachments:
History_power2013-10-27 12-53-32 ch1 tv ch 2 fan.csv ‏209 KB

Thank you for replying.
But I have problem displaying the whole CSV file.
However, I have a batch of CSV file to monitor, so is there a way to consolidate all the data in one page?
Attachments:
Open CSV file and history files.vi ‏33 KB

Use LabVIEW 8.x file layout

Hi there,
From the LV help:
Specifies to use a flat file layout to store source files inside a stand-alone application, shared library, or Web service. LabVIEW enables this option by default for build specifications you load from LabVIEW 8.6 or earlier. National Instruments recommends you disable this option for applications you develop in LabVIEW 2009 or later.
Why shouldn’t I use the LV8.6 way?
Or, why is the LV2009 or later method better?
Thanks in advance for any reaction!
Best regards

Okay yeah the OO reason is a good one, but let me make a more basic example that I think is also a common one.
Lets say I download some cool library from the tools network. This library can do things like read and write .DOCX files (this is just an example). This library contains VIs like "Open.vi" and "Close.vi". Other libraries may also have "Open.vi" but they are part of a different library. And in memory these names have the library appended. So my VIs name in memory is actually "Cool Office Library.lvlib : : Open.vi". This way LabVIEW can distinguish between the VIs that have the same name on disk, but are part of a different library.
Now it should be obvious that the "Open.vi" from one library cannot exist in the same directory as another "Open.vi" even if they are part of different libraries. Windows simply doesn't allow you to have two files of the same name, in the same directory.
And this is where the file layout comes in. In 8.x and older the layout was flat, putting all VIs needed for the EXE into a single directory. This would mean attempting to put my office "Open.vi" in the same directory as all the other VIs. In 2009 and newer this is handed by making an EXE that isn't a single directory, and instead it is layed out more or less like it is in Windows, where one "Open.vi" can exist in one directory, and another in another directory.
So if you choose the 8.x layout, and you have multiple "Open.vi" files, it will place them outside of the EXE without any block diagram. This gets messy because now you EXE isn't the only file you need, you also need the support directory some times called "Data". In the 2009 and newer layout all the VIs can be in the EXE in a nested directory structure. Generally just don't use the 8.x layout unless you need to, and really you should need to. Having that not checked helps fix naming collisions.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

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/

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...

Conversion of 5.1 file into Labview 2011

Could you convert this VI from 5.1 to 2011
Thank you
Solved!
Go to Solution.
Attachments:
from 5.1 to labview 2011.vi ‏959 KB

Attached as 8.2. Hope you know the password.
Attachments:
from 5.1 to labview 2011.vi ‏309 KB

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

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

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

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?

Application crashes when calling DLL built with LabVIEW 2011

Hello everybody,
Our application calls DLLs built with LabVIEW 2010 SP1. We installed LabVIEW 2011 and built some DLLs. So far so good. If we start our application and run 2010 DLLs it still works fine. If we run a 2011 DLL just once no error happens, but if we try to run the same 2011 DLL our application crashes reporting the error below. I saved the code for 2010 version and built a DLL and it works fine. Does anyone know why?
Thank you in advance.
#Date: Fr, 16. Sep 2011 16:25:25
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: PasTA
#Version: 11.0f2 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x30000000
16.09.2011 16:25:26.181
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 8a779b3f-51d7-4864-8e4d-6ab0195cd158
ExceptionCode: 0xC0000005
N
0x3072C804 - lvrt <unknown> + 0
0x3072CBB8 - lvrt <unknown> + 0
0x7C864191 - KERNEL32 <unknown> + 0
0x7C83AB50 - KERNEL32 <unknown> + 0
0x00000000 - PasTA <unknown> + 0
Attachments:
error.PNG ‏11 KB

On that note, you should be able to create DLLs in 2010 and run them with 2011, correct?? In my case, I have a 2010 built DLL (talking to sbRIO), most of the functions work when run in 2011, but a couple of them lock up LabVIEW on the desktop (but not the sbRIO), no lock ups happen with 2010 on the desktop.

Labview 2011 file layout in executable

Similar Messages

Maybe you are looking for