Remote execution of sequence being accessed from EXE via sequence context registration

[freak]

I used the concepts described in the example code posted with the article titled 'Access TestStand Variables and Properties from an Executable Code Module' (http://sine.ni.com/apps/utf8/niepd_web_display.display_epd4?p_guid=B45EACE3D9EE56A4E034080020E74861), and developed a CVI executable that accesses teststand variables in the context of the sequence that calls it (let's call this sequence B). Everything works fine there. This piece is a small component of a broader distributed application, therefore I need to be able to execute sequence B on computer B from sequence A on computer A, using the remote execution option for the sequence call step in sequence A. I can successfully use remote execution between computer A and B with other sequences, so I know DCOM is setup properly. However, calling sequence B on computer B from sequence A on computer A doesn't yield the expected result. Suspecting my implementation to be the culprit, I tested the same concept with the example code, unmodified, from the example mentioned above. That test consists of a test sequence A on computer A calling the example sequence GetSeqContextOrEngineHandleFromEXE.seq on remote computer B. This test generates an error during execution of the step 'Display Locals-Num' because the executable ExecutableWithSeqContextHandle.exe doesn't successfully create Locals.Num in the sequence context of GetSeqContextOrEngineHandleFromEXE.seq. Again if this example is executed by itself it works fine.

I need to understand how the remote execution affects the use of the teststand API from an executable, and how it affects the registration of the sequence context for use by the EXE (I have a feeling that might be the issue). And I also need to know how to make this work.

Any thoughts on this would be greatly appreciated. Thx! 

[RayFarmer]

Hi,

Do you have TestStand 2.x or are you using a later version TS 3.5.

TestStand 2.0 didn't handle remote execution, that wasn't available until TS3.0 or TS3.1.

This example, shows how an executable can access the same execution of a TestStand sequencefile not a remote execution.

If you have TestStand 3.x, then there should be some examples employing remote execution within theTestStand examples folders. or try this link http://zone.ni.com/devzone/conceptd.nsf/webmain/955A560B0B0052B88625698500563621

Regards

Ray Farmer

[freak]

I am using TS 3.5.

Also to clarify, the CVI executable does not access the sequence context of a remote sequence, only the sequence context of the local sequence that called the CVI exe via the Call Executable adapter.

Message Edited by freak on 04-26-2006 07:24 AM