1x1 building with one pipe input and output. It has a slider for how much is going through every 60 seconds, hence allowing better control over mixed belt inputs.

Add two modules, one for reading throughput and one for setting the slider. As mentioned in the chicken farm module proposal, we might need a generic slider control module.

This should be for all transports, be it belts, pipes or molten channel. That should make it match all cases regardless of what the game and mods comes up with later.

It's a bit of an open question if this should be a standalone mod or part of programmable controllers.

I was thinking about that, and I feel the counters, speed controllers are useful for this.
But still you can control the throughput by connecting multiple belts between two dividers and pause everytime one of them.

                 - 60 [Paused]  -
200 - [balancer] - 60 [Running] - [balancer] - 120
                 - 60 [Running] -
                 - 60 [Paused]  -

I think what we need is a module to read transport data

• maximum throughput
• tiles per second
• number of tiles for the transport in question

If that is available, then I can write a python module, which generates the on/off signal for a switch off module. The benefit of this approach is that reading the transport will auto adjust if the transport is upgraded.

If those data are available, then then together with the existing transport module it should be possible to calculate throughput if we really want that number. More importantly it should be doable to calculate duration of on/off in order to create the requested throughput.

That will be also hard to calculate, but it is more approchable.

Maximum throughout and tiles per second are in the GUI, so I assume they are fields somewhere, which can be read. Number of tiles should likely be cached because it's fixed. I do believe a transport changing size will make it a new entity, hence modules losing them and needs to be attached again. As such it's a constant once the module is attached. This means performance is not really an issue, something it would be if some sort of looping would be needed for each tick.

I'm able to get count of segments of transport, the amount of items on belt and how much items can be stacked and if it's moving.
So it can be calculated partially with having the average module connect to it.
But the same thing can be already done by two transport modules, because you know the capacity, the multiplied capacity, but what is missing is the speed.