LabVIEW Idea Exchange

Community Browser
About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
cancel
Showing results for 
Search instead for 
Did you mean: 

Do you have an idea for LabVIEW NXG?


Use the in-product feedback feature to tell us what we’re doing well and what we can improve. NI R&D monitors feedback submissions and evaluates them for upcoming LabVIEW NXG releases. Tell us what you think!

Post an idea

Quite frequently, I encounter a need to do something repetitive on clusters, which have identical elements. Sometimes, I use "Cluster to array" and then "Array to cluster" vi's, like in the example below:

For loop on cluster.PNG

 

Instead of doing this, I would like to use a kind of "For loop", which would be able to operate directly on clusters with identical elements. The loop would iterate already during the compilation (generating repetitive code for each cluster element).

 

Perhaps, the standard For loop connector might have something like an option "Iterate over cluster elements".

That would be usefull to elimimate all the files needed by a polymorphic VI and would also be useful in malleable VIMs where a portion of the code is needed in multiple cases but will or should never be used outside of the VIM.

It might be worth exploring the feasibility of having an online vi upgrade/downgrade service, where you could submit your vi, and receive back the new vi.

 

I realize this wold be a huge undertaking, however, a reasonable fee could be charged. It could be a second option, in case the customer:

Has tried to do this on their own and failed

Does not have the intermediate versions to perform the required jumps

Isn't worth their time considering the cost of the service

 

In the case of upgrading a vi, this could serve as an added incentive to invest in the latest version of Labview, especially if the customer is several versions behind.

Add a new button to the search results dialog called "Set Aside" so I can have multiple search results open at the same time.  Put it near the bottom just below the search results.  When you click it, it changes the title of the window to "Search Results - Set Aside 1".  If you click "Set Aside" again when #1 is open, it will open "Search Results - Set Aside 2" ... and so on.  This way you can have several different search results open simultaneously.  I love the check mark feature in the search results, but it resets every time the search windows is closed or overwritten by a new search.  Thus I lose my place if I want to make sure to check every instance of something but need to search again while looking at one item.

Just upgraded to 2018 and found that all the icons in the palettes, toolbars, etc. now have a wider border. "Nice"... Now that breaks all my mouse macros that I had build to make up for the forever missing keyboard shortcuts that NI never has time to work on (because is working in "features" like making wider borders on icons).

 

NI had time to mess with toolbar icon borders, but STILL didn't put toolbar icons to save the current VI, Save All VIs, etc.Smiley Frustrated

When developing a Complex LabVIEW Applications, we may need to create N Number of Folders as a part of Configuration information.

This requires the developer to make a check "Check if File or Folder Exists"

Instead of that Create Folder Function can have a Boolean "Optional Input" to create the Folder only if not found in the specified Location and Eliminating the Error when trying to create same folder again.

Hope this will help Smiley Happy

Originally, I asked this query on NI discussion forum Retain Default Data Type of Input Terminal in VI . Thanks @GerdW and @crossrulz to encourage me to share this on IdeaExchange. I need such functionality in one of my project.  


Hello,

When I take Open VI Reference function and create a constant for Option input terminal it shows Numeric constant with HEX radix (Default). So to add same functionality in TEST.vi I put numeric control on front panel with display format set to HEX. But when creating a constant to this input terminal the default data type is DEC and does not show HEX radix likewise in Open VI Reference function. I also tried by making Numeric control strict typedef but didn't work. So how to do this?

Below are the screenshots for same.

MAIN_VI.png

 

SubVI_Test.png

 

 

