Additional NI Software Idea Exchange

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

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.

In Veristand you can add a alarm with one low and one high limit. Often it is helpfully not only have alarm limits but also warning limits. In some automation systems (e.g. Morphe from D2T) we can define three limits.

 

For example:

Warning: The oil pressure of a engine fall below the warning limit we could log that, show a dialog and stop smoothly the engine.

Alarm: But if we fall below the alarm limit its very important to stop as fast as possible.

Problem: If you import a model dll you did not create on your own you have no information how to use the model and its channels. Neither the description nor any unit string comes with the imported model.

 

Please rework the VeriStand model generation tool that the description property of the VI and the channels are transferred to the model dll.

Also please make sure the default descriptions are loaded into VeriStand when importing the model.

 

Getting the default unit might be more complicated as there is no unit property for LabVIEW controls and indicators. I am sure you have a smart solution for this 🙂

 

I appriciate!

Hello,

 

Today I have a need that is a bit difficult to perform: I developped a soft that convert a xml file into a VI, but I'd like this soft to create a VeriStand model from this VI.

So it would be very interesting to be able to dynamically create a Veristand model in Labview, wheter thanks to an API or an invoke node, ...

I appears that for the moment the only way to do it would be to open the LVSV Dialog.vi by script.

 

Thanks,

Luc.

Currently error messages are quite vague - they say what failed, but don't say where. It might be fine in LabVIEW development, where error pops up in the exact location on the block diagram, but it's not well suited for Veristand, where all we have is the error message. Take this as an example:

 

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The VeriStand Gateway encountered an error while deploying the System Definition file.

Details:
Error -1074384704 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi

Possible reason(s):

NI-XNET:  (Hex 0xBFF630C0) A property value was out of range or incorrect. Solution: specify a correct value.
=========================
NI VeriStand:  NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi >> NI VeriStand Engine.lvlib:VeriStand Engine.vi >> NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi >> NI VeriStand Engine.lvlib:Initialize Inline Custom Devices.vi >> Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 

I'm trying since 2 days to figure out which property is invalid - I have 4 CAN channels and 2 LIN channels in the SDF... If there was an information about the channel/value that causes the error, it'd be far easier to sort the problem out.

Currently there is no specific upgrade path for VeriStand. This affects code reuse and portability when trying to keep up with the latest version. It's understandable that there are going to be limitations, but lack of documentation makes this task very difficult. 

Hi,

 

We are using the VeriStand SystemDefinition .NET API to automatically generate VeriStand .sdf files. However the SystemDefinitionAPI only seems to work when accessed in 32Bit applications (in our case Matlab/Simulink). As in the future more and more applications will only be available as 64Bit versions, this very convenient VeriStand feature will no longer be usable for us. Thus I strongly suggest for to provide also a 64Bit compatible version of the SystemDefinition .NET API. Interestingly, other VeriStand .NET APIs (like the Execution API) seem to work well even when accessed from 64Bit applications.

 

Best regards,

Thomas Zettl

 

During the test phase, the possiblity to add a a formula or a conditionnal channel instead of just a number, would be really appreciate.

This feature was included in TIV, a competitor software and we really missed it.

 

add formula.png

 

When we have to develop add-ons for Veristand, we need to search into examples and existing add-ons to find how to implement some basic or advanced functionalities.

For example : using the node browser control in a labview dialog box, or finding the list of the optional inputs for custom workspace.

 

This is really time consuming !

 

Veristand is missing documentation for add-ons developpers. It would be good to have a Reference Manual like in TestStand.

When configuring a system definition file in VeriStand, you can spend a lot of time expanding all of the tree items even if there's only one other item under it. I think it would be nice if the tree auto expanded down to the first set of user-added branches. For example, say I have a simple System Definition as shown below:

 

sysdef.PNG

 

If I want to get down to the CAN port I've added, I need to expand Controller, Hardware, Chassis, NI-XNET, and CAN. It would be nice if, assuming the only hardware I've added is the CAN Port, that when I expand Hardware it automatically expands all the way down to CAN 1 since it's the first node I've added. Obviously if I'd also added a DAQ card I'd be ok with it only expanding down to under chassis. Alternatively, or in addition, a button that completely expands the currently highlighted section would be nice.

Currently the stimulus profile message box prompt allows user text input, but the user text isn't usable anywhere. I'd like to the text to be returned for use in the profiles/sequences. Thank you.

Because we use sequences as function calls, it'd be great if they could return multiple variables or return arrays.

I have hundreds of signals and I want to be able to set a values to them all at once without listing each one individually in every sequence. How do I write to many signals at once?  Is there away to assign all the signals to one variable or array of some type and just write to that variable?  I did not see such mechanism and NI support says nothing similar exists.  Maybe this should be considered.

I'd like to see a system channel that can point to the line number of the real time sequence being run. This would add additional debugging capability. Something similar was available in VeriStand 2009 where a "GENxyz Current Step" would indicate what step the profile was on. Thank you.

When I talk with customers who wants to create stimulus test pattern signals, many customers say "I want to create test pattern signals by similar meathods to Signal Builder in Simulink. In "Signal Builder", user can change value by mouse action, and user seems to like that way. (I think Signal Builder in Simulink is not so intuitive and flexible) And user wants to create multiple signals in stacking graph because it is easy to compare each signal timing.

 

image.png

Hello,

 

Sometimes, customer want to change current model file with another model file. Once the model file is deleted on system definition, mapping infomation related to deleted model also disappear. To workaround this, we have to export map info, then delete mdl file and add new model, and then import map info...but this process sucks.

 

To save our time, I want to suggest "replace" function as below. When replace the model files, map info for the same inport/outport are kept.

 

Img.png

 

Saku

 

Way back when VeriStand was first introduced recorded files could automatically be broken apart when they reached a set size.  This feature went away and I would like it back.  I am running test that will last days at 10Hz or faster, so large files are generated.  This really bogs down DIAdem when the data is analysed.  I would like to be able to set the logging file size max  (i.e. 50 Meg) and when the file hits that size a new file with an incremented name (i.e. TestFile_1) is created and data is now logged to it untill it reaches the set size limit.  This not only creates smaller files that can analysed, it lets the data be looked at sooner in the test cycle.

Currently the avaliable Controls and Indicators are not enough for some projects using verisatnd. Since most of the user's doesn't have labview to create, it is better to have more generic controls and indicators.

Hello,

 

Most of Workspace Controls, like nob and bool button,  are not resizable. Resizable controls will allow user to organize Workspace easily.

 

Kind regards,

 

Saku

 

Hello,

 

Matlab/Simulink is used for ECU development process, where .mat file seems to be used as test signal pattern definition. NI products is used for ECU verification process, but the same .mat file could not be used by VeriStand. If VeriStand support .mat file, that would help customers save their time. So I hope: 1.Stimulus Profile can read not only .csv file also .mat file  2. custom device supports .mat file for signal play back.

 

regards,

 

Saku