Custom VeriStand Steps for TestStand Feedback

[Kevin_F]

Hey Jiri,

Initialize VeriStand should be scripting those file globals. It was the last time I looked at it but multiple people have been having trouble with it lately so I can check it out.

EDIT: If you look at the Initialize VeriStand step it should be calling a VI called StartVeriStandBundle_CreateReferences located: C:\Users\Public\Documents\National Instruments\TestStand 2013\Components\TypePalettes\StartVeriStandBundle_Create Reference Locals.vi- this all works on my machine. Is that VI present on your machine?

[JL@NI]

We designed the current version of the step types to create the FileGlobal varaibles needed to manage the VeriStand references automatically when you place the step type "Initialize VeriStand" in your Sequence File:

If you would not like to use this bundled step type, you must create the following FileGlobal variables:

Regards,

Jeff Langston

National Instruments

Inside Sales Engineer

Certified TestStand Architect

[TylerJ]

Kevin,

I attached a picture of what the Initialize Veristand step is adding to the project.

Jiri,

Do I need to add all the local and globals you have on that project?  There are a lot and I just want to make sure I get what I need.  Or should I just do away with the Initialize VS step for now and make it look more like the one you attached? 

[Kevin_F]

Hey Tyler,

You shouldn't need to add any references starting out of the box if you use the Initialize VeriStand step - I think Jiri had to update the engine example since it is an older version of the steps. 

Your screenshot looks like all the required variables are being created so its strange that it can't find the stimulus profile file global (which is correctly present in your screenshot).  I'm going to experiment a bit and see if I can reproduce the error.

[TylerJ]

Sorry, that screen shot is wrong, I had added that global in an attempt to correct the problem, but it just caused another error.  I deleted that step and all the variables associated with it and then added the initialize step back in.  Now I get this error.

[daufdi13]

I am using TS/VS 2013.  I installed the v300 Add-on.  I did not have a previous version installed.  I am unable to reference VeriStand aliases with the Channel Selection .NET dialog in the 'Get Channel Value' step.  The Add-on is using NationalInstruments.Veristand.VeristandSteps(1.0.0.1)

[TylerJ]

Jiri,

I'm getting an error with the setup you sent me.  I added all the locals and globals I need, but now I'm getting an error with the "Get Sequence State" step.  Also the RT sequence doesn't actually run in VS.  Any ideas what it means?  I've attached my setup, and the error message.

[Kevin_F]

I posted a new v300 installer on the download page. Give that a try. It should fix all the issues with needing to add references.

[TylerJ]

Kevin,

That did the job, however, now I can't get TS to actually run the RT seq on VS.  I tried adding a Get Sequence State with a loop to make it run until the sequence is complete, but it errors on the Get Sequence State with the same error I showed in my last post.  Thoughts?

[Kevin_F]

I think its probably using the wrong name - take a look at the results of the previous GetSequenceName step and see what it returns when deploying your sequence, use that in the GetSequenceState step