Home Community Idea Exchange LabVIEW Ideas : Hot Ideas

LabVIEW Idea Exchange

Community Browser
Top Authors
View All
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Post an idea
8 Kudos
v_strane_chudes

Remake For Loop

Status: Declined Submitted by Member on 06-07-2010 01:22 PM 7 Comment
6e3fb8943920.png
Message Edited by Laura F. on 06-07-2010 02:03 PM
View All (3)
5 Kudos
CyGa

Cloud LV version Migration Service

Status: New Submitted by Active Participant Active Participant on 06-06-2014 03:51 AM 10 Comment

Hi !

 

Often dealing with old code it's always a pain to install old versions of LabVIEW to get the code compiled the newest LV version.

For example, porting code made in LV 5.0 implies converting first to LV 7, then convert to LV 2009, and finally convert to LV 2013.

You then have to install these version, licences, ...

 

It would be nice to have a service on NI.com website from which we could send a zip archive containing the project to convert.

Then selecting the target LV version, a could service could unzip and compile the code across all versions of LV to have the code matching the requested version.

View All (4)
5 Kudos
DanyAllard

Installer Build Specification should not depend on the exact result of an EXE build specification

Status: Declined Submitted by Active Participant Active Participant on 03-06-2013 01:15 PM 1 Comment

When you create an Installer you need to select what is the other build spec that will be used to be installed.

 

Some time in the resulting files of an EXE build spec we got files that we don't need to be included in the installer.

 

So I propose to be able to select only the file that need to be installed, not the entire EXE build spec result.

 

Currently the EXE build spec result files are grayed out and we can only select the entire EXE build spec result files to be included in the installer.

6 Kudos
SI-JE

Report Generation Toolkit - Power Point Addition

Status: Declined Submitted by Member on 06-28-2011 01:52 PM 1 Comment

Add power point added to the programs supported by the report generation tool kit. 

6 Kudos
David_L

Option to Easily re-link drivers to newly installed LabVIEW installation

Status: Declined Submitted by Active Participant on 02-14-2011 12:32 PM 4 Comment

One of the biggest issues that I see new customers run into is the proper install order of LabVIEW and it's drivers.  It's not directly obvious to most that you HAVE to install LabVIEW before the drivers.  When they install another version of LabVIEW and do not update drivers, or they accidentally install drivers first nothing works correctly (DAQmx VIs don't appear in the palettes, New>Targets and Devices doesn't appear in the project menus, etc).  The solution to this is to completely uninstall the drivers that were installed, and then reinstall them.  This is annoying and takes a long time. 

 

My proposed solution would involve an easy "repair" option or tool that will simply reconnect the components and VIs etc to avoid the massive headache that most new users seem to get themselves in.

 

6 Kudos
Dale_Chayes

(Reasonably) equal treatment for OS X (please)

Status: Declined Submitted by Member on 11-24-2010 05:44 PM 1 Comment

While NI provides (thank you) reasonable support for OS X these days, the support for installs and updates "on line" are very far behind those for Windows.

 

For instance, there does not appear to be any option to download Labview 2010 for Mac but I can for Windows.

 

 

1 Kudos
usrfrnly

Add Instructions to the Block Diagram for Online CLD Exam

Status: Declined Submitted by Member on 03-12-2021 11:04 AM 2 Comment

Trying to toggle back and forth between the instructions and the code for the online CLD exam was both distracting and difficult since most hot keys didn't work. Placing the instructions or goals in the block diagram would allow easier reference for those taking the exam. 

View All (2)
2 Kudos
Jason_Reece

NXG home edition

Status: Completed Submitted by Member on 07-03-2018 04:38 AM 3 Comment

How about an NXG home edition, so folks can try it without any heavy time or cash commitment. It would help acceptance and uptake in the LabView community.

5 Kudos
Charles_CLA

Cloud Preferences

Status: Duplicate Submitted by Active Participant on 05-29-2012 03:19 PM 3 Comment

Would like to see LabVIEW implement "Cloud Preferences". Basically store the LabVIEW.ini file in my NI.com account and be able to log into LabVIEW and have it download the ini and use it. Even allowing it to be *easily* stored on the network would be an improvement.

5 Kudos
alpha1

Bulk Add Computers / Users To VLM

Status: Declined Submitted by Active Participant on 09-15-2011 06:41 AM 1 Comment

I would like to suggest implementing the capability to add a bulk of users or computers in Volume License Manager. I suggest to allow a text (maybe csv or similar) file's content to be imported in, which would greatly speed up the setup of a new VLM server. Addionally, for the adding computers, it would be good to discover all PCs on the network and allow the administrator to select the computers to add using a checkbox.

6 Kudos
aeastet

Automatically Update all my NI Software.

Status: Declined Submitted by Trusted Enthusiast on 10-19-2009 03:08 PM 5 Comment
It would be nice if LabVIEW automatically check for updates and notifies the user of all of the upgrades available for everything that they have registered. It would be nice if patches were just down loaded and installed much like the Windows Updater function. It would keep LabVIEW, all of the tool kits, Measurement and Automation Explorer, and every licensed software up to date. It could also push down labview as long as you are on the subscription and current.
4 Kudos
Jokelnice

Improvements to the "NI Update Service" (shut down the system, when you finish the download.)

Status: Declined Submitted by Active Participant on 05-28-2013 11:41 PM 3 Comment

Some software updates ("NI Update Service") are quite large, it would be quite nice an option that would allow the system shutdown when downloads finish.

 

NI update sofware.png

View All (2)
3 Kudos
sfrinak1

It should be easier to change the default copyright company in Application Builder

