LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

In Front panel and Block Diagram when we place a control (Graph) over another control (Numeric) everything is fine and we don't have any clue that an object is overlapped. The only way to find the control (Numeric) is by going to the BD and navigating to the FP by using the Find Control menu. So it would be nice if we get a shadow for the object which is overlapping any other object. This is also applicable to the BD objects where there are chances where the VIs gets duplicate when we try to create a copy by using Ctrl+Drag.

Using the "Find Control Option" in BD

This would be simple if we come to know that an object is overlapped by a shadow

During the run time this shadow can be removed like how we use controls over the Tab container.

Please ignore if it is already suggested.

View All (1)

For Loop (conditional terminal)

One of the major obstacles to LabVIEW adoption is the difficult learning curve (perhaps it’s easier than learning a text-based programming language, but still). A simple reevaluation of whether certain options are in the most logical place might help make it easier for first-time users.

The two that caught me up the most when I was first using LabVIEW:

I expected to find the Tools Palette under Tools not under View. This tripped me up a number of times, saying, “Where on earth is the Tools Palette!?” Over the last several years I have observed a number of new users have the same difficulty. If the first place the average user looks for something is not where it is, then it is either in the wrong place or perhaps something is poorly named. The things under Tools may be better thought of as “Utilities” or something so I wouldn't keep looking for the Tools Palette there.
I expected to be able to click View>>Block Diagram to view the block diagram, not Window>>Show Block Diagram. Again, you watch someone who is new to LabVIEW poking around trying to navigate and I guarantee they’ll click View before thinking to look for it under Window.

The more I use LabVIEW, the more I find things that just seem to be in weird places. I know this may seem silly, but I think it would be worthwhile to do some new usability studies on things like this.

Auto-label items in a cluster

When adding a control as a cluster constant it's important to see what's the controls name in order to use the constant correcty.

As you can see on the right side of the image there's how a control will be added when you drag&drop it into the block diagram.

To show every label it's quite a lot of work to click on each single item (it's hard enough to hit the control correctly!) open the contect menu and select "Description" to show up.

It'd be a great relief, if you can simply select "Show all labels" to perform the same operation with 3 but 20 clicks.

Also there should be a function to automatically select if the text should be upper, lower, left or right to the constant.

View All (4)

Bulk binding Variables to OPC Client

The current way to bind many shared variables to an OPC client, is through browsing a tree and selecting.

This is very time consuming when you have hundrends or thousands of tags to bind. Specialy if the all the tags are not in the same path.

A better way, is to bind the variables, by simple text.

Example: We will insert the following text

A1M01Z1:value

A2M01Z1:value

A3M01Z1:value

and LabVIEW will automatically create 3 variables, bounding to those addresses (with the same name, prefered). Many OPC Servers supports this type of address.

Note that the true path of A1M01Z1 could be something very big, like:

My Computer\OPC ABB.lvlib\_OPC1\[Control Structure]\Root\NETWORK 1\Nodecm3\Extended Process Objects\MB300 AI\A1M01Z1\VALUE

This way you can add thousands of items in minutes. It is quite easy for the R&D team to implement and will help many professional engineers.

Most probably, this idea will not accept many kudos, but i think R&D must consider to implement this.

