Synchronize Release Wave

Question

question

Tommy Heyser asked Feb 13 2019 at 12:11 AM Tommy Heyser commented Feb 18 2019 at 7:17 AM

Synchronize Release Wave

Has anyone come across the following error message when using Synchonize with the Max Wait Timer option ticked? In the OnWaitTimerFired, the "Release Wave" command is pre-defined. I removed the Set Label command.

time: 1.000000 exception: Exception caught in TreeNode::callMemberFunction() c++/dll execution. Throwing... MAIN:/project/exec/usercommandlist/Process Flow/releasewave/node c: MAIN:/project/exec/usercommandlist/Process Flow/releasewave/node i: MAIN:/project/exec/usercommandlist/Process Flow/releasewave/node thisClass: MAIN:/project/exec/usercommandlist/Process Flow/releasewave/node

I'm running FlexSim 2018 Update 2, 18.2.3.

max wait timer synchronize

· 2

Joerg Vogel commented · Feb 13 2019 at 8:55 AM

Please attach the model.

0 ·

Tommy Heyser Joerg Vogel commented · Feb 13 2019 at 8:24 PM

Please see attached file, releasewave.fsm. I couldn't attach my working file, but I created a new model that resulted in the same error.

What I'm trying to achieve is a push to/pull from list logic that triggers on a periodic cycle. If the pull activity before the Synchronize doesn't occur within a set time (Max Wait Timer time) then I expected the Synchronize activity to release the token from the Delay activity. What I'm seeing is the error in the System Console and a token appearing in the Push to List, even though a token remains in the Pull from List.

0 ·

releasewave.fsm (22.2 KiB)

releasewave.jpg (70.4 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-02-15T21:59:19Z

tannerp answered Feb 15 2019 at 9:59 PM Tommy Heyser commented Feb 18 2019 at 7:17 AM

The problem we found was that the OnWaitTimerFired logic was incorrectly looking for the token's parent and didn't have a designated connector.

See the attached image for the corrected values.

Let us know if this helps!

hereyago.png (15.9 KiB)

· 1

Tommy Heyser commented · Feb 18 2019 at 12:12 AM

Hi Tanner, thanks for your reply. However, that's not quite what I'm after with the logic. In your example, the token coming down the pull from list side of the Split ends up on the delay side, rather than going to the push to list.

I was hoping to use Release Wave to release any and all tokens waiting at the Synchronize activity to the output connector with the same rank as the input connector. Perhaps my understanding of "Release Wave" is incorrect.

Having said that, I've taken your suggestion of using "Release Token" and instead of specifying a static value for the Destination, I used an Assign Labels activity to set the value of a label on the child token (first declared on the Split activity) with a value of the intended destination. This effectively ties the pull & push activities to a "clock".

I am using this to tie multiple sets of pull & push logic together, using another synchronize after the clock-side Delay, so that when all sets have successfully pulled a token, they all wait for the clock before pushing their respective token. In the event that one or more of the pulls cannot pull a token, their clock still ticks along and doesn't stop others that did successfully pulled a token.

0 ·

releasewave.jpg (188.7 KiB)

question