NI TestStand Idea Exchange

トップ賞賛投稿者

ユーザー

カウント

アイデアを提案

There is a major flaw with packed project libraries in LabVIEW. That is that they pull the dependencies in to the same folder as the PPL. For example if you use advanced math functions then lvanlys.dll will be put in the directory. The problem is that LabVIEW doesn't like it when you try to load multiple files with the same name. So if I have a test system with multiple ppls that use the same dependencies I could potentially run into collisions. There is a document here that discusses a solution for this:

https://forums.ni.com/t5/LabVIEW-Development-Best/Packed-Project-Library-Pitfalls/ta-p/3523762

I would like to see the option to prefix my dependencies for PPLs. This could easily be added to the Packed Project Library Options dialog.

Enum Step Type Test

Now TestStand 2016 supports enums, I found myself in need of an Enum Step Type to check the value of a Enum.

I have VI that returns the UUT's current status as an enum. E.g. Booted OK, Bootloader, Timeout or Error.

In this case I want to check the UUT has got to the Bootloader...

I intially worked around using numeric limit test with Datasource set to "Val( Enum("Boot_State","Bootloader"))". But then in results it would be nicer to see "error" than the enum constant.

Then I relaised I could use the String test instead.... which is better. Example attached, casting to Str instead of Val.....

すべてを表示 (3)

Hello,

As we can read in this very good document, we can add information in header for UUT in Report.

It is mentionned that we can do that for StationInfo in the same way:

"The report below includes the custom data in the AdditionalData container. The process for adding custom Station data is similar, but uses the Parameters.ModelData.StationInfo property instead of Parameters.UUT."

In fact, it doesn't work in TestStand 2014 and later, certainly the same for 2013 because the default report plug-ins doesn't support it as you can see in the help of TestStand 2016.

Maybe NI can add it like it is done for UUT.AdditionalData. The goal is to avoid to put some Station Info in UUT result to show it easily in reports.

Best regards.

MaximeR

CLA - CTD

すべてを表示 (1)

すべてを表示 (2)

Defining a custom step type is an iterative process getting the Post Step VI, Edit VI, Step Type Fields, etc. all matched up and working together. I often tweak controls and indicators throughout the process. If I have defined the substeps in TestStand, that means reloading the VI prototype throughout this iteration.

If my controls/indicators are numerics, strings, or arrays of either, the existing parameter values are retained during the reload. Containers are different, however. If the cluster input of the VI is unchanged between the exisiting prototype and the reloaded version, the container parameter values are retained. My complaint is that if one element in the cluster changes, the entire container gets thrown out during the reload.

In this particular case, all I did was change a cluster element from an array to an element. Nothing else (cluster labels, etc.) changed. Because of this, the entire container gets thrown out during the reload along with 30+ values that I had assigned.

Unfortunately, I find myself doing this multiple times during development so the time it takes to re-type everyhting adds up over the entire dev cycle.

My idea is to have container values retained (similar to non-container values) during a VI prototype reload.

Thanks,

Jacob

すべてを表示 (4)

My original thought was to have a context menu appear when you right click the response box of the popup so that you could then click 'Paste' but having a right click paste like in a Linux console would be even better since it is pretty rare that someone would be copyiing data from the input box. The feature could be selectable in the Property Browser (e.g., "RespRightClick" with two options--"Enable" and a toggle between "Paste" and "ContextMenu") or maybe just check boxes on the "Options" tab.

すべてを表示 (6)

When running teststand deployment licence there is no Teststand GUI available to set or configure Results Processing.

I think it should be easy to export the active configuration to file. And then have a property loader type step to load the settings back into the sequence at runtime on the deployed machine. Note in my case I want to run different sequences with different reporting requirements on the same deployment PC.

I have found https://decibel.ni.com/content/docs/DOC-32076
and after more stuffing around than was justified I have got it working with TestStand 2014.

Also it should be much easier to specify a relative UDL file.

I resolved this by adding an expression after ReadEx that was:

Parameters.ModelPlugin.PluginSpecific.Options.ConnectionString="\"FILE NAME="+Left(RunState.SequenceFile.Path, Find(RunState.SequenceFile.Path, "\\", 0, True, True)) +"\\60467Database.udl\""

This means I can select an absolute path to the UDL file in the development directory on my laptop and then use a relative to sequence path in the deployment.

I feel there should be an more obvious way or am I missing something?

Currently, the step icon for a custom step type is defined statically:

It would be nice if the step icon could also be specitied via expression. This would allow step types where the step icon changes based on the configuration. For example, the lock step could be made more intuitive:

Current static icon:

With dynamic icons:

To accomplish this currently, you need to update the icon for the step via the API in the edit substep, which is cumbersome and adds coupling between the edit substep code and the icon names.

NI TestStand Idea Exchange

Expression Function "AllOf()" should accept BoolArray as a parameter

Prefix Dependencies for PPLs

Enum Step Type Test

Support Additional Station Info into header for standard Report generation plug-ins

lvoop class choose implementation of dynamic dispatch VI

Add Arry Elements

Add an Operator /Function to convert values(Numeric,string etc) to dotnet object and viceversa

Add Teststand type libraries to give namespace to types.

Match Container Values within Cluster during Prototype Re-load

Allow Containers to be Set/Get by Property Value VIs

Support "Add Array Item" for Array of Structs in .NET code modules

Right Click Paste into Message Popup Step

Add XML file support to Property Loader step

Add FOR function in Operators/Functions

Add Wait function in Operators/Functions

Precondition on Multiple Numeric Limit Test for each measurement

Export Result Processing Active Configuration

More Options in Include Step Results for Report Options

Step Name in Precondition Builder

Support Expressions for Custom Step Type Icons