VeriStand Steps for TestStand Feedback

[User002]

wielro_1,

Thank you for the info.  That sure sounds like a bug to me.  I will look into it and see what we can do.

Thanks,

Andrew

[wielro_1]

Hello Andy,

have you checked and analyzed this behaviour ?

Should it really necessary to have at least one parameter in every real-time sequence even if it´s for example only a RT Sequence Action step.

Regards,

Robert

[User002]

wielro_1,

We did look into it.  It doesn't appear to be an error in our code, but it's not clear yet if it's a bug in the VeriStand API.  We haven't had the time to test that yet.

I think I agree with you that it shouldn't be necessary for there to be a parameter.  If it's a bug in the API, we'll treat it as such.  Though, it's possible that the API allows it, and the problem is a subtle difference in the way we are handling the parameter references in the Step type code.  That should be easier to fix.

I'm glad there's a workaround for now by adding a dummy parameter. What is your timeline for needing it fixed?  I can't promise anything, since we have been busy, but I can try.  You can also shoot me a private message if you prefer not to discuss things here.

Thanks,

Andrew

[D4N!3L3]

Hi all,

I've faced the same problem ofwierlo_1. I've found that the problem is related to the way the configuration dialog box of the custom step react to a realtime sequence whitout parameters. In this case the Step.VeriStand.Param___Array assume the value of {""}

Then, at run-time, those parameters are passed to the VI that launch the realtime sequence (ie "Run RT Sequence Pass Fail Test.vi") as arrays with a single empty string instead of empty arrays.

This empty string is interpreted as a "Default" parameter so the "Parameter Assignments" array passed to "Create Sequence Call.vi" contains an invalid element and cause the error.

A quick fix is to enable the "conditional" on the auto indexing terminal that builds the "Parameter Assignments".

Hope this will help 🙂

[Andy-C]

Good catch!

We actually found this yesterday while testing that code.

We're going to try to include this change in an updated version of the installer for the steps, but it may be a couple of days before we have a chance to get this done.

Best,

Andy

[User002]

gardowp,

The references used for talking to VeriStand are in the FileGlobals >> VeriStand group.  If you pass those to your VI, that code should be able to easily operate on the same session that TestStand does.  That would be the method I would use.  One thing to watch out for there is to make sure the VI stops using the references before TestStand runs the Stop VeriStand step.  That will close the references and cause problems.

If you want to have the application open its own references to VeriStand, that should work well too. 

If you keep getting errors, can you post some screenshots or code/sequences?  That would help narrow down what's going wrong.

Thanks,

Andrew

[Andy-C]

Hi wielro_1 and D4N!3L3,

We finally had a chance to finish fixing the RT sequence parameter issue. My apologies for the delay.

I just posted an updated version of the installer for VS 2015 SP1 which should allow you to run RT sequences without any parameters. We updated the code with the same change D4N!3L3 suggested.

https://decibel.ni.com/content/docs/DOC-40123

Please let us know if you encounter any problems using the updated version.

Thanks!

Andy

[nookie]

Is a release date for NI Veristand 2016 and TestStand 2016 established?

[j_dodek]

Hi ,

both were relased in august during NI-Week

regards

juergen

[wjrt]

Is there any news on an installer to support steps for Veristand 2016 in TestStand 2016?