question

gilbert jerald avatar image
2 Likes"
gilbert jerald asked Adrian Haws edited

how to make my operator to return immediately when the item is unloaded on the processor

in my model the operator takes the item from queue to processor , here the operator waits near the processor until the process is finished in the processor , he is not return back immediately to the queue to load the item after unloading the item on the processor , how to over come this problem . i have attached the model for your reference priority-model.fsm

Choose One
processoruse transporttask sequencestravel to locationtravel to a home location
priority-model.fsm (20.7 KiB)
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Brandon Peterson avatar image
2 Likes"
Brandon Peterson answered gilbert jerald commented

Gilbert,

The easiest method would be to change the "Transport Resource" trigger on your queues. Currently that trigger is "centerobject(current, 1)". The following steps will cause the operator to return back to the queue the flowitem came from:

  1. Select the "Task Sequence Example 1" pick list option for the TransportResource trigger
  2. Open the code editor for the same trigger
  3. Copy and paste the first inserttask code line (currently line 21) after the last inserttask code line (currently line 25)

This is the code for the first inserttask line:

  1. inserttask(ts,TASKTYPE_TRAVEL,current,NULL);

If you would rather have the operator travel to a different location than the original queue then you can change the above specified line of code such that "current" is replaced with a reference to a different object. Another alternative would be to specify the coordinates of the location by replacing the "TASKTYPE_TRAVEL" with a "TASKTYPE_TRAVELTOLOC".

I hope this helps,

Brandon

· 5
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Joerg Vogel avatar image
4 Likes"
Joerg Vogel answered gilbert jerald commented

you can activate the template Travel to a Home Location onResourceAvailable in the Triggers of the Operator.

Change the centerport to the Object the traveler should go. It is the number in the command

  1. centerobject(current,1)

vtlnq.png (42.0 KiB)
· 1
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

martin.j avatar image
3 Likes"
martin.j answered gilbert jerald commented

The reason this happens is because the operator doesnt get a new order to fetch the next item for the processor befor the processor is finished with its current task. It is in fact the processor that issues the order for the operator to go get a new item when it is ready.

The absolutely easiest way to solve this is to insert a queue before the processor and change its flow settings to match the processors. Now the operator will continually walk back and forth between the queues, and the processor will automatically take it its items from the new queue: 1956-priority-model-1.fsm

Another and somewhat more complicated but also more acurate solution would be to create the task sequence for the operator your self, and tell him not to wait for the processor to be done with its current item before issuing a new task. You would also have to include the round robin object selection of your processor /NewQueue into this task sequence so the operator knows where to go for the item.


· 4
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.