Rack with Dwell SendToPort - Use List and Transport

Question

question

Kris Geisberger asked May 16 2018 at 8:45 PM Kris Geisberger commented May 18 2018 at 5:43 PM

Rack with Dwell SendToPort - Use List and Transport

In the attached model a turquoise item arrives at the rack at time 143.60 (Type 10), dwells for 1 sec, then is pushed to a list partitioned by Type. A turquoise token in the process flow pulls the item and then releases it using releaseitem(item,1), the item is selected red in the same code. Unfortunately the ASRS transports a purple item next, which is still on the list. How can this be?

sendtoport-use-list-and-transport.fsm

Software Version:

FlexSim 18.1.1

lists racks send to port use transport

sendtoport-use-list-and-transport.fsm (45.2 KiB)

· 1

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2018-05-17T14:21:49Z

Kris Geisberger answered May 17 2018 at 2:21 PM Kris Geisberger commented May 18 2018 at 5:43 PM

I changed the return value of the Send to Port "Push to Item List" pick option to -1, now the model works as expected. Only items that have been released are transported. WHEN and HOW a given item is transported is governed by the availability of resources and default port connection logic. Which is great, because it saves the user a lot of work involving some more challenging concepts. This is a common system of pulling inventory based on orders.

Now I ask: How does the FlexSim interpret these return values differently? (-1 vs a non-valid port) Should this pick option be changed to return -1?

sendtoport-use-list-and-transport-queue-2.fsm

sendtoport-use-list-and-transport-queue-2.fsm (83.0 KiB)

sendtoport-push-to-item-list.png (18.6 KiB)

· 2

Phil BoBo ♦♦ commented · May 17 2018 at 5:22 PM

If you are returning an invalid port, then the item is still being released, just not immediately released to a specific downstream object through a specific port.

That picklist is designed to be used in conjunction with the downstream object's Pull From List in the Pull Strategy field. That doesn't call releaseitem(), it calls pullitem() or pushitem().

The item has already been released. You shouldn't call releaseitem() again.

You should only call releaseitem() again on items that returned -1 (do not release item) in the Send To Port.

1 ·

Kris Geisberger commented · May 18 2018 at 5:43 PM

@phil.bobo, thanks for the clarification.

1 ·

Answer 2 · 2018-05-16T21:15:09Z

Joshua S answered May 16 2018 at 9:15 PM Kris Geisberger commented May 16 2018 at 10:03 PM

So what was happening is that there was a mismatch of the "Type" label between your tokens and your items being pushed to the list. So when it pulled from the list, the token wouldn't match the item you wanted to pull, so it would wait till there was an item of that Type available. In the file I uploaded I have a token created when your item is created with a matching Type label, so you will see it begins pulling in order of what was placed in the rack. Tokens are also now colored coded to match the item. See if the modified model is what you are looking for.

11900-sendtoport-use-list-and-transport-fix.fsm

11900-sendtoport-use-list-and-transport-fix.fsm (46.9 KiB)

· 1

question