LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

All the other Build Specification has already this function available. Why not the Installer and the ZIP File.

 

Dany

When I run the installer for my application, I want to display to the user the version of the exe that will be installed.  Since this exe already exists, I should be able to embed a tag in the installer dialog text as a placeholder for this version.  Something like:

 

This installer will install version %my_exe_version% on your machine.

 

When the installer is built, the tags are replaced with the actual versions.

This should also work for all components being installed (DLLs, web services, etc)

 

As a bonus, it would be nice to have access to user defined tags in the build spec that can be embedded into installer dialogs.  Perhaps allowing a prerun VI to populate these so we can invent new ways of adding infomation in the future.  (like accessing user information from the OS and using that to customize the dialogs)

When I build a web service in LabVIEW, there is no version number updated for each build.  If I then install that web service on my target, I have no way of determining what build has been installed.

I have solved this by creating some scripting VIs that update a VI control's default value when the build is run.  This VI is available via my web service so I can ask it what version it is.

 

I think everything that can be built from the project should have a version attached to it and that version should be accessble and reportable.  Also, it should be possible to auto-increment it.

Currently, if you want to install LabVIEW 64bit, you need to download it from ni.com.

 

My idea is to put it on the LabVIEW Platform DVDs. 

 

It should be there.  I am paying to get my software on a DVD.  Please include it on my DVD.

 

