question

Yokota T avatar image
0 Likes"
Yokota T asked Yokota T commented

Dispatcher does't sent a task sequence to an available taskexecuter

Hi all,

I created a model that moves the TaskExecuter to a specific place when it goes to idle state, but the behavior is different than I intended.

See this model.

dispatcher_doesn't_sent_task_to_available_AGV.fsm

In this model, when Processor1 first completes the process, TaskExecuter1 is unavailable and TaskExecuter2 is available.

Nevertheless, the task sequence to retrieve the item from Processor1 is assigned to TaskExecuter1.

Please advise the cause of this problem and a solution.

Thank you.


FlexSim 22.0.13
dispatchertasksequences
dispatcher-doesnt-sent-task-to-available-agv.fsm (41.8 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

1 Answer

Nil Ns avatar image
0 Likes"
Nil Ns answered Yokota T commented

Hey,

I have seen that the error occurs in the state of TaskExecuter1. A new task is assigned to it at the same moment that it changes state to Idle. This causes the token that assigns it a new mission to execute before the state change is completed. Therefore, the Task executer has a new mission but when the first token comes out it goes back to Idle again.

To solve this you can use a delay of 0 seconds, which makes the token be the last to move that turn.


dispatcher-doesnt-sent-task-to-available-agv.fsm


dispatcher-doesnt-sent-task-to-available-agv.fsm (41.7 KiB)
· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Yokota T avatar image Yokota T commented ·

@Nil Ns, Thank you for your response. I now understand the cause and the solution.

1 Like 1 ·