Jump to content

What am I doing wrong with shutoff filter?


Recommended Posts

Spoiler

Cut3IEN.png

YBKt6GQ.jpgG6azPf0.png

I made a simple shutoff filter automation with gas element filter and it allows gas element to spill through the gate that should be shut off. What am I doing wrong? Are there no workarounds fro gas filter? They cost huge amount of power to maintain for their function.

In other words, you have to provide a loopback mechanism so that when packets are blocked from travelling 

through the pipe they are supposed to go through, they instead loop back into the main feed (endlessly until

the blockage is cleared) rather than slipping through to the other output line they aren't supposed to be using.

23 minutes ago, Technoincubus said:

It seems like not gonna work with constant flow from geyser

For nat gas geyser you don't even need it.
Place pump and gas sensor ("above 500g" for example) at a lower point near gayser. Nat gas is heavy and will stack at the bottom of the room. If you use sensor to prevent pumping to vacuum there will be always nat gas and you don't need a filter.

1 hour ago, Technoincubus said:

Checked it again and it is, sadly, not viable. Once the flow stops they filtering breaks and even the slightest stop will cause gasses to go to the wrong pipe. Sad.

My power grids always have a battery on the circuit.  Unless there's an extended power failure, you shouldn't have any issues.  In fact, you could set up a transformer, smart battery, and shutoff valve as the only draw on that circuit and run for 10+ cycles without power before you'd have a problem.

To get the design to work you only need one shut off, and you only need it to run if the gas is not natural gas, tonight I will post the picture that will do what you want, the downside is that again with all versions of this if the power runs out it will break

Here you go, you need 1 shutoff and a not gate.

The idea:

  • input gas from below.
  • filter for Natural gas, then NG will go up because "not" gate blocks the shutoff
  • everything else goes through the shutoff and to the left, given that the left pipe is free. If it's not free it goes up
  • In case of power failure everything goes up.

You can also put the shutoff vertically and remove the "not" gate to change the behavior - NG goes up, everything else goes left, but in case of full upper pipe or no power everything will flow left instead of up. (of course you need to link it to the power grid unlike me in this picture :D ). I made it in sandbox mode just to show you the idea, but below is a link to a thread with a filter that I tested and it's the same, if not simpler.

Normal view:

5b44e43d13c5d_NGfilter.thumb.png.c2ba03b69f7e08128a4078dd1f0083d0.png

Logic:

5b44e43273ca6_NGfilterlogic.png.e4ac8b53d3cb7fea00aef6a90d28a9a2.png

Ventilation view:

Spoiler

5b44e435a0ecb_NGfilterventilation.thumb.png.8eb2cf5ee784c4eedb6773c2b163f3ee.png

 

I just figured this on my own a few days ago, so here is the thread with more discussion  :)

You can see also the variant without "not" gate - that saves you some(35) refined metal, reducing the total cost to 85.

Also, someone remarked that the shutoff doesn't actually use power, it just requires to be linked to a working power grid, so it it s pretty nice solution.

 

15 hours ago, Technoincubus said:

Is there any advice on solution to create a looping flow?

Just connect the output to the input and there you have it - a looping flow ! What exactly do you want to achieve? You need to know a few simple rules in order to make your pipes:

  • Bridges take priority over normal pipes(materials flow in bridges first, and then if the bridge is full, materials travel in the other pipes)
  • Filters(and shutoffs) take priority over normal pipes(again, materials flow first in the filter/shutoff and if the shutoff is closed or the filter is full, then materials travel in the other directions)
  • Splitting at any place in multiple directions makes packets alternate between directions, but packets don't split in pieces(you need to use a filter to split the packet into smaller packets and that will slow down the liquid/gas flow in that direction)
  • After a bridge/filter/shutoff liquid will flow further even if the pump is not working anymore, creating an artificial reservoir  inside that pipe.
  • Merging - if you connect 2(or more) output pipes - packets will mix if possible, while alternating which direction goes in the junction.
    • Note that the difference with splitting is thin, so you might have cases where a packet goes crazy and alternates between 2 pipes. This might happen if you have a setup where you split 2 outputs and then connect 2 of the pipes. In that case packets might start going up-down. In this case the game doesn't know whether to treat the "<" as split direction right, or as merge direction up/down, so I would avoid these scenarios
                 - - - - => OUT
    => - - - <
                \
    
                /
    =>  - - - <
                - - - - => OUT

     

12 minutes ago, martosss said:

 

  • Bridges take priority over normal pipes(materials flow in bridges first, and then if the bridge is full, materials travel in the other pipes. 

This is only half the story. Bridges (and filters and anything else with a white input) take priority and pull the full amount they can from a pipe, if available. 

What you missed mentioning is that anything with a green output looses priority to the pipe, pushing only what will fit into the liquid/gas packet, if anything. So, if you bridge into a loop, you will just top off what is used in the loop while letting what didn't get used to continue to circulate. 

3 hours ago, beowulf2010 said:

This is only half the story. Bridges (and filters and anything else with a white input) take priority and pull the full amount they can from a pipe, if available. 

What you missed mentioning is that anything with a green output looses priority to the pipe, pushing only what will fit into the liquid/gas packet, if anything. So, if you bridge into a loop, you will just top off what is used in the loop while letting what didn't get used to continue to circulate. 

I'd generalize this as merging packets from 2 pipes - if you merge 2(or more) pipes - packets will mix if possible, while alternating which direction goes in the junction. I'll add it to the list above.

2 hours ago, martosss said:

I'd generalize this as merging packets from 2 pipes - if you merge 2(or more) pipes - packets will mix if possible, while alternating which direction goes in the junction. I'll add it to the list above.

No problem. I find bridging into pipes just about as useful as priority bridging out of them. All kinds of loop shenanigans are possible. 

At one point I was playing with a base that had 4 massive water loops going (hot and cold versions on water and polluted water). 

Other than the announce of weird bridging zones, it worked surprisingly well. 

My base is usually a labyrinth of bridges, since a bridge is always better than no bridge ... just USE ALL THE BRIDGES... + you have less buffer in the pipes that way. And yea, you need P water loop, clean water loop ..maybe a 2nd clean water loop without germs ... then different temperature loops .... Still not sure how to best organize it .. for now I tend to do whatever works, although putting some thought in advance can make your life easier down the road.

Archived

This topic is now archived and is closed to further replies.

Please be aware that the content of this thread may be outdated and no longer applicable.

×
  • Create New...