v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

v0.34:Fluid logic

From Dwarf Fortress Wiki
Revision as of 22:44, 8 April 2014 by Brightgalrs (talk | contribs) (→‎Faster Version: clean up, typos fixed: higher then → higher than)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
This article is about an older version of DF.

Fluid logic is a form of computing which uses a fluid (generally water), controlled by various means, to trigger pressure plates and hopefully accomplish some desirable result.

Infinite Flow Gates[edit]

These logic gates are relatively simple and cheap to make, but require an infinite amount of flow and infinite drainage to operate. You can build a circuit system to prevent the loss of water, but closing constructions like floodgates will always destroy water, so you'll always have to replace it somehow. The following examples use raising bridges and floodgates, as they have the same delay of 100 steps when reacting to on/off signals. The bridges work as inverted input as they block passage when receiving an on signal while floodgates open in that case. The channel in the gates stands for the drainage.

There are two versions of these gates here.

AND

X
X
^
·

An AND gate is simply created by putting two floodgates in a row, each one connected to one of the input triggers: XX. When both floodgates receive an on signal, they will open and let the water from the left side pass. The pressure plate behind the floodgates has to be constructed to react on 4-7 water.

  • If you use two 1x1 raising bridges, you'll get a NOR operation instead.
  • The output can also be inverted by using a 0-3 pressure plate.
  • You can add more floodgates to process more than two signals in the conjunction.
  • You can use a 0-3 and a 4-7 pressure plate at the same time to get the result and its inversion at the same time.
  • You can use a single floodgate and a 0-3 pressure plate to get a NOT gate.
  • You can use a single 1x1 raising bridges and a 4-7 pressure plate to get a NOT gate, too.

OR

X
^
·
X

An OR gate is simply created by putting two floodgates in parallel, each one connected to one of the input triggers: XX. When one of the floodgates receives an on signal, it will open and let the water from the left side pass. The pressure plate behind the floodgates has to be constructed to react on 4-7 water.

  • If you use two 1x1 raising bridges, you'll get a NAND operation instead.
  • The output can also be inverted by using a 0-3 pressure plate.
  • You can add more floodgates to process more than two signals in the conjunction.
  • You can use a 0-3 and a 4-7 pressure plate at the same time to get the result and its inversion at the same time.

XOR

X
^
·
X

A XOR gate is created by putting 1x1 raising bridges and floodgates together. The red bridge and floodgate X are linked to the same input and the green bridge and floodgate X are both linked to the other input. When one of the inputs sends an on signal, the bridge will raise/close and the appropriate door will be opened. Only when the floodgate and the bridge at one passage are open, what happens when exactly one input signal is on, the water will flow to the right. The pressure plate behind the bridges has to be constructed to react on 4-7 water.

  • If you exchange bridge and floodgate for one of the two inputs, you'll get a XNOR operation instead.
  • The output can also be inverted by using a 0-3 pressure plate.
  • You can use a 0-3 and a 4-7 pressure plate at the same time to get the result and its inversion at the same time
  • Processing more input signals is possible but requires an exponentially increasing number of bridges, floodgates, and mechanisms. It is easier to link the output to another XOR gate.


As mentioned, you can just add more floodgates and bridges and even pressure plates to expand your gates to process more input signals and process more complex operations at once. You can combine floodgates and bridges as you need them. Putting them in a row will connect them as AND. Every time you add a new parallel passage with floodgates and bridges this will work as an OR for each other passage. The XOR gate for example is nothing else than combined logic: A XOR B = (A AND NOT B) OR (NOT A AND B). But sometimes it is easier to use more but simpler gates.

Fluid Preserving Gates[edit]

At the moment there doesn't exist a full concept of a fluid-preserving fluid logic gate. Each design working with floodgates or equivalent components in the gates will have to deal with the destruction of the fluid. A way to handle this can be the usage of hatches. Evaporation is another known problem.

CMOS Transmission Gate and Inverter Logic[edit]

Perhaps the closest to utilizing water as a stand-in for electricity, transmission gate logic can be accomplished by simply having an infinite water source in place of all +Vs, and infinite drainage for all grounds. Simple floodgates behave as standard transmission gates, while bridges are inverted gates. However, unlike the other forms of fluid logic, but as with real world electrical circuits, a dedicated inverter is required, which must be hooked up to +V and ground.

Advanced CMOS Gates[edit]

This type of logic uses the same concept as real CMOS circuits do, which causes them to minimize power (in this case, water) consumption. The idea is that water should only flow when there is a state change.

Basic Design[edit]

Let's say we want to evaluate the logical expression f. It can be a simple AND or OR gate, or anything more complicated. Follow the following scheme:

A
^
B
#

Here, A is a set of floodgates and/or drawbridges that let water flow exactly when f evaluates to true, B is the same except that it lets water flow when f evaluates to false, ^ is a pressure plate set to activate on water levels 4-7, and # is the drain.

Examples[edit]

In the following examples, X is a floodgate, and is a drawbridge. Red ones are connected to input A, green ones to input B and blue ones to input C.

NOT[edit]

^
X
#

AND[edit]

X
X
^
# #

OR[edit]

X X
^
#

XOR[edit]

This is not as straightforward as the previous ones. The true expression is the following: (A and not B) or (not A and B). The false expression: (A and B) or (not A and not B).

So the gates look like the following:

X X
^
X
X
# #

Advantages And Disadvantages[edit]

The basic advantage of this design is that it uses much less water than infinite flow gates. A river is enough to supply even the more complex systems, maybe with an added reservoir to neutralise flow irregularities. Similarly, for the drain, it is enough to excavate a cavern where the water can evaporate.

The disadvantage is that it requires many more resources to construct, and more careful planning, since floodgates tend to block paths.

Faster Version[edit]

The main factors that affect the speed of these gates are the delays of floodgates and bridges, and the switch-off delay of pressure plates. These cannot be eliminated, although designs that seek to replace as many buildings as possible with doors and hatches may minimize delays.

Another factor is the flowing speed of the water. It can be improved. First, the water should flow in from a reservoir a few z-levels higher than the gates themselves (the more the better). This way, water will flow in much faster. Next, replace the pressure plates with up stairs, and make a 2x1 room one z-level above. On one tile is a down stair, and on the other is the pressure plate. Now the water will also flow out faster, or at least the pressure plate will switch off sooner. To minimize latency when deactivated, assuming sufficient inflow, the pressure plate can be set to trigger only on a full 7 units of water. This increases the water consumption a bit, but it still remains relatively low.

Edge Detector[edit]

In some situations, it is beneficial to have logic that triggers during a state transition rather than based on steady states - for example, turning a lever "on" could trigger one brief event while turning the lever "off" would trigger a different event (or possibly the same event).

Z+0
X
X
Z=-1
^ #
^ #

Both pressure plates should trigger on depth 2-6. Link the bottom pressure plate to machines you wish to activate on positive transitions (e.g. stepping onto a pressure plate, or pulling a lever) and the upper pressure plate to machines you wish to activate on negative transitions (e.g. stepping off of the pressure plate, or pulling the lever again), then link the trigger itself (a lever or pressure plate) to both floodgates and both raising bridges.

Each time the input trigger is toggled, the appropriate pressure plate will activate, remain active until the water finishes flowing, then deactivate after about 100 steps.