Is there a known problem when debugging Labwindows DLL used as Teststand Code module ( using the Labwindows CVI Adapter)? My setup includes to powersupplies with IVI instrument drivers ( Agilent 6032A and and E3634 A) a a few other instruments with non-IVI instruments drivers. When start CVI, load the dll project and then start the Teststand Sequence editor as program to be debugged an then step into the C-Code it looks like there is process that watches both powersupplies and tries to reset them again if I access them from my C code through the instrument driver. There is no such effect with the non-IVI instruments and also if I run the code outside the debugger there is no such effect. Any Ideas whats going wrong here ?

Markus, to my knowledge, one would not start CVI prior to the TestStand Sequence Editor for debugging purposes. CVI is launched automatically when needed. Keeping this in mind, I can imagine that the instrument handle is reset after each step when having an IVI project open in CVI and using CVI parallely to debug a DLL. So please try the following: --8<--------------------------- 1. Open the sequence file. 2. Complete the following steps to enable the LabWindows/CVI Adapter to execute steps in an external instance of LabWindows/CVI. ❑ Select Configure»Adapters. ❑ Select the LabWindows/CVI Adapter. ❑ Click Configure. ❑ Enable the Execute Steps in an External Instance of CVI option. ❑ Click OK to close the LabWindows/CVI Adapter Configuration dialog box. ❑ In the Warning dialog box, click OK to unload all modules. ❑ Click Done in the Adapter Configuration dialog box. 3. Place a breakpoint. ❑ Click to the left of one of your CVI code module sequence steps to place a breakpoint at the step. 4. Compile a debuggable DLL. ❑ Select the step with the set breakpoint. ❑ Click Edit Code in the Module tab. ❑ In LabWindows/CVI, select Build»Configuration and verify that Debug is enabled. ❑ Select Build»Create Debuggable Dynamic Link Library to compile the debuggable DLL. ❑ Click OK when prompted that the files were created successfully. ❑ Close LabWindows/CVI.5. Execute the sequence in TestStand. ❑ Select Execute»Single Pass. ❑ When the execution pauses, click Step Into to step into the LabWindows/CVI code module. The LabWindows/CVI Debugging window launches, where you can use the LabWindows/CVI debugging tools, Watch window, and Variable window to debug code. --8<---------------------------Are your power supplies then reset, too?Best regards,Sebastian

LabWindows/CVI

Debugging Labwindows dll in teststand with CVI 9.1.1

Solved!

Author

Did I undertand you right: When using an "external instance of CVI" for debugging Teststand starts CVI, CVI starts then the DLL code , which calls the init-function of the IVI driver which spawns the IVI session and therefore is no alien process in IVIs point of view. But when CVI starts Teststand, which starts then the DLL code then CVI is considered as alien process because it didn't start the DLL.

My example also shows that IVIs procedure to reinitialize fails, if the instrument doesn't understand *IDN?.