Additional NI Software Idea Exchange

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

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.

I would like to able to build Simscape models successfully using the VeriStand Model Framework for my real-time targets. 

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 Smiley Happy

Saku

Working in Veristand is much easier in engineering units as this is what models often require.

 

It would be beneficial to add scaling to DAQ channels using DAQmx scales. This could be applied on a channel by channel basis.

VeriStand can log data in Stimulus Profile, whose extention is .tdms. That include dt(time step) information, but that is not handled as waveform data in DIAdem. That way, it is a bother to gemerate time stamp data.

For example, when DIAdem opens .tdms file created by LabVIEW, the data is handled as waveform data.  So it is easy to generate time stamp data by "Numeric Channels<-> Waveform Channels" functions in DIAdem. However, .tdms file created by VeriStamd is not handled as waveform. So, it is a bother to create and add time stamp data.

 

Improvements: It is better to give some file format options: 1 .tdms format as waveform  2. .csv format with time-stamp

 

Saku

Under labview we were able to define some signals as differential and others RSE.  In VeriStand, the devices settings applies to the card not the channel in the System Explorer.

This needs to be an option.