Waldemar,
there is no reasonable limit for the amount of TestSockets. But there is of course a limiting factor: the performance of the system, mostly RAM. Running 32 TestSockets shouldn't be a problem if the sum of RAM needed for each UUT does not succeed the available RAM.
To answer your further questions, you have to learn some things about the parallel/batch model:
Those models constists of two areas, one for global management and one for each socket. The area for each socket looks a bit like the SequentialModel, but differs due to synchronization issues (report, batch synchronization, ...).
The other area calls the socket area for each socket as NewExecution, meaning a parted dataspace for each socket. Another thing you have to know: each socket executes exactly the same sequence!
So the simplest way to accomplish your task is to generate one general sequence which handles all sockets. Using if-statements and precondition, you can then asign certain functions for certain sockets. You can always get the info, which socket is currently active by reading the RunState.TestSocket.MyIndex.
Synchronization you are looking for is indeed done with the batch-synchronized section.
hope this helps,
Norbert
Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.