LabVIEW Idea Exchange

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

It would be nice if we could programmatically set the inclusion of the upper and lower limits in "In Range and Coerce" function by having two additional input terminals in this function. This two extra terminals should be optional. With a value connected, the context menu option should be override.

 

Now it's possible to do it with a case structure. We may need to have up to 4 cases to cover all possibilities.

Hi,

 

for a complete validation of a software, it is mandatory to perform tests. When testing, we differ between two major tasks:

- static code analysis

- dynamic code analysis

 

For static code analysis, we got the VI Analyzer toolkit. It automates the task of looking into the sources (front panel and block diagram) and compare the current layout against recommended layout (style guide). Additionally, it detects known sources of issues for lack in performance or even crashes and misbehavior during runtime.

 

So it makes perfect sense, to define requirements that static code analysis has to be performed before proceeding to dynamic (runtime) code analysis.

Yet, VI Analyzer tasks have no option for creating such a link as a field "comment" or "description" is missing for the configuration!

 

I suggest to add such a field in the cfg-file level (exported VI Analyzer configuration) where we can add strings like [Covers: <req_ID>] as we are used to in LV code.

 

Norbert

Hi this is the first time a summit an idea, if there is anything else I would need to add to make the idea clearer I am open to suggestions. My idea is:

 

In the LabVIEW Core 1 - The Software Development Method it is mentioned among the design steps is the use of a flowchart and a state transition diagram. I believe it would be a great idea for the the LabVIEW project file (*.lvpj) to have a special type of file where we can create said charts or diagrams and develop them in an special environment all inside the LabVIEW IDE

Granted that I’am a new user of LabVIEW 8.2, I wonder if you could define the parameters skweness and curtosis not only using moments but also using K-statistics (there’s a bit difference).

 

I apologize for my English.

Luca De Vecchi

There needs to be a LabVIEW API for Requirements Gateway.  API functions would be

 

1. Open/Create Requirements Gateway Project

2. Add/Remove Requirement Document

3. Add/Remove LabVIEW VI 

4. Get Code coverage

5. Create Report

etc

 

I think this would be extremely useful with trying to dynamically get code coverage, and really extend functionality

The Logical Shift, Rotate, Boolean Array to number and Number to Boolean Array primatives should work with 64 bit values. Currently they are restricted to 32 bit values.

Match regular expression will return sub matches for any groups in your expression. So this expression: (\w+)_(\w+) would be sub match 1 and 2.

 

temp.png

 

However, LabVIEW only returns the string of the sub match, not its offset and length. This makes doing replacements on sub matches difficult and technically impossible because you then have to do a search and replace on the sub match and hope there isn't an identical string somewhere in the full string (causing an incorrect replace).

 

Other languages deal with this easily by addressing sub matches by slash codes. For example the first sub match is \1 and the second is \2. So you can say... search for this and replace \1 with that.

 

So I propose:

temp2.png

Currently the Labview Database Tool Kit doesn't support returning or working with temp tables in a stored procedure.  This makes a SQL/Labview developer have to make complete hacks (such as returning tables in comma delimited form) to return results that take multiple table manipulations to generate.

 

See this thread for an example:

 

http://forums.ni.com/t5/LabVIEW/SQL-Query-Works-in-MS-SQL-Server-2008-but-not-when-using/m-p/2151492

 

The second element in the ROI cluster is an array of Contours yet many sub vis will only act on the first contour in the array. Both the required contour descriptors(line and annulus) are available in the example image, but since the first element is a line, the circular edge find - which wants the annulus - throws an error. 

 

All it would take would be a simple index and logical test to fix this issue.

The lack of 64-bit Labview support has been fustrating. Having the availability of Labview 64-bit for so long now but still limited by the features that are not supported (slow to recieve toolkit support, mathscript, etc.)

 

I am in need of accessing common data types such as HDF5 and EDF. Discovering that these formats are avaialble in dataplugins was exciting, however to find that they dont work in 64-bit Labview was dissapointing.,

 

 

Regards,

Brian

This is being discussed lots.. There are replies like, each and every element can't be assigned with property of its own and it may require a huge memory..!! But, there is a property called Index Value which when written with Zero, it returns the Value of the Active element ( The Element visible or last edited element).. And this will be very helpful if just the Index Value can be assigned by us and we get the necessary Value we require..

 

array element reference.png

 

This will be of huge help and save a lot of time when working with Referencing and array whose Data Type is a Variant (Unknown)., Eg: Unknown Cluster..

 

