Wait For Event Issue with Referenced 3D Object's Token Value Change

Question

question

Stan Davis asked Aug 31 2021 at 10:31 PM Ryan Clark commented Sep 07 2021 at 11:16 PM

Wait For Event Issue with Referenced 3D Object's Token Value Change

I am testing logic where a token will wait until its 3D object's label has been updated by another token. Ultimately, the 3D object's label value will provide move destination information.

The test logic works except for implementing the 'Wait for Event' activity to monitor for a change in the 3D object's token value.

I have created a simple model demonstrating my issue.

In process flow, a 'creation' token creates and pushes a 3D object to a list. The 'creation' token then waits until the 'Main' token arrives, pulls the object from the list and updates its 'Line' label.

I have created the 3D object's 'Line' label as a regular label and as a tracked variable. Both methods result in the same 'Wait for Event' error:

Error: Invalid triggering event, event rank 1, at wait for event activity

Any help will be greatly appreciated.

Wait for Label Value Change Event Issue.fsm

Software Version:

FlexSim 21.1.5

processflow event trigger flexsim 21.1.5

wait-for-label-value-change-event-issue.fsm (40.0 KiB)

· 1

______

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 · 2021-09-01T07:15:06Z

Felix Möhlmann answered Sep 01 2021 at 7:15 AM

I would suggest you instead wait for the puller token to enter the next activity after it assigned the label value. That seems much easier than listening for a value change. Or would this not be possible in the model you want to integrate this in?

Another way could be to wait for message to the process flow containing the id of the token that created the item. (Create a label on the item to reference the token, then the puller token can send a message with its id value)

In both cases, a delay should be added after the "Pull from List" activity (and removed after the "Push to List") to make sure the first token has arrived in the Wait for Event activity before the puller token sets the label.

wait-for-label-value-change-event-issue_alternative.fsm

wait-for-label-value-change-event-issue-alternativ.fsm (41.8 KiB)

· 2

Stan Davis commented · Sep 01 2021 at 5:04 PM

Felix,

Thank you for the alternative solutions. I really like the 'Wait for Message' solution as it helps me understand messaging much better. I updated the messaging solution to have the change on the creation token itself instead of the 3D object's token. The whole point of this was to be able to have the Main token reference the Creator token. I am proceeding with your messaging solution.

I would still like to understand why the original example of waiting for a token value to change didn't work. I see scenarios where that would be the most elegant solution. Obviously, I do not have the wiring correct to set a wait for token value change event on a 3D object's token.

Thanks again. Very helpful!!

Stan

0 ·

Felix Möhlmann Stan Davis commented · Sep 01 2021 at 7:09 PM

It took me some experimenting to get it to work as well:

First up, in your upper flow, you only create a "normal" label on the item, not a tracked variable.

More importantly, in the "Wait for Event" activity the object reference has to be written as

token.FS.labels["Line"]

This references the treenode of the label instead of the value directly. (You could get the value with "token.FS.labels["Line"].value)

wait-for-label-value-change-event-issue_fixed.fsm

0 ·

1630523174842.png (10.4 KiB)

wait-for-label-value-change-event-issue-fixed.fsm (34.9 KiB)

question