How to I change the 'processdispatcher' variable of a processor with code?

Question

question

Jonathan asked Jun 03 2022 at 8:57 PM Jonathan commented Jun 16 2022 at 6:07 PM

How to I change the 'processdispatcher' variable of a processor with code?

I have a Separator. I want to change the process operator on a trigger, then back on another trigger. I see that 'processdispatcher' is the variable in the tree I need to change.How do I do that?

Reason: In my model, my operator uses downtime behaviour to go on bathroom and lunch breaks. During that time I have a Utility Operator that I want to take over and run the machines.

Is there a better way?

Software Version:

FlexSim 22.0.1

operator

· 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 · 2022-06-03T21:05:31Z

Regan Blackett answered Jun 03 2022 at 9:05 PM Jonathan commented Jun 16 2022 at 6:07 PM

If you are using center port connections for the primary task executer an easy approach would be to have a label on the separator with a default value of 1 to represent needing the primary operator. Then in your trigger set the value of that label to say 2 to represent needing the utility operator. Then set the expression for using an operator to current.centerObjects[current.YourLabelName]. Then make sure your primary operator is connected to the first center port and the utility operator to the second center port.

· 1

Answer 2 · 2022-06-03T22:53:04Z

Joerg Vogel answered Jun 03 2022 at 10:53 PM Jonathan commented Jun 16 2022 at 6:06 PM

If you connect your operator to his replacement by an object connection “a” type, he becomes himself a dispatcher. And when he is going to lunch by an preempting tasksequence his previous interrupted tasksequence will be dispatched by him to his replacement. Standard functionality of FlexSim.

· 2

Jason Lightfoot ♦♦ commented · Jun 06 2022 at 11:03 AM

But that by default has the secondary operator take all jobs that the primary can't when the primary is just normally busy - not only when they go on a break. If the secondary has another dispatcher to service then you wouldn't want to close its inputs either, which otherwise could be an answer.

1 ·

Jonathan commented · Jun 16 2022 at 6:06 PM

That didn't work for me. I had to connect both to center ports on the machine, then dynamically change which center port was the current operator.

I have a label called 'whichOperator' that reads either 1 or 2 and is set by the Down Behaviors 'On Down' and 'On Resume' code.

In my machine 'Operator' box I put:

current.centerObjects[current.whichOperator]

This method reliably works.

0 ·

changeoperatorcode.png (165.3 KiB)

question