Event-Triggered Source with OnResourceAvailable generates an unexpected token

Question

question

wooram-kim asked Jan 22 2025 at 9:32 AM David Seo commented Jan 23 2025 at 6:22 AM

Event-Triggered Source with OnResourceAvailable generates an unexpected token

Event-Triggered Source with OnResourceAvailable generates a token after the resource is resumed even though it has a task sequence to fulfil.

In the attached mode (OnResourceAvailable.fsm), the man goes right 10 m and then, he goes left by 10 m. The man repeat this movement because I used Event-Triggered Source with OnResourceAvailable. If I stop and resume the man while he moves, the Source make a new token and the existing token does not move anymore. In case of using one time source, the exsisting token works as well as I expected.

Is it intended that the source make a new token? What happened to the existing token?

Thank you.

Software Version:

FlexSim 24.1.1

event-triggered source on resource available

onresourceavailable.fsm (37.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 · 2025-01-22T09:56:54Z

Felix Möhlmann answered Jan 22 2025 at 9:56 AM David Seo commented Jan 23 2025 at 6:22 AM

This is intended. Stopping a task executer really just dispatches a preempting task sequence to it. When the TE is resumed this task sequence finishes, firing the On Resource Available event.

This is why pickoption like "Travel to a Home Location" by default have a condition that prevents them from doing anything if the task sequence queue is not actually empty.

You can do the same in Process Flow by checking whether the "Next TS" parameter of the event holds a valid TS or not.

Previously the original token gets stuck due to how the timing works. When the event fires the original task sequence is the queue. Due to this the newly created TS immediately becomes the active sequence, locking the original TS in the queue forever.

1737539336437.png (5.3 KiB)

1737539415554.png (4.5 KiB)

1737539684299.png (61.5 KiB)

· 2

question