Keep calling the same operator for transport

I´m wondering if someone has an idea of how to accomplish this. I have a lot of operators connected to a dispatcher for transporting flowitems from several racks. What I need is once a certain rack calls just one available operator this same operator completes the job of moving flowitems from the rack without the help of any other operator and without transporting flowitems from another rack.

What would be the best way to keep calling the same operator until all the flowitems has been moved?
Thanks for any input!
Jorge.

Jorge,

If the rack is emptying out into something other than a queue (ie only one flowitem can leave at a time!) then here is a solution.

Upon entry of the first flow item you can clear a label to zero that you will use later. In the flow you want to check that label and if it is zero send the task sequence to the dispatcer. Upon exit of the first flowitem you can set a label to the tonum() of the operator. Then you can send the rest of the flowitems to the operator directly instead of the dispatcher. This way the operator won't try to pull from the dispatcher because he already has a task sequence. Upon exit of the last flowitem you can clear the label. The next flowitem in will repeat the process.

Good Luck,
Brandon

Thanks Brandon for your help. Do you mind helping with the following:

1) I dont' want the operator already asigned to a rack to transport flowitems from another rack when the numbers of racks is greater than the operators. The "Break To" same load station until empy doesn't do the trick.

2) Should I set the operator label value of the rack from the trigger OnLoad of the operator or is there a hidden parval() or parnode() on the Exit Trigger of the rack that makes reference the transporter?

Thanks!

Jorge,

The Break To requirement should only come into play if your operator has a content > 1 and if only 1 object can be moved at a time then it's unlikely that the operator would be able to move more than one at the Break task anyway.

I would try using the OnLoad trigger but it may not work because the next item may already have released before the trigger fires.

Brandon