Problem with preemptions

Question

question

Oscar C13 asked Jun 09 2022 at 5:24 PM Jason Lightfoot edited Jun 10 2022 at 4:11 PM

Problem with preemptions

Hello everybody,
I have a problem with mi moden and I tried to replicate it with this example.

While an activity that lasts 60 seconds is being executed (being in fr1), every 40 seconds the operators must go to FR2 and stay 5 seconds. When the operator finis the activity that he is doing in fr1 he has to go to fr3 but he have to keep in mind that every 40 secons he still has to go to fr2. fr2 has to go a totl of 2 times. I made a tracked variable so that it looks at the times it has already fone fr2 and make the save context with differente values. It gives me an error and it doesn´t work either.
Any ideas?

preempt.fsm

Software Version:

FlexSim 22.1.2

preemption dispatch activity milestone tasks

preempt.fsm (40.9 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 · 2022-06-09T18:02:55Z

Jason Lightfoot answered Jun 09 2022 at 6:02 PM Jason Lightfoot edited Jun 10 2022 at 4:11 PM

Please take a look at this post where the use of task sequences and milestone is outlined. This is a better way to preempt that the token context saving method you have tried.

This is the example model:

interruptionv2-jl3.fsm

interruptionv2-jl3.fsm (51.5 KiB)

· 9

Oscar C13 commented · Jun 09 2022 at 6:47 PM

Thanks for your answer

The problem with the attached model in your answer is that it is not doing exactly what is requested. The 10 seconds are counted all the time, and not from the moment the operator arrives at queue2. Another problem is that it is an infinite loop, it does not stop when the operator has been in queue2 for 40 seconds.

On the other hand, I didn´t understand the use of milestones and how they can help.

0 ·

Jason Lightfoot ♦♦ Oscar C13 commented · Jun 09 2022 at 7:52 PM

It was from another question (linked) so I didn't expect it to have the same parameters as yours.

It isn't in an infinite loop - the 'core system' task completes at 479 seconds, having been preempted away for the other 439 seconds.

It's an example of how to preempt a task executer using the best method. If you had any number of core tasks at different locations , the use of the milestone allows you to preempt to a different location and not worry about knowing where the operator needs to return to complete a task - the milestone does it for you. Change the timing and see how it works.

0 ·

Oscar C13 Jason Lightfoot ♦♦ commented · Jun 10 2022 at 7:00 AM

Sorry really, but I don´t understand how your model works. What makes it stop at that time?

0 ·

Show more comments

question