Custom VeriStand Steps for TestStand Feedback

[Holt]

Thanks TylerJ and Kevin.  I took the example and changed the "ToBoolean()" to "ToDouble()" and it works.  Thanks for the example.

[TylerJ]

Kevin,

I'm having a new problem, when I try to run my sequence I get an error with the initialize VS step.  It says that StartVeriStandBundle_Create Reference Locals.vi is broken or can't be found.  I found the VI and it is in the right spot and works.  I attached a picture of what's happening.  When I hover over the exclamation point it says it failed to load the VI in the version 13.0.1f2, and that a version of a subVI might not match the version of the run time engine.  Can you help with this?

[Kevin_F]

Hey Tyler,

I haven't seen that before. When you open the VI itself in LabVIEW it is runnable (no broken run arrow)?

[TylerJ]

No broken arrow.  All the subVIs exist and everything looks good.

[Kevin_F]

I'm putting 2013 SP1 (and the f2 patch) on my machine to see if that makes a different - I don't think it will but its the only difference between our setups that I can tell.

[TylerJ]

I've tried uninstalling Teststand along with the custom steps, then reinstalled both.  Same problem.  I also have another computer with TS and the custom steps, but it doesn't have the problem at all.  It has an older version of the custom steps though.  I'll try installing the latest version and see if that breaks it.

[TylerJ]

The latest version of the custom steps does not break my other installation.  It has to be something particular to this setup.

[Kevin_F]

I just reproduced it after installing SP1 and the f2 patch. Something weird is going on with the run time engine. I'm going to investigate further.

[Kevin_F]

Check these settings: http://digital.ni.com/public.nsf/allkb/CE431BA1A3B61953862573540078DAD8

After I installed SP1 and f2 TestStand was defaulting to the wrong LabVIEW version. I closed everything - opened and closed LabVIEW and then opened TestStand and everything was OK - I think its a case of whatever the last thing opened is what is uses as the LabVIEW version.

[TylerJ]

Kevin,

I'm having an issue running sequences again.  When I try to run them with the initialize veristand step in it, it analyzes the sequence and gives me an error.

Severity	Rule	Category	Text	File	Location
Error	Code modules must be able to load	General	Module for Step 'InitializeVeriStand' not Loadable. Failed to load VI 'C:\Users\Public\Documents\National Instruments\TestStand 2013\Components\TypePalettes\StartVeriStandBundle_Create Reference Locals.vi' in the LabVIEW Run-Time Engine version '13.0.1f2'.

LabVIEW:  The VI is not executable.  This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it.

VI Path: C:\Users\Public\Documents\National Instruments\TestStand 2013\Components\TypePalettes\StartVeriStandBundle_Create Reference Locals.vi

BLC 2.seq

InitializeVeriStand.Substeps["OnNewStep"].TS.SData

I have located and opened that VI in LV 2013 and it runs just fine.  Thoughts?

Tyler