oncontinuetriggerdoesnotfire.fsmI don't know where I've made a mistake, but when the task executer 1 tries to reach the 1st node on the left and it passes through the previous node NN6, the continue trigger of Node NN6 does not fire. Thanks in advance for your support.
Source code line in the OnReceiveTasksequence Trigger Taskexecuter1
inserttask(ts,TASKTYPE_TRAVEL,node("NN2", model()),NULL);// JV
force the taskexecuter to travel to NN2 in each tasksequence.
The following line in the OnContinue Trigger of NN6 prints "OnContinue " and the edge the traveler goes to in the Output Console.
pr();pt(concat("OnContinue ", numtostring(toedge)));// JV
And you see, the taskexecuter1 fires in NN6 the OnContinue Trigger
Carlo,
When I run your model, task executer 1 never goes back through NN6 going to NN2. Your code will only fire in the OnContinue when the node that is being traveled to is NN2. I don't see that ever happening in your model. What am I missing? Can you give more details as to exactly what is supposed to happen in the model?
Task Executer1 comes back to node NN2, which is a parking node, in order to allow the Task Executer2 to go to the maintenance position, which is its reset point: this is due to the fact that there is only one rail which connects all the stations in the plant. When the Task Executer1 reaches node NN6 and continues to NN2 it sends a message to dispatcher in order to open the way for the Task Executer2 which is blocked at node NN16.
@carlo.timossi, yes, that is OK. But as @Jeff Nordgren has pointed out the attached model runtime ends 480s after start and until that time the Taskexecuter1 has never traveled back to NN6. The Taskexecuter starts from the parking node, then the Taskexecuter travels via NN6 to a processor. Though the Trigger OnContinue fires once for the Taskexcuter1. In my Test I haven't found any error. The model behaves as you have described it. So when should the Taskexecuter1 travel back to the parking node and fire again the OnContinue-Trigger?
2348-oncontinuetriggerdoesnotfire.fsmThe TaskExecuter1 travels back to the parking node when the TaskExecuter2, serving the Queue2, enters on maintenance and goes to its reset position. In any case, I've made some changes to my little model, taking into account your suggestions, and now it works fine. In this version the trigger OnArrival of node NN2 fires when TaskExecuter1 reaches it and send a message to the dispatcher in order to allow TaskExecuter2 to cross node NN16 and go towards its reset position. When the replacing machine TaskExecuter3 reaches the node NN16 in order to serve Queue2, the TaskExecuter1 is freed sending freeoperators to dispacher and including TaskExecuter1 as 2nd argument. Perhaps it is possible to block the TaskExecuter1 when it arrives at NN2, without setting it into UTILIZE state, but I haven't had no success in doing it. I annex here .my last version of the model. Thanks all for your support and advices.
Carlo,
I found the problem with your model. In the Dispatcher OnMessage trigger line 75, you were setting the first parameter to TEi, which is a reference to a TE. Normally, this would be a reference to a flowitem that is being "worked" on. But because no flowitem is involved in this Utilize task, the first parameter should be NULL and the second parameter, by default, should also be NULL. So I changed that line of code.
Then in NN16 in the OnArrival code on line 22, you specified the dispatcher as the TE to free and as the second parameter (usually the flowitem but per the above paragraph we used NULL) the TE. I changed this line of code to use the TE as the first parameter and NULL as the second parameter.
This seems to have cleared the problem of TE1 not getting freed up. Check out the attached model and see if it is now doing what you are wanting it to do.
4 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.
