Sequence File Translator Example

[TobyD]

When I think of recursion I would assume that Vidula is referring to the ability to call another custom sequence file (text based LVTF) from the main sequence file and have the translator translate it and treat it like a normal subsequence. However, so far I have not been able to make this work. TestStand locks up whenever I try it (window dims and cursor remains busy).

Even if I create a normal .seq file that contains a step to call a .lvtf subsequence the program locks up. It seems like something is broken, or perhaps the translation functionality is only available when you choose "open sequence file" from the menu.

[Anand_Jain]

Toby,

I would like to clarify your statement.
If I follow the following steps, SeqEdit will hang. Is that correct?

1. Open a new sequence File
2. In the main sequence of that sequence file you drop a sequence call step.
3. In that sequence call step you specify to call a custom sequence file.
4. When you execute MainSequence, SeqEdit locks up.

Regards
Anand Jain
National Instruments

[TobyD]

Yes. That is exactly right and much easier to follow than my description

[TobyD]

I should also mention that I am running TS 4.1 Beta on Windows Vista. I have not tried this on 4.01/XP.

 - Sorry for the double post - I just found the edit button

Message Edited by TobyD on 03-03-2008 09:21 AM

[V_T_S]

To be more specific:

1st file: sample1.lvtf

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

Line 1: LabVIEW Sample Test Description

File:4.0.0.0:4.0.0.6

Line 2: Display msg to User,MsgBox,,MessageExpr:string="This example sequence file is stored on disk in text format. The source code for the translator plug-in which converts this format into a sequence file is located in the same directory as this file.The format of this file is documented in TextTranslateToSequenceFile.vi",TitleExpr:string="Sequence File Translators"

Line 3: Display

Graph,DisplayGraph,RMSValue:number=RMSValue,ACValue:number=2

Line 4: sample2.lvtf

Line 5: Display

Graph,DisplayGraph,RMSValue:number=RMSValue,ACValue:number=3

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

2nd file: sample2.lvtf

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

Line 1: LabVIEW Sample Test Description

File:4.0.0.0:4.0.0.6

Line 2: Display

Graph,DisplayGraph,RMSValue:number=RMSValue,ACValue:number=5.

Execution in TestStand:

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

When TestStand opens the file sample1.lvtf, Line 4 should be replaced with another sequence (sequence call) and at the same time the sample2.lvtf sequence should also be generated.

Notes:

1. sample1 and sample2.lvtf files are in the same folder.

2. sample2.lvtf file should automatically be opened.

I tried many work arounds, and I was able to make it work for 1 sequence, but the solution which I have I not feasible when I want to call 100s of sequences automatically.

Another thing is these sequences sample2.lvtf can be executed only at run time, but one cannot see the contents of that sequence.

-Vidula

[Anand_Jain]

Toby,

I have filed a bug report about this issue and will update you once I have more information.
You can also report beta issues from the beta website.

Regards
Anand Jain
National Instruments

[TobyD]

I have been playing with this some more and it looks like it only crashes teststand if I set the "Sequence Call" step to "Preload when execution begins" under Run Options.

Both "Preload when opening sequence file" and "Load Dynamicaly" seem to work as expected.

[Josh_W]

Vidula,

In response to the four questions that you asked on the previous page:

1. The ActiveX calls that do the dynamic translation of the LVTF files.

The sequence file translator framework works for any programming language via standard fuction prototypes.  If you would like information about what each function is supposed to implement, please see the TestStand Reference Manual, Chapter 15 for more information.  If you are asking about the TestStand ActiveX API calls you might use in the process of creating your translator, please see the TestStand API Help

2. Something which will assist me in my application architecture.

What specific information are you looking for?  There are many whitepapers regarding TestStand: TestStand Style, Test Management Software Developers Guide, Process Model Theory, Software Deployment Strategies, Benefits of Parallel Testing, Guide to Effective Test Software Development with NI TestStand, Best Practices with TestStand Types.  I found all of these by doing a search on NI.com for TestStand and then browsing Tutorials.  Of course, the Reference Manual is going to have the most detailed information.

3. Recursion within the text to sequence file translator.

I think this has been addressed in the comments above.

4. Customizing the teststand reports.

Once again, what specific information are you looking for?  Please see Chapter 6 of the Reference Manual for an overview of TestStand reporting.  Also try this link: Report Generation Explained, and these examples: Generating Two Reports In TestStand, Modifying TestStand Report Path and Filename, Expanding the XML Report Failure Chain to Include all Failures.

[V_T_S]

Josh,

There is another example to Modifying the Failure Chain of the HTML Report to Include All Failed Steps it is at http://zone.ni.com/devzone/cda/tut/p/id/4563

I opened the service request back in Oct 2007 and worked with NI Application Engg. for nearly 3 weeks; at the end he found that; that document is developed for TestStand 2.0, and is not forward compatible.

I am still waiting for NI to update the document. (Reference#7173708)

After you sent the link for Expanding the XML Report Failure Chain to Include all Failures I tried that example but look like that example is also not compatible for 4.0 (at least I am not getting the result), today I opened another service request (Reference#7189207)

If developer zone can mention in which version these examples were developed and whether they are compatible with current versions or not then it will be of real help to us.

Thanks,

Vidula

[V_T_S]

Toby did you go any further with recursion? Is it working for you?

I am still looking for a better way to make it work.

My goals are

Goal 1: File1.lvtf calls File2.lvtf

Goal 2: File2.lvtf calls File3.lvtf

Goal 3: File4.lvtf calls File5.lvtf and File6.lvtf and so on…

I achieved goal 1 but still struggling with goal 2 and 3.

 

Regards, 

Vidula