Memory Toggle

[Falcore55]

I have no idea how the Memory Toggle automation works.  Could somebody that understands it explain how it works please.  Pictures of in-game setups that integrate this would be fantastic.  Thanks.

[Tobruk]

Memory toggle has two inputs (Source, Reset) and one output. The defining characteristics of a memory toggle is that it "remembers" that Source was active until Reset is active, then it reverts to standby again.

It's best to illustrate it on an example.

You want to fill a tank with water only if it is empty and stop if its full. Here, bottom sensor is false, top sensor is false, and so - the output will be false.

If the bottom sensor (SOURCE) sends an active signal (there is no water), the memory toggle will go active and turn on the inlet with water.

Even if the sensor goes off, the memory toggle remembers that the source was active. (this is the point at which the water may be midway through your tank and neither of the sensors is active)

The memory toggle, now, can only go into standby if it is reset by the RESET input (which here means that there's enough water at the top)

Again, even if the RESET input goes inactive, the memory toggle has to be turned on by SOURCE again.

 

[Falcore55]

nice, exactly what I was wanting to know!

[martosss]

Now here are some fun questions:

1. What if you give active signals to both the S and R? S overrides O
   • O => 0.
2. What if you connect S+R? - both the Source and Reset to the same logic signal? Useless
   • O => 0.
3. What if you connect O+R? self-connected NOT gate with "off" control
   • If S = 1,  O - alternates 1/0(same as a NOT gate that has its input connected to the output) 
   • if S =0, O => 0
4. What if you connect S + O + R? Useless
   • S => O
5. What if you connect S + O and keep R separately? Memory switch with active override
   • if S = 1, O => 1
   • if S = 0, O is active until R resets.
     • Basically this overrides the reset switch in case of S = 1 - even if R is active, O will be active

I'm not sure if this will be useful to you, but it sure was useful to me - this shows 2 more potential uses of the memory gate - namely 3 and 5.

Here's a possible use case for 3:

Use a smart battery => memory gate => Not gate => generators - turn them on when battery needs charging, keep them at 50% working speed if battery is sufficiently charged(alternating signal passed to a generator causes it to work at 50% speed). Now why would you want 50% speed instead of turning them off completely? That's what I am trying to answer for myself too. I guess you could want to slow down power generation, but not stop it completely in order to keep a big battery bank charged longer, or you can supply constant consumers(lights and pumps) at 50% power output. I've noticed that you can achieve the same result by just connecting an empty smart battery with both sliders set to 0 to a generator - it halves its power production speed, but the battery stays empty and you need to control it manually. This memory gate setup(3) will allow you to do the same + automation.