Support files in LabView 8.0 Executables

I am using Lab View 8.0 to write a program and I have some suppot files such as JPG pictures, pdf files and (.wav) audio files that I use in the program.
For Example:
I have made a ‘Help’ button in the program. If the user clicks the button, in my block diagram I have the pointer/path going to C:\Program Files\SCUorderSupport\Help Pics\Pic2.jpg. I basically have set the default value of the ‘path’ to that location so everytime the user presses the help button, that picture comes up on the front panel.
I have similar paths for audio files (.wav) and pdf files when the user clicks certain buttons on the Front Panel.
I tried to generate executables of the program to provide it to the intender users. But when the user runs the program in his computer, how will the program find those support (pictures and audio files) files in his folders? The program in not responding to those buttons in the executable.
Could I get some steps to do this? I have never made an executable before, so maybe I am missing something!!
Thanks.

I seem to have tried everything. Here is what I did:
1.      I created a new Project.
2.      I added the VI to it.
3.      I didn’t see any support files in the project tree, so I right clicked and added the jpg and pdf support files.
4.      I created a new application.
5.      In the Source Files, I gave it the correct startup VI, and the support pdf and jpg files.
6.      I built the application.
7.      I created an installer.
8.      In the source files, I added the application and the support files (pdf,jpg) from the tree into the destination area.
9.      I built the installer.
10. I ran the installer in the user’s computer.
Here is the issue:
In my labview program I have the path for the jpg file directed to C:\Program Files\SCUorderSupport\Help Pics\Pic2.jpg in my computer. But in the user’s computer he has the Pic2.jpg file loaded in a different folder after running the installer. So when the user runs the program and presses the button on the front panel to pop up the Pic2.jpg, he gets an error since the program cannot find that path in the user’s computer.
Am I doing something wrong!!

Similar Messages

Problems with installation of system and support files with Labview 5.1 on Windows NT.

I make installations disks with Labview 5.1 on Windows NT and I need to add some system files and other support files. When I'm in App Builder I choose them in "Add support files" and I mark their "custom directory destination" (c:\winnt\system32, c:\est\base) but, when I test the installation I see that files don't save in this directory, they save in 'C:\c\winnt\system32' and 'C:\c\est\base'. How can I solve this problem?

Jorge,
I know there were some problems with the LabVIEW 5.1 Application Builder that were fixed in the LabVIEW 5.1.1 Updater. I recommend you download that update to see if this fixes the problem. Also, double-check to make sure you have typed the file paths correctly. If you continue to have problems after installing the 5.1.1 updater, please let me know, and please attach your .bld file so I can examine it for any problems.
Thanks for your patience on this issue, and have a pleasant day.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Convert executable and supporting files to msi

Hello all,
Wanting to know if it is possible, or if anyone has tried, to roll a labview executable and supporting files into a .msi microsoft installer package. Wanting to do this for its auto exection and encryption. I have attempted using third party applications like "Advanced Installer" and Altris wise package studio with no avail. I found the following old post describing this exact problem using a different third party applicaiton and labview 6.1. I am currently running Labview 2011 professional.
http://forums.ni.com/t5/LabVIEW/Repackaging-Labview-using-Veritas-Wininstall-fails/td-p/89442
I know that Lab-windows can be used to package a .msi installer but I do not have access to it nor am I trained to use it.
Just wanting some information, any information, on how to make this happen.

When you built the exe in the project, you should have noticed the option to create an installer. Fully documented in the LabVIEW help.

Error 7 when opening file running LabVIEW 2010 executable

I am using Open/Create/Replace File in LabVIEW 2010 to open a text file. This works fine until I compile the code. I then get Error 7. I have tried paths that look like the following but none work.
c:\<directory name>\file.txt
c:\<application name.exe>\file.txt
c:\<application.exe>\<directory name>\file.txt
Thanks
Solved!
Go to Solution.
Attachments:
read.vi ‏17 KB

You have to get the path to the folder of the .exe. Then strip off the .vi name and the .exe name. Then Build onto the path from there to get to your .txt file. The way you have it, you are treating the .exe as a folder rather than a file. The text file is not part of the .exe, so you can't create a path that includes the .exe name.
Why Does My Executable Not Work When Using the Current VI's Path Constant?

I get an error 1 when I'm building an executable file in Labview 6.0

I'm trying to create an executable file in labview 6.0 but I get an error 1 (see attachment) with a GSim file (control and simulation toolkit). I didn´t install the toolkit (on the computer i´m trying to create the executable) because we lost the CD and we had the toolkit installed on another computer so I copy the files I needed.
Attachments:
error1labview.doc ‏56 KB

