VeriStand Steps for TestStand Feedback

[Andy-C]

Yep - that looks fine to me.

Another quick test would be to create a simple sequence to open the Engine Demo shipping example and run one of the provided example RT sequences.

Otherwise feel free to attach your TestStand and VeriStand RT sequence files here and we can take a look.

Best,

Andy

[WMohsen]

Hi Andy,

When executing a Teststand Sequence developed in a different computer, "Start VS Logging" step does not work.

The attached images shows the details of the error.

Things we have tried to avoid this issues:

1. Recreating the "Veristand Initialize" Step

2. Recreating the "Start VS Logging" Step

Thank you,

[Andy-C]

Hi WMohsen,

I'm not completely sure about this problem, but I'm wondering if you may have different vesions of the VeriStand Custom Step Types installed on each machine.

Can you let us know which versions of VeriStand and TestStand are installed on each PC?

Best,

Andy

[WMohsen]

Thanks Andy-C for the quick response.

I am using Veristand Custom Steps version 2.3.1.

I've updated the Veristand Custom Steps in my PC to match the version used in the development PC.

The problem is solved!

Thank you again,

[Languanxue]

Hi Andy,

When I use "Start VS Logging" save faw channels(>500 chs) data. It does not work. If I just save about 300 chs data, It works fine. I want to know whether there is a limit of channels?

[Andy-C]

Hi Languanxue,

There is a setting in the System Definition for maximum streamed channels.

Have you tried changing this value?

Best,

Andy

[wielro_1]

Hello,

I have the sampe problems like at posting (No 164. from 08.08.2016 16:06 by swbpnole).

When I try to use a RT Sequence Step, e. g. RT Sequence Numeric Limit Test then I get the following error:

Error:                                    Error executing substep 'Run RT Sequence Numeric Limit Test'.

Konstruktorknoten System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. System.NullReferenceException in RTSequenceVIs.lvlibp:NI_VS Sequence Execution Interface.lvlib:Create Sequence Call.vi->RTSequenceVIs.lvlibp:Run RT Sequence Numeric Limit Test.vi->RTSequenceVIs.lvlibp:Run RT Sequence Numeric Limit Test.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,                     User-defined error code.               ]

I am running:

Windows 7 64 bit

TestStand 2014 SP1 (32bit)

NI VeriStand 2015 SP1 (32bit)

Installed version of  NI VeriStand Add-on (VeriStand Steps for TestStand) = TS 2014 SP1 32b VS 2015 SP1.msi

The Engine Demo shipping example runs with of the provided example RT sequences without any errors.

My RealTimeSequence is without any parameters used, only returns a static double value.

At the TestStandSequence I am only check if the numeric limit is between the limits.

I hope someone could help me what is going wrong.

[User002]

weilro_1,

Those versions look correct.  And if you can run the examples, it has to be something more specific.  Sadly, the error message in this case isn't very helpful.  Can you post the TestStand and RT sequences?  Or at least some good screenshots of them?

Thanks,

Andrew

[wielro_1]

Hello Andrew,

here I add the screenshots of TestStand and RT sequences.

When I run the TestStand sequence without the step RT Sequence Numeric Limit Test  then it works without any error,

that means initialisation, running of VeriStand project incl. VS logging, undeploy and close of the project at the end of the TestStand sequence.

[wielro_1]

Hello Andrew,

we have found out the reason for this behaviour themselves. For every step to run a real-time sequence (RT Sequence Numeric Limit Test, RT Sequence Pass Fail Test, RT Sequence Action) you have to use at least one parameter. Real Time Sequences without any parameter implemented will cause such a behavior. I think that is not documented in the rudimentary documentation of this VeriStand Add-on.