hello, I have worked on this for a while then left it there for months, so here it is at last sorry for the wait !
my transmitter/decoder duo. If yo uhave any questions, post up on my forum. also, you may join my server here : lazserver.com
that's pretty compact nicely done. I think possible one of the most compact single wire transmitters I have seen.
It's not new however and for such a system people tend to prefer speed to compactness I think people have managed to get it down to 1 tick pulses a while back using pistons.
I agree, though this was meant for very basic use, so the size of it was really the only thing I really had to work on, I could get it to work with pistons at 1 tick, would probably take up 1-2 blocks more on one side wich is acceptable. Thanks for the feedback ^^ also, you have some pretty nice circuits of your own, very nice stuff :biggrin.gif:
Piston based decoders are often unreliable when operating at 1 tick. Redstone is not meant to propogate through repeaters and torches when its only a 1 tick pulse. After discovering this I made a 4 tick transmitter and receiver that does not require a separate write for the write signal. Because the write signal is 4 ticks, it never fails, even when rotated and flipped in worldedit. On the rdf, we are using groups of 3 these to send data at a rate of 1 byte per second, which is Faster than any machine can actually interface with the transmitter and receiver. Using these, we have made a fifo serial buffer that allows us to send data from three machines at almost the exact same time, and receive them by a single machine with ONE input, with no data loss. This serial buffer operates at a speed that is too fast for the devices, and we
Will actually need to slow it down.
It will be the basis of our internet. Credit to idenoh for his parallel buffering system, credit to me for my serial transmission, and credit to us for integrate the two to be able to send data serially from two machines down a single wire at the same time and be received by a single machine with one input
Piston based decoders are often unreliable when operating at 1 tick. Redstone is not meant to propogate through repeaters and torches when its only a 1 tick pulse. After discovering this I made a 4 tick transmitter and receiver that does not require a separate write for the write signal. Because the write signal is 4 ticks, it never fails, even when rotated and flipped in worldedit. On the rdf, we are using groups of 3 these to send data at a rate of 1 byte per second, which is Faster than any machine can actually interface with the transmitter and receiver. Using these, we have made a fifo serial buffer that allows us to send data from three machines at almost the exact same time, and receive them by a single machine with ONE input, with no data loss. This serial buffer operates at a speed that is too fast for the devices, and we
Will actually need to slow it down.
It will be the basis of our internet. Credit to idenoh for his parallel buffering system, credit to me for my serial transmission, and credit to us for integrate the two to be able to send data serially from two machines down a single wire at the same time and be received by a single machine with one input
Sounds full of quirks. After fiddling with such systems for such a long time, I think I could find a few flaws to your "internet" though it must serve your purpose well. However my contraption also works flawlessly for what/how it is supposed to be used. No data lost here man, just a couple bits travelling a wire in one direction, like a control pannel. Btw I'm the one who posted under Moz's username my account was not working for some reason
Sounds full of quirks. After fiddling with such systems for such a long time, I think I could find a few flaws to your "internet" though it must serve your purpose well. However my contraption also works flawlessly for what/how it is supposed to be used. No data lost here man, just a couple bits travelling a wire in one direction, like a control pannel. Btw I'm the one who posted under Moz's username my account was not working for some reason
No quirks. if you happen to ever be on the rdf you are welcome to try it out. But don't come trashing what I say when you have never seen it. The fastest piston based transmitter and receiver were developed on this server and I tried as hard as i could to use it but it simply want reliable for long distance transfer and the speed, which was the source of the unreliability was unnecessary anyways because none of our cpus could transfer 16 bits to a register ever 4 seconds.
I'm just offering my experience. Fast serial transfer is as unnecessary as the device that has to transfer the incoming data makes it. Its cool to send data serially super fast. But lets talk about practicality. Serial transmission is best for long range bussing, where transmission time is large compared to conversion time.
No quirks. if you happen to ever be on the rdf you are welcome to try it out. But don't come trashing what I say when you have never seen it. The fastest piston based transmitter and receiver were developed on this server and I tried as hard as i could to use it but it simply want reliable for long distance transfer and the speed, which was the source of the unreliability was unnecessary anyways because none of our cpus could transfer 16 bits to a register ever 4 seconds.
I'm just offering my experience. Fast serial transfer is as unnecessary as the device that has to transfer the incoming data makes it. Its cool to send data serially super fast. But lets talk about practicality. Serial transmission is best for long range bussing, where transmission time is large compared to conversion time.
Don't get all offended now :tongue.gif: I'm just giving you my concerns about such a setup.
my transmitter/decoder duo. If yo uhave any questions, post up on my forum. also, you may join my server here : lazserver.com
I agree, though this was meant for very basic use, so the size of it was really the only thing I really had to work on, I could get it to work with pistons at 1 tick, would probably take up 1-2 blocks more on one side wich is acceptable. Thanks for the feedback ^^ also, you have some pretty nice circuits of your own, very nice stuff :biggrin.gif:
Pistons were not out when I made this one though :tongue.gif:
Will actually need to slow it down.
It will be the basis of our internet. Credit to idenoh for his parallel buffering system, credit to me for my serial transmission, and credit to us for integrate the two to be able to send data serially from two machines down a single wire at the same time and be received by a single machine with one input
Sounds full of quirks. After fiddling with such systems for such a long time, I think I could find a few flaws to your "internet" though it must serve your purpose well. However my contraption also works flawlessly for what/how it is supposed to be used. No data lost here man, just a couple bits travelling a wire in one direction, like a control pannel. Btw I'm the one who posted under Moz's username my account was not working for some reason
No quirks. if you happen to ever be on the rdf you are welcome to try it out. But don't come trashing what I say when you have never seen it. The fastest piston based transmitter and receiver were developed on this server and I tried as hard as i could to use it but it simply want reliable for long distance transfer and the speed, which was the source of the unreliability was unnecessary anyways because none of our cpus could transfer 16 bits to a register ever 4 seconds.
I'm just offering my experience. Fast serial transfer is as unnecessary as the device that has to transfer the incoming data makes it. Its cool to send data serially super fast. But lets talk about practicality. Serial transmission is best for long range bussing, where transmission time is large compared to conversion time.
Don't get all offended now :tongue.gif: I'm just giving you my concerns about such a setup.
You mean, improve on my design? Sure, come along I'll let you on anyday. Lazserver.com is where you can apply :tongue.gif: