question

pc neo avatar image
0 Likes"
pc neo asked Phil BoBo commented

model with rack 20.0.0 stops running

sample-rack.fsmI have a model with rack connected using 'A' connection, the rack is configured to accept flowitems if there is space within rack. These flowitems will leave the rack after some dwell time. After running for some time (simply run with max run speed) the model will stop and there is no more events in the event list, though there are flowitems waiting to be sent into the rack.

Is this a bug?

FYI. This issue is not seen in FlexSim 2020.

FlexSim 19.2.4
rackmodel stops runningconnect as fixed resource
sample-rack.fsm (48.7 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

1 Answer

Phil BoBo avatar image
1 Like"
Phil BoBo answered Phil BoBo commented

This is fixed in FlexSim 2020 because we modified the default Pull Requirement for the Rack object in FlexSim 2020 to address this issue.

See New Rack not emptying

· 2
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

pc neo avatar image pc neo commented ·

Thank you for your quick reply. The link to New Rack not emptying is very helpful.

Is there a plan to have the fix in 2020 be rolled into 19.2.4?

I've tried out the suggestion from the above link as follows:

  • Add the OnExit trigger that opens inputs as mentioned above.
  • Go back to the way the rack used to work. Turn off the rack's pull, and change its slot assignment strategy so it doesn't use hasSpace() and will always find a slot to put the item in, (e.g. random bay/level/slot assignment with no hasSpace() requirement).
  • Change the rack's max content to 96 (the number of boxes in the rack when it is full). This will make it so the rack closes its inputs when it gets up to 96, and then automatically reopens them when an item exits.

I observed that if the Slot Assignment strategy uses:

a) matching labels without "hasSpace" but if I have set the max content set to 12, the same issue will still appear again after some time.

b) random/level/slot with max content set to 12, the same issue will still appear.

Is there any other workaround?

0 Likes 0 ·
Phil BoBo avatar image Phil BoBo ♦♦ pc neo commented ·

There's no plan to make any more 19.2 releases. We only support 2 branches at a time: the latest branch and an LTS branch. Right now, that's 20.0 and 19.0.

You can copy/paste the Pull Requirement code from a rack in 20.0.0 to a 19.2.4 rack if you want.

1 Like 1 ·