NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Debug TestStand sequence inside LabWindows DLL

I have a TestStand sequence which uses a DLL made with LabWindows. For debug, I need to run the sequence step by step, and I want to go inside the functions of the DLL to run step by step. Is it possible ? How to "connect" TestStand and LabWindows ?

 

Thanks for your help !

0 Kudos
Message 1 of 7
(4,252 Views)

This is possible, and fairly easy to do. One way to do this is to launch TestStand sequence editor from within CVI. Open your DLL project in CVI and set the configuration to Debug. Then in the Run >> Specify External Process and set the Program Name field to "c:\Program Files\National Instruments\TestStand 4.1\Bin\SeqEdit.exe" or whatever version of TestStand you're using. Then Select Run >> Debug SeqEdit.exe.

 

Open your TestStand Sequence from the editor, set the breakpoint on your DLL call, and use the Step Into function of TestStand to step into the DLL source code.

 

That's it.

 

-Jack

Message 2 of 7
(4,248 Views)

Hi SFL,

 

This can be done by:

 

1). open the DLL project in LabWindows

2). select "Run->Specify External Process..." and set TestStand (seqedit.exe)

3). click "Run->Debug SeqEdit.exe"

 

This will execute TestStand and you should be able to step into your DLL functions.

Charlie Rodway | Principal Software Engineer | Certified TestStand Architect (CTA)

Computer Controlled Solutions Ltd | NI Silver Alliance Partner | GDevCon#1 Sponsor

0 Kudos
Message 3 of 7
(4,245 Views)

Thanks for your help but it does not work.

 

1- I open the DLL project in LabWindows => OK

2- I Run/Specify External Process and set seqedit.exe => OK

3- I Run/Debug SeqEdit.exe => OK, TestStand launches

4- I open my sequence in TestStand, set a breakpoint on the DLL call => OK

5- I execute the sequence => OK, it stop at the breakpoint

6- I use Step Into function and it does not work, I do not go inside the DLL => KO

 

Have you an idea of what happens ?

0 Kudos
Message 4 of 7
(4,211 Views)

Make sure that your TestStand sequence is calling the debug version of your DLL, which in CVI may be built to a different location than the release DLL, or with a different name (*_dbg.dll).

 

-Jack

Message Edited by Capt. Jack on 11-05-2009 11:07 AM
0 Kudos
Message 5 of 7
(4,203 Views)
hello,

If I correctly understood your problem, here is the procedure

the DLL must be compiled in debug mode (not in release mode)
In TestStand menu , configure -> adapter, choose Labwindows and click configure.
choose "Execute Steps in an Proceeding of external CVI" and click OK

During Teststand execution, a window CVI (TSCVIRUN) will open with the code of your DLL to debug and you be able debug
0 Kudos
Message 6 of 7
(4,197 Views)
I believe you must also have a braekpoint set in your code
0 Kudos
Message 7 of 7
(4,194 Views)