Actions

User

Difference between revisions of "Carsten Milkau/D-Latch"

From Unofficial Stationeers Wiki

< User:Carsten Milkau
(Using Select Unit and Logic Reader: store the value *to be* stored)
(D-latch: input 1 and 2 of select unit were mixed up in intro)
Line 11: Line 11:
 
|}
 
|}
  
In theory, a single [[Kit_(Logic_Processor)#Logic_Select_Unit|select unit]] can do this (selector input = enable, input 1 = data, input 2 = output, output = output). In practice, this is not possible as the game does not allow it to have its own output as input. However, several constructions using two or more circuits are possible.
+
In theory, a single [[Kit_(Logic_Processor)#Logic_Select_Unit|select unit]] can do this (selector input = enable, input 1 = output, input 2 = data, output = output). In practice, this is not possible as the game does not allow it to have its own output as input. However, several constructions using two or more circuits are possible.
  
 
=== Connectors ===
 
=== Connectors ===

Revision as of 15:57, 17 July 2018

D-latch

A d-latch is a circuit that stores the last value seen at its "data" input while its "enable" input was on.

enabled data previous output output
0 x y y
1 x y x

In theory, a single select unit can do this (selector input = enable, input 1 = output, input 2 = data, output = output). In practice, this is not possible as the game does not allow it to have its own output as input. However, several constructions using two or more circuits are possible.

Connectors

  • Enabled: if 1, store data, else do nothing.
  • Data: input
  • Output: stored value

Using Select Unit and Logic Reader

D-latch using select unit and reader

This d-latch can store any value. It works in two steps:

  1. a select unit determines whether to store the last output or the "data" input using the "enabled" input. i.e.
      if enabled
      then stored = data
      else stored = output
  2. a logic reader mirrors the value to be stored and feeds it back into the select unit so it can circulate (effectively being stored). This would be obsolete if the select unit could read its own output.
      output = stored