Qiana C avatar image
Qiana C asked Ben Wilson commented

Load and Unload times not working AGV process flow

I am currently using the AGV process flow and am trying to use the experimenter to change the load and unload times in each scenerio to see how throughput is affected. However, every scenerio provides the same throughput no matter how long I set the load/unload times to.

I found this link that may be my problem:

and was wondering if this bug has been resolved yet.

FlexSim 20.1.0
agvprocessflowexperimenterflexsim 20.1.0load and unload
· 6
5 |100000

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

tannerp avatar image tannerp commented ·


I looked through the Release Notes and searched for anything related to this, and it appears that the issue you referenced has not been addressed yet. @anthony.johnson would know for sure.

Just to confirm: Are you using the Use navigator for offset travel option?

0 Likes 0 ·
Joerg Vogel avatar image Joerg Vogel tannerp commented ·

I don’t think it is a bug. It is more a misunderstanding of process flow. Most options in 3D object properties are designed to be part of a fixed resource logic, but process flow is a logic structure beside the standard 3D logic. If you start to implement process flow, as it is recommended, to control a model, you leave the path of 3d standard logic. You are responsible to read option parameters in process flow by your own and then delay tokens.

If I build a process flow structure, I try to build a 3d standard logic model first and then incorporate process flow as a substitute of written triggered source code.

There might be a slightly difference in the task types load/unload vs frload/frunload, too. load/unload matches better with a process flow logic, but both tasks aren’t anymore involved with the concept “number of items in transit” of standard 3d logic in process flow activities.

There are templates of process flow which emulates a 3d logic perfectly, but it is still an emulation and not a native 3d model logic. Please don’t misunderstand me, I am a fan of process flow, but not as it is introduced in tutorials. For me it is a supporting tool to document a written source code in a better way and not as a replacement. A classic 3d logic of connection edges “create>store>process>destroy” driven by FlexSim engine has still not found a suitable replacement in process flow with all dependencies you have implemented back from your earliest FlexSim versions like 2.6 or 3.5.

1 Like 1 ·
Qiana C avatar image Qiana C Joerg Vogel commented ·

thanks! I was actually wondering if it was because i was setting load/unload times in the 3D model instead of the process flow, where everything else is handled. My follow-up question then, is how can i use experimenter to play with load/unload times and other typical agv characteristics/variables? Thanks!

0 Likes 0 ·
Show more comments
Ben Wilson avatar image Ben Wilson ♦♦ commented ·

Hi @Qiana C,

We haven't heard back from you. Were you able to solve your problem? If so, please add and accept an answer to let others know the solution. Or please respond to the previous comment so that we can continue to help you.

If we don't hear back in the next 3 business days, we'll assume you were able to solve your problem and we'll close this case in our tracker. You can always comment back at any time to reopen your question, or you can contact your local FlexSim distributor for phone or email help.

0 Likes 0 ·

0 Answers