VeriStand Steps for TestStand Feedback

[OlegS]

Hi Andy,

my customer is using TS2016 and VeriStand 2016 and needs the VeriStand Steps for TestStand for this two current versions.

 Do you know when they will be available at the Community page for download?

Kind Regards,

Oleg, M.Eng | Staff Applications Engineering | National Instruments | NIG |

[kent.wedeking]

VS2016/TS2016 is available for download now.  Thanks Andy and Andy.

Next question ... I'm still working in VS2014/TS2013.  Has anyone else been unable to drive the ProjectPath input from a variable?  When I press "Ok", go back to TestStand, and then come back in, Locals.SysDefPath has been converted to "Locals.SysDefPath" as a string.

Before and after are attached.  I'm driving my project path from an INI file everyewhere else in my sequence.  I'd like to do it here as well.  I have NOT tested this in TS2016/VS2016 yet.

[Russell_G.]

My customer currently has TS 2014 SP1 and VS 2014.  I didn't see that combination as one of the installer options.  Do we need to build a new installer for this combination?  Or will an existing one work?  Thanks!

[rajamodol]

Hi,

I want to upgrade my test system to version 2016. I have installed LabVIEW 2016, Veristand 2016, and Teststand 2016, and NI VeriStand Add-on: VeriStand Steps for TestStand (TS2016 32b VS2016).

Here is the issue:
1. Open Teststand 2016
2. Call Veristand 2016 with step "Start Veristand" as shown in the picture.

3. Veristand 2016 is opened, and Teststand keep hanging.

4. There is no way to push sequence to stop unless:

    a. Close Veristand 2016 and open Veristand 2015. Teststand will be executed and terminated properly.

    b. Do not close Veristand 2016 and open Veristand 2015. Teststand will be executed and terminated properly but with veristand error.

This issue is not occured on Veristand 2015, in relation with LabVIEW 2015 and Teststand 2014.

Anyone can help? If we can't solve this issue, upgrading test system from version 2015 to version 2016 will be useless.

Thanks,

Rajamodol

[Andy-C]

Hi Rajamodol,

I ran a quick test and with TS / VS 2016 the 'Start VeriStand' Step did work as expected on my system after I updated the VSInstallPath property of the Step. I haven't tried this with previous versions of VS installed on the same machine.

In general the 'Low-Level' Advanced Step Types haven't been updated in awhile and haven't been tested with the newest versions of TestStand and VeriStand. They should still work, however. 

Do the primary, high-level Step Types (e.g. Initialize VeriStand) work in your environment?

Andy

[SajK]

Hi HandyAndy,

Installed VeriStand 2016 Adapter for TestStand 2016 (TS 2016 32b VS 2016.zip). On running test sequence (in TS2016), I am getting the following error with 'Set Alarm State' step type. Original test sequence was developed using VS 2013 & TS 2013 and just upgraded to 2016. Also getting error with 'Get Alarm State'. The Host PC has both 2013 & 2016 Versions of TS and VS. Other steps are working OK. Can you help?

Thanks

SajK

--------

Details: 

Error executing substep 'SetAlarmState'.

An exception occurred inside the call to .NET member 'SetAlarmState':

NationalInstruments.VeriStand.VeriStandException: Could not connect to the VeriStand server. Make sure you have the correct address to the gateway, the gateway is running, and any firewalls are configured correctly before attempting to connect. ---> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/NI/VeriStand_Gateway/2013/AlarmServer that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/NI/VeriStand_Gateway/2013/AlarmServer' could not be found on your local machine.

   --- End of inner exception stack trace ---

 Server stack trace:

   at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri, IPipeTransportFactorySettings transportFactorySettings)

   at System.ServiceModel.Channels.NamedPipeConnectionPoolRegistry.NamedPipeConnectionPool.GetPoolKey(EndpointAddress address, Uri via)

   at System.ServiceModel.Channels.CommunicationPool`2.TakeConnection(EndpointAddress address, Uri via, TimeSpan timeout, TKey& key)

   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)

   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)

   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)

   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

   at System.ServiceModel.Channels.CommunicationObject.Open()

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at System.ServiceModel.ICommunicationObject.Open()

   at NationalInstruments.VeriStand.ClientAPI.ClientWCFBase`1.MakeConnection()

   --- End of inner exception stack trace ---

   at NationalInstruments.VeriStand.ClientAPI.AlarmImpl..ctor(String name, String address)

   at NationalInstruments.VeriStand.ClientAPI.Factory.GetIAlarm(String name)

   at OpenWorkspaceDialog.VSDialogs.SetAlarmState(SequenceContext seqContext)

----------------------------------------

Error Code: -2146233088; User-defined error code.

----------------------------------------

[Andy-C]

Hi SajK,

So far I haven't been able to reproduce this behavior here. I created a sequence to Get/Set Alarms in TS 2013. I then ran the sequence in 2016 and did not see any issues. 

Unfortunately the VeriStand Custom Step Types do not currently support having multiple versions of the Steps installed simultaneously. 

Did you uninstall the previous version of the Steps through the Control Panel before using the 2016 installer?

Thanks and let us know.

Andy

[SajK]

Hi Andy,

Thank you for your reply. Did you use VS 2016 adapter for TS 2016 in your experiment?

I did my previous tests with both VS 2013 and VS2016 adapter installed on the same PC. Today, I uninstalled VS 2013 adapter for TS 2013. Also uninstalled VeriStand 2013 from PC. Created a new VeriStand 2016 project and NI TestStand 2016 sequence (used TS 2016 32b VS 2016 adapter). Now I am getting error even during configuring set alarm state step (screen shot attached). Am I doing something wrong?

Thanks

SajK

[Andy-C]

Hello SajK,

I used the VS2016 / TS2016 Step Types in my test here. 

I would try uninstalling the 2016 Step Types through the Control Panel and then reinstalling the 2016 Step Types again.

Let me know if that doesn't fix things. I'm setting up a test machine here so I can give this a try myself.

Thanks!

Andy

[SajK]

Hello Andy,

I did try reinstalling VS 2016 adapter steps, but it did not help. However if I install VeriStand 2013 back, I am not getting error during configuration of set alarm state step. Still it will error during runtime (same error in my 1st post).

Thanks

SajK