A more robust logic for AGV park

Question

question

Akshay P asked Sep 12 2019 at 9:30 AM tannerp commented Nov 06 2019 at 8:01 PM

A more robust logic for AGV park

staticfinal-a-link-between-processors-n-queues.fsmDear all,

I am building a simulator for factory automated lines. One of the key metrics on which the simulator will be judged is its robustness and for the very case I want my process flow logic to be as flexible as possible.

For the above mentioned reasons, I want to change my park logic so as to accommodate more AGVs (if need be for optimization studies etc.) in my process flow. Right now, my park logic works on actual referencing wrt to the actual physical park spot in the 3D model. Now, this works for now as the number of AGVs are less, but in case the number of AGVs increase this logic would require more modifications (for eg - with 3 AGVs itself, I have required the use of "decide" activities.

Can someone suggest me a more robust logic, something on the lines of a " AGV(i) parks at location i"?

Please find my current model as attached.

Regards,

Akshay pundir

Software Version:

FlexSim 19.1.1

agv process flow agv network agv process flow agv park

staticfinal-a-link-between-processors-n-queues.fsm (204.1 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 · 2019-09-13T17:41:59Z

tannerp answered Sep 13 2019 at 5:41 PM tannerp commented Nov 06 2019 at 8:01 PM

This is just a shot in the dark and may not solve the issue, but it might get you started with some things to try.

What if you assigned a label to each AGV with a pointer to its designated location? That way, when the token decides that the AGV needs to go to a parking location, it simply looks at the pointer label for which location to travel to?

If scarcity is an issue (i.e. there are more AGVs than there are parking spots), you could consider pushing all of the parking spots to a list and then pulling one whenever an AGV is directed to park itself.

· 5

Akshay P commented · Sep 16 2019 at 8:14 AM

@Tanner Poulton thanks for your reply!

I will tackle both of your comments individually.

Regarding the first comment, I am already doing that but my issue is to point to the destination without it actually being there in the 3D model. I want to build a "robust" logic that does not have to relate to the actual physical destination everytime I build a new model. I am kind of doing that now and the problem that I face is that I have to modify a part of my process flow everytime I simulate a new layout. I want to eliminate that. You can also refer to my "AGV to park" logic for more understanding on what I am trying to convey here.

Now moving on to the second comment, I do not think I will be faced with a scarcity in parking spots, so that shouldn't be an issue :)

I hope I have explained myself well and please do get back to me with your comments.

Regards,

Akshay Pundir

0 ·

tannerp Akshay P commented · Sep 17 2019 at 6:44 PM

@Akshay P,

I would add the parking spots to a group, push all the members of that group to a list, and then pull from that list whenever a parking space is needed by an AGV.

Here's a model (not the best model, but it at least shows that you can push/pull parking spots from a list): agv-parking-example.fsm

1 ·

agv-parking-example.fsm (38.7 KiB)

Braydn T tannerp commented · Oct 10 2019 at 8:41 PM

@Akshay P

Did this answer help you? If so, could you please accept it? If not, could you let us know what else we can do to help you? Thanks!

0 ·

Show more comments

question