Configuring VI Server for LabVIEW Run-Time Engine Adapter

[LVB]

I would like to connect to use the desktop execution trace toolkit to debug LabVIEW code modules using the Run-Time Engine Adapter in TestStand.  How can I configure VI server when using LabVIEW VI's within the LabVIEW Run-Time Engine Adapter for TestStand?

[Frank_L.]

Hi LVB,

Thanks for posting in the NI Discussion Forums!

I haven't seen any precedent for trying to debug LabVIEW code modules using just the LabVIEW Run-Time Engine. However, I can try to do more research to see if this is possible.

[SerJames]

Hi LVB,

If you would like to debug your LabVIEW code you will need to use the Development Engine adapter setting. The Run-Time Engine setting does not support editing or debugging capabilities. The Run-Time Engine is intended for deployment to Test Stations that have no need to edit or debug and only execute the program.

For reference, you can read more about the switching of environments and what capabilities they provide here:

http://digital.ni.com/public.nsf/allkb/CE431BA1A3B61953862573540078DAD8

Regards,

[LVB]

---

@SerJames wrote:

Hi LVB,

If you would like to debug your LabVIEW code you will need to use the Development Engine adapter setting. The Run-Time Engine setting does not support editing or debugging capabilities. The Run-Time Engine is intended for deployment to Test Stations that have no need to edit or debug and only execute the program. 

---

James,

Although the Run-Time engine does not allow editing code, it does support debugging.  There is a need to debug run-time code when it works within the Development adapter but does not work in run-time.  This can be done using VI server and the Desktop Execution Trace Toolkit.  A LabVIEW executable can be configured for VI server using the following link:

http://digital.ni.com/public.nsf/allkb/DCFB5E8D9D658F2586257832006093E2

The link above demonstrates how to provide VI Server access for code running in an executable (LabVIEW Run-Time engine ).  How can this be configured for code modules running with a TestStand sequence?

[dug9000 · Accepted solution]

Have you tried creating seqedit.ini (really <appname>.ini) or similar in the directory of the executable that you are using for the TestStand UI?

-Doug

[LVB]

---

@dug9000 wrote:

Have you tried creating seqedit.ini (really <appname>.ini) or similar in the directory of the executable that you are using for the TestStand UI?

-Doug

---

Doug,

Thanks for the tip, placing a seqedit.ini file with the VI server settings next to seqedit.exe works!