I personally believe that this will be possible.. Because, if Memory and all such matters, there wont be a property like Index Value and get its Value alone. We just need to Extend this.. It will be useful in lots and lots of projects.. :):)

Following Robbob's advice from the end of this http://forums.ni.com/t5/LabVIEW/LV-2009-error-bar-plots-suggestions/m-p/987381/highlight/true#M441998 thread, I'd like to "bump", and extend, X.'s idea posted there:

 

A true, built-in, native (not x-control) error bar option on a standard fully-fledged X-Y graph- perhaps implemented simply as a different bundling of arrays to the graph indicator- eg bundle(Xvals, Xerrs, Yvals, Yerrs) or bundle(Xvals,SD(X), Yvals, SD(Y)). In the latter case, the depiction of each data "point" as a gaussian intensity "blob" would be the answer to a years-old dream of mine...!

 

Thanks for considering....

It will be good to have a option like "Close all but this" in File Menu; which will be very useful to close all the sub Vis after debugging and just run the main Vi with all sub vis closed. i feel it would be very good to have this feature.

 

This is similar to the one in Notepad++.

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.

Ich hätte gerne die Möglichkeit, in einem Diagramm mit 2 Y-Achsen 2 Graphen darzustellen,

die unterschiedliche Einheiten haben, z.B.: Spannung[V] und Volumen[m^3]

This is really just a small time-and-space-saver...

 

It would be nice if the * Array Elements functions found in the Numeric and Boolean palettes would work directly on clusters:

bd.png

Yes, the names would probably need to be changed ... but on the positive side, these functions do not even reside in the Array palette!! (Maybe they were destined for better polymorphism from the start Smiley Wink)

 

addmult.pngandor.png

 

 

It would be an added bonus if Darin's complementary idea was implemented at the same time.

Hi all,

 

Tried looking for this suggestion but could not find it so I'll bring it up:

 

Automatic Precisional Rounding of  Write to Fractional String and/or Decimal according to input's bit-precision.   Determines formatting string of and/or converts to string with the level of significant figures or precision inherent to the number and bit-precision of its input, all done automatically.    Example:   A single precision numeric, after arithmetic operation, expects a value of 0.52, but due to precision is representatively stored as 0.51999998903.  When you wire this value into the Write to String but select  "automatic" on the precision terminal, it truncates to the maximal precision theoretically (0.520000).

 

suggestion.png

I have been working a lot with the Microsoft office add-on toolkit for report generation and noticed a few missing functions. One thing was that if you had a template that has tabs in the workbook that were charts ( when asked where you want to display the data when creating a graph you have the option for in the worksheet or in a separate chart) the worksheet selector does not recognize these tabs. So if you needed to change the worksheet name based on say a test name or configuration it will just skip over the tab. Or if you wanted to change the data going to the graph it will not let you select it with the select worksheet sub vi in order to further process it.

 

A second problem I had was replacing the Title of a graph in excel sheets. Apparently you can only manipulate graphs created by Labview using the toolkit. Ones that are already present in templates that are loaded are not changed by the toolkit functions. This means graphs are pretty much useless unless you write a lot more code that grabs data from sheets and creates graphs in different workbooks. It can be done, but for a workbook like mine that had 64 tabs it can be a nightmare. Just a thought I had that would save a lot of time and be useful for a lot of people interested in manipulating excel sheets and doing post processing on them. Still love Labview though.

Hi !

 

I haven't seen a post in this section about the colors of a cluster.

 

I think it could be usefull to allow people to make custom colors and custom wires for their cluster, as it is possible with a lvclass.

 

Here is an example of the actual clusters : you got a pink wire if you cluster contains chars, but you gor the same color if there is only boolean commands or constants. that is not logical.

 

ClusterColors.PNG

Could it be possible to do the same asan lvclass ?

In the porperty window of a lvclass we can modify the color and the shape of the wire, which is very usefull to quickly find the one we are looking for.

 

Here is a screenshot with this window :

 

customcolors.png

 

sorry for the french LabVIEW ! Smiley Very Happy

 

Thanks for considering this idea,

 

Regards

 

At present VI analyzer allows you to check a single VI or a complete project. However, within my Project files I often have clutter from imported librarys such as test functions which are not required for the application I am building but will be analyzed if I select the project, making it difficult to tell what is actually important in the results.

 

What I would like is an option to do a "top down" evaluation of the VI where you select your top level VI and run the analyzer on that VI and all the VIs below it in it's tree. This would allow me to ensure that in large projects I can only analyse and fix those VIs that are relevant to my current application rather than wading through potentially hundreds of useless results to find the useful ones.