Logistics Router
Posted: Tue Mar 05, 2019 9:23 pm
This is a system to request items back and forth between disjoint logistic networks. It basically reads roboport logistic data and sets requests on requester chests. This was useful for me in belt pathways snaking through biter nests where repair items were needed and to prevent bots from flying over nests.
Constant combinators define a set of items that will be requested from the parent network if they fall below the set number, and excess items will be sent to the parent.
These can be used in a chain, and requests happen on each parent in a hop so there is no waiting for multiple transactions. You can fork multiple children off a single parent in any fashion. Requests from children that don't appear in a hops list is forwarded up the chain.
The Router:
The router circuit fulfills requests from child networks and accepts excess items. A bot switch ensures that items being ferried by bots will not cause duplicate requests. An adjustable belt timer allows the items to travel along the belt before accepting another request. The belt timer uses a constant combinator T to set the number of tiles between the router and bridge. Set T to the number of belts between the router steel chest and bridge active provider plus 2 for the inserter time. The belt speed multiple is set to 32 ticks per tile for yellow belts. Change this to 16 for red and 11 for blue.
Inventory Control:
The inventory control circuit sends item requests. Requests for items from parents are on the red channel and requests for items to parents are on the green channel. Constant combinators set the desired inventory to be kept within the current network. An excess multiple is used to determine how much excess items are kept before sending them upstream. This can be +1 or *10 for example. Items not specified will be sent to the parent network.
It also accepts requests from downstream and simply adds the signal to its own inventory signal.
Additional constant combinators can be added if needed.
Bot Control:
The bot control circuit determines whether logistic bot total = available and blocks requests if not. It also includes a requester chest for adding bots to the network.
- lr1.png (990.7 KiB) Viewed 6181 times
These can be used in a chain, and requests happen on each parent in a hop so there is no waiting for multiple transactions. You can fork multiple children off a single parent in any fashion. Requests from children that don't appear in a hops list is forwarded up the chain.
The Router:
- lr2.png (1.31 MiB) Viewed 6181 times
Inventory Control:
- lr3.png (936.24 KiB) Viewed 6181 times
It also accepts requests from downstream and simply adds the signal to its own inventory signal.
Additional constant combinators can be added if needed.
Bot Control:
- lr4.png (806.01 KiB) Viewed 6181 times
. I have developped similar system to request different materials into buffers from the same train stations. So i did a order booking system for the buffer that I can see the similarities even without going into the details. So it's nice to have another combinator enthusiast creation shared!