Clock overflow problem related with unload time of transporters

Clock overflow problem related with unload time of transporters

cindy_azuero
Not applicable
117 Views
3 Replies
Message 1 of 4

Clock overflow problem related with unload time of transporters

cindy_azuero
Not applicable

[ FlexSim 16.0.1 ]

In a previous model I obtained some Clock Overflow advice. I wrote to FlexSim support and we found that there was a bug on the calculation of the unload time of the transporters when there is a floor rack.

This was the answer:1143-clock-overflow-answer.png

One solution was to leave the max quantity as 1, but when I answered that I needed to use more than that I obtained the following solution:

1144-clock-overflow-solution.png

I implemented that work-around and it seemed to work, but now I'm having the same problem even when I use the command you guys gave me.

1145-clock-overflow-1.png

1146-clock-overflow-en-m16.png

I hope you can help me. Thank you very much.

Accepted solutions (1)
118 Views
3 Replies
Replies (3)
Message 2 of 4

Brandon_Peterson
Autodesk
Autodesk
Accepted solution

Cindy,

Without seeing your model the only reasons that I can come up with for why a z location would result in such a large value is that you have flowitems with extraordinary large z sizes or you have an extraordinary amount of flowitems bing placed in the storage location. The options that I can come up with for you would to try are:

  1. Reduce the size of the flowitem z height
  2. Use Queues instead of a single floor storage - They will place things sided by side instead of on top of one another if there is enough space (i.e. for tall skinny objects)
  3. Select the option "Do not travel offsets for load/unload tasks"

If these options don't work for you the best course of action would be to post your model or a sample of the model so that we could look at it directly and respond back with a solution in the model file itself.

Brandon

img src="https://damassets.autodesk.net/content/dam/autodesk/logos/autodesk-logo-primary-rgbblack-small_forum.png" >

Brandon Peterson
Principal Technology Consultant
>
Message 3 of 4

cindy_azuero
Not applicable

Thanks for the ideas. Even though, someone indicate me that that kind of issues are likely to be solved on flexSim 16.1.0 so I migrate my model to this version and it seems to work. Note: Also it seems that the upgrade for flexsim (16.0.2) do not work.

0 Likes
Message 4 of 4

philboboADSK
Autodesk
Autodesk

Yes, this was a bug that was fixed in 16.1.



Phil BoBo
Sr. Manager, Software Development