I found that when I use Resource to model multiple operators that connected to networknodes, the copied operator may connect to a different network node than the node connected to the original operator. This sometimes cause the error that a traveler's destination is not reachable. Please see attached model for an illustration.
resource-and-travel-network-in-process-flow.fsm
Update to the latest version of FlexSim 2017. (17.0.2) This bug was fixed. Resources are copied at the same location as the orignal, connected to the same network nodes.
As far as I know, when duplicate task executers are created they automatically connect to the first network node in the model tree. There may be a better solution to this, but I just created a custom code activity after each "Acquire" activity which creates a connection from the operator to the desired network node using contextdragconnection(). However, the duplicate operator is still initially connected to the first network node, so it will have to travel to the correct one when acquired (only when you increase the resource count).
As far as referencing an individual resource member, what do you need it for? Of course you can reference the operator's name, or set a label.
Adrian, Thanks very much for your answer and solution.
Without using the custom code, I can also just connect the network nodes NN1 and NN3 to avoid the error and the model will still work, similar to the way you described. But one thing interesting about your solution is after the first run, Operator2_1 will always connect to NN3, the node that Operator2 connects to.
In my opinion, it should be natural to assume all operators under the control of the same Resource should have the same initial condition, including the networknode that they connect to.
If I can get references of individual members of Resource, I can do a lot of things on Reset using Reset trigger, including connecting to the right network node. I am not sure how this can be achieved by referencing the name or setting label as you suggested, because the model is not running yet.
12 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
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.