The only reason I can think of for NOT putting it on the DVD, is that NI is worried that inexperienced users will install the 64 bit version (afterall, doesn't 64 sound bigger and better than 32! Smiley Happy), and NI will get tons of technical support phone-calls from the resulting confusion.

The latest release of the Vision toolkit (Vision 2012 SP1) provides some much needed improvements to the AVI functions.

 

But at the same time, it introduced a new issue:

 

"The Quality input in the IMAQ AVI2 Create VI is only implemented for Windows
codecs. The Quality input is not implemented for codecs installed with the
Vision Development Module."

 

This is very unfortunate, because it worked fine in the previous release (see here)!  This means you may want to reconsider upgrading to SP1!

 

My idea:  Fix this!  Re-allow the use of the quality parameter in the AVI functions so we can better compress our video!

The list of available LabVIEW modules and device drivers is very long. Their names tend to be long too, which is compounded by the many levels of nesting. Modern screens are large.

 

Given all that, why are we selecting software components by scrolling around a tiny window which can't be expanded?

 

tinyinstaller.png

(Note: most of the trees above aren't exen opened yet!)

 

 

Proposal: Make the window bigger (vertically and horizontally), or resizeable, or both.

 

Thanks for listening!

When you run the LabVIEW Platform DVD, the default setting is that LabVIEW gets installed and nothing else. You can then go pick and choose what modules and toolkits to install. I like this default because I usually only want to install LabVIEW and a few other modules and toolkits. It is faster for me to select the few modules that I want to install rather than unchecking all of the modules I don't want to install.

 

When you run the Device Drivers DVD, it tries to guess what drivers you want installed based on the software you already have installed. However, it usually wants to install more drivers than I want it to install. It is a hassle to go through the driver list and unclick the drivers I don't want to install because most of them have dependencies that you have to unclick first. 

 

Idea: Their should be a button on the Device Drivers installation screen to unselect all of the drivers (see image below). I don't think the Device Drivers DVD default should be the same as the Platform DVD; a lot of new users won't know what drivers they need and installing all of the recommended drivers is a safe bet. However, many users do know what drivers they want and it saves time and hard drive space to only install the necessary drivers. Adding an "uncheck all" button would make this process faster and less frustrating.

 

device drivers.png

Add an "Uncheck All" button!

All service packs should be useable for the version you own, regardless of your SSP status. Currently, service packs are only good if you have a SSP active or had enough forethought to buy it in the middle of the year between versions.

Dear All,

Currently to use LabVIEW in a functional way you have to spend about $5000 to get the bells and whistles.

Large corporations don't have a problem, but there is a lot of normal people that would like to have LabVIEW but are not students and can't justify spending that amount on software that they may use only occasionally, but would like to have.

 

Adobe has moved away from the (legacy) model where you buy and own your copy of the software, to a subscription based model ($20 to $50 a month) where you get ALL the LATEST version of EVERY application they make, as long as you pay your monthly bill. I was reluctant to use that model but I finally subcribed, and let me tell you it saves me a ton of cash, and I get whatever I need at the latest version. 

 

National Instruments high-level management and marketing department should seriously consider moving forward and making an AFFORDABLE monthly subscription scheme, like Adobe succesfully did. This would benefit NI by getting some money out of folks like me, and would ensure that the whole world would be using the latest versions of it's products.

 

Successful companies are the ones that make available the best products and services to the BROADEST range of people (e.g. Google, Microsoft, Adobe). Restricting access to technology based on income will hurt National Instruments in the long run. 

 

With best regards,

Rollin McCarty

When you create an installer package with a default destination path that is not available on the machine where you want to install the package later, the installer stops with an error message. You have not the chance to install the package somewhere else.

 

So my idea is to show a warning only and let the user define a new location afterwards.

 

here I create a installer with the default destination path D:\...

installer property.jpg

 

When I run this installer on a machine that has no D:\ drive, I have no possibility to install the package. I also cannot select annother location.

error.jpg

 

 

Note: of course a bigfix for this problem is a default destination path that is available on every machine (e.g. c:\), but in some usecases you want to force the user to install the application in a defined folder like D:\tools\

Currently the only want to back up an entire lvproj and all the vis is with Save to Previous Version. Otherwise you need to create a source distribution or zip file for each system (my computer, crio, FPGA). Could we add a project build spec that would allow you preserve the project structure like in Save to Previous Version but allow you to customize the output folders to help users reorganize their projects when moving from computer to computer. 

 

It could feel very similar to a source distrbution but for the entire project. So any dependencies are also pulled for their respective 

 

Ideally everyone would have they project nicely organized in a folder with perfect subfolders but when you're given a project written by someone else, sometimes files are scattered everywhere and we end up missing dependencies when moving. 

 

project build spec.jpgBuild Spec.jpg

I use the Labview Development Environment usually on multiple PCs (my working place, my laptop, the customers development PC, etc.).

 

It takes a lot of time to install the whole environment and I think nothing can be done about. But it always angers me that there is no way to transfer the settings so that the environment behave exactly the same.

 

It should be possible to transfer the following settings easily:

- user.lib

- all changes done to the labview pallets

- settings in the configuration

- user added templates (VIs and projects)

and so on

 

Mayby that should work like the Easy Transfer Function for Windows from Microsoft.

This would speed up the installation and on every system I could experience the same behaviour of the development environment

When creating an Installer for a Labview project, make it possible to execute not only exe files after installation. It shoult be also possible to execute *.reg or *.bat or other files.

 

This should work for the two options on the Advanced page of the Installer property dialog:

Installer Registry - Run executable.png

When creating an installer for a Labview project it is possible to add Registry keys. But only with type REG_SZ and REG_DWORD.

 

Make it possible to add keys with other types. Often it is necessary to use the expandable String Type REG_EXPAND_SZ when adding path entries using for example %ProgramFiles% variable.

 

Add Registry Key page

The I2C Digital Waveform Reference Library is a good choice to test the I2C Interface with timings that

are outside the specification. This is important for the developers to invesigate what happens when a

new designed chip get a not specified I2C signal.

Citation from the readme file:

 

Supported Targets

This component is compatible with the following LabVIEW 8.6 (or later) targets

  • LabVIEW for Windows Vista/XP/2000

 

The API library and installed examples may be compatible with other LabVIEW targets, but they have not been tested.

---

 

Unfortunately the Library needs the LabView 8.6 Run-Time Library installed and it is not certain that it work with Windows 7 and

LabVIEW 2012. (I tested it and it works with this combination Smiley Happy ) It would be nice if the Library can be updated and tested for

Windows 7 and LabVIEW 2012, to prevent that developers are uncertain if this "old" Library still works.

 

With Application Builder installers there is no way to flag a file as a 'shared' component in the build specification.  This feature is used in MSI installation when files are shared or common among multiple product installers; for example, the files located in \National Instruments\Shared are common dependencies for NI products or in LabVIEW-built EXEs this could be a shared dependency between two applications, like a DLL.  Currently, if two product installers built in Application Builder install the same file, when either of these products is later removed the shared dependency goes with it and the second product is broken!

 

Some good news is you can use MSI editors like InstallShield to edit the MSI after creating it with Application Builder in order to enable a tag/setting for your shared files:


InstallShield.png

 

There are also open source MSI editors available, like Inst Edit, with similar options for tagging files as shared components.

 

What can be done in Application Builder?

Could an option be added to 'Source File Settings' to tag files as 'Shared' so a third-party MSI editor is no longer necessary?

AppBuilder.png

Hi all,
For a lot of reasons, I have to work with several LabVIEW versions.

My biggest fear is to save something in a later version : projects are quite big, and a save for previous version is hard when using terce parts (such as OpenG, JKI, etc.)

My whish would be to have a warning message when I save a vi in a new version, such as :

"You are saving a 8.2 file in 11.0 : do you want to continue ?"

 

 

Have a nice day !

Activating an NI Software licence on a computer without internet access works fine but take too long and is user mistake prone because we need to type long strings of characters.

 

Now we have to :

 - go on PC/tablet/smartphone that has internet access

 - go to ni.com/activate,

 - select the product type,

 

 - select the product version (be carefull to select the version we installed, not the version we recieved*),

 - type the serial number,

 - type the computer ID,

 - then we obtain the activation code that we have to type on the computer.

 

Bold steps are human-error prone.

 

If you've done that once from a smartphone, you know how painfull and error prone this process is.

This process should be shorter and much less error prone, something like :

 - the PC without internet show a QR-code that contains product type, version needed and computer ID,

 - launch the "NI Soft Activation" app on your smartphone

 - scan the QR-code

 - type the activation code given by the app onto the computer.

 

Only one human-error prone step in that process.

 

 

 

* : when you purchase a runtime licence from NI you automatically recieve a serial number that can activate the most recent version of the product, but you can use it to activate older versions of the product as well. Say youwant to activate Vision Development Module RTE 2010 but you recieved a serial number valid for up to version 2012, when you go to the ni.com/activate you have to be carefull to select the correct product version (2010 in this case), one more possible human mistake.

The Vision Utilities are currently installed with either the Vision Acquisition Software, Vision Development Module, or NI-IMAQ.  Since NI-IMAQ is a free download that anyone can install and deploy without any additional licensing it makes sense to include it in the LabVIEW installer.

 

The Vision Utilities provide superior image management , are owned by NI-Vision (meaning they are actively developed), and best of all are free.  Including the Vision Utilities in the LabVIEW installation will expand their exposure and use.  Below you'll see the first three results returned when one seraches for IMAQ on ni.com and sorts by examples.  In addition to the examples shown below you can find a list of all the VIs currently included for free in NI-IMAQ here.

 

Region of Interest Spotlighting With IMAQ Functions                

Spotlight front panel.png 

 

Semitransparent IMAQ Overlay

Front Panel.png

 

IMAQ Skew Image

skewimage.png

Downloads and updates that self-extract to an installation image are often placed into different folders under "\National Instruments Downloads" even for very similar products or even updates to the same product.

 

For example, LabVIEW 2012 extracts to "\LabVIEW English\2012" but the f1 update extracts to "LabVIEW Development Environment\2012 (32-bit) f1"

The 2012 Run-Time Engine extracts to "\LabVIEW Run-Time Engine\2012 (32-bit) f1" while the 2011 Run-Time Engine extracts to different folders depending on which update it is.

The 2011 f2 extracts to "\LabVIEW\Run-Time Engine\2011 f2 32-bit\Standard" but f3 extracts to "\LabVIEW\2011f3\Run-Time Engine\Standard"

 

This can make it difficult when looking at one of the top level folders to know what it contains.  Is it a Run-Time Engine, an update ,or a main program file ?  If the main program and all its updates were under one folder, then by copying just that one folder one would know that all files and updates were included in the copy.

 

Steve