VeriStand Steps for TestStand Feedback

[Holt]

It must be due to the "Channel References" that got added to 2014.

[Sarci1]

Hmm so it is literally a blank system definition for you. I thought you may have had a channel reference under that node. But I added one here on my end and was able to run without error.

Please try the attached RT seq with the Engine Demo project.

[Holt]

I simply created a new 2014 RT Sequence and saved it.  I didn't add any Channel References or anything else.  It must have something to do with it being blank.

[Sarci1]

Ok, so I am able to run an rt sequence with both parameters and channel references within it that was newly created in VeriStand 2014 Stimulus Profile Editor within TestStand 2014. However, I get this error when attempting to run a blank rt sequence:

I'm not able to replicate the error you originally posted. Are you able to run non-blank rt sequences?

[Sarci1]

Are you using the TS 2014 32b VS 2014 version of the steps? When you test the 2013 versions are you uninstalling the steps and reinstalling the version for 2013?

[Holt]

I did an uninstall and reinstall of the TS 2014 32b VS 2014 steps and everything works now.  I'm pretty sure I had the 32 bit version installed before because I can see it in my download folder from a month ago.  Not sure what the issue was but thank you for your help.

[DCatz]

Hi all,

Just some feedback after using the RT Sequence steps with VeriStand 2014 (and TestStand 2014), It seems that there is a bit of a mix of parameter type naming supported in the various helper vis that come with the sequence steps.

The custom steps configuration window which parses the RT sequence file seems to write I32 parameter types as "I32" string in the parameter types array, but the "Run RT Sequence Pass Fail Test.vi" support vi (found inside "C:\Users\Public\Documents\National Instruments\TestStand 2014 (32-bit)\Components\TypePalettes\RTSequenceVIs.llb") only translates/supports parameters of type "Int32" (and "Int32 Array").

However a similar support vi "Run RT Sequence Numeric Limit Test.vi" found in the same llb translates/supports types of "I32" (and "I32 Array").

I came across this when attempting to run a "RT Sequence Pass Fail Test" which would not respond to the parameter included (it always used the default value).

It would seem sensible to support both naming conventions or standardise on the correct one! You can "get around" this by manually changing type to "Int32" in the TestStand Step Properties (or of course by modifying the helper vi yourself and modifying the step type definition), but it would obviously be better that the RTSequence support llb was updated.

Not sure if this changed in TestStand/VeriStand 2014, but hope that this info helps someone! Best wishes.

David Catto

Austin Consultants (UK)

[Sarci1]

Hello David,

Yes, this is a bug we are aware of in the current version of our steps that we will be addressing in the next release.

Thank you,

Lynn

[DCatz]

Great thanks Lynn. Apologies if it was posted before - I did take a look, but couldn't see it. Thanks for an otherwise great Add-On!!

DC

[FLQ]

Hi all,

I encountered a problem when trying to pass parameter values from TestStand to an RT Sequence if the parameter values are saved in TestStand variables (in this case Locals).

The values to pass don't reach their linked parameters in the RT Sequence, there the parameters are just set to value 0.

If I don't use TestStand variables and pass a particular number, it works.

In the attached file the values for Param1, Param3 and Param4 don't reach the RT Sequence, the second parameter ("1") is passed correctly.

As TestStand makes suggetions to choose between TestStand variables when I type "Locals." in the Parameter Value lines of the Configure Real Time Sequence window, I wonder if passing values from TestStand variables is a feature that is not (yet?) supported and just not resulting in an error/hint.

Supporting this would be some kind of key functionality for me to keep my TestStand sequences modular and scalable for the users.

Thank you in advance for your help!

Flo