Clock overflow problem related with unload time of transporters

Question

question

Cindy Azuero asked Jul 6, '16 Phil BoBo commented Jul 29, '16

Clock overflow problem related with unload time of transporters

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:

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:

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.

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

Software Version:

FlexSim 16.0.1

bug clock overflow floor racks unload time

clock-overflow-answer.png (31.8 KiB)

clock-overflow-solution.png (31.9 KiB)

clock-overflow-1.png (24.4 KiB)

clock-overflow-en-m16.png (29.8 KiB)

Answer 1 · 2016-07-28T14:33:48Z

Brandon Peterson answered Jul 28, '16 Phil BoBo commented Jul 29, '16

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:

Reduce the size of the flowitem z height
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)
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

· 2

Cindy Azuero commented · Jul 29, 2016 at 04:39 PM

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 ·

Phil BoBo ♦♦ Cindy Azuero commented · Jul 29, 2016 at 05:39 PM

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

2 ·

question