Status: Declined Submitted by Member on 06-19-2015 03:10 PM 1 Comment

It should be easier to change the default copyright company in Application Builder.  

 

I got the following from NI support to change the name of the company that is copyrighting the software.

 

1. To show the desired hidden folder, you must select Tools>> Folder Options >> View >> Under 'Files and Folders'>> 'Hidden files and folders' >> check the 'Show hidden files, folders, or drives' >> Select 'ok'

2. Navigate to C:\ProgramData

3. Open ProgramData >> National Instruments >> LVProductDLLInfo >> 12.0.0 >>LabVIEW_ADE_120000.ini   ***Please note that the folder 12.0.0 may instead be 14.1.0 or another numeric value based on which version of LabVIEW you are using***

4. Change the RegisteredOrganization and RegisteredOwner to the appropriate organization and owner respectively.
 

The fix NI support sent me was to change the name of the current software owner.

 

The company that owns the software is usually writing the program for another company that is paying to have it developed. If the software owner is not careful they may assign the copyright to their company or to the company that they developed software for last.   I am sure that the company that had software developed will be surprised if their name is not listed as the legal copyright owner.

 

Stan

5 Kudos
pachook

Allowing proxy settings for LV

Status: Declined Submitted by Member on 08-27-2010 03:25 AM 4 Comment

At my current work place we use proxy servers as an internet connection. With LabVIEW it makes it difficult not only while the NI software is being installed (to check for updates, connect with server for veryfication etc) but also during typical work it makes troubles with finding examples and drivers from a development enviroment.

 

I would suggest adding some advenced internet connection options for proxy settings etc.

 

Another little thing with a company computers is that, even when installing NI software on a D drive it still installs some example software on C:. It makes problem when your IT limited your C drive for absolute minimum, because with huge amount of NI software the amound of "additional" data is getting bigger and bigger.

 

Regards,

 

PacHOOk

5 Kudos
taddwoods

Add header to LabVIEW file to contain the version of LabVIEW.

Status: Declined Submitted by Member on 08-25-2010 11:12 AM 8 Comment

LabVIEW opens the file in the version of LabVIEW that was most recently opened instead of the version the file was saved in.  Add a header to the file to allow LabVIEW to open the file in the correct version.  This will save a lot of time and lower frustration of accidently saving a file in the newer version.

4 Kudos
Thoric

Upgrade LV Project RT targets

Status: Duplicate Submitted by Trusted Enthusiast Trusted Enthusiast on 07-30-2012 04:14 AM 3 Comment

I've had a look around and can't see anything in here like this already (which surprises me so I'm suspicious that it's just the search algorithm failing) but I'd like to see options in the LabVIEW Project tree for changing target hardware.

 

For example, I have a development underway using a cRIO-9114 chassis with a 9024 controller, and a 9144 EtherCAT expansion chassis. The primary chassis is about to be upgraded to a 9116, as we need a bigger FPGA, and although the hardware upgrade process is straightforward, upgrading the chassis in the LabVIEW Project is not a possibility. Instread, I need to create a whole new target, and copy and paste every VI, node, FIFO, DMA etc. across. There's quite the possibility that I'll miss something, or the new target won't have all the same settings (Scan Mode period and priority settings for example), leaving me with that niggling feeling that something under the hood will be wrong. It would be much neater if this was an automated migration.

 

Furthermore, as the hardware is not here yet, I need to create the new target and all it's modules manually, which will take me quite some time. An automated migration would save me that trouble.

4 Kudos
Jacc

Specify installer "..\volume" files - such as autorun.inf and autorun.ico

Status: Declined Submitted by Member on 05-29-2012 09:41 PM 1 Comment

I would like to be able to specify an autrorun.inf, an autorun.ico file and a copyright file in the Build properties for the LabView (or CVI) installer properties to be copied to the ..\Volume directory for the built installer. I can then simply build a DVD from the installer's ..\Volume directory and the DVD will autorun on insertion (if autorun is enabled). Of course, I can manually add these files to the DVD build, which I do, but if it is simple fix to the installer, well, Ithe next person who takes over my projects is less likely to make a mistake.

4 Kudos
jimg12

Help folks that use the Volume License Manager

Status: Declined Submitted by Member on 04-27-2012 11:03 AM 2 Comment

We are a site that use multiple NI software products(LabView, Realtime, Vision, sound & Vibration, etc.) and multiple copies of each so we use the Volume License Manager.

 

My idea is to simplify installation, maintenance, and updates for folks that have a large usage base by:

 

  1. Stop needing to keep a record of all my S/N's of products and type them in when I need to do an install by:
    1. Allowing the install CD to query the License Manager for licensed products on the target and then automatically select them for installation without needing S/N's since the LM has that info.
  2. Make the NI Update Utility configurable to allow it to update all software available(service packs, and new software releases like LabView 2012) not just bug fixes.

 

The current system is pretty abusive to admins who need to maintain 50+ systems...how about a little help out here 😛

5 Kudos
Damir

Version information in EXE

Status: Declined Submitted by Member on 09-19-2009 02:25 PM 5 Comment
Builder should automatically attach version of LV to EXE so it can be seen in Windows Explorer. So you can always ask unexperienced end user about version. I drove 1000 km with wrong version of LV on my laptop... Upgrade to new version is not always straitforward... And I always forget to set version information manualy...
View All (2)
4 Kudos
Mathieu_T

LabVIEW 64bit french version

Status: Declined Submitted by on 09-21-2011 04:54 AM 10 Comment

A lot of customers are asking why a french version of LabVIEW 2011 64bit is not available. Is this idea take part of the future roadmap ?