topic Re: How can I crack my processor? in FlexSim Forum

How can I crack my processor?

felipe_v3 — Wed, 17 Jul 2019 20:12:31 GMT

[ FlexSim 17.0.13 ]

I need to set up a chance to my processor crack.

Than, I need an operator to come and fix it, but if possible, I don't want that the processing time pauses while he fixes it.

Re: How can I crack my processor?

sebastian_hemmannE3JAU — Fri, 19 Jul 2019 07:04:44 GMT

Maybe you can explain more exactly what you are trying to do. What is not working as expected and what you already tried out. Best would be if you could share an example model with us.

For me it sounds as if the solution should be quite easy if you use Process Flow. But I think I missed some information.

Re: How can I crack my processor?

joerg_vogel_HsH — Fri, 19 Jul 2019 08:30:03 GMT

If the processor doesn't stop when an error occurs, then you can call just an operator to stand next by the processor. How long the operator has to stay, can you define by a delay task or you set the operator into an utilize task and you free the operator later. The attached model does this.

call-just-an-operator.fsm

Re: How can I crack my processor?

felipe_v3 — Wed, 24 Jul 2019 17:19:55 GMT

@Jörg Vogel

Sorry I didn't answer before, for some reason I didn't receive a notification.

So, it's almost that, except that I want to add this "fix" to my financial analysis.

Which logic did you use ?

Does the trigger "reset" refers to the end of process of the current item?

Thank you!

Re: How can I crack my processor?

joerg_vogel_HsH — Thu, 25 Jul 2019 03:19:05 GMT

The whole crack process is totally independent of items, because as you have wished the processing must continue. The process is controlled by messages. If you press reset on simulation run start, the OnReset trigger eventually fires and sends an initial message. The OnMessage trigger receives the delayed message later, calls the operator, changes the color of the processor and sends a delayed message to free the operator in the future. The operator is arriving, gets into utilization. The next message is going into the processor. The OnMessage trigger fires again and the source code to free the operator is executed.

If your question was answered, can you please be so kind to accept it and ask a NEW question, that involves the NOT mentioned conditions. Many thanks!