Time Table stop input not working

Question

question

Carlos Marcelo LZ asked Nov 25 2020 at 8:08 AM Ben Wilson commented Dec 12 2020 at 1:56 AM

Time Table stop input not working

Hi I am trying to configure a timetable so that when it downs it only closes its input but the only way I´ve made it work is by stopping the process. My problem is that by doing so the objects get stucked and instead of finishing processing it while not accepting another one.

modeloFinalEscOriginal_autosave.fsm..

Software Version:

FlexSim 20.2.0

flexsim 20.2.0 timetable down behavior stop input resume input

modelofinalescoriginal-autosave.fsm (73.5 KiB)

· 2

______

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 · 2020-11-25T16:26:40Z

Jason Lightfoot answered Nov 25 2020 at 4:26 PM Jason Lightfoot commented Dec 08 2020 at 11:47 PM

Okay - it looks like you need this line in the resume behaviour:

nodefunction(getvarnode(downobject,"receivefromport"));

This isn't ideal as it assumes that the downbehaviour knows something about how the object is pulling, but it should get you past this issue.

You also need this change to the receivefromport trigger where you pull from the list:

#define BYPASS_ALL_BUT_INPUT_CLOSED 0x6F 
pullitem(current, pulled, 0, BYPASS_ALL_BUT_INPUT_CLOSED));

instead of

 pullitem(current, pulled, 0, BYPASS_ALL);

Attached is an example model.

Test_stopresumeinput_pullingfromList_nodefunction.fsm

test-stopresumeinput-pullingfromlist-nodefunction.fsm (33.2 KiB)

· 2

Carlos Marcelo LZ commented · Nov 25 2020 at 6:50 PM

modeloFinalModificado.fsm

Hi!

First of all thanks for helping me!

Secondly, I applied the logic to my system and it seemed to work but then suddenly in each of the groups I have (i have 5 timetables, one for each group), every processor but one stops receiving boxes before the programmed down behavior.

0 ·

modelofinalmodificado.fsm (74.6 KiB)

Jason Lightfoot ♦♦ Carlos Marcelo LZ commented · Dec 08 2020 at 11:47 PM

Attached is a solution where we manage any backorders when the object is stopped while idle, and in normal running, use a condition to check if we are stopped when we would normally be pulling from a list. It means a change to the 'receivefromport' logic and we should also avoid stopping/resuming inputs since we're not using those ports.

modelofinalmodificado_jlManageBackOrders.fsm

0 ·

modelofinalmodificado-jlmanagebackorders.fsm (76.9 KiB)

question