Auto schedule across multiple instance of user interface

[husni h]

I am trying to create a test sequence with auto schedule that would work across multiple instance of user interface.

I have tried the following,

1. Use lock name in Use Auto Scheduled Resource as "*POWER_METER". TestStand returns error

"Error executing 'Use Resource' step.

User-defined error code."

2. Use Acquired Lock in Use Auto Scheduled Resource as StationGlobals variables and lock name as "POWER_METER". TestStand does not report any error but the Auto Scheduling does not work across the user interfaces.

However, when I used "*POWER_METER" as the name in Lock step type, it worked correctly across the user interfaces.

I am using TestStand 4.0

Is there a way to make the auto scheduling work across multiple user interfaces like the other synchronization step types e.g. Lock

Thanks. 

[Dennis_Knutson]

The first question I have is why you are doing it across multiple user interfaces instead of using either the parallel or batch model?

[James_Grey]

AutoSchedule will not work across processes. However, if you take each of your AutoSchedule blocks and transform it to a separate thread that acquires a cross-process lock, you will get a similar scheduling result, assuming you don't need to use the AutoSchedule alternative lock feature.