Build specification missing properties

I have created a build spec for my project but the tabs for Dialog Information, Shortcuts and Additional Installers are missing. See attached screen shot. How do I make them appear?
David
Solved!
Go to Solution.
Attachments:
My build spec.png ‏81 KB

You will create two specifications: (1) build the exe. (2) build an installer for the exe. One you have both in your project, you can do a "build all" when right-clicking the build specifications section header.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

Missing Build Specifications in LV8 Full Development package

After installing LV8 Full Development Version, the only Build Specification option available is "Source Distribution". The options "Application", "Installer", "Shared Library" and "Zip File" are missing. The correct serial number appears on the About screen so I assume I activated the package correctly.
How do I make those other build options available?

Buy the application builder - or upgrade to the professional version...
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Use of "Open FPGA VI Reference" function --- Build Specification vs VI vs Bitfile

When using the "Open FPGA VI Reference" function in a LV2012 cRIO application, there are 3 options: Build Specification, VI, or Bitfile. What would be the reasons for selecting one over the others? Does it affect the resulting startup.rtexe when the cRIO application is built? I searched through the help and in these forums, but I don't see criteria for selecting one over the others; maybe I missed it.

Hello Chris,
Apologies in advance for a long reply.
The reference method won't change the functionality of your rtexe.exe. They all end up dropping a bitstream, based on a bitfile, onto the cRIO's FPGA.
To a degree, the method used to reference the FPGA code is a matter of taste, but there are situations where one method is better suited than the others.
Reference by VI:
Setting the configuration options to open reference by VI is helpful during development when you are making changes to an FPGA VI often and building/testing using the same spec. When this option is used, a bitfile is selected based on the default build specification for the project. A project may have only one default build specification. You can make any build the default by checking the option under the Source Files category in the build properties. The default build is indicated in the project explorer by the green box around the builds icon.
Reference by Bitfile:
This option references a bitfile directly. Through the configuration window, you can select one specific bitfile to open a reference to (this is not dynamic and does not change unless you physically go make a change to that path). If you're using this method, it helps to give your bitfiles more meaningful names than the ones that are automatically generated by LabVIEW. When you run subsequent compilations off of the same build specification and do not change the bitfile nname or path in the build configuration, the old bitfile is overwritten and replaced with the new one. When you are using this option, it is critical that you keep up with which bitfile is the one you want to be using. There is an option now that will help alleviate any problems referencing by bitfile through the Open FPGA VI Reference function. There is a new VI called Open Dynamic Bitfile Reference. It is typically used when you want to chose a specific bitfile to load depending on something in your host code (a configuration option etc) - but it allows you to dynamically reference a bitfile on the block diagram by path.
Referency by Build Specification:
This option is good for when you want to always use a bitfile that is associated with/compiled with the same build configuration. Say you have two options for top level FPGA VIs in your project (each with its own build spec). Both of these VIs have the same interface (read/write controls, DMA) but they run different algorithms or something. This is nice because you can easily switch your host application between them by picking the build spec associated with the FPGA VI you want to use. In this type of sutation, referencing by VI is no good because you can only have on default build spec.
cheers.
Matthew H.
Applications Engineer
National Instruments

Build specifications gone

LV 8.5 on XP Pro
I have a project with the build specifications for an executable. The problem is that the startup VI's that are designated in the properties keep coming up missing. The ICON is still in the project, but when I go into the "source files" they do not seem to save. The problem is intermittent. I have tried entering the properties, saving and then closing and reopening LV and had no problems but then the next time I go to do a build I receive error "You did not specify any Startup VI's."
Also the installer properties continually are corrupted and I have to re-create the installer.
Any suggestions?
~gold

Hey Gold,
Thank you for contacting National Instruments. I'm not exactly sure if I understand your problem, so I do want to clarify what you have going on.
If I understand you correctly, you have a project with VI, documentation, etc, to create an exe as well as an installer. All files appear in the project explorer, and there does not appear to be any problems with the files there. When you go to build an exe, you select your startup VIs, and move them into the Startup VI's section of the build page. When you go to click build, you get an error that you have not selected any startup VI's. Is this correct? Are there any details you would like to add to that?
Also, can you please explain what you mean when you say the installer seems to be corrupted? Can you give any error messages, or a better description of what is going on?
Thanks,
Kevin H
National Instruments
WSN/Wireless DAQ Product Support Engineer

Scrambled destination view in installer build specifications LV8.5

I don't think this build specifications bug has been mentioned yet. I am using LV8.5 Pro under Win XP.
When configuring a new installer build specs, under Source Files, I select my application item in the Project View and click on the arrow button to add it to the Destination View. The latter then faithfully reproduces the application files hierarchy, for example:
Application Directory
    Manuals Directory
       Manual.pdf
    Application.exe
    Application.ini
    Startup.exe
    Startup.ini
