accumulating path

Question

question

anon-user asked May 21, '21 Eric M commented Jun 1, '21

accumulating path

It is set to private for NDA.

This data is a sensitive model created by a business partner.

This simulation

An error will occur when 14:28:21 2021/05/19 is reached.

About the error content

> time: 19701.187754 exception: HU transport AGV_6 has run into HU transport AGV_2 on an accumulating path. This is not allowed.

However, in this simulation, there does not appear to be an accumulating path.

Question 1

Is there something wrong with the settings?

Or is it a bug?

Question 2

Is it related to this bug?

https://answers.flexsim.com/questions/87493/agv-redirect-does-not-work-on-in-all-cases-on-accu.html

Software Version:

FlexSim 20.1.3

agv flexsim 20.1.3 agvpath path accumulation

· 2

anon-user commented · May 24, 2021 at 12:30 AM

Our business partners think:

He seems to think that the cause of this error is a bug in Join Paths.

Is this guess correct?

0 ·

Eric M commented · Jun 01, 2021 at 10:46 PM

Hi anonymous user, was Logan Gold's answer helpful? If so, please click the red "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 ·

Answer 1 · 2021-05-27T16:59:49Z

Logan Gold answered May 27, '21

anonymous user, I don't think the issue is the same one as the post you linked as part of Question 2, because you still get the same error when running the model in FlexSim 20.2, which is the version that fixed the bug in the linked post.

However, I believe the issue is fixed by right-clicking on an AGV path and choosing "Refresh Path Links" > "Entire Network". You can find more information about that option here:

https://docs.flexsim.com/en/20.1/WorkingWithTasks/AGVNetworks/Troubleshooting/

It's possible this is fixing an issue with Join Paths, or a path got inadvertently moved, or a number of other possible causes. Whatever the cause, using this option makes it so the error no longer occurs at time 19701.18, or anywhere else around that time.

However, I do see an issue occur around time 44115, but it's the "An invalid task has been encountered" message:

Which is usually an issue with how the Travel task was created - possibly something in a Process Flow that needs to be addressed. I haven't had a chance to debug it any further, but it should hopefully be easier for the model creator to track down. Let us know if there are any questions, though, and we can try to find out what else may be going on.

invalidtaskerror.png (9.2 KiB)

question