[LV -> TS] How to execute a SEQ file, get the result (PASS/FAIL) and the report file ?

[Kochise]

Hello j_dodek,

you might find a pre(c/v)ious attempt to use the old sequencer with

TS in this old post :

http://forums.ni.com/t5/NI-TestStand/Enqueue-Teststand-cluster-to-Labview-return-a-cluster-by/m-p/30...

Just remember that what I'm asking for is a VI

interface to TS that permit to transmit a SEQ

file to run, a UUT serial, get the result and the

report covers 99.8% of the cases someone

into unit testing would require.

That TS doesn't provide such a simple and

elementary interface is beyond comprehension.

The operator is not always to scan a UUT serial

into a dialog box, this can be provided by a

serial code server, hence the API interface

allowing to provide an optional UUT serial.

I can stand that TS allows very complex testing

scenario through the use of very complex

systems (sequencial or parallel batch) but

why rendering the most simple procedure

into an obnoxious development implying

data transfert and message passing.

It's been more than 6 months now that I just

want to try doing simple things with TS,

starting by communicating clusters into

containers (and vice versa) only to discover

that it cannot works.

Then using TS as a simple test engine

without all the fancy stuff around but again

it seems to be too simple, TS requiring

quite a complex testing allegory using

models and things just to execute steps

just to conclude if the unit is good or not.

I am frustrated that it takes so long to get

things done using the KISS principle, just

because NI wants to show some muscles.

Yeah, the old sequencer was quite enough,

it would just have required to add the

expected functionnalities, but I'm the

contractor, I was requested to switch from

the old sequencer to TS.

Something that would have required a

simple API wrapping reveals to be rather

difficult, not speaking about deployment

and relative path resolution.

But I digress...

EDIT : thanks for the 4th version of your C#

implementation. Could it be possible to get

the serial included in the report file name,

and also provide an optional report path

for the report generation ?

I do a ReleaseSequenceFileEx, but you

don't, is it because it is automatically handled

by the .Net GC ?

David Koch

[j_dodek]

Hi David

Sorry that i am not going to answer stuff from old thread, because i have to do a job as you, too.

Maybe the blue ones...

But your questions here:

UUT to reportfilename, You dont have to care in your code! It is a simple configuration of your station. Just enable it!

If using TS2014 take care use the right version 32 or 64bit (My Example is using 64. Normally i am using 32, so i was just wondering why missing

but great! working on both versions as well. This effort here will help me in future tasks!!)

The release stuff:

You are right. I have just forgotten it..

Regards

Juergen

[Kochise]

Thanks, considering the informations you provided

me with, here's a modified version of the LV runner

that still requires some clean-up to do by removing

the dependencies to the 'RunState.Root.xxx' stuff 🙂

David Koch

[j_dodek]

Hi David,

well LV is not my first choice programming language.

So it is a little bit hard to understand whats going on.

Just a few things i wonder:

why do you need RunState.Roots stuff?

stuff between  NewExecution and WaitForEndEx ? Looking really Strange! but when playing with true/false

there is a cominbation everything is "empty"

You are creating your report path as well, too. Sorry understand that, even if comments are not french.

I would recommend to remove all that.

Try to get LV running in a way like my example.

That means configuring the ReportPath in TestStand via SequenceEditor for your maschine.

if this is running. Let start disscussion again if it is still necessary to define ResultOptions via LV

Please tell me which TS Version you are using and which model "Type" the legacy or the plug-in one.

Regards

Juergen

[Kochise]

Hello again 🙂 Well, basically I'd like to have to do

with TS as little as possible, hence configure and

set things from LV would be perfect.

I'm not the one who chose the LV path, I'm a text

coder as well, but the legacy code here was in LV.

I'll do some clean-up and testing and get you

informed of the results.

EDIT : LV 2013 and TS 2014

David Koch

[Kochise · Accepted solution]

Here we go, final release of the VI, it seems to work,

I still have some trouble configuring 'ReportOptions'

on the fly to keep only errors in the report.

David Koch

[Kochise]

In order to work correctly, here are the 'Cfg' files

you need to place in the following folder on your

development or deployment machine :

c:\ProgramData\National Instruments\TestStand 2014 (32-bit)\Cfg\

David Koch

[j_dodek]

Hi

I was on holyday.

Task still open?

Juergen