VeriStand Steps for TestStand Feedback

[Andy-C]

Hi Peter,

Can you confirm whether you are using VeriStand 2015 or 2015 SP1?

Do all of the other VeriStand Step Types appear to work correctly?

Andy

[peterlakey]

I’m using 2015 SP1. 

I don’t know about all of the other types yet because I’ve only called two of them so far – Set Channel (which works) and Get Channel, which doesn’t.

Thanks,

[Yusuke.T]

Duplicated

[vravi]

Hi Andrew,

I am currently using TestStand 2016 and VeriStand 2016, if I upgrade to VeriStand 2017 and use the latest released version of VeriStand custom steps 17.0.5.0, will that affect the previously created sequences in 2016. Will I be able to use the sequences as it is or will there be any updation needed on the sequences.

Ravi

[Andy-C]

Ravi,

That's a great question. 

There are two big things that will likely need to be changed in your Sequence Files. 

First, the Type Version (e.g. 17.0.5.0) of all the VeriStand Steps in each of your Sequence Files will need to be updated. TestStand can usually do this automatically on first load of the sequence file after the new Step Types are installed. We have tried to maintain the same interface for each Step between versions, but any modifications to a Step Type made by users locally (e.g. using the Type Palettes configuration tab to add a property to a Step Type) will not be included in the versions available on the community page. 

So although we have tried to avoid making any breaking changes between versions, it is always recommended to backup your Sequence Files before upgrading the VeriStand Custom Step Types because they will be mutated by TestStand to the new version before execution. 

Second, all file paths used by the VeriStand Step Types are currently stored statically. So, if your file paths are dependent on VeriStand 2016 directories or will be in a different root directory then you will need to update them in each Sequence File. File paths can be updated either through a particular Step's GUI or directly through the Step properties dialog.

Updating the Step Types version via Automatic Type Conflict Resolution dialog:

After installing the 17.0.5.0 version TestStand should prompt you to update the VeriStand Step Types version in all the VeriStand steps in each of your Sequence files. You should see a Type Conflict Resolution dialog when you try to open your sequence for the first time with the new Step Types version installed.  If you do not see this dialog you may need to disable Automatic Type Conflict Resolution in your TestStand Station Options. 

I'm attaching two screenshots to show the Type Conflict Resolution dialog options. 

I hope this helps!

Andy

[vravi]

Hi Andy,

Thanks for the reply. I will share my experience of upgrading the VeriStand once i complete. I also want to check about upgrading from TestStand 2016 to TestStand 2016 SP1. Can I use the version 17.0.5.0 with TestStand 2016 SP1.

Regards,

Ravi Vijayarajan

[Andy-C]

Ravi,

The SP-version of TestStand shouldn't make any different for these Step Types. The TestStand 2016 version of the Step Types should work with either TestStand 2016 or TestStand 2016 SP1. The same goes for TestStand 2014 and TestStand 2014 SP1. 

Andy

[MaWei]

Hi,

I'm having troubles with Teststand&Veristand 2016 (veristand2016-teststand2016-x86-16.0.6.0).

I'd like to call a Stimulus Profile using the "Run Stimulus Profile" step. When I try to configure the step (in fact, all the steps having the "Configure" button), the attached error message pops up.

I already tried reinstalling Teststand and the VeriStand steps for Teststand but to no avail.

Regards,

MaWei

[Andy-C]

Hi MaWei,

I found a problem in the TestStand 2016 installers which would require you to have TestStand 2016 SP1 installed.

I have corrected the problem and updated the TS 2016 installers. They should now work with TestStand 2016 or 2016 SP1. 

Please let us know if you continue to encounter problems after reinstalling with the updated version from the community page.

Our apologies for the inconvenience.

Best,

Andy

[MaWei]

Hi Andy,

thanks a lot! The new version works for me.

Unfortunately, there seems to be another issue with the steps. I'd like to use them to run multiple stimulus profiles sequentially.

I have a for each loop that iterates over an array of paths. I then want to pass the current element to the run stimulus profile step. As soon as I reopen the "configure stimulus profile" dialog, the expression (in my case Locals.CurrentStimProfPath) is enclosed in quotation marks.

I suspect, that this causes my sequence to fail with message

Report

Run Stimulus Profile	Error
TestResults/Data
Path:	''
Error Message:	Error executing substep 'Run Stimulus Profile'. Konstruktorknoten Error creating instance of StimulusProfile in assembly NationalInstruments.VeriStand.StimulusProfileDefinitionApi.StimulusProfile, NationalInstruments.VeriStand.RealTimeSequenceDefinitionApi, Version=2016.0.0.0, Culture=neutral, PublicKeyToken=a6d690c380daa308, (System.IO.FileNotFoundException: File does not exist) System.IO.FileNotFoundException in RTSequenceVIs.lvlibp:Run Stimulus Profile.vi->RTSequenceVIs.lvlibp:Run Stimulus Profile.vi.ProxyCaller LabVIEW: In einer externen Assembly ist ein .NET-Ausnahmefehler aufgetreten. Für Hinweise zum Beheben dieses Fehlers kopieren Sie den folgenden Ausnahmefehler (fett gedruckt) und suchen Sie auf der Website des Microsoft Developer Networks (MSDN) oder im Internet nach einer möglichen Erklärung.[Error Code: 1172]

Am I doing something wrong here or is there another way to pass a variable as Stimulus Profile Path?

Regards,

MaWei