Gas/Liquid Filters Replacement

[Kabrute]

that puts the second valve after the filter valve, actually wachunga is using 2 separate filters and a feedback loop, you would need to add an additional filter for every type of gas you wanted filtered off the loop or in wachunga's case just "Not" the element you are filtering to main so that your bypass pulls everything but that,

[martosss]

On 4/28/2018 at 1:24 AM, Kabrute said:

so its basically either one way or the other, the not gate ensures that its always one and not the other, it would be me space convenient to lay it behind the ladder to the left of the setup and just wire it direct but this shows it more obviously

What do you mean by a filter valve? Anyways, you are correct as far as I understand for more gases - 1 more filter + 1 more "not" filter, probably with their own feedback loop after the current "not" filter .. so the logic would be A => not A + loopback to A => B => Not B + loopback to B  => continue for other gases

[Kabrute]

[SamLogan]

On 19/05/2018 at 10:32 PM, wachunga said:

Loop back excess resulting from a clog with another sensor/shutoff. Prioritize the loop by having your input bridge into it. Both sensors are set to the gas you want filtered, second sensor runs through a not gate to the second shutoff. Left is input, middle is selected gas, and right is everything else. You can do the same with just bridges, but it's uglier and bulkier. 

Also as Dude42 and Midnight said the OP's design is flawed as the shutoffs are after a T.

Great setup. Is it from you? Someone tell me it's a Brothgar's creation.

[McDude]

I was able to build a water cooler which can turn hot water to cold using 1 HVAC using automation with automated loop.  Essentially lets water out of loop when reaches <=14 degrees

Only glitch is rarely getting <14 degree water back into the HVAC which will freeze the water and break the pipes.  Put more sensor splitters to reduce chance.

1. Have liquid valve set to 2500 g/s so it allows loop not to backup and get pipe blocked by water

2. Temp >15.9 degrees by thermo sensor on mid sensor which gets inverted to bypass system if water is >14 degrees so don't break pipes on next loop.

3. Temp <14.9 on bottom in case water gets too cold then it just bypasses system

4. Temp <15.9 on top sensor to bypass system in case one of the drops gets through previous sensor which happens time to time.

5. HVAC in water with water bypass so water does not get hotter and hotter and water vents on top keep dripping on it so it gets new cold water.

 

[Chipplyman]

On 9/17/2018 at 5:46 PM, McDude said:

Only glitch is rarely getting <14 degree water back into the HVAC

There's a packet of possibly wrong temperature water sitting behind each shutoff valve input. That packet will go through first when the valve opens.

Your pipe temp sensors are all on an intersection. When water (or gas) in a pipe encounters an intersection, the packets will take every available path alternately. For shutoff valves to work reliably, you have to take this choice away. The only choice should be the one controlled by automation: whether to go through a valve or continue past its input port.

Pipe bridge priority rules also apply to shutoff valves.

[Storm Engineer]

On 5/19/2018 at 10:32 PM, wachunga said:

Loop back excess resulting from a clog with another sensor/shutoff. Prioritize the loop by having your input bridge into it. Both sensors are set to the gas you want filtered, second sensor runs through a not gate to the second shutoff. Left is input, middle is selected gas, and right is everything else. You can do the same with just bridges, but it's uglier and bulkier. 

Also as Dude42 and Midnight said the OP's design is flawed as the shutoffs are after a T.

I just started playing after a long hiatus so I'm still new to these buildings. I'm trying to distill down the key points. So am I right in the following conclusions?

1; When shutoff input is on top of the pipe (instead of a T joint) then it is prioritized over the ongoing pipe
2; With shutoff on top of pipe and sensor right on the previous pipe the shutoff will never allow the wrong element through
3; So the first shutoff is "Only the right element may ever pass" and the second is "the right element will never pass" so we realized a 100% reliable filter (and the loopback is only to avoid a clog between the two shutoffs)
4; Then if I only care about the filtered branch and doN't mind the filtered element going the other way can use just a single shutoff to have perfect filtering for that branch

I was struggling with my Oxygen gen, separating Oxgen and Hydrogen perfectly. Now I'll build this loopback design.

 

[Storm Engineer]

This still doesn't work. As soon as either branch clogs up, the loopback setup will start malfunctioning too:

[Djoums]

2 minutes ago, Storm Engineer said:

This still doesn't work. As soon as either branch clogs up, the loopback setup will start malfunctioning too:

Try something like this, you have a priority problem with the bridge.

Spoiler

 

I recommend reading this thread.

 

[Chipplyman]

@Storm Engineer your design has the input prior to the loop. The reference design injects new input within the loop. Your loop will get backed up and stop moving, and the sensor will read the wrong packet. In the reference design, packets will never stop moving within the loop; instead, the input line will get backed up if the loop is full. 

[Storm Engineer]

@Djoums and @Chipplyman you are right! I didn't have an understanding of the prioritization, but now everything is clear.

As soon as I made the loop go through the output end of the input bridge it started working properly.

Thank you! <3