LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

In many of my programs, it is frequent that I have to issue a command, then wait for a period of time before reading a response. Usually, if there is a timing delay in code, it is usual to end up with something like this:

To do this more neatly, I created a timing subVI with errors wired in and out, and a number wired to it, to instruct the program to stay in that subVI for that period of time. It takes up much less space.

By doing this, I can easily control timing and execution. However, it's be nice to rework the 'milliseconds to wait' diagram so we could wire errors through it, as this would make the block diagrams so much neater...

If i am creating a new control of the same type as the first one, for the second time, the name automatically changes by concatinating "space 1 ". that is fine. but simultaneously i have option of having the same name as the first control by editing. When i am creating variable it is confusing for which control i must relate it to untill unless i find the control and check.

I want to know (some kind of information on availability of the same name for another control) while editing the variable name of the same type is available.

Should it be allowed?

needs some clarification on this..

Focus Color

To improve the quality of interfaces, we need to change the color of the focus rectangle. Otherwise we do not see anything on a dark interface.

Download All

View All (1)

multipage tiff format

View All (1)

array sort

Imagen multipaginas

Making zoom to a Block Diagram

View All (4)

Parallelise the FPGA Compiler

I don't know if this idea belongs in the "LabVIEW" Ideas Exchange necessarily, but this idea is something that would really make a big difference to my LabVIEW development, so I offer it anyway: "Parallelise the FPGA Compiler to take advantage of modern multi-core computing power".

The FPGA compiler takes approximately four hours to compile my large FPGA VIs, which makes for long and tiresome debugging processes. It's clear that the compiler uses only one core of my CPU when compiling. If the compiler could be written to take advantage of the many cores of today's multi-core computers, it could potentially reduce my compilation times to an eighth! (Where I work we have an eight-core number crunching server ideal for just this task, and I'm sure we'll get even greater core counts in the near future - thinking GPU here).

I know the compiler is probably the intellectual property and responsibility of Xilinx Corp, and not National Instruments, but I expect NI can give them a big push if we all asked nicely for it!

Thoric

View All (3)

View All (4)

Indexing array from the end

For whatever reason, the end of an array is just as natural a location as its beginning. Go figure...

Hence it would be nice to have an index array function that could be started from the end (for instance with an "invert" indexing option accessible with a right-click).

At this point, one has to either flip over the array (time and memory costly) or clutter the diagram with a "Array Size" + "Minus One" (and more if one wants to access previous elements).

My 2 cts,

View All (1)

All the time I make type def enum's in order to use with a state machine. Most of the time I create the enum from the block diagram instead of the fp. Maybe I should change my habit but I wish there was a "create type def" option on the bd right click menu so I didnt have to change to control, switch to fp, customize, then change back to constant.

View All (5)

In their current form, Auto-Indexing tunnels only operate on a single dimension of an array. For example. If you input a 2D array, through an auto indexing tunnel into a for loop, and display the resulting 1D array in an indicator inside the for loop as below, you will always get the last row.

I'd like to see a feature where you can right-click on the tunnel or something, and set it to auto-index by column, instead of by row, and get the last column instead.

It could be as simple as an option in the context menu for the auto-indexing tunnel to say "Index by rows" or "Index by columns" It gets more complex with 3D 4D and moreD arrays, but you could do something like a submenu flyout that says "Index By Dimension" > "1", "2", "3" etc

I often use strict type definitions to change data between SubVIs. The wires of the type definitions are always pink and this is sometimes a little color chaos.

Strings are pink, clusters are pink, ...

It would be nice to have the feature like in the LabVIEW classes. There you can definie the look of the private variables wire (form and color).

Hello!

What I really would like to se implemented as a future feature is a 'Search 1D Array.vi' with the option to do a case insensitive search.

Usually I just plug a "to upper case" vi on both array and search string inputs. It would be nice to be able to select it right on the vi instead.

The functionality should work as with the case insensitive match in the case structure.

Cheers!

//Beckman

LabVIEW Idea Exchange

Setting CRIO time through MAX

Better timing structures

Multiple Variables/Controls of the same name

Focus Color

LabVIEW version identification in windows task bar

multipage tiff format

array sort

Imagen multipaginas

Making zoom to a Block Diagram

Parallelise the FPGA Compiler

Link to Build Path from Project Explorer Build Status box

Indexing array from the end

Block Diagram Should Open if Holding the Key while Clicking a VI from in the Project Explorer Window

Allow zooming on the block diagram.

create enum type def from bd constant

Add "Auto Dispose Reference" and "Wait Until Done" to VI Properties

Auto-indexing Tunnels and Multi-Dimensional Arrays

Individual wire color for type definitions

auto populate icon with text from vi name

Array string search case insensitive