How to generate a .seq file from XML using Building a Sequence Using API - XML.seq?

[john78912]

I’m trying to automatically generate a TestStand sequence (.seq) file based on step information defined in an Excel file.
My goal is to speed up the process of creating multiple repeated steps that follow a similar pattern — instead of manually adding each step one by one inside TestStand.

So far, I have successfully generated a .seq file from the NI example — the XML-to-sequence conversion itself works correctly.
However, I’m still having trouble generating steps that call LabVIEW VIs from my Excel (template) data.
Whenever I include a LabVIEW step definition in the Excel/converted XML, the generated sequence either fails to load the module or throws an error related to the adapter or module path.

Additionally, I created a Python-based converter (with the help of an AI tool) that automatically converts my Excel file into the XML format used by the example.

the version in use

• TestStand Version: 2017 (64-bit)

• LabVIEW Version: 2017 (64-bit)

I’m looking for guidance on the following:

1. What is the correct XML structure (tag hierarchy and attributes) required for LabVIEW VI call steps?

2. How should the Module and VI Path be represented in the XML for the LabVIEW adapter?

3. Is there a working example of an XML file that successfully generates a LabVIEW VI step using this method?

I’ve already confirmed that the example works for basic steps like MessagePopup or NumericLimitTest, but the problem occurs only when trying to generate LabVIEW VI call steps from the Excel template.

Any suggestions or example XMLs would be greatly appreciated.

Building a Sequence Using API - TestStand Expressions (XML) : 

https://www.ni.com/docs/ko-KR/bundle/teststand/page/building-a-sequence-using-api-teststand-xml.html...

[Oli_Wachno]

What do those errors say? Maybe this gives an indication....

Since the data structure behind a step can be pretty delicate, I would recommend a "re-engineering" approach: build that very LabVIEW step using SeqEdit and look at what the structure  should be. And what it actually is.

If you haven't already done so, make the hidden properties visible

Are you aware, that TestStand can also save .seq files as XML? 

The content is quite overwhelming, but also here: the data structure / settings needed may become more visible.

BTW... there was a GLA Summit presentation back in 2022(???)  about building an own editor based on this XML format.

Just wasn't able to find it on youtube at the moment.

No solution, but some further hints...

[john78912]

I’m currently using TestStand 2017, but I wasn’t able to find the option to save a sequence file as XML. Could you please advise how I can enable or access this feature?

I changed all the options in the “File Format Options” window to XML, but the sequence file is still not being saved in XML format when I save it. Do you know why this might be happening, or is there another setting I need to change?

[Oli_Wachno]

My oldest available version is 2019, but it shouldn't be any different: As most of the times, there are different options due to differnt contexts...

Station-default can be set 

If you want to change the setting on a per-file base

To avoid confusion: though saved as XML, the file will still be named a .seq file!

[john78912]

Thanks a lot, Oli_Wachno.
I followed your advice and finally managed to save the sequence file as XML.
I really appreciate your help — now it’s time to move on to the actual work.

I’m completely new to XML, so I’m not sure how far I’ll get 😊