Want an easy way to just request a stack or two of items to Nauvis but you don't want to take the time away from defending Gleba to set up something complex? How's about a simple 4x4 circuit that will let you select how many stacks of any item you want in one input? Well, that's what this achieves!
I've set up a cargo requester circuit that allows you to hook up your bot network and landing pad, and request any items you want a certain number of stacks for if the network is low on them. Set up is super simple and making any changes is as simple as changing a signal value in a constant combinator.
To setup:
Connect your roboport to the power pole with a green wire, and connect your landing pad to the power pole with a red wire. That's it, you're ready to request items from space!
To use:
Open the constant combinator and set the item signals as you desire. Just remember that the quantity number that you set is per stack. i.e. requesting 2 stack inserters will send 2 stacks of stack inserters to your landing pad. So, say if you want to export basic materials from Volcanus to Gleba, like 10 stacks of iron, copper and steel. Just set 10 iron, 10 copper, 10 steel in the combinator on Gleba and the pad will request up to 10 stacks for your network. Keep in mind though, the way the garbage cleanup works will make it so the cargo will request items up to the requested stack but will also let the storage drop by a stack before it'll top it off. So if you are requesting 1 stack of items, it'll request that 1 stack when the logistic storage is empty of that item. The example earlier of 10 stacks of stuff will fill to 10 stacks and wont request an extra stack until storage is below 9 stacks.
Technical info:
As with the nature of roboports and how they send logistic storage signals now, you'll often get a ton of garbage signals of things requesting items from the network and causing a bunch of negative numbers to spam the cable. Not to mention all the small requests of items through the network making tons of requests that are less than a stack. This will clean that up by ensuring the signals going through want at least a stack of an item. This filter is set at the end of the line of logic, which cleans out any signals that are less than a stack, leaving a more stable set of requests. This is also why it will try to keep the storage level in between two stack values, the stack set and a stack less. Because if you have any of a requested item that is below the requested stack but above the requested stack, the part that checks your logistic network will subtract from the requested amount. Since that is less than the full stack, it wont send that partial stack though, just up to the full stack amount. An example of this would be if you're requesting 2 stacks of assemblers and you have 5 in your logistic network, it will only request 50. If there is 0 assemblers in your network, it will request the full 100.