You probably have a linkage issue.
Open the top level VI on the machine that has the toolkit installed, and make sure that it opens without an error (the run arraow should be white). Press : ctrl + shift + run arrow. This forces a recompile of the code, and will update the internal links to all the sub-VIs. Then, save the top level VI, and close it. Open a new VI, so that there is only one VI in memeory, and it is a new (blank) VI, and try to build the applictaion again.
J

Error 8 File permission error while building executable for a RT

I got error 8 File permission error while building executable for a RT. It happened always after build, I mean new startup.rtexe and startup.alias files have been created. At the build properties, it was set use default .alias file.
I had the executable built successfully at one time.
The detail message is:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 8 occurred at Open/Create/Replace File in RTBEP_Generate_Deploy_Instructions.vi->RTBEP_Invoke_Build_Engine.vi->RTBUIP_Build_Invoke.vi->RTBUIP_Build_Rule_Editor.vi->RTBUIP_Open_Properties.vi->RTBUIP_Item_OnDoProperties.vi->RTBUIP_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
I checked relevant posts, couldn't find any clue.
Please give me some ideas.
Thanks.

Hi Ya-hoo,
Error building application in LabView 8.0 seems to describe a similar situation. The .alias file is important, as described in that discussion forum.
Cheers.
| Michael K | Project Manager | LabVIEW R&D | National Instruments |

Would a LabVIEW 8.5 Executable play nice with LabVIEW 7.1 Development on the Same System?

Our testing computer right now just has the user run the corresponding .vi file since we have LabVIEW 7.1 installed on the computer.
If I use 8.5 to compile this .vi to an executable, I realize that I must install the run-time support for 8.5. My question is what effect will installing the 8.5 run-time have on the ability to continue to run the other 7.1 VIs with LabVIEW 7.1.
Should I be concerned with losing MAX settings when installing the run-time support for 8.5? I want to be able to run 8.5 executables but also able to open up a 7.1 .vi file in LabVIEW 7.1 and run it that way also.
Thanks for your help! I have 8.5 on my system and the idea is to slowly replace the running of the .vi files with .exe files, I was just curious in case my .exe doesn't work I can still run the tests with .vi in the mean time.
Thanks for your help folks!

Just note one thing - installing the 8.5 RTE should have no effect on 7.1, but if your executable requires drivers (e.g. DAQmx) and you install a version which no longer supports 7.1, you will lose the ability to work with that driver in 7.1. I don't think NI has any drivers yet which are not supported in 7.1, but I believe there are some which are no longer supported in 7.0.
Try to take over the world!

How to make the Installer place support files in specific folder

Hi,
I'm trying to use the LabVIEW2009 installer for the first time. I haven't used any earlier ones, so my understanding is limited. I have created a project and an executable and wish to direct the installer to place some groups of files in a number of directories other than the one in which the executable goes. On the Source Files page I can see a number of Folder descriptions in square brackets. I don't understand how to use these. Are they to be set up to point to specific directories? If so how?
So far I have managed to create an installer which puts all the support files from the project in a single directory. My attempts to select a subset of files within the Project View window and place them in a separate directory were not allowed since they are treated as an indivisible group. Basically i don't know enough about the installer and my searches for information have only yielded very basic information.
If anyone can help by supplying or pointing to more detailed information I'd be most grateful.
Thanks
George
Solved!
Go to Solution.

Hi George
This is from the LV help:
Destination View—Specifies the location and directory structure of the files when they are installed. Select an item from the Project View tree and click the arrow button or drag the file to the Destination View tree to include it in the installer directory structure. You can drag multiple files at the same time. Click the buttons below the Destination View tree to add, remove, and rename folders in the directory. You also can right-click the folders and select a command from the shortcut menu.
The folders in the Destination View directory that do not have an LV prefix correspond to Microsoft Installer (MSI) properties that install files in the following locations.
[CommonAppDataFolder]—Files you include in this folder install to the Application Data folder.
[CommonFilesFolder]—Files you include in this folder install to the Common Files folder.
[DesktopFolder]—Files you include in this folder install to the Windows desktop of the current Windows user.
[LVxxRTEDIR]—Where xx is the LabVIEW version currently in use. Files you include in this folder install to the folder of the Run-Time Engine for the LabVIEW version currently in use.
[LVDIR]—Files you include in this folder install to the folder of the LabVIEW version currently in use.
You can find a full list of the MSI properties here. Scroll down to "System Folder Properties"
Best Regards
David

When running labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. Could someone explain this error?

I have a set of vi's that work when run under labview. However, when calling these vi's from labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. in Assign Connector Pane.vi->Call Test.vi->Execute Pre-Run.vi->Test Executive. Could someone explain this error to me? (or ideally tell me how to fix it?) Thanks.

