LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Enlarge the Invert Circles

I have become a huge fan of the compound arithmetic node, and there are a growing list of good ideas on this Idea Exchange that involve adding invert capability to more boolean inputs/outputs. Unfortunately, the circles used to show that an input/output is inverted are too small for my taste which makes them easily missed by the untrained eye. Filling the circles black is one possibility, but there is room between the terminals to at least double the size. With a more prominent indicator that a node is inverted, I will easily support adding invert capability anywhere it makes sense.

I know that most of the wildly popular ideas here involve making things smaller, hopefully with some of that reclaimed real estate we can make room for some slightly larger circles.

View All (2)

Swap Colors in Tools Palette

View All (6)

Inspired by

THIS
and

THIS

I would like to suggest always showing the exponent of a numerical value in a contro or indicator regardless of the data format chosen.

We've all been confused by dispalys of near-zero numbers hiding the exponent, haven't we? The exponent is arguably more important than the integer art for certain applications so I vote it should always be displayed.

While we're at it, the same should be true for SI units cush as "m" or "M"

Obviously colours and display details would have to be discussed, but personally I would love to have this feature. Being able to click on the SI unit and change it during run-time would also be amazing!!

Shane.

Allow to name array indexes

Hi,

As in the subject.

Now when you create an array the indexes of the array can be only labeled as the static comment field. There is not any build-in label/handler which could be used. Current situation looks like that:

It would be better for readibility if developers could name the indexes and use it later on.

Picture represents the idea only, whole point is the description shoud be a build in handlers.

Now LV names first four indexes (when you hover over on it) as column, row, page, vol; later on are only dim 5, dim 6 and so on.

I believe if would increase readibility and save coding and debugging time.

View All (4)

Having sold applications that use functionality from the OPC UA Toolkit we run into an issue if we upgrade our LabVIEW version and continue to develop those applications beceause the OPC UA deployment license will then stop working if we upgrade the software we have delivered to them to one developed in a newer version. So, even though the customer has an OPC UA deployment license and we have an updated developer license it is not enough because the deployment licenses have to be updated as well (and it does not help that deployment licenses are not something we can bunde with the upgrade of the software either). From what I understand new deployment licenses will not actually cost anything, they are provided by NI as long as you already had a deplyment license for the previous version - but the logistics of this is a nightmare for us. Instead of just delivering a new installer with an updated version of our software we have to get involved in upgrading the dpeloyment license for all of their systems each time we have gone to a new version of LabVIEW.

View All (4)

The Cursor Legend pop up menu on graphs has an item: Bring Cursor to Center. Very handy when the data changes and the previous cursor position is now 4000 screens to the right.

I suggest that an Invoke node be made available which provides this action. This will allow use of a push button on the front panel to bring the cursor back with very simple code. Obviously NI has already done all the work because the menu item exists.

This can be done with property nodes but it is rather complex to examine the scales, check the current position of the cursor, calculate the center, and set a new position.

I asked about other ways to do this in this thread.

Lynn

View All (1)

Grouping blockdiagram objects

When you right click on a user created object you are only given the following options for the create submenu

In order to access the properties (like in the below image) you need to manually drop a property node and wire it up

It would be really nice if you could create properties through the right click menu. This is possible with other built in classes like the shared variable refnum (see the following image)

And that creates a property node like this

It would be nice if that was possible for user created class objects as well.

View All (7)

LabView BeagleBone support

View All (1)

Uninstaller improvements

Make it easier to find the right product in the uninstaller

If you install a lot of National Instruments developer tools the uninstaller becomes very crowded. You can have 50-100 components, often with similar names and varying name structure. Finding the component you want to uninstall/modify/repair can be difficult.

The fact that things a split into so many separate components is practical, but the components should be organized better:

They could be:

logically grouped
have descriptions
there could be a search/filter function available (that accepts wildcards)

Allow us to specify a new source location

If I want to repair or modify an installation it might turn out that the original source for the installation is gone, or I have a new (identical/compatible) source that I would like to use instead. It would be nice if the uninstaller handled this, instead of insisting on the original.

Equation Node

View All (1)

View All (9)

View All (1)

A big project can take more than 10 minutes to load, especially on an older computer. If subVIs are missing, the Ignore Item and Ignore All buttons become available when the first VI is missing. This can happen anytime during the loading and the process stops until the browse box is canceled and then the Ignore All button is pressed.

It would be better if the Ignore All button was always available where it can be clicked at the beginning to insure the project is loaded in the expected time.

Ignore All.png

Many of the Mathematics and SIgnal Processing VIs retain state, rendering them unusable inside reentrant VIs: http://digital.ni.com/public.nsf/allkb/543589DF37BA48CF8625744A00543FF3

Many of the VIs in this list (all those in my current application, unfortunately) can only work with single-channel data. When manipulating multi-channel data, you can work around that fact by running the channels serially through the VI you need, but that (1) takes much longer for large data sets or several channels, and (2) is not an option when performing live manipulation of streaming data block-by-block.

I ran into this problem while developing code in the Actor Framework, where Do.vi and Actor Core.vi (the two main framework methods) are both Shared Reentrant. Now that AF is a native feature in LV, I expect that more people will run into problems with these VIs.

We need stateless versions of these VIs so we can use multiple copies in on a multichannel data set. You can probably keep backward compatibility by pushing the core logic to a new stateless subVI and keeping the shift register or feedback node on the main VI's diagram.

Cleanup Diagram with Option

Excuse me if it has been already proposed.

In many cases I don't use the Cleanup diagram feature instead I would clean the code manually. In those cases its time taking to check for the bend wires so it would be good to have an option along with the cleanup diagram feature to have only to remove the broken wires, Clean up the bend wires like that. If the VI doesn't have a Breakpoint for example that can be disabled and whatever applicable can be enabled. Here is what I propose

I guess this can be extended with other usefull options also.

View All (3)

I find it annoying to have to wire the User Event Refnum around my entire code loop in order to explicitly destroy it upon completion. It can get pretty ugly with larger loops and creating/destroying multiple user events.

It seems it would be nice to have an Unregister For Events primitive that could return a reference to each of the events that had been registered:

The dropdown might have to include the name of the user event in order to make it clear to the user which event is which, but hopefully the above drawing gets the idea across.

View All (1)

Howdy!

It would be really cool if I could drag and drop a polymorphic VI from its icon on the the block diagram of a VI, just like a standard VI would do it. The other ways include via the LabVIEW Project or from disk, but I would find this new method quicker when I already have the Polymorphic VI open.

Whilst I am at it, some other things that could be supported include better context help - I get this when really I want the description of the Polymorphic VI to show:

Cheers

-JG

View All (11)

LabVIEW Idea Exchange

Enlarge the Invert Circles

Swap Colors in Tools Palette

Always show the exponent and SI units of a numeric regardless of indicator/control width

Allow to name array indexes

OPC UA deployment licenses should be version agnostic

Graph: Bring Cursor to Center via Invoke Node

Grouping blockdiagram objects

Create Object Property Node via Right Click Menu

LabView BeagleBone support

Uninstaller improvements

Make "array subset" and "string subset" resizeable

Equation Node

Allow Destroy User Events and Unregister for Events to Accept Cluster of Refnums Input

Execute project-based cfg with VI Analyzer API

Add the ablity to monitor a compiled executable to "Profile Perfomance and Memory Monitor"

Ignore All should not be greyed out until the first VI is missing

Stateless Mathematics and Signal Processing VIs

Cleanup Diagram with Option

More elegant wiring option for properly destroying User Event Refnums

Allow Drag and Drop of Polymorphic VI to Block Diagram From Icon