However, after I close and reopen the installer properties, the Destination View hierarchy appears scrambled, for example:
Application Directory
    Manuals Directory
       Startup.ini
    Application.exe
    Application.ini
    Manual.pdf
Supporting files get moved around the directory tree, some disapper, and others actually appear in duplicate. The outcome is exactly the same every time I repeat this process, but there is no apparent pattern to it.
Now, when I actually build the installer and later use it, the application gets installed properly, with correct files hierarchy. What doesn't work are the shortcuts. For instance, in the above example, if I create a shortcut to Manual.pdf, it will actually point to Startup.exe. And if I need a shortcut to Startup.exe, I cannot create it because the target is not part of the Destination View.
Thoughts?

Dear Zador,
Bug number 4CM921LJ titled "Shortcuts Added in Installers Are Not Created Properly" is a LabVIEW 8.5 Known Issue. More information on the bug can be found in Knowledge Base 4EGEL6HY: Wrong or Incorrectly Disabled File Names Displayed in LabVIEW
8.5 Installer Builder. If you need an alternative to the workaround presented in the Knowledge
Base, you can create separate folders for each file you need to have a
shortcut created for instead of putting them all in one.
This issue has been fixed in LabVIEW 8.5.1. Please post back bug 4CM921LJ does not describe your problem.

RT Build Specifications: Component Definition Category is unresponsive

Hi,
I am using LabVIEW 2013 SP1 f2, with Real-Time 13.0.1
When I open the Properties page for a Real-Time Application build specification (to run on a cRIO-9075), and select the Component Definition category, I find that the following occurs:
- LabVIEW becomes unresponsive, and thinks for a while. It takes approximately 20-30 seconds or so to finally show the Component Defintion page.
- When I click on Create a component definition file (.cdf), nothing happens. As I write this, I see "Required software components", and then these are greyed out: "Software component description", and "Software version" - but there is nothing to select or change?
- If I click on another category, it takes in the order of 20 seconds to finally show this category.
- To close the build spec (by pressing OK), it also takes a long time (more than 60 seconds).
- Things are fine with the build spec if I never enter the Component Definition category.
Is anyone else experiencing this?
Any help would be appreciated.
Christopher Farmer
Certified LabVIEW Architect
Certified TestStand Developer
http://wiredinsoftware.com.au
Solved!
Go to Solution.

Hey Chris,
I believe the following patch is the fix that you are looking for.
LabVIEW Real-Time Module 2013 SP1 Application Builder Patch Details
http://digital.ni.com/public.nsf/allkb/D72B45C6905D327A86257CC800547992?OpenDocument
There's a link to download the patch at the bottom of that page.
Regards,
Ryan

Build specification freezes when trying to view "Shared Variable Deployment" screen

Labview 2009 f3
For some strange reason, any applications that include shared variable libraries will no longer build into executables.
I was able to build these applications without issue a week ago. However, when I went to make an updated build today, the build failed and I had to force Labview to close. When I view the build specification properties, I can navigate through all the option screens except the "Shared Variable Deployment" screen. As soon as I click on that option, the interface freezes up and I have to force Labview to close.
This problem does not occur for applications that do not include shared variable libraries.
I tried removing the shared variable libraries from the applications that were failing, but that did not correct the issue.

I never did find a proper fix to this issue.
One day I attempted to build the application again, but this time I got distracted doing something else. When I finally checked the build status a few minutes later I expected it to still be frozen, but to my surprise I found that the application did successfully build. To this day, that particular application still looks like it is going to lock up, but about about 8 minutes later it finally takes off and builds like nothing was wrong...like every other shared variable application I have created. So I guess my only suggestion is to let the application sit for a while and see what happens.

Build Specification does not include all files for my VI.

Hi!
As a part of a semester project i have build a VI to control a filtration unit. The VI is working fine on my computer, but I graduate next month and I have to deliver the files on to a person on the university. The problem is that even though i use the "Build Specification" function (i use LabView 2011 Professional Development System), files are still missing when the program is started on the new computer. A warning in the project file indicates that files are missing or removed to a different location. A file named pid.lib is not found, and it seems like the path to each file is the same as on my computer, but the build specification doesn't change that to fit the new computer.
I am a LabView newbe, and I have searced this forum and help files to try to solve this by my self, but now my time is becoming limited. Can anyone help me with this?
Henrik jepsen
Masterstudent Chemical Enginnering
Denmark
Solved!
Go to Solution.

