01-05-2006 06:01 AM
01-05-2006 06:28 AM
01-05-2006 06:32 AM
01-05-2006 07:17 AM - edited 01-05-2006 07:17 AM
Thanks for the prompt reply, I tried what you suggested and it works fine. It doesn't use the SequenceCallModule object though, do you know how to get a handle to object to the SequenceCallModule for the Step being processed? I am a little concerned about doing it using the method you specified as any future modifcations, by NI, to the properties is going to give me problems.
Thanks again
Steve
Message Edited by SercoSteve on 01-05-2006 07:19 AM
01-05-2006 07:41 AM
01-06-2006 03:11 AM
Hi,
you can actually do this. I was speaking to Steve yesterday on this :
starting with the handle to the appropriate step (I've done it in the attached sequence file in TS, but should translate nicely to LV)
so I use the sequence to get the step by name
I can then get the step.module
then using the TESTAND ADAPTER API (and not the Teststand API)
I can use the module returned above with the SequenceCallModule class from the TestStand AdapterAPI then. (you have to know ahead of time what the appropriate module / adapter type is otherwise it will have problems)
Hope that helps
Sacha Emery
National Instruments (UK)
01-06-2006 03:23 AM
Thanks for your responses guys, most helpful.
Sacha, your sequence was easy to translate into LabView and my sequence creator is now generating correctly formated TestStand Sub Sequence calls without the need for hard coded lookups, nice.
Thanks again
Steve