LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

It would be nice to have an easier way to initialize simple vectors such as v1= [1, 2, 3, 4, 5], v2= [-6, -4, -2, 0, 2, 4, 6], or v3= [0, 0.1, 0.2, ..., 0.9, 1.0]. In MATLAB, this is easily accomplished as v1= 1:5, v2= -6:2:6, and v3= 0:0.1:1. No ugly for loops are necessary! Likewise, MATLAB has many matrix/array construction funcitons such as repmat() and toeplitz(). (NOTE: I am using an older version of LabVIEW: 2009 SP1.)

Particularly when I have many VI's (and often also their block diagram) open, it gets very tricky to find the correct one in the list (as Windows lists them as e.g. "15 LabVIEW....") . It would be useful to split this up, eg. in an item "9 LabVIEW front panels" and "6 LabVIEW Block diagrams"

When I am debuging, sometimes, i have over 20 VIs opened.  If I step into a VI, and accidentally click on another VI, I will have to find the VI that I stepped into before I can continue the execution.  We should be able to click on the pause button on any VI to continue execution of the program.

Create a format painter (format übertragen) button like MS Excel,Word,... to format buttons,... quickly

 

I am adding comments from outside the sequence diagram onto 2 frames and the arrow doesn't go past the frame boundary. Arrow from decorations palette needs to span across frames. Thanks. 

 

Pavan 

 

A double click on the boarder of a constant (optionally even on a control or indicator) of types string should open the in LV 2012 added editor dialog.

 

The same could be done for the path control to open the Browse... dialog.

 

Double click to open dialog.png

My idea is to ass a right click menu item to unbundle elements from a cluster, waveform or even extract an element from an array.

It will make it easier that adding an unbundle or unbundle by Name and then choose a certain element to unbundle.

 

With just a simple right click you can choose any element from the cluster :). I attached a picture of how it may look like.

LabView could use plugins (like Adobe!) for a lot of the features suggested by those on this forum, instead of implementation only with the latest release. For a lot of university computers that are running on old DAQ boards or simply cycle through their programmers quickly, upgrading to newer versions of LabView isn't an option, both from a price perspective and from a "reprogramming everything" logistics perspective. (I'm in this situation, with a lab using 6.1)

 

Plugins that I have in mind are:

 

  • Block Diagram Cleanup Utility plugin for versions of LabView before version 8.6. Whatever algorithm the 8.6+ versions use would still work for wires and other objects strewn across the block diagram, so adding this shouldn't be too difficult.

 

  • Zoom functionality for LabView, period. LabView is a graphical programming language, and anything graphical should have some sort of zoom utility. Whether it be to see a large block diagram in its entirety or to zoom in for people with poor eyesight, or simply a graphical readjustment to suit a different sized monitor, zooming is critical to any graphical process. Certainly, LabView wasn't created for artists, but I still think this is very important. Again. Not too difficult to create a plugin that works natively. Failing that, even an NI-supported zoom-in/zoom-out tool that wouldn't allow editing in those zoomed modes would be helpful.

 

  • LabView canceling when opened. I believe I saw this elsewhere in the forum, but basically just something that would allow you to close LabView if it opened accidentally without going to Task Manager. On older machines it takes forever to open. Easy to implement; basically just a GUI change to allow closing earlier.

 

  • An "Open Recent" option. I don't know if later versions have this, but it just allows opening the last project you worked on so much faster than what directory browsing allows. Again easy to implement as a plugin, I'd imagine. Some sort of cache'd memory and a new menu item.

Thank you for your time.

There are times when I will open a VI, make tweaks to it to test an idea. In some (most?) cases those ideas do not pan out so I just want to close the VI without saving it. However, the only choices I get are to defer or save it. If I defer it then when I close the whole project, where there may be some 80 vis that need to be updated, I have to step through manually to ensure that I don't accidentally save the changes to the VI that I don't want.  A lot of times, I end up saving all and then I have to debug and remember the changes that I made to the VI to get it back to its original configuration.

 

My suggestion: When asking the programmer if they want to defer or save the VI, have an option to just close the VI without saving. Then upon closing the project, have a second pop-up that states that "These are VIs that were closed without saving you may:

"Close all without saving"

"Save All"

"Save specific VI(s)"

 

Thanks for listening,

Dan

 

Is it posible to set Fillet/Chamfer for wires in LabVIEW block diagram, like in CAD...

Right angle everywhere looks a little rigid...

 

When I print the documentation for my VI's on every single SubVI an entire page is wasted telling me the details about the error in and error out clusters. As this is the same on every SubVI it's a massive waste of paper.

 

