Is it possible to debug VIs being run on a deployed TS System?

[mc_vibraphone]

I have a VI that is intermittently wandering off into left field to look at all the dandelions. It's being run from TestStand (base deployment engine) on a deployed system. I'd like to debug it from my development box.

Is there a way, perhaps along the same lines as the LV App Builder 'Enable debugging' option, to hook my development system into the VI as it's executing on the deployed system?

I've dug around a bit, and keep finding the notes on App Builder, but haven't seen a way to do it through TS.

Thanks for any help

Tom McManus

Message Edited by Thomas McManus on 07-13-2009 02:11 PM

[Kelly_R]

Hi  Tom,

Unfortunately there is no remote debugging option available with TestStand.  An option is to deactivate your license on the development machine and activate it on the deployment machine to perform the debugging.  You can also look into a TestStand Debug Deployment Environment License.

[mc_vibraphone]

Hi Kelly - thanks for the reply.

Just to clarify, because you mentioning a TS debug deployment makes me wonder if we're talking about different things: there's no way to attach to a VI that TS has called remotely, then?

I'm not looking for, say, a remote Sequence Editor, but the ability to attach my LV dev environment to a remote VI that TS has called.

Thanks again for your time

Tom McManus

[Kelly_R]

Hi Tom,

You will not be able to remotely access a VI that has been called by TestStand.   You can, however, create a debuggable DLL (with the problematic VI), and remotely connect to that.  To do this, you will need to rebuild your VI as a shared library and enable debugging on the Advanced Tab of the Application Builder.  Once this is complete, you will need to change the step type to C/C++ DLL.  You will also now need to manually configure your parameters for this step.  Lastly, you will need to re-deploy your system.  Once the the TestStand Application is running, you can go to Operate»Debug Application or Shared Library from the LabVIEW Getting Started Window on the development machine.  From here you can access the shared library that is running.

The other options you have, as I mentioned, are to bring the VI over to the development machine and debug there, activate the full version of TestStand on the deployment computer, or purchase a debug-deployment license.  I hope this was helpful!