How to make the Task Executer wait until a queue is empty?

Question

question

Marco Busatto asked Jan 10, '20 Jason Lightfoot edited Jun 21, '22

How to make the Task Executer wait until a queue is empty?

Hi,

In my model (flexsim-transfer-question12.fsm), I want the task executer "Transfer1" to take 18 boxes from the queue called "Only boxes" to the queue called "RM1 buffer" and to wait until the RM1 buffer is empty again before travelling back to its origin.

I can see that the task executer "Transfer1" moves back to pick up 18 more boxes as soon as there are 18 boxes ready in the queue "Only boxes" instead of waiting for the "RM1 buffer" to be empty first.

How can I do to make the Transfer1 wait until RM1 buffer is empty before it travels back to its origin?

Thank you in advance!

process flow queue task executer wait for event

flexsim-transfer-question12.fsm (79.4 KiB)

· 2

5 |100000

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

Bradley S commented · Jun 21, 2022 at 07:42 PM

I have a very similar question. I need my ASRS to get the item while it is waiting for my Task Executer to deliver its items and this works well when I don't use process flow and make the "maximum content" of the queue set to 1. However, using process flow logic this doesn't work. Please Let me know if there is any way to fix this. Thanks

Optimization_autosave.fsm

0 ·

optimization-autosave.fsm (10.7 MiB)

Jason Lightfoot ♦♦ Bradley S commented · Jun 21, 2022 at 09:35 PM

It's going be an answer specific to your question so you should post a fresh question, which will be better tracked. When you do maybe you could explain at which point you first see something going wrong and what you expect to happen. It sounds like you want the ASRS to alternate between pulling out of the racks and putting into them when there are both jobs - but a more detailed description will help.

0 ·

Answer 1 · 2020-01-10T14:37:02Z

Braydn T answered Jan 10, '20

@Marco Busatto

The easiest way I can think of is to add process flow for Transfer1's logic, and add a wait for event before you release Transfer after it drops off the items at RM1.

5 |100000

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

question