Conveyor routing based off flowitem characteristics?

Question

question

Lilian Fonseca asked Jun 02 2016 at 9:32 PM Matthew Gillespie edited Jun 03 2016 at 8:19 PM

Conveyor routing based off flowitem characteristics?

My production line needs to work in a way that if the flowitem beam is longer or equal than 80 inches, it turns to the left, otherwise it goes straight ahead. I have been trying to use decision points,

but it just doesn't work. I have tried to use the function "xsize(current)", on the OnArrival trigger in the first decision point. I have attached a figure illustrating what I have been doing.

Thanks.

Software Version:

FlexSim 16.0.1

conveyor flowitem decision points routing send to

conveyorissue.png (64.3 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 · 2016-06-02T21:34:57Z

Matthew Gillespie answered Jun 02 2016 at 9:34 PM Lilian Fonseca commented Jun 03 2016 at 3:42 PM

You need to use xsize(item) and not xsize(current).

In the decision point triggers:

current is the decision point

item is the flowitem

· 6

Lilian Fonseca commented · Jun 02 2016 at 9:45 PM

@Matthew Gillespie

I have just corrected what you said, but it is still running incorrectly. Would you mind to check my model file? It is attached to this comment.

0 ·

automation.fsm (5.3 MiB)

Matthew Gillespie ♦♦ Lilian Fonseca commented · Jun 02 2016 at 10:03 PM

There are at least 3 more problems with this model that I can see:

You need to send to outobject(current, 1) and not outobject(item, 1). You want to the item to the 1st decision point connected to the current decision point.
Your case function is xsize(item)<=60 which will only return a 0 or a 1 (true or false). So your cases need to be 0 and 1 and not 1 and 2.
All of your boxes are 1x1x1 cubes, but you're looking for boxes less than or equal to 60, so they're all less than 60.

Attached is a model where I have a simple example conveyor system doing what you're trying to do.

0 ·

sendbywidth.fsm (18.9 KiB)

Lilian Fonseca Matthew Gillespie ♦♦ commented · Jun 02 2016 at 10:40 PM

I am trying to apply in my model the same logic you used in your example. However, it still doesn't work. About my boxes, there is a dashboard attached to three global variables that will determine the dimensions of the flowitem following a trigger set up on creation on each source, so before the simulation runs the user is able to decide for the size of the product that will come from the source. I think the problem is due the queue that is placed between the first and the following decision points, but I still didn't figure out what the problem might be.

0 ·

Show more comments

question