Some minor additions: First of all, if a machine uses 2 belts for the input, you should place the belt from which more items get grabbed as the closer one to the machine, this greatly increases the throughput. Secondly, for energy-efficiency with beacons, its always a good idea to have beacons rather in the middle, so each beacon covers the maximum amount of possible machines, needing less modules and consuming less energy with the same output.
The first one is a good point, although if the machine runs slowly enough that the long handed inserter can keep up, then it doesn't actually matter. Was it a serious problem on any of the designs? I don't remember it being! Beacons along the middle for conserving power (and speed modules) does make sense - I'll point out to Marc that he was being inefficient 😀
1st: The beacon per machine ratio is max in this design. 2nd: I normally have multiple rows of setups like this, so the outer beacons are shared with the next design.
I guess it depends of your needs, but imo, a kovarex system needs to be able to not overflopw itself on 238 and keep making more 235 without the requierement of using the 238 on something ( and this having an exit belt of 238 going somewhere ) Which is why I guess the belt was missing at the end of Marc's design.
Yes, ideally your full system would be able to deal with any level of demand from the later factory - although a factory that just uses 238 and no 235 would be tricky, since you'd eventually overflow whatever buffer you had. I think all the systems we set up should be OK with only 235 being used though.
No green belts in vanilla 😛 And yes, I took some shortcuts with getting the systems running because this is a video about designs. I also used infinity chests to generate the ore!
My comment the other day went poof, but I wanted to share a blueprint string for the method I prefer. It's most similar to Marc's final counting method, but avoids the need for circuits. In order to 'count' the 235 coming out, you use multiple filtered stack inserters with stack sizes set to equal exactly 41 total (one inserter grabs 1, the rest grab a combo of 40. When the craft finishes, all the inserters grab at the same time. you route the 40 directly back in (with the leftover 238) and your inserter grabbing the one can send it on it's merry way. no backup or 'kovarex wait' The machine won't fill up it's inventory until the 235 output line is backed up. It's a tad bulkier with the extra belts and expensive with all the inserters, but by this stage of the game..... ehhhhh. Easier than figuring out perfect circuits. You DO have to manually prime it by dropping the first 40 in though. After that, smooth sailing. Here's the blueprint string on pastebin: pastebin.com/XPUEAfB6 Thanks for your content. I enjoy watching.
I can see how that would work - thanks for the suggestion. Yes, a little bit bulkier, but I think it would probably be easier to see how it works at a glance. Nice one, I'll take a look 🙂
Some minor additions:
First of all, if a machine uses 2 belts for the input, you should place the belt from which more items get grabbed as the closer one to the machine, this greatly increases the throughput.
Secondly, for energy-efficiency with beacons, its always a good idea to have beacons rather in the middle, so each beacon covers the maximum amount of possible machines, needing less modules and consuming less energy with the same output.
The first one is a good point, although if the machine runs slowly enough that the long handed inserter can keep up, then it doesn't actually matter. Was it a serious problem on any of the designs? I don't remember it being!
Beacons along the middle for conserving power (and speed modules) does make sense - I'll point out to Marc that he was being inefficient 😀
1st: The beacon per machine ratio is max in this design.
2nd: I normally have multiple rows of setups like this, so the outer beacons are shared with the next design.
I made a smaller Mike design. After I finish Krastorio , this design work for 200h with no repair. It was super robust
Nice one! Having a design just keep running without needing maintenance is a great step forwards! Somehow one I always seem to struggle with...
I guess it depends of your needs, but imo, a kovarex system needs to be able to not overflopw itself on 238 and keep making more 235 without the requierement of using the 238 on something ( and this having an exit belt of 238 going somewhere )
Which is why I guess the belt was missing at the end of Marc's design.
Yes, ideally your full system would be able to deal with any level of demand from the later factory - although a factory that just uses 238 and no 235 would be tricky, since you'd eventually overflow whatever buffer you had. I think all the systems we set up should be OK with only 235 being used though.
Noo green belts!!
also, I don't believe you waited for the 235 to build up, since your inventory has suspiciously fewer stacks of 235 at 5:50 than at 5:30. Busted
No green belts in vanilla 😛
And yes, I took some shortcuts with getting the systems running because this is a video about designs. I also used infinity chests to generate the ore!
My comment the other day went poof, but I wanted to share a blueprint string for the method I prefer. It's most similar to Marc's final counting method, but avoids the need for circuits. In order to 'count' the 235 coming out, you use multiple filtered stack inserters with stack sizes set to equal exactly 41 total (one inserter grabs 1, the rest grab a combo of 40. When the craft finishes, all the inserters grab at the same time. you route the 40 directly back in (with the leftover 238) and your inserter grabbing the one can send it on it's merry way. no backup or 'kovarex wait' The machine won't fill up it's inventory until the 235 output line is backed up.
It's a tad bulkier with the extra belts and expensive with all the inserters, but by this stage of the game..... ehhhhh. Easier than figuring out perfect circuits. You DO have to manually prime it by dropping the first 40 in though. After that, smooth sailing.
Here's the blueprint string on pastebin: pastebin.com/XPUEAfB6
Thanks for your content. I enjoy watching.
I can see how that would work - thanks for the suggestion. Yes, a little bit bulkier, but I think it would probably be easier to see how it works at a glance. Nice one, I'll take a look 🙂