Hello,
There are any number of possible causes to this problem. Which version of Test Executive are you using? Have you upgraded your Test Executive recently? The latest version is 5.1.1. If you have changed anything about Test Executive on your computer recently, I recommend you perform a mass compile of all your VI libraries, as having different versions of the VIs on your system could often result in the "Call to Step XYZ Failed" errors. Also, are you using any DAQ or Analysis VIs in your steps? We have seen problems where the use of DAQ or Analysis VIs in the sequence can cause intermittent "Call to Step...Failed" errors. There are some KnowledgeBase entries on our website that discuss this problem. Are you using the Test Executive in the VI environment, or
as an executable? Again, there are some problems with using Test Executive as an executable that result in these errors, and there are also KnowledgeBase entries that discuss these problems.
If you have a pared-down application that demonstrates the problem, feel free to send me your VIs and your .seq file and I will try to reproduce the problem.
Alternatively, I would suggest you visit www.ni.com/teststand to learn about TestStand, our state-of-the-art Test Sequencing software that completely outperforms Test Executive. It is very easy to use and much more powerful, and we have a top-notch support team available dedicated exclusively to supporting TestStand. As you are probably aware, we are no longer developing Test Executive, and instead are concentrating our efforts on making TestStand the penultimate solution for all our customers' test sequencing needs.
I appreciate your patience on this issue. Please let me know if I can offer further assistance.
Have a pleasant weeken
d.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Supporting files outside .exe file

I have a labview executable which uses some resources.Currently I'm using the resources by giving file path.It becomes a problem when uploaded the executable and support files in the Internet and accessed from there.It loads only exe file and misses resource file.
Is there any option to embed resource files inside executable ?
Solved!
Go to Solution.

If they are not LabVIEW VIs - e.g. documents, external code (dlls) then no, I don't think they can be included 'inside' the executable. In your build specification you can set them to 'always include' and then in the destinations page select where they end up (e.g. in the same directory as the .exe, in a support directory etc.).
If you use the 'application directory' VI in the File I/O palette - this will return the path to either the project if in the development environment or the folder of the executable in the runtime engine. This should allow you to specify the path that will work whether in the runtime engine or development system. You can use conditional disable structures or the App.Kind property to determine if the VI is running in the dev suite or the runtime engine.
Also, the paths will only work on the local (or network) file system - you can't specify an internet address - LabVIEW won't be able to download the files from the internet unless you program your application to do that.
You should put the executable (build specification output that includes the .exe and your supporting resources) in a .zip file if you are uploading to the internet or create an installer.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Unzip files within labview

I have been playing around with the new zip functions in labview 8. I like it, nice and simple. Then I realized something. They don't have any functions listed to unzip files?!?! Am I missing something, or is there another method to call zip files in labview, unzip to a location, and then grab files from the unzip within labview programatically? The only method I can think of is to have winzip installed on the machine so you can use the command line execute function (but that is an awful method IMHO). I would have thought that if NI got the license to build zip files they would have also gotten the rights to include the unzipping as well.

Mads wrote:
Unzip functions in native G would be very useful, simply because that code is supported on the RT targets. There is an unzip option in the palette in LV 8.5, but it returns error 2 if I try to unzip anything with it...if the file only contains one file it works, but it retunrs the error and with more than one file inside the archive it fails....is it supposed to work, or is there still no proper unzip support?
I have code I want to move from a PC to a RIO unit, but the lack of a G-version of unzip makes this difficult, the OpenG alternative is not native G so no luck there...It seems the VIs available in LV 8.5 could do the job, if only some minor bug-fixing was done(?)
ZIP/Unzip support as native VIs is not very practical. Compression is a very tricky business and developing such algorithmes in a way that always works is not very easy and quite time consuming, not to mention that LabVIEW is not the ideal invironment to do low level bit shuffling and manipulation.
Combine that with the fact that there are ready made and VERY throughly tested open source libraries with the needed functions (of course mostly in C) and you really realize that trying to reinvint that wheel in LabVIEW itself is simply an exercise in vain.
The OpenG ZIP/UNZIP library is based on the wide spread zlib library that just about compiles on any C compiler that dates from after the early 1960ies and so it should be no problem to grab the according C source code from the OpenG Toolkit depository on sourceforge.net and recompile it with the correct C toolchain for your CRIO realtime target.
Oh and if you mean to transport the unzip algorithme to the FPGA target instead of the realtime target, keep dreaming. Once the FPGA chips start to reach the 1 Billion gate count this could actually start to get feasable. 3 Million gates is really nothing for such a task.
Rolf Kalbermatter
Message Edited by rolfk on 11-28-2007 11:22 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Print text file with labview 2011 and windows 7

