Task Executor/Transporter Drop Off

Question

question

Zhao asked Jan 28, '24 Jeanette F commented Feb 5, '24

Task Executor/Transporter Drop Off

Currently simulating a system and I need a Task-executor or transporter to drop off the designated flow units at the correct queue (Which I have designated by setting type in the source). However, my transporter will only drop off the flowitem if it is at the top of the transporter and will not drop off all the relevant flow items. This makewip 2.fsms it go in repeated circles to unload one singular load.

How should I resolve this and is there any major difference in utilising a task executor verses a transporter?

Software Version:

FlexSim 21.0.10

task executor transporter logic

wip-2.fsm (37.4 KiB)

· 1

Jeanette F ♦♦ commented · Feb 05 at 04:07 PM

Hi @Zhao, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.

0 ·

Answer 1 · 2024-01-29T09:59:22Z

Felix Möhlmann answered Jan 29, '24

The first thing you can do is what is described in the post below. That will get the transporter to unload all items at the current station before continuing to the next. However, the order in which it will travel to the stations is then still dependent on the order in which the task sequences were created. For example, if the last loaded item must go to Queue4, the transporter will go there first.

https://answers.flexsim.com/questions/142016/why-is-the-order-of-the-box-in-the-3d-model-incons.html

To drive to the stations (and unload everything) in the logical order, you can alter the priority that is given to the task sequences based on the type of the item. This will however mean that this priority will also be used when loading the items. If not all items can fit on the transporter, it will prioritize based on type and not arrival order.

And since this option already requires some coding, since the "Priority" field does not allow for variable expressions, you can go with the "best" solution:

In the load trigger of the transporter, change the priority of the item's task sequence according to its type. If its the last item that is loaded (either the queue is empty or the capacity is reached) create a preempting task sequence for the transporter that finishes instantly. This will lead to the transporter reevaluating which task sequence it will continue next, instead of unloading the last item first. The task sequence is generated in the message trigger after a 0s delay, so that the "Break" task has finished. Otherwise the transporter might accept a new task sequence before it has unloaded all items.

wip-2-fm.fsm

wip-2-fm.fsm (36.9 KiB)

question