A right click option for each auto indexed array that allows will not use the length of that array in choosing the number of iterations. If there is no input to the count terminal all auto-indexed terminals can go beyond their length otherwise at least one must remain as a driver for determining the length. If multiple are left with the default (existing) behavior, the shortest length will be used. For any iteration where the array is shorter that the "i" of the loop, the defaults for the data type will be returned (just as if "index array" blocks had been used inside the loop. 

 

Similarly the loop could be set to use the longest array instead of the shortest.

 

Additionally a similar function could be done when any array compare or math functions are done. In the case of compare functions if set to use longest array, the result will be false for any compare to an empty element of the shorter array, and math functions will use the default data type for empty elements.

It would be necessary to insert an alert when opening .vis made with different versions of LabVIEW than the latest used. "This file has been created with LabVIEW 13. Current version is LabVIEW 15. Do you want to open?" Y/N I work with at least 4 different versions of LabVIEW and sometimes happens to open a project (and to work on it for hours....) with another LabVIEW version, without noticing the automatic upgrade. Then time for downgrading again. Thanks

Right-clicking objects on the block diagram in LabVIEW produces a shortcut menu appears. When placed on replace, a menu is shown that is sensitive to the selected item and the option to access all the palettes. Often, when we want to replace an element, we also want to use some other element from the same palette.

 

Palette_02.png

 

When we access the palette, the thumb tack pins are missing, and if we need to access more than one element, it is necessary to navigate in the block diagram through the functions palette. In addition, when we get used to using the "Quick drop", when we need to access items that we don't normally use, it is difficult to locate on the paletta, so I propose, include in the palette from shortcut menu the thumb tack pins.

Currently, we can make inputs to subVIs optional (or indeed recommended) and not wire them - in this case, the default value for the input terminal is used. By default, this is the default value for the type, but it can be easily changed to another value (at least for terminals you can easily set).

 

Since there is no "optional" type, this leads to code potentially like

Example_VI_BD.png

If -1 is always an invalid value here, this might not be so terrible. The issue becomes more pervasive with, for example, empty strings (or string constants) when an empty string or that constant might conceivably be a valid value.

 

Class objects could be an additional problem, especially if a hierarchy is considered, because you might want to wire an uninitialized child object to an Init Object method, and it would fail an equality check vs the terminal type. You might then mistakenly conclude that it was already partially/fully initialized, and carry out the incorrect processing (in this exact case, probably dynamic dispatch followed by an equality check against the specific child, then calls to a static dispatch "Init Object_internal.vi" in the parent might work).

 

We can work around this if needed by using a boolean clustered with the value, and then checking the boolean, but this makes wiring the subVI and creating its inputs more frustrating.

 

I would like to see an optional terminal type that could be checked using a primitive to indicate if it was wired by the caller or not.

Example_VI_BD.png

(Apologies for the ugly icon, and probably dubious naming)

 

 

For the draft of the proposing paper in C++ for the std::​optional type, see http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3672.html

A LabVIEW application installer generated from App Builder creates multiple folders and files in the folders. It is desirable to have a single file installer so that customers see only 1 file to install.

The In Place Array Index/Replace Elements function not only can save memory by avoiding copying arrays, it can also create "neater" and more transparent Block Diagrams.  For example, here are two ways to triple the third element in an Array of 3 elements:

 

Array Index-Replace 1D.png

I needed to do the same thing, but for a 2D array (three channels of A/D data, I wanted to triple the third channel).  The Help for the In Place Array Index/Replace Subset function suggests this is possible, using language like "element or element(s) of an array", noting the similarity between this In Place Structure and the two Array Functions that form the Input and Output nodes, and in earlier versions of LabVIEW (specifically LabVIEW 2012), explicit reference to rows, columns, and pages as replacement items.  Here's what happens:

Array Index-Replace 2D.png

The Index Array left node forces you to specify both row and column, meaning you cannot operate on a single row (or single column), "breaking" the functionality with the separate Index Array/Replace Subset functions.  This also, I believe, will force an Array Copy operation, something I'm (also) trying to avoid.

 

At its most benign, there is a Documentation "Bug" that should warn users that this In Place function is only designed for single array elements (which, in my opinion, severely limits its usefulness).  I would like to suggest that this function be "fixed" to (a) for multi-dimension Arrays, allow, as with Index Array and Replace Subset, flexible choice of one or more Indices to be specified, with the unspecified Indices implying "All of the Elements", i.e. an entire Row, Column, Page, etc, and (b) maintain the "In Place" functionality by having this function generate the necessary code (behind the scenes) to access the specified elements and do whatever operation is required inside the Structure.

 

I appreciate that requirement (b) might be difficult.  For instance, operating on a row in a 2D array should be easy, as the (row) elements should be continguous, making getting and putting them simple.  However, if a column is specified, getting successive elements and putting them back becomes more complex.  To the User, it all "looks simple" -- you get a 1D wire out, operate on it (say, multiply it by 3), and stick it back "in place", but the LabVIEW compiler has to "get" elements from non-continuous locations and put them back where it got them, but that's what Compilers are for!

 

Bob Schor

Hello,

Build array is one of the most VIs used with shift register. 

2017-09-01_16-33-23.png

 

 It is always a bit annoying from UI perspective only to see this curly line which would be much better if connector of appended array is moved below as proposed in the picture above.

 

 

Many programs use shift+mouse wheel to scroll left and right, I would love to see labview enable this for in the block diagram edit window.

 

Simply put, click and hold middle mouse should use the pan tool, as opposed to duplicating left click functionality. This should be trivially easy to implement, as opposed to the universally desired zoom function.

 

User-configurable input mapping would be nice in general. 

I have made a printout VI to show variable names and values. But values will not get proper names until it reach destination. One solution I am using is typecasting (see alternative 2). But typecasting is dangerous. If data in is not of same type as data out, it might be converted to rubbish without warning.

 

Dear LabVIEW team, could you please give us a function to convert data names in wires? 

 

Debugging would also be easier if content of wires had proper names.

 

Idea exchange.png

 I would love to see an optional input node on the edge of a while loop for loop wait. 

When I build, I like to test each step.  That means that I make a bunch of "debugging" indicators.  Some might prefer probes and breakpoints, but I like the "build as you go" and "don't use too many tools".  The challenge here is that about 80% of indicators that I make, I have to delete.

 

I wish there were a version of "diagram disable" that is specified in the block diagram, that worked for the front pane, and left me some tiny asterisk instead of the indicator, that didn't hit program execution times, and that when I configure execution the asterisks can be made to disappear. 

 

This would allow me to revisit my code, to access all of my debugging methods very quickly and intuitively, and to not necessarily change the final layout of the front panel after my debug is done.

Hi all,

                     I would like to suggest any labview program that uses simple codes (which doesn't use rio, dac and all) should be given inbuilt options to be converted as a .apk file for android systems. so the mobile's Bluetooth or wireless networks should be able to utilize the code without the aid of computer system.

                Actually I developed a code for getting data over WiFi and process it through labview, if it can be converted into an application file that can be used in mobile phones means i can further enhance its use for my graduation project. Please let me know if there are possibilities.

 

Regards,

Premkumar.