I am having some strange problem, hope someone out there knows the solution.
We have a labview program running under windows xp, the program runs some test and print label from a local label printer. Last week, I have to upgrade the computer to windows 7 and all the sudden the printer will not print any more.
The print vi is very simple. I am using the report function and I am attaching the diagram of that vi below.
If I use windows notepad to open that small text file, I can print fine. This means the printer driver itself is OK. However, if I print the same text file through Labview printing vi, from the printer's task list, I can see it does not recognize the char. From the attached png file, the top one is the task from notepad, it shows 2 pages and the bottom one is from the labview, it becomes 33 pages.
For the printer part, I use Generic / Text Only printer driver which comes from windows itself. And I am aslo attaching a sample of the text file, there are quite a lot of special char, it is for print bar code. When I tried to use labview print text vi to print general text from my computer to a regular printer, the vi works. So it seems Labview print can not handle the special char? Although it worked many years under windows XP in the past.
Welcome to any suggestions!
Thanks
Attachments:
print vi.gif ‏9 KB
labview print bug.png ‏26 KB
SerialLabel.txt ‏1 KB

DGU wrote:
where to check RAW or TEXT? the print report vi only asks for file name and printer name.
When I print from notepad, everything just goes by default. This is a label printer, so I never need to specify printing parameter such as size, orientation, etc in the past
Famous last words go something like this: "...never had to do that before." Maybe you have to do that now. It's worth at least comparing the defaults settings for bothe generic drivers. It could save you a lot of headache if you notice something different.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

How can I read pdf files from LabVIEW with different versions of Acrobat reader?

How can I read pdf files from LabVIEW with different versions of Acrobat reader?
I have made a LabVIEW program where I have possibility to read a PDF document. When I made this LabVIEW program it was Acrobat Reader 5.0.5 that was installed on the PC. Lather when the Acrobat Reader was upgraded to version 6.0, there was an error when VI tries to launch the LabVIEW program. And Later again when we upgraded to Acrobat Reader 7.0.5 I must again do some changes and rebuild the EXE files again
It isn't so very big job to do the changes in one single LabVIEW program, but we have built a lot of LabVIEW programs so this take time to due changes every time vi update Acrobat Reader. (We have build EXE files.)
The job is to right click the ActiveX container and Click "Insert ActiveX Object", then I can brows the computer for the new version of acrobat Reader. After this I must rebuild all the "methods" in the Activex call to make the VI executable again.
Is there a way to build LabVIEW program so I don't have to do this job every time we update Acrobat Reader?
This LabVIEW program is written in LabVIEW 6.1, but I se the problem is the same in LabVIEW 8.2.
Jan Inge Gustavsen
Attachments:
Show PDF-file - Adobe Reader 7-0-5 - LV61.vi ‏43 KB
Read PDF file.jpg ‏201 KB
Show PDF-file - Adobe Reader 5-0-5 - LV61.vi ‏42 KB

hi there
try the vi
..vi.lib\platform\browser.llb\Open Acrobat Document.vi
it uses DDE or the command line to run an external application (e.g. Adobe Acrobat)
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

File path of a currently executing teststand test step

How do i extract the file path for the currently executing LabVIEW test step within my operator interface.
Many Thanks,
Dave.

Hi,
I assume you need the SequenceFile Path where the LabView test step is located in TestStand.
To reach to the currently executing step SequenceFile path you have to:
1. get the SequenceContext for the execution
2. get the currently executing step from the SequenceContext (SequenceContext.Step)
3. get the sequence in which the step resides from the Step (Step.Sequence)
4. get the containing sequence file for the Sequence (Sequence.SequenceFile)
5. get the Path from the SequenceFile (SequenceFile.Path property)
In case you want to determine the VI file path for the LabView test step Module one approach is:
1. get the SequenceContext for the execution
2. get the currently executing step from the SequenceContext (SequenceContext.Step)
3. get the PropertyObject for the step (Step.AsPropertyObject)
4. get the VI relative path from the step subproperty using "TS.SData.ViCall.VIPath" lookup string (PropObject.GetValString)
5. now use the Engine.FindFile on the retrieved path at the step 4. above, to get the path to the executing VI
Hope this helps,
Silvius
Silvius Iancu

Is it possible to overwirte data in a *.pdf file using LabVIEW??

hi,
i have a requirement to overwrite a pdf file using LabVIEW, i have to use coloring text also.
i have downloaded Exaprom PDF 1.0 toolkit. but it is to generate a new pdf file.
please suggest ideas
regards
phani srikanthSpell Check
phani srikanth

Modifying an existing PDF file is several magnitues more complicated than creating one from scratch. The PDF standard is VERY complicated and contains a myriad of features with their specific syntax elements. In order to modify an existing PDF you have to be able to understand every syntax element that occures in the PDF, or you may end up corrupting the file.
When you create a new PDF you can pick out the syntax elements that your tool supports and forget about the 95 other procent.
There are many PDF Toolkits than can create PDF files, a few that can open PDF files and present them, and almost none that can edit them. The Adobe PDF Editor being one of the few that can do that, but nobody is going to give away such a Toolkit for free.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Support files in LabView 8.0 Executables

Similar Messages

Maybe you are looking for