(this was discussed with NI technical suport, Reference#3279019)

Thank you all, for reading

View All (2)

A value change for the autoscale setting of a graph / chart scale is currently not registered. It can only be detected by polling for the scalefit value. The range of detectable events on charts and graphs is currently incomplete. The scale range change event and the autoscale range change event trigger at the same time in unpredictable order. This makes it hard to detect whether a user manually adjusted scale minimum and maximum or adjusted the autoscale settings value in the scale attribute. Different user actions all trigger a scale range change event without any way to discriminate the cause of this event.

I wish there was a simple check box or rotation option for the Y-Axis name label on charts/graphs rather than having to do it programmatically.

Here is what I mean:

I emailed tech support and they confirmed there is no direct way but sent me a workaround which I've attached for reference.

Regards

Mitch

Type Casting Strictly Typed VIs

Allow type casting between Strictly Typed VI References

Why:

The asynchronous methods require strictly typed VIs. Strictly typed VIs depend on the connector pane and terminal wiring type (Required, Recommended, Optional). Depending on your development environment and configuration options (Front Panel > Connector pane terminals default to required), newly connected terminals may be Required -or- Recommended.

Opening a VI reference or calling an async method with the wrong terminal wiring type will result in Error 1057: Type mismatch.

To work around the connector pane variance, we need to type cast check every connector pane terminal variance in order to call the proper async method without getting the Type Mismatch error.

The amount of unnecessary complexity to call and collect a thread is infuriating. There is already enough complexity when it comes to spawning a new threads; between the conditional options (Non-Reentrant, Reentrant, Async Forget, Async Collect), VI type specifier (Generic, Strict), Connector Pane Type (Pattern, Rotation), Terminal Wiring Types (Required, Recommended, Optional), etc. Threading in LabVIEW needs improvement.

Idea:

To better support Asynchronous calls, we need the ability type cast the required strictly typed VIs to:

1. Add an option to Start Asynchronous Call and Wait on Asynchronous Call methods to ignore the VI terminal wiring type flags:

Required (0x21000), Recommended (0x20800), Optional (0x20000)

2. Support type casting VIs To More Generic Type and To More Specific Type to avoid the error 1057 Type Mismatch all together

Regards,

A LabVIEW Enthusiast

View All (3)

File Path Control browse options

View All (4)

error source includes case name

free label format

How often do you find the need to orginize data into a table format while documenting your vi? I for one, could & would use it all the time! Creating a resizable table free label we all use in word & excel seems like a simple task and would aid in organizing and documenting data into a more readable format. A ctrl+double-click or shift+double-click could serve as an easy access method, tab through the contents, and resize rows and colulmns vis a cursor change while hovering at the specific borders. Free Label, New type, table format, organize data, rows, columns.

Two more suggestions

There has also been a need for rising edge and falling edge triggers for boolean values instead of having to manually code this in every time. I know this would take extra memory space but could be turned on or off maybe in the control settings dialog.

I also have to manually code in time delay functions because everything I do is in loops with parallel code. The timers can't execute properly this way and would be nice to be able to use the built-in timing functions instead of hand-coding.

How to Spread "Tribal Knowledge"

In response to another post, Darren suggested someone start a new topic about how to more effectively spread information about new or esoteric features (sometimes referred to as "tribal knowledge").

One idea is to have a database of these gems and display one at random during the splash screen. So, while we are waiting for LabVIEW to start, we can learn a potentially useful "trick", if we care to.

Example: "Control-click on some primitives will reverse the order of the inputs. By also holding Shift, any inversions will follow the connections."

(Note: the second have of this example is not actually implemented yet.)

View All (4)

I sometimes need to add (paste) text documentation to the block diagram. This often results in a single line of text that can stretch, as a single line, for what seems like miles off to the right of the text-block insertion point. I then need to make multiple drag-edge/shift-block/repeat adjustments to beat the text block down to something that will fit on the screen. It would be nice to instead be able to select the text block and either specify a width or else say to make it the same width as something else on the block diagram.

Scroll bars in text blocks would be nice too, as long as I am wishing.

LabVIEW Idea Exchange

Display Shadow for Objects which overlaps other objects

Search Index/Replace Element in In Place Element Structure

Step into subVI Highlight Execution option

For Loop (conditional terminal)

Shared memory between RT and FPGA

Consider reevaluating the organization of menu options.

Auto-label items in a cluster

Always display the full value of a control or indicator in the help window

Bulk binding Variables to OPC Client

Interface based messaging for Actors.

Events for all Graph / Chart property value changes

Rotate Y-Axis Name on Charts/Graphs

Type Casting Strictly Typed VIs

Allow type casting between Strictly Typed VI References

Why:

Idea:

File Path Control browse options

Confirmation dialogue when changing type definition to control

error source includes case name

free label format

Rising Edge / Falling Edge and timer delays

How to Spread "Tribal Knowledge"

Add "Resize Objects" option to to block diagram toolbar