LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Idea Exchange for NXG!

NXG needs an Idea Exchange. The feedback button is a lame excuse for a replacement. Why?

I can't tell if my idea has been suggested before. (And maybe someone else's suggestion is BETTER and I want to sign onto it, instead.)
NI has to slog through bunches of similar feedback submissions to determine whether or not they are the same thing.
Many ideas start out as unfocused concepts that are honed razor sharp by the community.
This is an open loop feedback system.

Let's make an Idea Exchange for NXG!

View All (2)

Bring NXG C Node to LabVIEW

View All (2)

Hello,

In many of my applications i had to run dynamic assynchronous VIs using a VI path.

When the VI you want to launch has some problems (VI broken, missing ressources, ... ) you get the generic error 1003. (The VI you want to launch may be broken ... ? )

This error can be easily solved when you are using LabVIEW IDE.

But sometimes, this error can occured in an executable you have deployed to your final user computer.

And then, the error 1003 (The VI you try to call may be broken ... ) is a little bit poor in order to analyse the problem.

This error occurs, for example, when the dynamic VI tryes to access missing DLL's.

It would be nice, if the error 1003 message, could be filled out with and additionnal "error description", giving more informations about the error source.

For example, an error list, like the error list in the LabVIEW IDE. (Broken arrow error list !)

Thanks a lot.

Manu.

View All (4)

Round towards Zero Primitive

We have a Round towards -Infinity (3.8 becomes 3, -3.8 becomes -4)

We have a Round towards +Infinity (3.2 becomes 4, -3.2 becomes 3)

We have a Round to Nearest (Rounds up or down to nearest integer, if 0.5, banker's rounding to even integer)

Why is there no Round towards Zero? Basically a truncate. (3.2 becomes 3, -3.2 becomes -3)

I have a use for that right now, but it takes several primitives to work.

As a corollary, a Round Away from Zero. (3.2 becomes 4, -3.2 becomes -4)

Message Edited by Ravens Fan on 01-19-2010 04:53 PM

I need a format into string that is capable to format numeric with thousands separators.

Like this (Visual Aides - Numeric Separators) idea but also for the conversion and scan functions.

Looking at the syntax

%[$][-][+][#][^][0][Width][.Precision || _SignificantDigits][{Unit}][<Embedded information>]Conversion Code

the <Embedded information> currently used only for time formats would be ideal to extend to a more general form.

Something like <+ nnn nnn.ddd ddd> would be nice 🙂 ( the d is already occupied ... # or whatever .... maybe similar to the excel format syntax or maybe there is a (better) standard??? )

Currently I use the attached vi to add the separators, however it would be nice to have it in a general form

I would like to have an XY Chart that has the same functionality as the Waveform Chart, but with x and y inputs instead of just the y. The XY Graph is not efficient to be used inside of a loop, mainly because it redraws the plots each iteration, and I've had a hard time trying to make a buffer that is as efficient as the waveform chart. The Waveform Chart does not allow you to define the x-axis as anything that is not an interval. For example, I might want to plot pressure vs. flow rate. Many customers also request the ability to change the sampling rate during an experiment. this would be much easier to handle with an XY Chart.

It would also be nice to have the buffer size included in a property node.

It would also be nice to have the ability to change the size of the graph palette.

It would also be nice to have the nearest plot coordinates (x and y values), or interpolated values, to mouse movements over the plot area as a "visible item" in the shortcut menu (this should show a dot over the plot's trace)... I've done this with an X Control, but I'd like the ability built into the new XY Chart on a lower level to improve effiecency.

View All (3)

It would be a great add-on if the graphs have got in-built measurement features/properties/methods like an oscilloscope;

Trigger
Basic arithmetic function like Ch1-Ch2, Ch1/Ch4, etc.
Event trigger based on plot value change. Example an event will be generated if Ch1 value is greater than a set value, an event will be generated if Ch2 value is greater than Ch4 value
In built average plots. Example add plots like 10SMA(Ch3), 30EMA(Ch1) etc.
Threshold based graph visual property change. Example configurable out-of-threshold or in-threshold plot color change.

Advantages;

Save time in development.
Integrated code will be efficient as no data unbuild/build/pass overheads.
Block diagram would be neat and easily readable.
Lightweight code.

Thank You

Adarsh

LabVIEW from 2006

CLA from 2014

PlusAndMinus function

From an AE:

I confirmed with the Product Support Engineer for the PID Toolkit that the toolkit does not officially support the Mac OS X and therefore, we do not have an installer available for it. However, she also did mention that the PID Toolkit is created using LabVIEW code, so it is possible that you would be able to open VIs that come with the PID Toolkit in the Mac OS. I can submit a product suggestion for you to request Mac OS support for the PID Toolkit in the next release.

So here is the product suggestion. NI has gone to the trouble of building a cross platform set of VIs for PID and then stumbled in merely packaging it. Just build an installer.

View All (2)

Python

It would be great if LabVIEW supported the Python language, including any of its various packages such as numpy. Such computations would be much more transparent and easier to support than calling code in DLLs. They would also be much more open and flexible than the existing built-in computational solutions in LabVIEW, e.g., expression/formula nodes. Currently, I have to call Python scripts via System Exec.vi, which complicates data exchange. (NOTE: I am using an older version of LabVIEW: 2009 SP1.)

View All (1)

Allow booleans for array indexing

3D Plot Should Not Plot NaN as Zero

View All (4)

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

LabVIEW Idea Exchange

Idea Exchange for NXG!

Use a more random Random Number algorithm in LabVIEW

Bring NXG C Node to LabVIEW

Asynchronous VI Run : Get explicit error message when VI is broken ...

In range and coerce should have additional polymorphic functionality like accept tolerance

Round towards Zero Primitive

Add "Akima Spline" option to the existing interpolation functions

Format into string with thousands separator

Include the constant "Tau", the circle constant

Support new floating point formats in IEEE 754-2008

XY chart

In-built features in LabVIEW Graph

PlusAndMinus function

PID Toolkit installer for all platforms....

Python

shift register loop tunnel connection issue

Allow booleans for array indexing

3D Plot Should Not Plot NaN as Zero

TDMS function to delete channels and groups

Link VI Analyzer to NI Requirements Gateway