Additional NI Software Idea Exchange

Hi,

Here is a small idea that will be really value added in Alarm Handling

In cases of using sensors like inclinometer, thermocouples, LVDT and etc, there are chances where noise peaks in signal might go Out Of Limits. These kind of peaks are usual in the sensors where it stays not more than 5 msec. So in these case, We can use Persistance to avoid inducing false alarms. We can ignore the noise peaks whose period is not more than the defined time (mscec).If the peak remains more than the specified time, then the alarm should be induced.

The Persistance might be given in msec.The user should also be able to enable/disable this option.

-SID

Hello,

In VS 2011, font of Workspace control label can not be changed. If you can change the font and size on item property window as below image, it is better for users to arrange Workspace. Moreover, I hope that the label would support multi language 🙂

Regards,

Saku

Hello,

One of my customers wants to scale voltage to scaled data with look-up table, but calculated channel in VeriStand 2011 does not support it. Custome device doing LUT scaling might be created, but it is better to offer LUT scaling function

Saku

Hi,

LLBs are outdated, suffer from name collision because it doesn't embedded lvlib nor classes, and force the VIs to match the exact same LV dev version with VS runtime version (to be able to run the compiled code of raw VIs on the target without the need to recompile them).

It would be preferable if custom devices/controls could be built into lvlibp instead.

It has many advantages such as:

* Source protection

* Respect of lvlib and lvclass namespace (avoid name collision)

* Only the compiled code is stored so they are smaller than LLBs

* Compiled code made with LV 2017+ is compliant with upper versions of the run time engine (would allow keeping the version of LabVIEW while upgrading Veristand)

I'm pretty sure the limitation nowadays only relies on file extension filtering to find the 'main' VI to launch in the SysExplo and engine. If I'm right the change could be done easily.

Aside from the fact that most of the errors are just pulled up from device drivers which makes them vague and not at all related to the actual VeriStand function happens (so part 1 of this feature request is an overhaul of our error reporting in VeriStand), it would be great if it actually logged these or gave you the option to save to a file. This means that you can then send this to NI Support for assistance or at the very least, document issues.

Currently when trying to see errors we need to enlarge the window, scroll through the items, and then take a screenshot of the dialog. This was encountered when trying to share my errors with support. We should make this easier through the proposed ability.

The types of scale is limited to lookup table, polynomial and thermocouple.

For thermocouple the scale is only available for input (electrical -> physical).

It will be interesting to add other scales, like thermocouple on output, time to frequency (1/x).

The best will be the capability to define custom scale.

Hello,

It would be nice to add some controls in VeriStand workspace screen objects in order to handle macros.

• A control to be abble to Start / stop a Macro
• A control to be abble to record a macro

The two controls could be linked to a combobox which could list the content of a "Macros" directory, located under the project root.

• A button to start a macro could also be usefull (With a label and linked to a project macro)

These controls could be helpfull when you want to build a simple screen, for users without big knoledges about VeriStand.

Manu.net.