LabVIEW Idea Exchange

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

Populating values to the "enum" control is not possible by using the "strings" property node and hence to populate a large data to a "enum" one has to create a "Ring" control use the "strings" property and replace that "ring" with the enum (or if you have enough time enter them manually) .

 

So why not use the "Strings" property of "Enum" to write values to it directly..See the image attached

 

 

I am not sure whether this is a repeated post or not.

 

However i would like to see the 'Tunnel wiring wizard" as a part of the upcoming LV version so that i can wire mutiple cases of my state machine in a single go instaed of wiring in each frame.

 

 

Here is the Tunnel wiring wizard attached

To make your code reusable as subvi's and have less connector space used the cluster is a way to go, but you need to define the types inside your cluster upfront.

If you want to add an other item inside this cluster you have to rewrite all the subvi's this cluster is wired to...... This is at least annoying. (or dull, boring, dreadful, tedious, dreary, tiresome, aggravating, exasperating, irritating)

 

If you could add new types of variables inside this "Dynamic Cluster Array" on the fly, you can expand the clusters on the fly when needed !

 

Example of a "Dynamic Cluster Array":

 

Dynamic_Cluster_Array_example.png

 Look also to the Search 1D node, to see how you can select an array cluster item.

 

You can read and write the cluster as normal clusters but if you want to read or write a variable that does not exist this variable is added.

Reading and writing this variable will add this variable in all clusters in the array, these variables will get the default value until your software changes this value.

 

This behavior is the same as structures in Matlab

 

John

The only method available to assign all the data from one chart to another is to use the History Data property node.  

 

chart property.png 

 

Without using the property node, all you get is the last value of the chart.   

 

Take for example this use case:

   I have several functional globals holding unique chart data.  Using one Front Panel chart on the main VI, i swap whichever operations data i'd like to see in and out of that chart.  Currently, i have to fumble around with searching for the correct reference number of the Func Global chart and use a property node to do my data assignment.  Totally inefficient! 

 

Adding the ability to select assignment of the entire history to the "Data Operations" context menu, and making the chart polymorphic to recognize the input difference would be incredibly helpful. 

I would like to use data probes and custom probes on front panel controls and indicators. I would especially like to pop-up on an indicator of a running VI and bring up a floating chart or graph.

I miss the possibility to 

 

- add COM compatibility to .NET Interop Assembly builds

- add COM  compatibility to Shared DLL builds

 

 

I missed LV help information about the need to add a key file (*.snk) to the project first, before you can select it for signing the assembly. Unless you do that the file filter (*.snk) seems to fail when browsing.

I would love to have an option to remove scrollbars from block diagram.  I have been using LabVIEW since 2001 and I am constantly having to modify code from engineers who are using LabVIEW for the first time.  If there was a way to enforce the good practice of making the block diagram the size of a single screen, this would help me a ton.  I realize that developers use computers with different screen resolutions so the option to display scrollbars still needs to be there but it would be great if it could be disabled.

The Lego NXT software release (not toolkit) is a wonderful interactive environment, that should be provided as an add-on application

on its own, call it "block application builder".  I see many useful applications in a variety of different industries where businesses wish to extend to their customers interactive and intuitive interface that they can program in their desired configuration of the product's behavior according to their own use cases.

 

That means we need an environment where we can prepackage blocks that is functionally specific to their applications, with ability to sequence them, run them in parallel, add conditional runs, and iterative loops. The blocks themselves could be computational in nature, or additionally provide user interface popups for interrogating the user, and have access to the full range of Labview functionality. Each block properties settings can appear as front panel settings for user to customize the behavior of that block. This is exactly how the

Log mindstorm software was configured, except we ask that you extend the availability of that functionality for the general users to develop their own intuitive applications using the same environment framework design. This application can target building the customer created sequence of operations as a windows .exe or .dll. We also would like to customize the menus in the application. In other  words, make the Lego mindstorm application a generic template for us to develop our own applications with similar intuitive framework.

For controls and indicators created through Block Diagram, the display of the Label in the BD can be made invisible by right clicking on it and select Visible items. I used to do this often when my diagram gets bigger and bigger.

 

Oops lot of mouse strokes.... Instead if by simply pressing delete key, if the label gets invisible, then it will be very good and easy..... Just a thought. Please comment on this.

parameter_system.jpg

In large application there are huge amount of parameters. If there is a lot of parameters usually there is also lot of parameter handling code in block diagram. This code can be moved to away if there is ready mayde parameter handling system. Here are my basic needs\ideas to this kind of system: 

 

- Parameter values are read from e.g. CSV-file when there is a first call 

- Parameter value must be changeable during code execution

