Custom VeriStand Steps for TestStand Feedback

[TylerJ]

Kevin,

I didn't expect VS 2014 to be out so soon.  Thanks for the info, and I'll be looking out for those custom steps.

Thanks,

Tyler

[Kevin_F]

Hey Jeremy,

It looks like there is some linking that got broken when just using just the run-time engine (so LabVIEW development is required on the machine running the steps currently). We have another version of the steps coming out in the next week or so where we are fixing this.

[ose88]

Hi Kevin,

I would like to know if there is any documentation about the communication time between TestStand and VeriStand when you use this add-on? I'm using TestStand 2013 and VeriStand 2013.

Thanks for your help.

Regards.

[Kevin_F]

Do you mean the latency of the communication, or if it is deterministic, or something else? The add-on uses the .NET Client API under the hood so you seem the same timing behaviors as with that so things will not happen deterministically unless you are downloading an entire RT Sequence to the target.

[ose88]

Kevin,

I mean if there is some documentation about the latency of the communication.

Thanks for your help.

[ElectricWraith]

EDIT: This is in response to Dan A's post, I thought the reply was going to include the quote, but it didn't.

I'm getting unhandled exception errors like this as well, but it doesn't happen on every RT sequence. Some of them will load in the Config dialog just fine, and all the fields are populated. I've had this happen on one machine that's running VS 2012, TS 2012, and LV 2012 and also I'm my laptop which is running 2013 version of everything. Any ideas?

[Kevin_F]

Hey ElectricWraith,

Can you post a screenshot of the error, your teststand sequence and your RT sequence?  I also just posted a new version of the 2013 and 2013 SP1 steps that some other folks have been working on. It addresses some of the issues with that RT sequence dialog.

[ElectricWraith]

I'll try the latest version of the steps (if I don't have them already) for 2013, but I really need to get it working in 2012. I'll try to grab a couple screenshots if I can, I need to make sure there's nothing proprietary in them first.

At first I thought this might be caused by some malformed XML is the RT sequence, I'm generating them programmatically. But, after I got the same error from a shipping example I realized that wasn't the case. Another interesting point is that I used some of the exact same steps from a sequence that threw the error in a much smaller sequence, no error. Is there a maximum number of steps?

[Kevin_F]

Shouldn't be a maximum number of steps. I just posted the new 2013 version this morning. You want the _v300 one.

[ElectricWraith]

OK, these are from my lab workstation, the one that's running all the 2012 versions.

Here'e the TS sequence, as you can see, it's dirt simple:

Here the config dialog from Open & Deploy RT Sequence after I've selected the sequence:

Note that none of the steps are populated. If I start populating them manually, weird things start happening, like slow, stuttering auto-scrolling, graphical glitching in the dialog (looks like all the steps are accordioning together), etc.

Here's the error dialog I get if I click the OK button:

I can post the entire text of the exception error, but it's rather lengthy.

Here's a partial screenshot of the RT sequence, if you want to see the whole thing I'll have to send it to you.

There are a lot of CAN commands in it and I'm not comfortable putting them out there for public viewing.

Let me know if you need anything else, and thanks a lot for the rapid response!