Container object enters (port 1) and triggers a task sequence for the operator. The operator gets a flowitem from one of two queues, depending on inventory availability. The flowitem should enter (port 2) and trigger more retrievals until pack quantity is met, but it is reading as coming from port 0 and therefore not triggering the code to create the next task sequence.
@Adam C I have take a look at what you have written. There are a few remarks:
1. Have you tried debugging your onentry trigger? Just open the code and click on the far left column of the code window (just before the linenumbers) such that a red dot appears. If you now run the code it stops there and you can see the values of all your variables or put some code in the watch variables window to check for your code. You will also see that it is entering through port 2 all the time so that is not the problem.
2. If you have done that you would see
current.stats.content.value - 1 == packQty
will never be hit. This is because current.stats.content.value is always 2. 1 being the bottom pallet, the other being the flowitem you just put in the combiner. After your code is executed the combiner puts your newly entered flowitem into the bottom so the content is 1 again until your next flowitem arrives.
3. because this code is never executed after a while your combiner spits out the bottom with everything in it and this messes everything up.
so what can you do. Most important remark: Learn about process flow. This is exactly made for these types of situations.
But I understand that coming this far, this is not the right solution. So you should look at the content of the bottom, so your line of code should become something like:
current.subnodes[1].subnodes.length
This will give you the content of your bottom (subnodes[1]) and not the content of the combiner. Actually I think to get the content of an object subnodes.lenght is the preferred way. (although I guess yours also works)
But then you should also make sure that you release the packed product from the combiner yourself, because now the combiner is doing that. If you fix this, together with the debug approach you should be able to build your model further.
Steven, I have tried debugging. When the first flowitem/tray enters, the local variables shows port to equal 0 when it should be 2, and the if statement checking for port equal to 2 is skipped over. Where do you see that it is entering port 2?
I see what you mean on the content vs subnode length now that I look at it in the tree.
Can you explain the need to manually release the packed product from the combiner? I do not understand the issue with letting the combiner handle it after the process time finishes.
@Adam C For the port number see attached picture. And if I step through the code it nicely enters the correct piece of code.
There was another error. Once it hits the correct amount you shouldn't bring any other products to the combiner until the next pallet has entered. So in the part where you check for the content you should add the line:
return dispatchtasksequence(ts);
You were correct that you don't have to release the product yourself if the amount matches the amount in the combiner table. So I also attached your model with the changes and I think that it now does what you want.
10 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.
