Hello everyone,
When I run my simulation with >= 7 units, my deflash machine is waiting for the opdfsh2 who has only one task : to do the process of deflash machine.
I don't get it why my machine is waiting for the operator who is utilized by her.
Here it is my simulation if anybody has an answer :
Thank you very much !
Hi @mad2411, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.
If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.
The short answer is: The Use Operator function is does not properly when the maximum capacity of the processor is larger than 1. This is also stated in the first warning box in the documentation.
This situation happens because when an item enters the processor and it currently has enough operators 'utilizing' it, it will not call new operators for that item. When the item that originally called the operator finishes processing, the operator is released and becomes idle. Any items that entered the processor in the meantime will keep processing. When a new item now enters the processor it will call the operator again. However, the next time any item finishes, the code that releases the operator will be executed, but possibly with the wrong item reference. The wrong reference causes the operator to stay utilized, but the processor thinks that it was released and will call the operator again for the next item that enters. Because the operator is still busy, this leads to the locking state you mention.
As a workaround, you can use the Task Sequence Example option for the operator reference. This by default implements the same logic as the default behaviour. In the attached model I edited it to prevent the processor from locking and to keep the operator state synced with the processor's. It works by creating a new task sequence right away when the operator is released and there are still other items on the processor.
Hi Thank you for your answer. I tried to apply your advice :
It still have the same problem. Maybe I did something wrong and couldn't found out.
You added the Task Sequence Example pick option but didn't edit the code therein to include the workaround. I guess the wording in the final paragraph of my answer could have been more clear on this.
Can I see the logic implemented in the Task Sequence Example which is to prevent the processor from locking and to keep the operator state synced with the processor's.
I have version 23.0.2 and unfortunately cannot see the code in the attached models.
Thank you,
Hi @Felix Möhlmann, I tried this with a dispatcher between the processor and operator, but it gave an invalid down cast error. Do you have an example that works with dispatchers as well? Thanks!
14 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
