Set requests for space platform hub via circuit signals

[gigantopithecus]

+1

Cargo landing pads and requester chests have this feature and it's odd that space platforms don't

In my case it I wanted to set requests for my promethium ship to request biter eggs only when all the promethium science packs on the ship are sent down.

Because this is not possible I had to do a work around on Nauvis to block all my rocket silos from sending biter eggs if there are enough promethium packs on the planet. But this is less intuitive and an inferior solution

[Amarula]

Being able to set requests via circuit conditions would be very cool, but what about a different paradigm? You can set the schedule to tell the platform to unload to a planet or not. What if you could have a setting in the schedule to tell the platform whether or not it could request from the planet? Then for example you could request a load of biter eggs, move to the next stop in the schedule which does not allow requests, the next stop to pick up eggs and then depart for the shattered planet? Lots of new ways to shoot yourself in the foot oops I forgot to allow loading uranium fuel cells at Nauvis...

[Smidget]

so i can do this with the cargo landing pad using an arithmetic combinator output to the pad a constant combinator tied to the output of the arithmetic. which thats what sets the numbered value of the request. and the input of the arithmetic is tied to a roboport to scan the inventory. and by doing this the request are handled via circuit network. but taking that same configuration put it on a space platform using the platform hub or belts or both as the inventory and you get nothing even though the pad and the hub have the same checkboxes as the landing pad... so im assuming the devs set it like that on purpose because of the logistics of rockets. basically you cant request exact amounts for rocket delivery easily and circuit network is used for micro manage so maybe thats why your space platform or ship cannot use circuit network for request even though the same circuit configs are available? hence why space hub doesnt have set request tick?

i attatched photos for reference

Arithmec config

Arithmec.PNG (1.51 MiB) Viewed 755 times

combinator config

Constant.PNG (1.24 MiB) Viewed 755 times

circuit layout

PS Circuit.PNG (2.48 MiB) Viewed 755 times

landing pad config

landing pad.PNG (692.27 KiB) Viewed 755 times

space ship config

Ship.PNG (185.29 KiB) Viewed 755 times

[Neuroplastic]

+1 here. Also for promethium

[malecord]

For me ATM it would be sufficient to have a multiplier taken from signal. But +1.

[Wilm0rien]

in my case I only wanted the space platform to request biter eggs only as last action after the refill process before starting to the shattered planet so the freshest eggs are in my platform.

the platform can only communicate to the planet via orbital requests including the biter eggs being requested from the very beginning.

I solved it like this:

1. the bite egg rocket is not filled automatically .

2. once biter eggs are requested I know there is a platform starting the refill process (rebuilding stuff, waiting for the hangar to fill with extra amunition)

3. if biter eggs are requested and other stuff is requested (iron plates, copper plates, explosives) the biter egg rocket is not filled because we need to wait for the refill process to finish first

4. after a while the rocket filled up and stopps requesting stuff except the missing eggs. in this case i start a yellow inserter to empty a box with 100 wood in it to create a delay timer for 2minutes. this box is refilled at any time if another requests comes from the platform to reset the timer

5. once the delay timer has elapsed (box is empty after no requests from the platform for 2 minutes) I start filling the biter egg rocket with biter eggs

6. once the platform has its eggs received it starts and the biter egg rocket is emptied egain

[Tertius]

[...]
5. once the delay timer has elapsed (box is empty after no requests from the platform for 2 minutes) I start filling the biter egg rocket with biter eggs

This seems a weird approach and unnecessarily long. You want an egg shipping platform leave fast and with freshest possible eggs?
Then make sure everything it might request is in the logistics network and you have enough rocket silos to send every request simultaneously and you have enough cargo bays in the platform to receive everything simultaneously.

And then there are the eggs. To get the freshest eggs to the platform, they cannot be provided by the logistics network, they have to be directly inserted from captive nests into dedicated rocket silos instead. However, you need eggs within the logistics network for local consumption.
To solve this, build dedicated rocket silos with 5 captive nests around it like this:

10-03-2025, 14-39-20.png (271.18 KiB) Viewed 127 times

Read requests from the landing pod, divide eggs by 500 to get the amount of egg rocket silos and activate moving eggs from the nests into their rocket silo so in about 1 second the silo is filled and being launched. This is faster than any automatic rocket silo is able to pull eggs from the logistics network, so the rockets with the directly inserted eggs will always win.
The other requests are fulfilled by the logistics network by the automated rocket silo at the same time, and everything will arrive at the platform at the same time, which can leave immediately.

How does this contribute to this suggestions thread? It shows current planet logistics is lacking. There isn't enough control for rocket filling. Either you go fully automated, or you go fully manual. My combined example just works by coincidence, but not by design - it's just because it exploits a race condition. And I worked rather hard to make sure the egg rocket silos will always win the race. I'd rather have a solution that works by engine design.

• I would like to be able to tell which items should be excluded from automated rocket filling.
• And/or which items to include.
• I'd like to be able to read requests before they are actually being fulfilled by the logistics network to decide which should be processed by the logistics network and which to ignore or process manually.