NI TestStand Idea Exchange

Hello,

CSV Input Stream allow to parse CSV files to input data into a Stream Loop for instance. By default, the separator is a comma (,). I use a non english version of Excel to edit a CSV file, and every CSV format write a semi-colon as separator (;):

A;0;0;2
A;10;30000;5
A;20;15;7
B;75;42;1
B;100;12;0

Using an expression, I am able to dynamically (at run-time) change the property SeparatorChar:

Locals.MyInputStream.AsCsvFileInputRecordStream.SeparatorChar = ";"

I think it could be more convenient to have a direct access to this parameter in the configuration pane, allowing also to check the content of the file  before execution with Parse Record Prototype funtions.

Best regards,

When assigning a type to a property, the list of types is in an unordered pile. In the next release, can someone please alphabetize it?

(PS. Do not ask about the context of this image. It's not pretty. 😏 )

See thread https://forums.ni.com/t5/NI-TestStand/Automatically-quot-Default-Value-quot-of-a-Parameter-in-a/m-p/3785701/highlight/false#M57087 for description of that case.

The solution could be to add a new flag: "UseDefaultValueByDefault" 

Custom TestStand UI suggestion.

I would like the same functionality as with Sequence Editor when double clicking on Sequence Call step (already configured) and it goes into the Subsequence directly and you can view the SubSequence.

I would like to see that functionality in the TestStand Custom UI when double clicking on the Sequence Call step with Sequence View Manager and it goes into the Subsequence so it can it viewed. 

This would come in handy when debugging a subsequence and setting break points in the subsequence and then viewing variables during execution.

I would love native support of regular expressions (PCRE regex) in TestStand expressions, with the ability to output captured groups.

For instance, hypothetically:

Number EvaluateRegex(String string, String pattern, Number indexToSearchFrom = 0, Boolean ignoreCase = False, Array CapturedGroups)

I have successfully implemented a sequence to perform Microsoft's version of regex evaluation...

...but it takes several steps and uses Microsoft's flavor of regular expression syntax. This is frustrating for me because I already use moderately complex PCRE expressions all the time, and Microsoft's syntax varies enough to present an additional learning curve. It's also much more cumbersome that just using a native TestStand function within an expression.

My idea is similar to this one, but I'm looking for a function. Whenever people ask for regex support on the forums, it seems that workarounds are presented using simple string functions, but these don't cover my more advanced use cases.

Since day one of using TestStand I have been looking for this feature and I have always wondered why it is absent.

Thank you,

Mr. Jim

As it can be done in Expression Browser, it is very helpful if we can use Step Name instead of Unique ID with Precondition builder!