I'd like to be able to supress the description for error terminals.

   I've developed a UI technique for creating highly-configurable apps that utilizes a lot of Text Ring controls to allow the user to select from a list of channels or labels or ...  I track the lists of channels, labels, alarms, etc. as the app is configured, and load the Text Rings with them so that the end user does not have to ensure absolutely correct spelling.  Then I convert the text ring to a string value before storing the configuration.  Since the list of channels is so dynamic, it is much safer to save each selected channel as a string than as a position within a list.

   The trick is that when I convert from the Text Ring to the String, I have to use the value of the Text Ring to index an array of all the strings.  Often I keep that array in a handy place, like a shift register, but at times, it is more convenient to read the Strings[] property of the Text Ring itself.  What would be even more convenient would be if there were a "Current String" property that returned the String value associated with the current Text Ring (integer) value.

I attempted to search if this is already existing so I apologize if this has already been struck down (I would be surprised if I am the first to request this).

 

There are many times when I place a not going into the T/F input of a select VI.  It would be great if we could invert the signal at the select VI similar to inverting the signal on a compund arithmetic vi..

 

This can help clean up code in some action engines or state machines, but mostly allows us to get rid of the big not vi in these cases.

 

Best,


Adam

I have a multiple step ATP systems that Operators would like to see Gray for Not tested, Red for Fail and Green For Pass. Currently I overlay two boolean indicator Enable the correct one and set it to true. It would be great to have a single boolean indicator with tri color output.

It would be useful to have a frame to group, comment and highlight parts of a blockdiagramm.

Comment and group.jpg

 

What is the idea ?

1) If a normally frame is used it don't changes the position when the items (VI's, wires, ...) 

change the position.

2) A comment function e.g. "subdiagram label" woud be a help.

3) A grouping function, e.g. "case structure" can help to hold the frame and items together.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

A dialog to select font information at runtime, or at least the capability to read system fonts so we can easily create our own dialog to use at runtime. There is an example here for Windows using .net. A LabVIEW native is preferred.

This is the current behaviour of LabVIEW: I develop a LabVIEW application and it is my fault to not completely figure out which connectors I do have to implement to perform a function by calling a subVI. It becomes later difficult to make a change on that. The process is, I have to add those inputs, which I forgot to the subVIs panel and to the connector pane. I choose save and close (STR+W) and continue with connecting the wire to the corresponding VI on the Main VI.This is difficult as one needs the right type of control on the subVIs pane. My way is to create a constant and copy it to the subVI, then choosing to make the constant a control.

 

My idea is, to finish those two actions (putting a control on the panel and wire it with connector pane) by a simple click to a "free" connector pane terminal. When the mouse covers the SubVI and the user has choosen the connect tool, the user presses a key and then the terminal of the subVI becomes visible. You only need to do one more click and the wire is connected appropriately. On the panel of the subVI the control was build without opening it.

 

Additional: By this method it should be also possible to connect to a terminal, which is currentrly not free but "is wired" to a control, and replace it with the new datatype of the current wire.

This is the current behaviour of LabVIEW: I develop a LabVIEW application and it is my fault to not completely figure out which connectors I do have to implement to perform a function by calling a subVI. It becomes later difficult to make a change on that. The process is, I have to add those inputs, which I forgot to the subVIs panel and to the connector pane. I choose save and close (STR+W) and continue with connecting the wire to the corresponding VI on the Main VI.This is difficult as one needs the right type of control on the subVIs pane. My way is to create a constant and copy it to the subVI, then choosing to make the constant a control.

 

My idea is, to finish those two actions (putting a control on the panel and wire it with connector pane) by a simple click to a "free" connector pane terminal. When the mouse covers the SubVI and the user has choosen the connect tool, the user presses a key and then the terminal of the subVI becomes visible. You only need to do one more click and the wire is connected appropriately. On the panel of the subVI the control was build without opening it.

 

Additional: By this method it should be also possible to connect to a terminal, which is currentrly not free but "is wired" to a control, and replace it with the new datatype of the current wire.

Many of my VI's have lots of long wires that go from one end of the block diagram to the opposite end. It would be nice to create some kind of block, to which you can connect as many wires as you want, and a twin block that you can place where somewhere else, and get the wires out of it, this way, all the wires across the vi won't be seen, and everything will be more tidy.To distinguish different wire blocks, a solution could be to change the block color, or edit the icon as you can do with sub VI's 

Hi all!

I am recently use LabView and SoftMotion for SolidWorks.
I have some problems.
I want use move contour, but I don't know what is "table" and how it use.

How I can use Waveform Chart with move Arc or Contour?
If it is possibly, give me detail instruction about this with examples.

Thanks!