LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Using "Select a VI" option, we constantly browse to a set of reusable/project folders at different location.

Getting vi's from Project folders is easy with project explorer window but this is not the case for reusable.

It will be better if we have an optional node in LabVIEW Palette that helps us in browsing LabVIEW files from a set of folders.

Documenting my suggestion below:

1. Consider the "VI Browser" is our required node as shown below.

2. On Right clicking the node, i should populate the folders and subfolders as pull right menu name [Assume that VI Browser node will get the folder paths from a ini file similar to LabVIEW.ini]. And LabVIEW files as the elements for the menu. Thus the menu can be customized from ini file.

3. Upon selection of an element, the node should get replaced with the vi or ctl as below.

This kind of feature prevent us working with windows explorer for browsing vi's in the middle of programming. Also adding this to Quick drop will further reduce our effort of browsing.

View All (3)

I'm a new user and have noticed data are put into folders with the project date as the name. An Example is: 10152012_111940_AM.

In one project I generated several folders which I realized cannot be sorted chronologically by name. My suggestion would be name folders using this format: YYYYMMDD_HHMMSS where HH uses the 24h clock. That way folders will sort chronologically. So the above folder would be 20121015_111940. The attachment shows a folder with renamed files.

View All (3)

Conditional Functions

When you search in the window of explorer some element of labVIEW all time shows the generic icon of the type of file

For controls

For Vi’s

For libraries

Etc…

This functionality is correct to identify the type of file, but when you change the representation to medium or large icons, the icon don’t change and you can’t identify the particular element.

Mi idea is that, in short icons maintain the actual representation, and in the medium or large icons represent the icon of the element (which has been designed by the user in icon editor)

In the same way this function could be implemented in the project tree into LabVIEW editor, this idea can be found more easily some element when the project is big.

Add a button to open a broken VI in the app instance where it would be built.

When a build fails because of a broken VI the application builder shows an error window. Since LabVIEW 12 all the broken VIs are listed inclusive the reason why they are broken. (The list is in the reasons field.) This is much better than before, thanks.

But today I had a list of broken VIs, every single one without a reason. (Example message: broken1.vi: \n broken2.vi: \n broken...)

So I come up with the idea I proposed in this thread (even there were improvements since):

"I ask for a possibility to open the broken VI in the BUILD application instance when this error occurs. This could happen automatically or with a button."

(A general idea about improving app builder: Better error descriptions for Application Builder).

View All (3)

Often I have parts in the code which are duplicates but differ in types (representation) so that I am not able to use a VI. So there is the possibility to use a Code Snippet and but it to these locations. A nice feature would be the possibility to capsule the code snippet. This should give the possibility to edit the contents and to apply all changes to the places where the codesnippet is in use. This would make it comparable to a strict typedef and give the possibility to edit code on different locations although no vi is used. This feature is also comparable with an include statement in an text oriented language. This feature would also be helpful in maintaining a polymorphic vi because there only would be one place to do your changes.

View All (1)

I came over the problem while creating a polymorphic vi. Most of the code in a polymorphic sub vis is equal only the representation of the controls and indicators differ. I build a polymorphic vi to handle a data reference to 1D, 2D 2D arrays with DBL,FLT,I64,I32,I16,I8,U64,U32,U16,U8. Which results in 60 nearly equal vis. If there might be a need for maintenance this results in a change on 60 positions which is boring and error prone by the best. So I was looking for a way to include the equal part from a vi or whatever with no dedicated early types on inputs and output. I did not find a way and therefore I but the idea here.

Please build a possibility to include a subvi without dedicated representation on the inputs and outputs.

Example:

I build a vi for saving XML description and array data to a file. (see attachment)

You can play around with that and will see that changing the AB value representation from I16 to U16 will break the wires. There is no valid U16 data value sub vi in the polymorphic vi. If you want to add that you copy the WriteDataBlock_I16_2D to Write DataBlock_U16_2D. Change the representation of the array data value reference in and out and save it. Than you have to add the sub vi to the polymorphic vi WriteDataBlock and the program will work again. You have to do this for every representation you want to give the user a possibility to work with. If a problem arises you have the change code in every subvi of the polymorphic vi

