[2.0.20] rocket doesnt create logistics request

[its a me]

I have a space platform requesting 50 logistics bot's and a rocket silo set to automatic fill requests how ever a circuit connection to a roboport on the logistics network shows no request for logistics bot's, i expect that like a requester chest a rocket that supply's space platforms to create a logistics request like a requester chest.

spacePlatform.png (4.97 MiB) Viewed 133 times

rocket silo.png (5.96 MiB) Viewed 133 times

roboport.png (5.77 MiB) Viewed 133 times

logisics request.png (6.85 MiB) Viewed 133 times

[MechBFP]

Do you actually have any bots in a provider chest anywhere?

[its a me]

no but it should create a logistics request like a requester chest.

[MechBFP]

It doesn’t, not until the network can provide the items to the rocket, at which point the silo will request it as the next item it will launch.

That is just how it works. The only way to see the requests ahead of time is to use the circuit network “Read orbital requests” from the silo.

[IsaacOscar]

Hmm, could you wire that up to a requester chest (and have it set to set requests from the circuit network), disable auto requests on the silo, and then put an inserter from the requester chest to the silo?

Personally, I think rocket silos and landing pads just shouldn't be connected to the planetary logistic network at all, that way you can use your own logistic chests to customise the behaviour (e.g. to allow controlling whether it requests from buffer chests)

[MechBFP]

This can be done but only if you out your silo on its own logistic network.

So what I do is put a requester chest on the edge of my network, with a bulk insterter that then moves items to a passive provider chest that is connected to the independent rocket silo logistic network. I then have some combinator logic that then takes the value in that provider chest and makes it negative, and then outputs that signal back to the requester chest so that items that have already been delivered by the main network no longer get requested.

Also because the circuit network from the silo only outputs the amount of items requested, you have to use the selector combinator in “rocket capacity” and “stack capacity” and do some logic so that your bots bring the appropriate amount of items, otherwise the rocket will never launch since it only auto launches with a full stack unless you use the “custom minimum” feature on all your space platform requests.


Note that if you use the custom minimum feature there is no way to tell from the circuit network, so if you normally being full stacks or full “rocket capacity” amount of items to that chest, then you will have some left over garbage. You can just leave it there for another ship that might request it later though.

I can share a blueprint later of my setup if you want. Also there is currently a bug related to that circuit network that I opened a bug report on that hasn’t been resolved yet, it is nothing major just that the silo will occasionally output negative signals for several milliseconds, which causes my bots to go and pickup some of those items (since I convert the signals to stack size/rocket capacity size with those selector combinators) and then when the signal disappears the bot goes and dumps the item to n a storage chest. Not ideal but since storage chests provide items over passive provider chests those junk items don’t accumulate so it’s not much of an issue other than making the storage network a little messy.