question

Rahul R avatar image
0 Likes"
Rahul R asked Ryan Clark commented

Gap optimizing merge not releasing from one specific slug lanes

While using gap optimizing merge controller, gap maintained on release is inconsistent and there is an error message. And if gap error is ignored, I notice one of the slug lane (right most) is not being released in a consistent manner. The model behaves well when the flow item induction rate is low. I am attaching conveyor tutorial model showing this odd behavior. Any support on identifying the issue is highly appreciated.

Model:

Gap_Optimizing_Merge_Example.fsm

FlexSim 22.1.0
gap optimizing merge controller
· 1
5 |100000

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

Ryan Clark avatar image Ryan Clark commented ·

Hi @Rahul R5, 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

The process flow that controls the lane releases does not take into account items that are added to a slug after it has been released. This occurs if the conveyor is completely full with one or more additional items pending in the source. (See pictures below)

1648449630047.png

To circumvent this, you could set a small gap for items entering the conveyor so they are not added to already releasing slugs.

1648449727434.png

Or set a maximum count for slugs so they can't extend to the end of the conveyor.

1648449838520.png


1648449630047.png (328.7 KiB)
1648449727434.png (1.6 KiB)
1648449838520.png (6.0 KiB)
· 2
5 |100000

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

Rahul R avatar image Rahul R commented ·

Hi @Felix Möhlmann . Thanks for your response and solution. The reasoning about items added to slug after releasing makes sense. Unfortunately the solution does not work in my actual model. I tried entry length + distance and max item count. Is the issue any different in this model? Model attached : Gap_Optimizing_Merge_Example_II.fsm

0 Likes 0 ·
Felix Möhlmann avatar image Felix Möhlmann Rahul R commented ·

In this case the gapping at the photo eye causes the flow on the conveyor to back up and delays the items from clearing the merging decision point. Because of this, the calculated clearing time is wrong and subsequent slugs are released too early.

To fix this you can adjust the process flow by adding the gaps that will be created to the "lastItemOffsetTime" calculation. This way, the back up is taken into account for the needed gap between releases.

1648535487601.png

(The rank of the last item is synonymous with the number of items in the slug. Multiplied by the gap introduced by the photo eye, this adds the total extra distance of the added gaps.)

1648535836606.png

gap-optimizing-merge-example-fm.fsm

0 Likes 0 ·