Flowitem entering combiner port 0 when task sequence sends to port 2

Question

question

Adam C asked Jun 11 2018 at 8:35 PM Steven Hamoen commented Jun 15 2018 at 8:09 AM

Flowitem entering combiner port 0 when task sequence sends to port 2

Container object enters (port 1) and triggers a task sequence for the operator. The operator gets a flowitem from one of two queues, depending on inventory availability. The flowitem should enter (port 2) and trigger more retrievals until pack quantity is met, but it is reading as coming from port 0 and therefore not triggering the code to create the next task sequence.

autefa-concept-v2.fsm

Software Version:

FlexSim 18.0.5

combiners ports task sequences

autefa-concept-v2.fsm (30.8 KiB)

______

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-06-13T20:06:49Z

Steven Hamoen answered Jun 13 2018 at 8:06 PM Steven Hamoen commented Jun 15 2018 at 8:09 AM

@Adam C I have take a look at what you have written. There are a few remarks:

1. Have you tried debugging your onentry trigger? Just open the code and click on the far left column of the code window (just before the linenumbers) such that a red dot appears. If you now run the code it stops there and you can see the values of all your variables or put some code in the watch variables window to check for your code. You will also see that it is entering through port 2 all the time so that is not the problem.

2. If you have done that you would see

current.stats.content.value - 1 == packQty

will never be hit. This is because current.stats.content.value is always 2. 1 being the bottom pallet, the other being the flowitem you just put in the combiner. After your code is executed the combiner puts your newly entered flowitem into the bottom so the content is 1 again until your next flowitem arrives.

3. because this code is never executed after a while your combiner spits out the bottom with everything in it and this messes everything up.

so what can you do. Most important remark: Learn about process flow. This is exactly made for these types of situations.

But I understand that coming this far, this is not the right solution. So you should look at the content of the bottom, so your line of code should become something like:

current.subnodes[1].subnodes.length

This will give you the content of your bottom (subnodes[1]) and not the content of the combiner. Actually I think to get the content of an object subnodes.lenght is the preferred way. (although I guess yours also works)

But then you should also make sure that you release the packed product from the combiner yourself, because now the combiner is doing that. If you fix this, together with the debug approach you should be able to build your model further.

· 2

Adam C commented · Jun 14 2018 at 8:20 PM

Steven, I have tried debugging. When the first flowitem/tray enters, the local variables shows port to equal 0 when it should be 2, and the if statement checking for port equal to 2 is skipped over. Where do you see that it is entering port 2?

I see what you mean on the content vs subnode length now that I look at it in the tree.

Can you explain the need to manually release the packed product from the combiner? I do not understand the issue with letting the combiner handle it after the process time finishes.

0 ·

Steven Hamoen Adam C commented · Jun 15 2018 at 8:09 AM

@Adam C For the port number see attached picture. And if I step through the code it nicely enters the correct piece of code.

There was another error. Once it hits the correct amount you shouldn't bring any other products to the combiner until the next pallet has entered. So in the part where you check for the content you should add the line:

return dispatchtasksequence(ts);

You were correct that you don't have to release the product yourself if the amount matches the amount in the combiner table. So I also attached your model with the changes and I think that it now does what you want.

autefa-concept-v2-tal.fsm

0 ·

autefa-concept-v2-tal.fsm (30.5 KiB)

portnrs.png (281.9 KiB)

question