Different Work Point Loops for Different Types of AGVs?

Question

question

Sofia G21 asked Jul 11 2023 at 12:20 PM Sofia G21 commented Jul 11 2023 at 3:44 PM

Different Work Point Loops for Different Types of AGVs?

I have a model with 3 different types of AGVs, and their paths overlap in different areas of the layout. Is there a way that I can have different NextWorkPoint or Work Point connections for different AGV types?

Reason for question: I don't want AGV1 going down the Work Point Loop of AGV2.

I looked at the AGV Process Flow template and the AGV Network properties. I have an advanced AGV Process Flow for each of my AGV types. It seems that the NextWorkPoint connections is based on a global list called 'NextWorkPoint'. Would it be as simple as creating a new goblal list NextWorkPoint (i.e. NextWorkPoint2) and updating anywhere in the Process Flow it is referenced? Thus having 3 lists, and each of the 3 AGV Types Process Flows using a different Global list?

Software Version:

FlexSim 22.2.0

agvnetwork agvpath agvcontrol

______

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 · 2023-07-11T13:45:26Z

Felix Möhlmann answered Jul 11 2023 at 1:45 PM Sofia G21 commented Jul 11 2023 at 3:44 PM

For the most part: Yes, you can just use multiple lists and determine which one to pull from based on some condition, like a label on the AGVs. You can create more connection types in the AGV network properties. If you check the List option, the automatically generated global list will have the necessary partition structure.

If a control point at which items are picked up belongs to multiple loops, you would also need to make sure that only the 'correct' AGVs can pull the respective items (if there is a distinction). For this I would further partition the WorkList by adding a number that signifies which loop the item belongs to to the partition id.

capture.png (21.9 KiB)

capture2.png (24.2 KiB)

· 5

Sofia G21 commented · Jul 11 2023 at 1:51 PM

Thanks Felix! Very helpful

As far as your second point, I have different AGVWork item lists for each of the 3 different AGV types. (These are the ones I am sending for 'Use Transport' at different queues) Wouldn't those lists take care of having the "correct" AGV pick up from the control points?

0 ·

Felix Möhlmann Sofia G21 commented · Jul 11 2023 at 2:01 PM

That can also work, but still needs some adjustments to be made. The AGV template pulls the item off the global list and pushes them back, partitioned by the pickup point. (So the tokens just have to check a single partition instead of filtering the entire list for eligible items to load.) If you want to use three separate lists, you need to change this lower section to also have three tokens pull from one list each. And later have the child tokens on the right also push back to that same list, the items came from.

0 ·

capture.png (49.0 KiB)

Sofia G21 Felix Möhlmann commented · Jul 11 2023 at 2:19 PM

Felix, that is correct! Part of creating 3 different 'AGV Work' item lists, involves also changing the reference list of the entire process flow. By changing it here, it should do those two things automatically no?

So ultimately, my plan is to have the 3 'AGV Work' item lists, and then, create three separate 'NextWorkPoint' Control Point Connections lists. Would I also need to create 'ParkPoints' and 'PickUpPoints' lists for the newly created 'NextWorkPoint' lists?

0 ·

1689084888074.png (49.5 KiB)

Show more comments

question