screenshot
video
Features:Hmm, I wonder what UPS-efficient Kovarex would look like?
--Me(more hours ago than I would like to admit)
- Direct insertion. Less inserter and belt activity
- Max beacons and productivity. Less centrifuges
- Tiling
- Stacked input and output
- Self-synchronizing, self-balancing, no thrashing
- No combinators
- Not clocked, but inserters spend many ticks disabled or sleeping
- Input inserters have hand size 4 to pick up stacks exactly
- Output inserters have hand size 16 to minimize swings
- Can be downgraded to base game
- Prime centrifuges with 40+ U-235. Half stacks is easiest
- Input up to 0.5 stacked belt of U-238 (any belt)
- Outputs up to 0.253 stacked belt of U-235 (same belt)
- Each tiling outputs 2.594/s U-235
The "passback" stack inserters read their own hand contents and blacklist it the next tick, forcing them to swing even if they're not full. Then the input and output inserters are simply enabled/disabled based on the contents of the centrifuge.Okay, but how does it work?
I say simple, but I needed help on the forums to reach this design. There isn't much leeway in output slots vs. input slots, nor is there a belt or chest that buffers items, so preventing jamming, thrashing, and desynchronization issues is harder than you might think.
U-235 is allowed to freely increase in the input slots, then output slots, via passback. The output inserter removes 16 once it is certain that at least 16 excess U-235 is in the output slot. (79 + 16) input + 16 output = 111 total
Meanwhile, the minimum amount of U-238 is maintained for nonstop crafting, as the centrifuges need room to offload U-238 output by Kovarex Enrichment, else 238 would jam.
Clocking this would be difficult, and I think the potential gains would be smaller than typical, considering the complexity of direct insertion Kovarex and seeing how this design is already disabling inserters that interact with the belt. I think most of the gains would be from simplifying the circuit networks, rather than from reducing inserter activity. But if you have first-hand experience with clocking something like this, I'd like to hear about it.UPS-focused, but it's not clocked?
Other links: