I've created an 18-bit Linear Feedback Shift Register. For those too lazy to click, it's basically a pseudorandom number generator that spits out a stream of bits. Assuming a 5-clock triggers the circuit twice each second, this setup will run for 36 hours before it outputs a duplicate value. (If you want it to run for 100 years before outputting duplicates, feel free to expand my design to 33 bits.)
The RAM is 7 bits wide because any more would require a repeater in the middle of each cell. (2 blocks per D-latch x 8 bits = a 16 block long write-enable line). Each cell is 23x8x11 (IIRC) and the total size of the memory block( not including the data bus connections at each end or the addressing decoders) is 23x32x44
It's hard waiting around for something that you know might never happen; but it's even harder to give up when you know it's everything you ever wanted.
Another vertical 5-clock. This one is 3x2xn, where n is the n-clock desired (a 5-clock is 3x2x5, etc). This has the same cost as designs B and C on the Wiki, and is scalable to any odd n-clock desired. To do so, make the upward torch stack have an even amount of torches (not including the top wall-mounted torch that starts the downward signal). A clock made this way will be a (2t+1) clock, where t is the number of torches in the vertical stack. It's really simple and it's probably been discovered before, but here's to variety! (no schematic, this is really simple to understand from the pictures)
A 5-clock
A 9-clock
Also, this clock is totally enclosable, meaning all the circuitry is contained within the 3x2xn size. No torches or wires are on the outside, so you can tuck it down somewhere and hide it.
*Edit* Just made another one that is 1x6xn-2 at most. Again, n is the n-clock you want. This one scales differently though. For example, a 5-clock is 1x6x3, but a 7-clock is only 1x5x5. A 9-clock is a 1x6x7. You can configure one of the components differently in every other clock. I might post that one later.
I don't know if I'm the OP you mentioned in your OP, or if you meant the guy who made the ancient 'redstone logic gates' thread, but either way my sig has two tutorials on redstone that you could put in your other resources section if you're looking for any more. They're forum threads, I'm not spamming for Youtube views :wink.gif:.
Hey, this may be a really dumb question, but what gate would I use for an "override" of sorts?
I want to do something so when input A is on (or off, it doesn't matter), something happens, but when input B is on (or off), the door/thing will stay in a certain position until B is turned off. I've tried a NOR gate, but that just ends up giving B complete control, instead of A operating except when B is on.
tl;dr:
How do I get A to operate normally but stop working when B is on?
Hey, this may be a really dumb question, but what gate would I use for an "override" of sorts?
I want to do something so when input A is on (or off, it doesn't matter), something happens, but when input B is on (or off), the door/thing will stay in a certain position until B is turned off. I've tried a NOR gate, but that just ends up giving B complete control, instead of A operating except when B is on.
tl;dr:
How do I get A to operate normally but stop working when B is on?
You need an "and" gate for that. Then inverse B if you want to change the state it is in for lock/unlock.
Hey, this may be a really dumb question, but what gate would I use for an "override" of sorts?
I want to do something so when input A is on (or off, it doesn't matter), something happens, but when input B is on (or off), the door/thing will stay in a certain position until B is turned off. I've tried a NOR gate, but that just ends up giving B complete control, instead of A operating except when B is on.
tl;dr:
How do I get A to operate normally but stop working when B is on?
He's already said a NOR doesn't work... (i think) he requires it to remember the last switch state before he disables it.
Use a D Flip Flop, A goes into D and !B goes into C.
[edit]Only wiki designs A, C and D work. B will not.
I think he's looking for what we provided, based on his "tl;dr". It seems like he wants input A to work as long as an override switch hasn't been activated. Once the override switch is activated, the output will not change no matter what A is, until the override is turned off.
Thanks, guys. I think an and gate will work, actually. I must have been looking for too complicated of a solution.
BUT GUESS WHO HAS A NEW PROBLEM?
This one's more straightforward, but probably more complicated. I want to make an alarm. When someone steps on a pressure plate, I want a torch to blink until I hit a switch to shut it off. Can anyone help?
Thanks, guys. I think an and gate will work, actually. I must have been looking for too complicated of a solution.
BUT GUESS WHO HAS A NEW PROBLEM?
This one's more straightforward, but probably more complicated. I want to make an alarm. When someone steps on a pressure plate, I want a torch to blink until I hit a switch to shut it off. Can anyone help?
Easy.
The easiest way to do it is to use a clock and an RS Latch.
Build a clock and an RS latch. Run the pressure plate's output to the RS Latch. Hook the ~Q of the latch into the clock. Be sure to use the ~Q (inverse Q, the output that is HIGH when the latch is not set). This way, the clock will stay off until the pressure pad is triggered, and will stay on as long as the latch is SET. Whenever someone steps on the pressure pad, the RS Latch is SET which starts the clock to flash the alarm. Tada!
After all that, make a reset button that resets the latch, which will consequently turn of the clock until the pressure pad is tripped again.
The problem I was having was getting vertical transmission out of the latch without extending it outward and keeping it 1-wide. Solution?
[]
It keeps the same size (3x3) and allows for inline vertical transmission of ~Q by adding redstone on top of the topmost block and going from there. ~Q can immediately be inverted by placing a torch instead of redstone on top if you want Q instead.
This came about because I needed a way to send a signal back to an indicator torch in my minecart station that told which destination was currently chosen. Using Design H RS Latches forced me to extend backward and come back over the top of the latch- inconvenient. With this, I can immediately head back to my indicator torch easily.
Anyways, figured this could help someone else out that may have had a similar issue.
I had made myself a 2-to-4 bit decoder that takes 2 lever inputs to connect to 4 output (4 direction indicator in my minecart station)
Now I want to change it into only 1 button input whereby each time i press the button it will cycle the output to north-east-south-west-north.
I took a look at the T flip-flop and think this would be the component for my 1st bit. Now how am I going to implement the 2nd bit ? Is it I click the button twice then only change, which is when the 1st bit turn back into 0?
EDITED: Nvm I think I figure out. the output of the 1st TFF is feed to 2nd TPP input thus the 2nd output will toggle upon 2 button cycle. I just need to compact them.
I had made myself a 2-to-4 bit decoder that takes 2 lever inputs to connect to 4 output (4 direction indicator in my minecart station)
Now I want to change it into only 1 button input whereby each time i press the button it will cycle the output to north-east-south-west-north.
I took a look at the T flip-flop and think this would be the component for my 1st bit. Now how am I going to implement the 2nd bit ? Is it I click the button twice then only change, which is when the 1st bit turn back into 0?
EDITED: Nvm I think I figure out. the output of the 1st TFF is feed to 2nd TPP input thus the 2nd output will toggle upon 2 button cycle. I just need to compact them.
That's exactly what I was going to suggest as I read your post. Good that you figured it out yourself. That's called a frequency divider, by the way.
Also, I need to know what to put in the OP as far as gates go. Which gates are good candidates? The smallest? Easiest? Let me know what you think needs to be put in the OP and it will probably end up there. Be sure to leave a schematic and any more information you can provide.
Also, I need to know what to put in the OP as far as gates go. Which gates are good candidates? The smallest? Easiest? Let me know what you think needs to be put in the OP and it will probably end up there. Be sure to leave a schematic and any more information you can provide.
Links to posts, IMO. I'd maintain lists of the following:
[*:17tpod12]Full-blown machines like RAM arrays, shift registers and adders. You should probably link all of these that come up, since rarely is one design objectively better than another.
[*:17tpod12]Common building-blocks like D/T/JK flip-flops, clock generators and decoders. List a variety of these, keeping in mind that different sizes, shapes and behaviors may be desired for a particular project. That said, you don't need to list every single flip-flop someone makes; if someone makes an optimization that doesn't take anything away from the precursor design, just list the improvement.
[*:17tpod12]Small components like gates and latches. These are usually beat to death, but sometimes there's a need for a specific variation on a gate. List common versions and alternatives.
[*:17tpod12]Redstone tricks/quirks like the North-South repeater, vertical transmission methods and torch burnout behavior.
[*:17tpod12]Tutorials for players of varying skill levels. Be sure to include links to tutorials that aren't purely about Redstone; important topics include minecarts, TNT, doors and water/lava redirection. These are things that can be controlled by these wonderful Redstone creations.
Start indexing the posts in this thread, and then start pulling from other threads. (Maybe write yourself a note with the reply number you stopped at in each thread.)
Those are just my thoughts, though. Proceed as you wish.
That's a pretty definitive list, and I think it's manageable.
Now the question is; pictures, or links to pictures? I'm thinking for latches/FFs/other common stuff, I'll embed some pictures. But big stuff and big animations will probably have to be linked to for the sake of load-time.
I whipped this up:
Two vertical RS Latches. The first one is Design H in the Wiki, and the second one is one that I came up with (as far as I know). The lower block in Design A can be pushed back any arbitrary length and the middle block of Design B can be stretched outward any arbitrary length to suit your needs. Of course, the inputs are not isolated, so S is also Q and R is also ~Q.
Schematic: link
Additional entropy might be provided by torch burnout or pressure plate input.
A 5-clock
A 9-clock
Also, this clock is totally enclosable, meaning all the circuitry is contained within the 3x2xn size. No torches or wires are on the outside, so you can tuck it down somewhere and hide it.
*Edit* Just made another one that is 1x6xn-2 at most. Again, n is the n-clock you want. This one scales differently though. For example, a 5-clock is 1x6x3, but a 7-clock is only 1x5x5. A 9-clock is a 1x6x7. You can configure one of the components differently in every other clock. I might post that one later.
I'll link to yours, too. Thanks.
I want to do something so when input A is on (or off, it doesn't matter), something happens, but when input B is on (or off), the door/thing will stay in a certain position until B is turned off. I've tried a NOR gate, but that just ends up giving B complete control, instead of A operating except when B is on.
tl;dr:
How do I get A to operate normally but stop working when B is on?
You need an "and" gate for that. Then inverse B if you want to change the state it is in for lock/unlock.
Blobfish's Emote Compendium
A is on the left, B is on the right.
*EDIT*
Eff'ing ninja.
I think he's looking for what we provided, based on his "tl;dr". It seems like he wants input A to work as long as an override switch hasn't been activated. Once the override switch is activated, the output will not change no matter what A is, until the override is turned off.
That's what I gathered, at least.
BUT GUESS WHO HAS A NEW PROBLEM?
This one's more straightforward, but probably more complicated. I want to make an alarm. When someone steps on a pressure plate, I want a torch to blink until I hit a switch to shut it off. Can anyone help?
Easy.
The easiest way to do it is to use a clock and an RS Latch.
Build a clock and an RS latch. Run the pressure plate's output to the RS Latch. Hook the ~Q of the latch into the clock. Be sure to use the ~Q (inverse Q, the output that is HIGH when the latch is not set). This way, the clock will stay off until the pressure pad is triggered, and will stay on as long as the latch is SET. Whenever someone steps on the pressure pad, the RS Latch is SET which starts the clock to flash the alarm. Tada!
After all that, make a reset button that resets the latch, which will consequently turn of the clock until the pressure pad is tripped again.
[]
AKA Design H on the Wiki (RSNOR Latch).
The problem I was having was getting vertical transmission out of the latch without extending it outward and keeping it 1-wide. Solution?
[]
It keeps the same size (3x3) and allows for inline vertical transmission of ~Q by adding redstone on top of the topmost block and going from there. ~Q can immediately be inverted by placing a torch instead of redstone on top if you want Q instead.
This came about because I needed a way to send a signal back to an indicator torch in my minecart station that told which destination was currently chosen. Using Design H RS Latches forced me to extend backward and come back over the top of the latch- inconvenient. With this, I can immediately head back to my indicator torch easily.
Anyways, figured this could help someone else out that may have had a similar issue.
I had made myself a 2-to-4 bit decoder that takes 2 lever inputs to connect to 4 output (4 direction indicator in my minecart station)
Now I want to change it into only 1 button input whereby each time i press the button it will cycle the output to north-east-south-west-north.
I took a look at the T flip-flop and think this would be the component for my 1st bit. Now how am I going to implement the 2nd bit ? Is it I click the button twice then only change, which is when the 1st bit turn back into 0?
EDITED: Nvm I think I figure out. the output of the 1st TFF is feed to 2nd TPP input thus the 2nd output will toggle upon 2 button cycle. I just need to compact them.
Got it myself with a 5-clock and RS NOR latch.
That's exactly what I was going to suggest as I read your post. Good that you figured it out yourself. That's called a frequency divider, by the way.
Also, I need to know what to put in the OP as far as gates go. Which gates are good candidates? The smallest? Easiest? Let me know what you think needs to be put in the OP and it will probably end up there. Be sure to leave a schematic and any more information you can provide.
Links to posts, IMO. I'd maintain lists of the following:
[*:17tpod12]Full-blown machines like RAM arrays, shift registers and adders. You should probably link all of these that come up, since rarely is one design objectively better than another.
[*:17tpod12]Common building-blocks like D/T/JK flip-flops, clock generators and decoders. List a variety of these, keeping in mind that different sizes, shapes and behaviors may be desired for a particular project. That said, you don't need to list every single flip-flop someone makes; if someone makes an optimization that doesn't take anything away from the precursor design, just list the improvement.
[*:17tpod12]Small components like gates and latches. These are usually beat to death, but sometimes there's a need for a specific variation on a gate. List common versions and alternatives.
[*:17tpod12]Redstone tricks/quirks like the North-South repeater, vertical transmission methods and torch burnout behavior.
[*:17tpod12]Tutorials for players of varying skill levels. Be sure to include links to tutorials that aren't purely about Redstone; important topics include minecarts, TNT, doors and water/lava redirection. These are things that can be controlled by these wonderful Redstone creations.
Start indexing the posts in this thread, and then start pulling from other threads. (Maybe write yourself a note with the reply number you stopped at in each thread.)
Those are just my thoughts, though. Proceed as you wish.
Now the question is; pictures, or links to pictures? I'm thinking for latches/FFs/other common stuff, I'll embed some pictures. But big stuff and big animations will probably have to be linked to for the sake of load-time.
I whipped this up:
Two vertical RS Latches. The first one is Design H in the Wiki, and the second one is one that I came up with (as far as I know). The lower block in Design A can be pushed back any arbitrary length and the middle block of Design B can be stretched outward any arbitrary length to suit your needs. Of course, the inputs are not isolated, so S is also Q and R is also ~Q.
Blobfish's Emote Compendium