Hi Henrik
You can see what versions of LabVIEW and which Toolkits is installed in Measurement and Automation Explorer (MAX). If you Open MAX, and Select "My System" --> "Software in the left menu, then you can see all software installed.
If you click on the LabVIEW installation. In this case LabVIEW 2011, you can see all toolkits installed.
When you run a LabVIEW project / application on another PC, LabVIEW will use a defined priority of where to load the files from. This is specified in Tools --> Options --> Path --> VI Search Path.
So LabVIEW will frist try to find the VI/VI library in the folder of your project and if the VI is not located there it will look for it as a build function in the vilib, userlib or instrlib folders of LabVIEW. These folders contains VI's and VI libraries installed with LabVIEW.
In this case, as mentioned above you properly don't have the same toolkits installed on both machines. Therefore the PID.lib is not found in the vilib folder as it should be, and thereby you get the error. You can confirm this by reviewing the installed modules as mentioned above.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark

Dynamically configure build specification version number

I have several build specifications in the same project under the same version control and I base my version numbers in part on my revision number:
<Major>.<Minor>.<Revision>
Right now, I'm keeping the full number in a text file which is distributed with all build specifactions. However, I notice the build specification configuration diaglogue contains an option to execute a VI before the build. I'm wondering if a VI executed at this stage can somehow edit the version number within the build specification that called it, such that I don't have to manually change the version number in every build spec, every time I want to build one.
Are there any canned functions that let you edit build specification things like version numbers?

Hi Kgolden and A. Zaatari,
Maybe it's not a current feature (I have to believe a NI Engineer ) but it's possible to do it.
I made a VI that automatically creates Build and Installer specifications and also changes their configuration (like name, path, and version number).
So, here is how:
- all this information are stored in the project file My_Project.lvproj
- My_Project.lvproj is actually a !!! XML file !!!
- Make a small VI that search in the XML for the following lines/properties:
      (1) App_fileVersion.build
      (2) App_fileVersion.major
      (3) App_fileVersion.minor
      (4) App_fileVersion.patch
For the App_fileVersion.build it should look like :<Property Name="App_fileVersion.build" Type="Int">115</Property>. Search for the pattern and change the value 115. Do the same for all four of them.
Pay attention!! After you change this value you have to restart (close and than open) the Project in order to apply changes. This can also be done automatically by using LabView Application invoke and property node: Invoke Node: Project/Close + App/Open.LV Document/Path. Be carefull that you should do this from a VI that is not added to the project.
Regards,
Paul

Weird error for build specification

I deleted some files from my project, and suddenly my build specifications aren't working anymore:
If I choose properties for "visualize", i get the error message:
Choosing "build all" from "Build Specifications" seemingly still works. I've tried deleting all project files and making a new project, but something is still amiss. Any clues?
Lars Melander
Uppsala Database Laboratory, Uppsala University
Solved!
Go to Solution.

OK, I threw out all files, made a new directory, rebuilt, and now it works. Dunno what went wrong though.
Lars Melander
Uppsala Database Laboratory, Uppsala University

How can I configure a Build Specification to install for current user only

Is there any way I can configure an installer build specification to install my application to the current user's folder? This does not seem possible at first glance due to the limited "destinations" available.
Ideally I'd want the application to be placed in "C:\Users\[USERNAME]\AppData", or some equivilent where it'd be protected from being run by other users without administrative access.
Has anyone been able to do this? Thanks!
CLA, CCVID, Certified Instructor

There is a destination called [Personal] that goes to the user's MyDocuments folder. Whether program files should be mixed with a documents folder could be debated.
I see the [Public App Data] choice, but I don't see a [User App Data] option.
Another possibility would be to allow it to go to Public App Data, but after the installation, run a VI that then moves the program folder to the User's Application Data directory. However, that probably means updating shortcuts as well. And I don't know whether that VI would essentially step on itself in trying to do that move.
Maybe another choice would be to allow it to install to the program file directory, but use CACLS to prevent users from accessing that directory except for explicit permissions to the one or more users you want to allow to execute it. An advantage is it would allow one user to install a program for another user to use. The disadvantage is the person doing the installing would almost certainly have to be an administrator.
A disadvantage of the method you desire is that a user has to be the person logged in and install it for themselves (assuming that group policies allow non-admin users to install their own programs). Another disadvantage is if you want to have more than one permitted user, it would need to be installed multiple times, one for each.
Perhaps you could install security at the front end of your applicaiton. Anyone can run it, but the application determines if the currently logged in user is permitted to run it when comparing against some sort of encrypted file that lists valid users. If the user is permitted, the program moves onto normal operation. If not on the list, the program tells them so and never advances onto normal operation.
Perhaps someone else can determine if there is a path tagged within the installer builder that goes to the User App Data that I am missing.

Java.lang.Exception: Missing Properties : [SQLINPARAM3]

