question

SudheerReddy avatar image
0 Likes"
SudheerReddy asked Felix Möhlmann answered

Deadlock trigger when TE's has run into, is not triggering

time: 15.279353 exception: TaskExecuter1 has run into TaskExecuter3 on an accumulating path. This is not allowed.

In this exception, would like to understand why deadlock trigger has not triggered

AccumulatingPath_3.fsm


1695547174997.png
FlexSim 23.2.1
deadlock
5 |100000

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

1 Answer

Felix Möhlmann avatar image
0 Likes"
Felix Möhlmann answered

As Jordan pointed out to me in this post, acculumation should not be used with two-way paths. In this case, the accumulation error you are seeing causes the Task Executer 1 to stop its travel before the deadlock would happen. Due to this, the TE is not trying to allocated the CP currently held Task Executer 3 and the resulting situation is not a deadlock cycle.

If you set the paths to have no accumulation, the deadlock reroute will trigger, but since Task Executer 1 is surrounded by two other TEs at that point, it can't find an alternate path to the destination.

5 |100000

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