Releasing unmatched token at wait for event

Question

question

Ryosuke S asked Sep 23 2020 at 9:11 AM Ryosuke S commented Sep 28 2020 at 11:40 PM

Releasing unmatched token at wait for event

I've learned from past answers in the community that in order to release unmatched token at wait for event activity is to use the Zone. But how exactly do you set the zone? Can you set to the sample layout? I want to set to the BlockEvent. Thank you in advance.

agv_blockedTime.fsm

Software Version:

FlexSim 20.1.3

processflow flexsim 20.1.3 wait for event

capture011.jpg (57.2 KiB)

agv-blockedtime.fsm (57.5 KiB)

· 2

Jeff Nordgren commented · Sep 23 2020 at 3:41 PM

@ryosuke.s,

I guess I don't understand what is supposed to happen in the model. It appears that you are waiting for events in your PF blocks for events that are never going to happen. But I don't know what to suggest because I don't know what the model is supposed to do. If it's just waiting for those events, then maybe the events need to change what they are checking for? Or you could check the box "Use Max Wait Timer" to release the token after a certain amount of time has passed.

Any additional information that you can give us would certainly help.

Thanks.

0 ·

Ryosuke S Jeff Nordgren commented · Sep 23 2020 at 11:52 PM

Hello @jeff.nordgren, Thank you for your reply. I'm sorry I didn't explain in detail. As you can see, there is one Travel activity, and I want to calculate the time of travel and also time blocked by other agv, if it ever happens. So, Block (wait for event) is there in order to calculate the blocked time. However, agv doesn't necessarily blocked by other agv. If it is NOT blocked, the token will remain at the wait for event, so I figured I need to release the tokens, otherwise many tokens will be accumulated here. This is the reason why I wanted to know how to release the token at the wait for event.

Thank you in advance.

0 ·

______

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-09-24T14:08:51Z

Jeff Nordgren answered Sep 24 2020 at 2:08 PM Ryosuke S commented Sep 28 2020 at 11:40 PM

@ryosuke.s,

In the Wait for Event process flow block, at the very bottom of the window, is a field called "Use Max Wait Timer". If you check that box, you will be able to enter a Time to wait. Then in the OnWaitTimerFired field, you select the option to release the token (see attached model).

Is this what you are needing to do? From your description, I believe that is all you need to do. Take a look at the model and see if this solution would work for you.

Thanks.

agv-blockedtime-JN1.fsm

agv-blockedtime-jn1.fsm (59.6 KiB)

· 3

Ryosuke S commented · Sep 25 2020 at 12:44 AM

@jeff.nordgren,

Thank you for your reply and sample file. I'm a little puzzled. Why did you have to change the Object in the BlockEvent from token.car to ControlPoint3?

Also, in this case, since you set the Use Max Wait Timer on BlockEvent, you don't need Zone2, do you? Is it used to restrict the number of token entering the BlockEvent activity? Thank you in advance.

0 ·

capture013.jpg (29.3 KiB)

Jeff Nordgren Ryosuke S commented · Sep 28 2020 at 4:38 PM

@ryosuke.s,

#1. I can't think of a situation where a Transporter can go into a Blocked state, on its own. So, in the model that uses this as the BlockEvent, won't work because that block will never fire that event. Where a DP can be in a blocked state. So I changed it from the transporter to the DP.

#2. You're right, I only changed things in the model that HAD to be changed. I didn't go through it all and make it "pretty". Attached in the model that has been "cleaned" up a bit.

If you have any questions or problems, please let us know. If this answers your initial question, please accept the answer.

Thanks.

agv-blockedtime-JN2.fsm

0 ·

agv-blockedtime-jn2.fsm (57.2 KiB)

Ryosuke S Jeff Nordgren commented · Sep 28 2020 at 11:40 PM

@jeff.nordgren, thank you for your kind support. I understand clear now. The transporter in this layout won't go into Block state on its own. You are correct. But in the actual customer layout, there will be lot's of transporter running at the same time, and there is a good chance that it will be blocked by one another. But of course it is not easy to reproduce that situation with this sample layout.

0 ·

question