java.lang.Exception: Missing Properties : [SQLINPARAM3]
I am getting the above message when I login to EM using a browser.
Why? How to solve this error message.
Oracle 10g R2 Windows 2000 Server.
Thank you,

Also if you could indicate latest non default changes to EM e.g any Blackouts settings, RAC etc

SOAP Use Adapter-Specific Message Properties and Variable Transport Binding

Hi Friends,
   I am new to use to Soap Adapter. Please help me out bellow doubts.
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
   2. Where exactly we r using below parameters.
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Thanks&Regards
G.Bhanuprakash

Hi,
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
SAP Help says both are needed to be checked when you want to process adapter attributes
Configuring the Receiver SOAP Adapter - SAP NetWeaver Exchange Infrastructure - SAP Library
These attributes can be get/set using dynamic configuration and their technical names are what you have pasted:
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Remote User - the username used to send a message to the adapter engine using SOAP
Remote Host - hostname which the remote user used
SOAP Action - SOAP Action of the XI webservice (sender) / SOAP Action of the receiver webservice
Variable Headers are additional key-value pairs in the HTTP Header that could be accessed in the XI Header using dynamic configuration. The limit is only three though.
Regards,
Mark

Instrument Control Build Specifications

Dear Sir:
      I am trying to build a working *.exe instrument control program. This is a simple program which only queries my test instrument with a *IDN? command.
      The program fails to call my instrument driver and the program also runs on boot up when (running under normal conditions) it should wait for me to input the GPIB address of my test instrument.
      Let's begin with the failure of Labview to communicate with the instrument driver.   This is some background information.
       When I run the program as simple *.VI in the Labview environment, the program runs perfectly.    No issues.
       When I use Agilent Connection Expert or MAX to communicate to the test instrument, communication is established and there are no issues - I receive a reply, connectivity is established.
        After I build the *.VI into a *.EXE program, this is where the program's issues arise.
       The *.EXE program fails to initialize correctly and fails to establish connectivity with my test instrument.
        Here are some issues that I have noticed about the program running in *.EXE mode
1) The program runs on "boot up" when you click on the *.EXE program.   In *.VI mode, the program does not run on boot but waits for the user to input the GPIB address of the test instrument - program run is designed to be enabled by the user.
      I do not believe this is the source of the problem but only an incidental consequence of the problem.   If I stop the program and input the GPIB address, I receive a message about not being able to communicate to the driver.
2) Once the *.EXE program runs, there is a condition whereby the operating system cannot close the program and WINDOWS itself cannot shut down itself unless I manually close all the programs associated with the *.EXE program in the WINDOWS operating environment.
3) If the labview program and *.EXE program are closed but the operating system is still running, Agilent Connection Expert and MAX can no longer communicate with the test instrument.   They no longer see the test instrument.
It is obvious that the *.EXE program is making a change which is causing the operating system to "hang" on shutdown and is also preventing the other programs from operating as they should.
I believe the source of my problem may be how I programmed my build specifications.     In reply, can you please tell me what are the minimum requirements for the build specification so that my test instrument can reply to a simple *IDN? query?   What files are normally required for a successful build?
Other information as to the source of my issues are welcome as well.
Thank you.
Solved!
Go to Solution.

Thanks for you advice.
I think this problem is a lot easier than you might think.   I just started using Labview and the *.VI is super simple. I am away from my development computer right now so I can't post it.
The information I need to know right now are the typical files that are needed to be added in the build.
I found this quote that I found on a webpage to be interesting, (although I am not building an installer):
" Do I need to include NI-488.2 2.7.3 module if I use only basic GPIB Write.vi and GPIB Read.vis in my project?
Yes, if you are making an installer ..."
This is a link to the webpage:
http://forums.ni.com/t5/LabVIEW/Uninstalling-LabVIEW-after-an-application-EXE-build/td-p/1553310
My program involves only simple reads and writes using NI-488.2 calls to a test instrument.   A simple list of files specified with filename extensions to get me started would be appreciated.

Adapter Specific Message Properties not available in SP 15

Hi
In the <b>/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14 blog Michal is saying that <b>Adapter Specific Message Properties </b> option in File adapter will be avalible from XI with SP 14. But i am using SP 15 and i am not getting this option in the file to file adapter. Can u please tell me the why its not available.
Thank & Regards
Ravi Shankar B

Hi,
Try reloading SAP BASIS software component version of SP15 only (check ) into repository.This might enable that option in the ftp/file adapter.
also see the below links
/people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
/people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
/people/michal.krawczyk2/blog/2006/10/09/xi-dynamic-configuration-in-adapter-modules--one-step-further
Regards
Chilla

Build specification missing properties

Similar Messages

Maybe you are looking for