Have a simple question about routing here：
Below in the screenshot, there are 3 type of parts, routing to 15 different processor, type 1 goes to processor 1 to 5, type 2 goes to processor 6 to 10, type 3 goes to processor 11 to 15, within each type, it's going to the first available processor, what I am doing right now is using pull strategy with specific item type.
Is there a way to do this routing in the upstream buffer? like simple code ?
Thanks,
Hi Chao,
Jing's solution works easier if you can think of the three queues as only virtual and only existing in the simulation model, but not in real life. But if that is not possible then the idea below should work.
If not possible to use Jing's solution I think you will need to write the code in the upstream queue SendToPort trigger yourself. You can have three if:s that check the itemtype and inside each if a for loop that goes through the processors that are accepted for that itemtype and checks if there is an available one. In case none of them is available return the port number of a port that is already busy, e.g. the first processor in the group. Then you also need to check the "Reevaluate SendTo on Downstream Availability" checkbox in the Flow tab of the upstream queue so that it runs the code again when a processor becomes available.
Hope this helps!
Axel
Axel,
Yes, this is what I am looking for. Return the port number of a port that is already busy + Reevaluate SendTo on Downstream Availability.
Thanks for your help!
Hi,
If the answer was what you were looking for then please mark the answer as correct so that others find the answer faster.
Thanks!
Axel
Chao,
In the current version you have the ability to uses a List instead of port connections for managing flow between objects. I have created a sample model for you that does what you described. The way that it works is that the send to port trigger pushes the flowitems onto a default item list. You can create the list by using the "Global List" -> "Item List" option in the toolbox. There are no port connections between the queue and the 15 processors. Instead, each processor "pulls" using the pick list option "Use List" -> "Pull from Item List". In that option there is a query that only pulls flowitems that have the correct item type.
The query to pull item type "1" would be: "WHERE itemType = 1"
In that query "itemType" is a field that is defined on the Global List by default. The neat thing about this method is that you can have processors that can take multiple item types.
Query for type "1" and "2" : "WHERE itemType = 1 OR itemType = 2"
Qery for types greater than 2: "WHERE itemType > 2"
There are definitely many ways to accomplish what you are trying to do and each has its own positive and negative sides so you will want to choose the one that works best for you.
Good Luck,
Brandon
Brandon,
I do really like the idea of using a list to push and pull, similar to an order list I am used to in AutoMod, in the sample model you provided, I am getting an error below, is this a version issue or something else? I am using 16.1.0.
LIST_RETURN_BACK_ORDER_IF_NOT_FULFILL)
This is in the code field of pull from itemtype list.
Thanks,
Chao
Chao,
I got the same problem on my computer here at home where I am using version 16.1.0 at work I am using 16.1.1
I would suggest doing the latest upgrade to get past the error. If that isn't possible let me know and I'll try to find another solution to get past the error for you.
Regards,
Brandon
Hi, chao.
Try to send different itemtype item to different queue before going to processor. These transit queues only connect the processors your item need and keep "First Available" in SendToPort.
I think it's the simplest way to solve your question, and May it helps you.
Thanks for the response.
The idea is to have a centralized buffer system, having 3 separate buffer will be expensive in our case, I can have a central buffer followed by 3 separate buffer with a capacity of 1, but again, that's not the reality, I am looking for a direct way of doing this in the central buffer.
Hi Chao,
As @Axel Kohonen suggested you can accomplish that with some code and alabel structure in the processors. I have attached a model which route-mapping depends on a label in the processors. The queue tests all processors to find a suitable station. If the Send To function can't find one, the item is hold in the queue and 4 seconds later the same item is tested again in the Send To function. To indicate the second test I changed the color of the item. The following test starts by the command releaseitem in the OnMessage trigger of the queue.
My approach does not depend on the option Reevaluate SendTo.
8 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.
