I have a single source and I would like to use unpack to separate into 3 different queues.
Issue is that I want it to always separate into 3 piles and not randomly.
Any idea how to do it?
Hi @night ,
The unpack mode on the separator requires there to be a container for flow items. For example, you could have a pallet containing items and unpack them into three different queues. You could, however use the "split" mode in your current model and split the flow item into 3 different parts to go to each queue. Documentation on these separator modes can be found here.
In the output of your separator properties, you can change the "send to port" section to divide flow items how you want. Round robin will alternate between output ports and split the flow item to fill the three queues.
You could also create labels on parts and use "port by case" to send parts to their respective queues. This would, however, require a combiner to make the container pallet that you can unpack like I mentioned earlier.
More send to port options are found here. Both of these examples are in the attached model above. Hope this helps!
To my understanding, split mode duplicates items when they split while unpack mode assumes that there are other items that has to be removed.
My program is to simulate an engine being received from the customer (source) and I have to disassemble the engine into 3 parts (the 3 queues). Which is why I wanted to use the unpack mode and why I do not use a combiner in the first place.
Is there a way to do it or is my understanding about the separator wrong? Or is there a way that the item that comes out from the source is already a combination of objects hence there is no need for a combiner? (then I could use the second method you provided)
Whether you have three separate and different items to begin with or you duplicate one item and then change the shape/size/... when the duplicates enter the queues probably wouldn't make a difference though, right?
With that said, there is nothing stopping you from adding additonal objects as subnodes to a an object in the FlowItemBin via the tree view (where you would also have to edit the position, size etc.).
The source will then produce those subnodes along with the main item, allowing you to directly use the separator in unpack mode.
The best way to accomplish your task is probably to make a custom flow item to unpack like Felix demonstrated. If you want to use 'split' to divide the engine into three separate parts, you can also use an On Exit trigger in the separator to assign labels and colors to the exiting parts.
4 People are following this question.
