Export Limits for Multiple Sequences in the Same Sequence File for TS3.0

[Morten_Pedersen]

Hi,

I am using TestStand 3.0 to a test application. Because we want to have our limits in a csv-file I have tried to use the Import/Export tools in TS. But this application only supports to export limits for the selected sequence (e.g. main, or subseq1) at a time. This makes it a pretty hard job to export limits from 30 test sequences. What I need is a possibility to export my limits from �all sequences� in my seq-file.

I have found an article on NI Dev. Zone about �Export Limits for Multiple Sequences in the Same Sequence File (TestStand 1.0.x)�.
http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3D9CB56A4E034080020E74861&p_node=DZ52236&p_submitted=N&p_rank=&p_answer=&p_sourc
e=External

I have tried to use this code but because it�s for TS 1.0.2 the limits from my multi num test step and my custom steptypes isn�t exported. So that doesn�t fulfill my needs.

Is there an updated version with �all sequences� added to TS 3.0? Is there other good solutions to my problem out there?

Best Regards,

Morten Pedersen
CIM Industrial Systems A/S
Denmark

[James_Grey]

It is likely that the next release of TestStand will provide the ability to import/export from all sequences in a file at once.

[David Mc]

Hello Marcus,

For TestStand 3.0, you could modify the source code for the import/export properties tool in "C:\Program Files\National Instruments\TestStand 3.0\Components\NI\StepTypes\Database", but I know that would be a lot of work.

David Mc.
NI Applications Engineer

[Morten_Pedersen]

Hi James,

Have you some knowledge about that is feature should be included in the next version?

Youre right. It wold be likely that the next release has this ability. But the scope of the next TestStand is 6-9 months. That's too long time to wait because my application need to be ready in the next 2 weeks... I have hoped that NI already has/or could made a solution like the one to 1.0.2 (see link in root) and then they could include it in the next version.

Best Regards,

Morten Pedersen
CIM Industrial Systems A/S
Denmark

[Morten_Pedersen]

Hi David Mc,

Thanks for your reply. I have already considered this solution because the source code is added in the folder described in your reply. But that is not a good solution. It will cost me a lot of time to establish the toolchain, reverse engineer the source code, make the implementations and build a new dll (most off these is already knowledge by NI). And when NI make future releases of TestStand I have some merge work to do every time NI have made some changes in the files I have changed.

But as I write above: I have hoped that NI already has/or could made a solution like the one to 1.0.2 (see link in root) to me. And then they could include it in the next version.

I don't think I am the only one in the TestStand world that ne
ed this feature.

Best regards,

Morten Pedersen
CIM Industrial Systems A/S
Denmark