- Joined
- Jan 19, 2014
- Messages
- 1,377
- Reaction score
- 646
I've been playing with these two circuits for a while, but I felt like sharing them in laymen would be helpful.
These are basically circuits to count in binary, half adders have two inputs and full adders have three inputs.
Read more in this post.
http://starmadedock.net/threads/volksschiff.8648/page-3#post-252974
These are basically circuits to count in binary, half adders have two inputs and full adders have three inputs.
Read more in this post.
http://starmadedock.net/threads/volksschiff.8648/page-3#post-252974
This one fires at 5Hz. But it can be expanded to accommodate any frequency.
http://starmadedock.net/content/vs-expandable-clock.3067/
It works by having the rotors spin at different speeds initially to get an even delay (see Expandable Clock to read more detailed information). I like this one because it uses no delay blocks, so it has a higher tolerance to server lag, but if it lags too bad, it will still fail and have to be reset to function properly.
The reason I put the four outputs (the two activators on the right *below* the clock and the two flipflops on the left, also *below* the clock) was to indicate which one had the highest speed. It appears that the activator on the bottom right of the picture produces the most ticks per second. It does come with a cost though, because it takes a second to start working, while the flipflop takes half a second.
The rotors I used before rotated at 90 degrees, which was giving me trouble because I either had to cut the speed back, or to try to use some weird delays. I got around this by having the rotors rotate at 135 degrees; just enough to allow a button to turn off.
If you have any questions, ask below.
http://starmadedock.net/content/vs-expandable-clock.3067/
It works by having the rotors spin at different speeds initially to get an even delay (see Expandable Clock to read more detailed information). I like this one because it uses no delay blocks, so it has a higher tolerance to server lag, but if it lags too bad, it will still fail and have to be reset to function properly.
The reason I put the four outputs (the two activators on the right *below* the clock and the two flipflops on the left, also *below* the clock) was to indicate which one had the highest speed. It appears that the activator on the bottom right of the picture produces the most ticks per second. It does come with a cost though, because it takes a second to start working, while the flipflop takes half a second.
The rotors I used before rotated at 90 degrees, which was giving me trouble because I either had to cut the speed back, or to try to use some weird delays. I got around this by having the rotors rotate at 135 degrees; just enough to allow a button to turn off.
If you have any questions, ask below.
I made a small clock. It fires ~4 times a second.
http://starmadedock.net/content/volksschiff-small-clock.3062/
It basically works in a spiral pattern, each button activates the next rail in the sequence. Normally you cant make clocks that well with 45 degree incriments at full speed because it's just too fast. When you stack them though you get their collective time, meaning that the clock takes exactly a full second to get to its *original* state. Activators are funny in that they just record the last input, so it takes half a second to start because all of the buttons going into the activator are turning on, but after that half second buttons start turning off, turning it off and on fairly quickly.
If you have questions, ask below.
http://starmadedock.net/content/volksschiff-small-clock.3062/
It basically works in a spiral pattern, each button activates the next rail in the sequence. Normally you cant make clocks that well with 45 degree incriments at full speed because it's just too fast. When you stack them though you get their collective time, meaning that the clock takes exactly a full second to get to its *original* state. Activators are funny in that they just record the last input, so it takes half a second to start because all of the buttons going into the activator are turning on, but after that half second buttons start turning off, turning it off and on fairly quickly.
If you have questions, ask below.
This is my expandable clock, you can make it fire as fast as you would like it to.
http://starmadedock.net/content/volksschiff-clock.2991/
It works by having the rotors move at different speeds to activate basic clocks sequentially. The speed in this version could be compressed, but I left it uncompressed for demonstrative purposes.
The time it takes for a rotor to get to its destination is inverse relative to max speed. At speed 10/10 (1), the clock takes the base time to move. At speed 10/11, it takes 11/10 the time to move. At speed 10/12 (5/6), it takes 12/10 the time to move. This creates an even delay for the clocks to start. I also have some memory cells in there just so that once the clock is started the rotators cant mess it up.
I'm working on this one, I want to get it to where it doesn't use delay clocks, because those tend to break.
If you have questions, ask below.
Also, Olxinos made an improvement to my clock, the link is here http://starmadedock.net/threads/fastest-and-smallest-clock-you-can-build.8419/#post-124945
I am not converting to this improvement because I am looking to make the clock more stable another way.
http://starmadedock.net/content/volksschiff-clock.2991/
It works by having the rotors move at different speeds to activate basic clocks sequentially. The speed in this version could be compressed, but I left it uncompressed for demonstrative purposes.
The time it takes for a rotor to get to its destination is inverse relative to max speed. At speed 10/10 (1), the clock takes the base time to move. At speed 10/11, it takes 11/10 the time to move. At speed 10/12 (5/6), it takes 12/10 the time to move. This creates an even delay for the clocks to start. I also have some memory cells in there just so that once the clock is started the rotators cant mess it up.
I'm working on this one, I want to get it to where it doesn't use delay clocks, because those tend to break.
If you have questions, ask below.
Also, Olxinos made an improvement to my clock, the link is here http://starmadedock.net/threads/fastest-and-smallest-clock-you-can-build.8419/#post-124945
I am not converting to this improvement because I am looking to make the clock more stable another way.
I don't have pictures of it at the moment, because I'm not at liberty to disclose it from my faction. All I can really say is that wireless logic doesn't have a signal range.
Here's my (horribly inefficient and old) counter. It counts the number of inputs to the activators regardless of which activators are on.
http://starmadedock.net/content/logic-counter.2143/updates
It works with a lot of old mumbo jumbo and half adders until I learned how to use full adders and then it uses full adders. It can count to 128 at the highest version I made. I'm really not that proud of it anymore because it was an interesting system to put together, but it was more brute forced than elegant.
http://starmadedock.net/content/logic-counter.2143/updates
It works with a lot of old mumbo jumbo and half adders until I learned how to use full adders and then it uses full adders. It can count to 128 at the highest version I made. I'm really not that proud of it anymore because it was an interesting system to put together, but it was more brute forced than elegant.
Last edited:
