I want to perform the Go to Bag operation in the image I shared, on an operator basis, every 5 cycles, I do not want the operator to perform the Go to Bag operation every cycle. How can I make this change?
Thank you.
I would suggest to define a "counter" label on the operator. This gets incremented a token runs through the subflow. If it reaches 5, the token is send to the "Empty Bag" travel activity and the label is reset to 0.
Currently that subflow is executed once for each item in the queue. Is this correct?
Hello, thank you very much for your support. But as you can see in the image I shared, the tokens are split into two different processes and this causes the operator to loop in the 3D model. In the sub-flow, 1 token is divided into many tokens, representing each of the packages in any chute. Therefore, all of the split tokens have to move together.
That is what my question was aimed at. Running through all activites once per item seems like a bad way to model this. Since moving the batch from the queue to the conveyor is a single process, it would be better to coordinate it through a single token.
Only the loading and unloading should be done in a subflow.
Furthermore:
- Why do the queues have tens of copies of the same state profile attached to them?
- Why do the operators have non-existant tokens as subnodes?
Thank you very much for your help, you have helped me a lot!
The reason why there are so many state profiles could be because of this code that I used to create these profiles automatically for each chute, it could be that I run the model multiple times and it keeps duplicating them.
Hello, in the first subflow process, you pulled the packets that fell into the chute from the list, but I need to use these packets again for the 2nd subflow process. For this I put push to list event in the first subflow but it didn't work. At the same time, the operator should not start carrying packets falling into other chutes before finishing with packets in one chute. How can I solve this problem?
You don't need the list for the unloading. At that point the items are loaded by the operator and can thus be accessed as its subnodes.
The operator shouldn't mix tasks, since the process flow keeps it acquired until the first task is done. If it does I would need to look at the model to see what might be going wrong.
flexsim_model.fsm.zipHi, I shared the model with you now. What I want to do in the last stage of the flow is that the operator drops all the boxes he carries on the conveyor at once and completes the flow and takes care of the other chutes. But now when it passes to the 2nd subflow event, the value of the labels named item is the same and they are all named as the 23rd box.
14 People are following this question.
