question

mark zhen avatar image
0 Likes"
mark zhen asked Ryan Clark commented

pf problem

26-1.fsmThere will always be a problem with finish ts in my model, but according to my inspection I can't find the error, and during the charging process, he will be stuck in the travel but my settings should be no problem, you can help me rule this out Question?

FlexSim 20.0.10
processflow
26-1.fsm (703.5 KiB)
· 3
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.

Jason Lightfoot avatar image Jason Lightfoot ♦♦ commented ·
This question seems to have been created over the weekend, rendering this other question duplicate so it has been closed.
0 Likes 0 ·
Jason Lightfoot avatar image Jason Lightfoot ♦♦ commented ·

The model runs poorly due to a delay time of 0.1 seconds for on average 60 tokens, resulting in 2.5 million entries by the stop time of 4320 seconds instead of the 70 they should have.

1647870231435.png

Instead of this you should be synchronising events using pull from lists or wait for events.

pf_Problem_MarkZhen_jl.fsm1647870774604.png

It looks like there are other delays in the model doing similar things which should be avoided.

0 Likes 0 ·
1647870231435.png (81.4 KiB)
Ryan Clark avatar image Ryan Clark commented ·

Hi @mark zhen , 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 unaccept and comment back to reopen your question.

0 Likes 0 ·

1 Answer

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

One of your sub flows assigns the task sequence to "AGV" and another one to "AGV1". The "Finish TS" that the token is send to through the A,B,C and D connectors expects the task sequence on the "AGV" label. At 1158.16s, when the error occurs, a token from the D connector arrives there whose task sequence is assigned to "AGV1". Hence the error message, because the "AGV" label on that token refers to the task executer instead.

1647781400859.png

Either only use one label name if possible, or add another Finish TS activity that handles the AGV1 case and connect the flows accordingly.


1647781400859.png (18.0 KiB)
· 38
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.

mark zhen avatar image mark zhen commented ·

But if I use AGV to name it, I will not be able to execute DECIDE, or there are other ways?

0 Likes 0 ·
Felix Möhlmann avatar image Felix Möhlmann mark zhen commented ·
Like I said, you could rename the task sequences that are currently refered to as "AGV" to "AGV1" as well, so there is a clear naming convention:

AGV -> Task Executer, AGV1 -> Task Sequence

Then the Finish TS activity can handle tokens from anywhere if the names are the same.

0 Likes 0 ·
mark zhen avatar image mark zhen Felix Möhlmann commented ·

Can you explain it with pictures? Sorry my English is not very good

1647782798294.png

Is the picture below what you mean?

0 Likes 0 ·
1647782798294.png (20.8 KiB)
Show more comments