question about splitter
Re: question about splitter
Robot(ic) Arm
Re: question about splitter
Something like that. But I'm just too used to "inserters" .
The only point of my otherwise useless intervention was that "is terminology that important ?"
Koub - Please consider English is not my native language.
Re: question about splitter
That important that we had a survey about it in a FFF.
Btw where is the result of it?
Re: question about splitter
sadly you both get 0 points due to not beeing able to read the challenge requirements protip: NO FILTERS
Re: question about splitter
Oh, i see. Here we go:
- no undergrounds
- no filters
- (however there are inserters, there are no limitations for them in challenge)
Chests are limited to one slot, inserters insert only when there are less than 10 items in chest (to prevent too much buffer), "extractors" only "extract" when there are at least 4 items in chest. Chests are manually primed with requested item. There are no filter spliters, no filter inserters, only regular inserter that will grab only things it can insert into chest and so it *magicaly* grabs only requested items
-- edit:
And because there are no restrictions that both transport lanes must occupy same belt:
-- edit:
Another solution: By reading belt if there are 8 items that means belt segment is full and so inserters can grab from belt. In that case they are guaranteed to grab from near side and so split is performed. Priority spliter can be achived by simple row of inserters. Priority feedback is to allow working in condition where one of "input" lanes is empty - there will be items to fill inner belts and so second lane will not be blocked.
-- edit:
Re: question about splitter
can you please qoute the part of the challenge description where it sais: it is guaranteed that the items on one part of the belt are always the same... despite the image that created the illusion of this text existing - this text is not part of the challenge description
to more clarify: it is NOT GUARANTEED that there is only ONE KIND of item-type on each side of the belt
----
anyways nice read your answer
Re: question about splitter
So my 4'th image from previous is a working solution:
better solution with inserters without need for feedback loop: Inserter only grabs when there are 8 items on belt (so it is full) so inserter grabs from near side only and proper split is achieved. Far side is never touched and so there is no need for feedback. It needs some items to be left stuck in setup, but this can be any item since it should never leave this setup
-- edit:better solution with inserters without need for feedback loop: Inserter only grabs when there are 8 items on belt (so it is full) so inserter grabs from near side only and proper split is achieved. Far side is never touched and so there is no need for feedback. It needs some items to be left stuck in setup, but this can be any item since it should never leave this setup
Re: question about splitter
ok i understand this works indeed with the only requirement to have full belt on each side... this is not perfect but it works. +1 gg
Now find a way so it works without having to buffer 8 items...
Now find a way so it works without having to buffer 8 items...
Re: question about splitter
If you initialy feed this inserter-lane-spliter with cheap crap item, only to feed far lanes on inserter section, then they should not be counted towards buffering as they never move anywhere. There are no restricion in challenge as to "not be using any helper items". In worst case drop belts as items and count them to total entity count required to build this thing.
This setup works fine with any lane imbalance, up to one side being empty. Because inserter section far lanes are occupied by crap, spliter will essentialy move all items incoming from left lane to left-belt-left-lane, and incoming from right lane to right-belt-right-lane and so there is split. Middle two lanes of spliter are blocked and so spliter will not output new items here.
This setup need to buffer at most 3 items per input lane - this is case where input for inserter is not yet full and so inserter must be disabled. Belts are not disabled so this 3 items will go to end of inserter secion where they will wait. By tweaking inserter stack size, checking which item it will grab and item count trigger level it should be possible to go to true 0 buffer.
With spliter-underground you also loose some items because spliter needs to output item on blocked lane to get feedback "this lane is blocked, i am better not giving more items here". Spliter-underground looses 2 items
--
This looks to work fine with 0 internal buffer (stuck items are not counted toward buffer - could be any crap item)
Re: question about splitter
Here is a design that does not use inserters:
Ok, it is very fragile and will break if input or output drops below 100%.
Here is an improved version that shuts down if it detects input or output problems, and does not require a higher tier belt.
Ok, it is very fragile and will break if input or output drops below 100%.
Here is an improved version that shuts down if it detects input or output problems, and does not require a higher tier belt.
- BlueTemplar
- Smart Inserter
- Posts: 3211
- Joined: Fri Jun 08, 2018 2:16 pm
- Contact:
Re: question about splitter
Interesting, I wonder how it compares to mine...
BobDiggity (mod-scenario-pack)
Re: question about splitter
Hey there!
Since they reworked the splitters, things like that are just so much easier. I really like that they can do input / output priority now, and in combination with the filter tool, you can get this result with just a few clicks.
Also, the belts don't need to be on 100%, hooray!
Cheers,
wicklig
https://www.twitch.tv/wicklig
Since they reworked the splitters, things like that are just so much easier. I really like that they can do input / output priority now, and in combination with the filter tool, you can get this result with just a few clicks.
Also, the belts don't need to be on 100%, hooray!
Cheers,
wicklig
https://www.twitch.tv/wicklig
- Attachments
-
- output priority.jpg (747.04 KiB) Viewed 3594 times
Re: question about splitter
Oh and one more thing, to state the obvious: If you add one more splitter for each lane, you get the same result as in the posts above. just in a much easier way.
- Attachments
-
- output priority filter.jpg (746.41 KiB) Viewed 3593 times
Re: question about splitter
I guess this is why they reworked the splitters
because else you got to find a complicated setup to work around, or just use inserter, or underground belt, but that's too easy right ? x)
Nice Ribbon anyway
Re: question about splitter
And next solution:
Lane split is performed on spliter where inner two output lanes are blocked by items and so left input lane will go only go left output left lane, and right input lane will go to right output right lane.
Lane extraction is performed using sideloading with condition controlled belt: output is released only when there are 8 items on source belt. This should guarantee that only one lane can sideload onto output belt. Because of this second lane will not move and so spliter works fine.
Pros:
- works with any lane imbalance
- true split with mixed belt content
- keeps item order
- full throughput even on blue belts
- no inserters required
Cons:
- non zero buffer
Lane split is performed on spliter where inner two output lanes are blocked by items and so left input lane will go only go left output left lane, and right input lane will go to right output right lane.
Lane extraction is performed using sideloading with condition controlled belt: output is released only when there are 8 items on source belt. This should guarantee that only one lane can sideload onto output belt. Because of this second lane will not move and so spliter works fine.
Pros:
- works with any lane imbalance
- true split with mixed belt content
- keeps item order
- full throughput even on blue belts
- no inserters required
Cons:
- non zero buffer
Re: question about splitter
cons:
when the output lane backs up it messes up everything.
When only one side of belt has material, it has to wait for material on the other side.
Every time you replace a splitter it makes something different
Pros:
Every time you replace a splitter it makes something different
in some cases it does the correct thing .
If you don't touch anything it stays the same for long time.
Edit: other slightly different version with protection from output problem detection. This one you don't need to change any splitter the system alter the sequence of items just enough so that it function properly the first time with no item getting in the wrong belt even the first few.
It stutter when the lane are imbalance which is not the exact same functionnality as op proposed though. It is count perfect for item.