- When value is changed new value must be updated to e.g. CSV-file

- User can change parameter name from project view. The new name is updated to all block diagrams (compare to shared variables)

- New parameters can be created from project view

- All parameter values can be changed and read from block diagram by using proper VIs

- Parameter library settings e.g CSV-file format and name can be set in project view

 

Is there any one else who needs this kind of system?

Make a new menu item available in the structures contextual menu (like the auto-grow) to enable automatic wiring off wires that go through the structure in other cases, events or sequences.

Why did National change the way pasting objects on either the front panel or block diagram?

In 8.2 the paste (Ctrl-V) would paste the clipboard where the cursor was last clicked. 

In 8.6 (or possibly 8.6.1) it always pastes it in the center of the panel or diagram and is floating.

This is very annoying.

 

Hi,

This is my first thread in the Idea exchange. The other "demands" are already put by others so didn't need to start a thread. I don't know if there is already a thread with this subject. My brief search didn't show any results.

 

Well, I have come across this requirement, and I am sure many of you must have in the past.

I think it would be nice to have "free labels" on the front panel whose text values can be set programmatically.

 

There are labels which come with a 3D frame by default, and there are free labels without these 3D "raised" background. But these cannot be set programmatically.

I know, we can customize the String Indicators, and make them transparent etc, and remove their borders also, so they appear like label, yet with properties.

 

But, like many other demands here, I guess this one would be good too, to have shipped with the next LabVIEW. This will reduce unnecessary burdern of controls, if I have many instances of this object on my FP.

 

Looking forward to comments.

I like very much the possibility to cycle between "wire" and "select" by pressing the space bar, when editing the block diagram. But usually, I need to edit string or path constants: so I'd like to select the "text edit" tool if I press the space bar again.

The same should apply to front panel editing: cycle should be:"operat value (finger)", "select (arrow)", and text. That's useful to edit labels.

I don't like using the "auto selection tool" when editing BDs or FPs, because you need to be very accurate when pointing the mouse.

A multiple case structure is always difficult to navigate to and understand. A toggle option like the below will add clarity

 

idea.JPG

Please note the Case summary text option suggested in the right of each case in this view. In the present view you have to navigate to each case to get a glimpse of what is done. A simple summary like below will add a lot of clarity and help in understanding what is actually being wired in the subsequent cases (just an example)

 

 

notes.JPG

 

Will be helpful while dealing with multiple case structures isnt it?

Please add an option to have a new custom control from the xcontrol management panel.  Currently I need to create a new control, and then add it to the xcontrol afterwards.

Wow,

 

This would be super powerful.

 

It's a little hard to grasp at first.

 

If you have sheets or tabs like EXCEL, you could write clean code in small chunks without have all the overhead of many SUBVIs!!!!!

 

I would use "local variables" to get data back and forth from different tabs/sheets.

 

TAKE 1 MINUTE TO THINK ABOUT!!!!!!!!

 

I've had case statements with 50 items.

 

It needs better tools

 

1. Delete cases in popup

 

2. Rearrange more than one case in the popup before it closes

In text based language, define some constants with meaningful names are very common task. For example, you typically define constant in C like this: 

 

#define RED          1

#define GREEN      2

#define BLUE         3

 

In LabVIEW, you can use ring to define them: 

color ring.PNG 

 

and then you can use the constant very simple: 

 use color ring.PNG

 

But the following definition can not be implemented with ring:

#define RED          1

#define GREEN      2

#define BLUE         3

#define DEFAULT   1

Here, DEFAULT is the same with RED.  But this is not permitted by ring, it will popup a warning if you try to do this: "Waring: Identical values in the Values list are not permitted. The oblject cannot be updated until you assign new values or remove items with identical values. "

 

I know you can use local or global varibles to define constant as a work around, but variables have performance overhead, it is not the best solution as a result. 

 

I propose to create a "const" that allow different items share the same value, and the other behaviours will be the same as a ring. You can also add "picture const" and "text & picture const". 

 constant.PNG

 

The following topic on NI discussion forums inspires me to propose this idea.  

 http://forums.ni.com/ni/board/message?board.id=170&thread.id=435687

 

It would be very useful to have a way of automatically create subvis when a single vi become too large. What we usually do is :

1. Select the portion we want ton encapsulate in a new vi.

2. ctrl-X.

3. Create new VI, save as, chose name, change icon.

4. ctrl-V.

5. Connect the front panel.

6. Add the new vi to the original diagram.

7. Connect the new vi.

8. Debug mistakes.

 

I think steps 2 to 8 could be automated with a single function (e.g. 'transmute selected code into a single vi'), saving a little time many times.