Talk:Redstone circuits/Clock

Small vertical repeater clock
I just learned a small vertical repeater clock (I think it's a 2-clock) from this video. Output is to the left. I'm going to attach a picture -- can someone with MCSim skills to a diagram for it? --Mental Mouse 15:09, 15 December 2012 (UTC)


 * This circuit would be a good addition to the article -- it's smaller than the others and it's 1-wide (though not tileable) which makes it sufficiently interesting. : )
 * A schematic isn't necessary if a screenshot can illustrate the circuit sufficiently, so consider going ahead and adding the circuit to the article. However, this screenshot could be improved -- you might want to take a look at the style guide I used for creating screenshots for Redstone Circuits.
 * Your picture is a 2-clock, but the torch will burn out unless the repeater is set to at least 2 ticks, making it a 3-clock, so this clock is good for a range of 3 to 5 tick pulses (0.6 to 1.0 second periods). You can toggle this clock on and off with a lever (or other power signal) on any of the four required opaque blocks (you retain smallest circuit volume by attaching a lever underneath the central block, either to it or the block supporting the redstone), by powering the redstone, or by locking the repeater. Output really can be taken from any part of the circuit (except the repeater), not just the left. &mdash;Munin295 &middot; Grid_Book_and_Quill.png Grid_Stone_Pickaxe.png &middot; 18:29, 15 December 2012 (UTC)


 * Hmm. I had one of these running for a couple minutes in my lair, with the repeater on default, and neither torch burned out, but I might not have waited long enough.  I'll look at the style guide -- I already know I'd need to switch back to the default textures.  PS:  I wasn't sure if it was a 2- or 3-clock because it does have two torches along with the repeater.  Thanks for confirming.   --Mental Mouse 20:56, 15 December 2012 (UTC)
 * Got one running now, and I noticed something interesting -- two of the maps visible in the background are flickering, from their usual state to another that shows more (apparently valid) mapped area. (Uploading screenshots now.)  Also, a redstone lamp next to it does not flicker quickly, it stays mostly lit with occasional flickers of darkness. --Mental Mouse 21:14, 15 December 2012 (UTC)
 * ETA: And now it's burning out within a few seconds... not only on minimum delay, but on the next delay setting as well.  Also, the maps should be showing the larger amount of territory, it's the smaller amount that doesn't match the copy I'm carrying. --Mental Mouse 21:20, 15 December 2012 (UTC)
 * The higher torch in the video isn't part of the clock, per se (unless you've got it feeding back into the clock in some way), the video is using it to change the clock's usual 5 ticks on/5 ticks off output (the video's repeater is set to 4-tick delay) into a 1-tick off pulse every 10 ticks (the torch on the bottom turns off but the torch on the top doesn't turn on until a tick later: an incorporated falling edge detector) to make the piston retract and then instantly extend again. My builds only burn out when the repeater is set to 1 tick, in all four orientations (v1.4.5). I can't see any difference in the maps you posted. I think I remember someone else saying that maps in frames don't always update properly -- you may need to pop it out, look at it, wait for the updates to load, and then put it back in the frame (which doesn't explain what's happening, but might fix it). &mdash;Munin295 &middot; Grid_Book_and_Quill.png Grid_Stone_Pickaxe.png &middot; 00:51, 16 December 2012 (UTC)
 * On closer inspection, the flickering maps are changing to a (the same) different, less complete map (which is not map #0, map #0 is one of the flickering maps (and the copy in my hand didn't flicker). I tried popping a couple of them off the wall and putting them back, and saving and reloading, but that didn't help.  It also continued happening after I turned off the clock, so it may or may not be related.  Regarding the clock, that's interesting -- but the lamps I tried stayed mostly lit whichever end I put them at.  --Mental Mouse 02:19, 16 December 2012 (UTC)
 * And... I just looked at it again, and it's behavior seems different (I hate when that happens). Both torches are definitely alternating at roughly 50:50, and lamps match that if the left lamp is a block up -- if it's on the ground, it does stay mostly on-- because it's being lit by two alternating torches!   It is definitely not producing 9:1 pulses that I can see, though I could believe I'm missing them on that second lamp.  Also, the maps are back to normal. --Mental Mouse 02:32, 16 December 2012 (UTC)
 * Redstone lamps take 0 ticks to turn on, but 2 ticks to turn off (even lamps moved by a piston) -- and if the signal turns back on within that time, the lamp won't turn off (try running redstone over a lamp from a short clock -- you'll see the redstone turn off, then the lamp). The two-torch falling edge detector produces a 1-tick off pulse, which isn't long enough to turn a lamp off (or some other redstone components -- you can extend a 1-tick off pulse with a sticky piston moving a block over a torch to power a repeater). But if you power a lamp from the 5-clock itself, not the falling edge detector, it will flash on a 7/3-tick cycle (5 ticks on, 2 more ticks on after the power turns off, then 3 ticks off before the power turns on again). Pistons are a better way to observe the behavior of a circuit since they react instantly to both rising and falling edges (or oscilloscopes can give precise read-outs for non-short pulses).
 * There's a lot of really unintuitive behavior like this in redstone components. Jeb said at Minecon that the Redstone Update will affect the timing of some components, and I'm hoping things like this get fixed (or at least made more predictable). &mdash;Munin295 &middot; Grid_Book_and_Quill.png Grid_Stone_Pickaxe.png &middot; 03:13, 16 December 2012 (UTC)
 * Amen on the fixups... on the other hand, adding a Nether ore sucks when I've already had to explore lots of it to find my fortress. But that's another discussion entirely.... --Mental Mouse 14:42, 17 December 2012 (UTC)
 * Just to note, I've confirmed that this clock still works in 1.5. Also, it can be turned off by a lever on the base block any of the blocks, or by pulling the upper block away with a piston.  (It seems to start fairly reliably when the torch is placed.)  --Mental Mouse 12:02, 16 March 2013 (UTC)

Boat Clock broken?
It appears that the Boat Clock in the video does not work anymore. I'm using 1.4.7 and it doesn't seem to work as shown in the video. Can anyone else confirm?

--Ioncupcake 08:09, 25 January 2013 (UTC)

Better Piston Clock
For anyone who wants to throw this in the article, here's a very simple and controlled piston clock. I actually created another one that requires less room as well, 3 x 5, and if anyone wants me to post it just reply on here. 

199.187.203.27 07:32, 4 February 2013 (UTC)

Hopper Clock
2 hoppers facing each other gives a 4clock, might be useful editing that in.

89.233.84.253 02:43, 27 April 2013 (UTC)
 * Whoops, my goof. You are right, though as it turns out, it's not quite a 4-clock -- I've got one running on an ocilloscope, and it's putting out 4 ticks high but only 3 ticks low. --Mental Mouse 21:17, 27 April 2013 (UTC)

COMPACT Piston Rapid Pulsar
I just made a compact rapid pulsar using pistons and the new Redstone block. It's dimensions are (X x Y x Z) 1x2x1. Pretty compact!

I don't know how to work with the schematics, so I'll just post a screenie.

--Icrawler 03:01, 28 April 2013 (UTC)


 * This is slower than a rapid pulser: it produces a 1 tick on, 2 ticks off pulse. But it is more compact than the 1-wide rapid pulser in the article (the one that looks like a bridge of blocks), so it might find a use.
 * Ideally, images should only be uploaded for articles. If you just want to talk about a new circuit you made, the forums (or reddit) are a better place since you'll get a lot more responses.
 * &mdash;Munin295 &middot; Grid_Book_and_Quill.png Grid_Stone_Pickaxe.png &middot; 04:09, 28 April 2013 (UTC)

Efficient use of the clock multiplier.
I've been looking at the relative efficiencies of extending a repeater loop vs. adding a multiplier, and when to break a multiplier bank into two. The results are a little odd, especially for the latter, so I'm not ready to put them into the article without some feedback. What I've got so far:
 * If you have a 5-repeater loop (20 ticks), it's slightly cheaper to double it with more repeaters than a 2-latch multiplier. If you want to triple it, or if the loop is any longer, the multiplier wins unambiguously.
 * The odder part: Once you have a multiplier with N=3, doubling it by extending the bank is only slightly cheaper than adding a second bank with N=2, but if you want to go much past that, you're better off adding a second bank with N=3.

So it looks like the max-efficiency uber-clock would look like a 5-repeater loop (possibly 6?), followed by a series of three-latch multipliers.

This is just from some pencil-and-paper noodling, not rigorous analysis, I'd appreciate if anyone else would look at it and see if they come to the same conclusions.. --Mental Mouse 13:02, 8 June 2013 (UTC)

Efficient use of the clock multiplier.
I've been looking at the relative efficiencies of extending a repeater loop vs. adding a multiplier, and when to break a multiplier bank into two. The results are a little odd, especially for the latter, so I'm not ready to put them into the article without some feedback. What I've got so far:
 * If you have a 5-repeater loop (20 ticks), it's slightly cheaper to double it with more repeaters than a 2-latch multiplier. If you want to triple it, or if the loop is any longer, the multiplier wins unambiguously.
 * The odder part: Once you have a multiplier with N=3, doubling it by extending the bank is only slightly cheaper than adding a second bank with N=2, but if you want to go much past that, you're better off adding a second bank with N=3.

So it looks like the max-efficiency uber-clock would look like a 5-repeater loop (possibly 6?), followed by a series of three-latch multipliers.

This is just from some pencil-and-paper noodling, not rigorous analysis, I'd appreciate if anyone else would look at it and see if they come to the same conclusions.. --Mental Mouse 13:34, 8 June 2013 (UTC)