subvi of polymorphic vi.jpg use of include vi.jpg

View All (3)

For giving an elegent look to the frontpanel it,sometimes needs to be bold,coloured,justified etc:-I want to make my listbox looking elegent,for that all the listbox values need to be justify on center.I searched and came to know that we have to select each row value one by one and then go to Application Font>>Justify.It is very cumbersome if our listbox contains 50 or more datas.why don't provide an option for:-

Rightclick listbox>>Justify>>left,Right or center.

View All (1)

When i created an Accessor for a Cluster of the class private data, i was able to access only the Cluster., but couldnt get the Individual elements of the cluster. If i want Individual element, i need to Unbundle the cluster again. But, I wish to get the Cluster's element too from the Property Node itself (Like how Unbundling of Cluster of Cluster can be done). So that, the Elements of Cluster will look like getting from a Sub Menu..

Large crosshair cursor in LabView

NI smartcams + VBAI provide a really neat and fast way to get results in image processing - however, predicting their performance is close to impossible. Information like "DSP coprocessor" is nice, but it's not adding any information that I can use.

I have benchmarked the devices that went through my hands with some standard resolutions+ROIs and algorithms, so I have some idea, but most of the time I just wonder "Would this work on a 1774?" "Would it work on something slower?" I usually call an engineer and try a loan device, but this takes time and rather static concepts.

I know that algorithm runtimes (especially the more complex ones) strongly depend on the sample data, so it's not just a matter of scaling, but even an estimate (like 8-12ms) would improve my experience rapid prototyping.So, I'd just use Profile->Performance Meter -> Profile for NI 1772..

View All (3)

For debug purpose TestStand and other programming languages provide a "Watch Expression" feature. Similar to this I would like NI to add "Watch Variable" feature in "View" menu:

When user would click on "Watch Variables" a he should be able to see all the locals and globals used in entire VI hierarchy and select the variable that he wants to Watch. These variable should be displayed in another floating GUI. This feature would be of immense help even when we want to debug an executable where probes can't be used.

Thanks

Amit Karia

View All (6)

View All (5)

The current behavior of the ""Array Max and Min PtByPt" library VI is to return only the FIRST occurrence of an element in the input array that is the minimum or maximum value. If the array contains data for which each element is unique, that's fine. But if the data is NOT unique, and more than one element can contain the same value, this routine could provide considerably more functionality by returning ALL min/max element indices.This is in fact the current behavior of the "Array Max and Min" library VI.

I'd like to see the "Array Max and Min PtByPt" library VI updated to match the behavior of the "Array Max and Min" fucntion, namely that instead of returning only the index of the first min/max element found, it would return arrays of indices for ALL max/min elements found.

The implementation of the functions that process arrays intact (like "Array Max and Min") and the functions that process 'arrays' point-by-point (like "Array Max and Min PtByPt") should be both consistent and factorially implemented. The decreased functionality of "Array Max and Min PtByPt" is inconsistent and unnecessary. The full implementation would make that routine much more useful.

All of the PtByPt routines should be evaluated to see if they are consistent with their array-processing counterparts.

View All (5)

LabVIEW Idea Exchange

VI Browser node for Reusable and most used labview files

Data Folders Name in sortable date format

User icons available in the Icon Editor

Conditional Functions

Display true Icons of controls and VI’s

Possibility to open broken VIs out of error dialog for Application Builder

Customized sub VI can be viewed as an icon

Including code snippets comparable to a strict typedef

Expand shortcut menu for "Display format"

SUB VI as an include with no dedicated controls and indicators - only include graphical representation into host vi

Justification of listbox values

Make label color for wires match wire color!!!

Problem in Accessing Cluster's element of class private data by property node

Call Library Function: retrieving funtion prototype while running

Large crosshair cursor in LabView

Profiling estimates/Emulator for Smart Cameras in VBAI

Add "Watch Variable" Feature in LabVIEW

Set Default VI Properties Globally

Enhancement to "Array Max and Min PtByPt" function

Quick-drop insert into correct wire segment