A lot of us have nostalgia for our childhood toys, and as long as they’re not something like lawn darts that nostalgia often leads to fun upgrades since some of us are adults with industrial-sized air compressors. Classics like Super Soakers and Nerf guns are especially popular targets for improvements, and this Nerf machine gun from [Emiel] is no exception.
The build takes a Nerf ball-firing toy weapon and basically tosses it all out of the window in favor of a custom Nerf ball launching rifle. He starts with the lower receiver and machines a pneumatic mechanism that both loads a ball into the chamber and then launches it. This allows the rifle to be used in both single-shot mode and also in fully-automatic mode. From there, a barrel is fashioned along with the stock and other finishing touches.
If you play with high speed design for long enough, eventually you’re going to run into clock skew and other weird effects. [Robert Feranec] recently ran into this problem and found an interesting solution to visualizing electric fields in a PCB.
A word of warning before we dig into this, for most of the projects we see on Hackaday something like this is completely superfluous. There aren’t many people dealing with high speed interfaces here, and there aren’t many people dealing with 100 Gigabit per second data links, period. That said, it’s not unheard of, and at the very least it’s interesting to look at.
The basics of this video is simulating the signals visually in a differential pair on a (virtual) printed circuit board. The software for this is Simbeor, and [Robert] talked to the founder of the company behind this software after watching a video on simulating electric fields in differential traces. This software does what it says, and is a great illustration of why differential pairs must have the same length.
While this might not be for everyone, it is a fantastic visualization of signals in high-speed design that goes above and beyond what you would expect from a Spice simulation. Even if you’re not doing high-speed design, you may someday and it’s never too soon to get an intuitive understanding of how electrons work.
Designing circuit boards for high speed applications requires special considerations. This you already know, but what exactly do you need to do differently from common board layout? Building on where I left off discussing impedance in 2 layer Printed Circuit Board (PCB) designs, I wanted to start talking about high speed design techniques as they relate to PCBs. This is the world of multi-layer PCBs and where the impedance of both the Power Delivery Network (PDN) and the integrity of the signals themselves (Signal Integrity or SI) become very important factors.
I put together a few board designs to test out different situations that affect high speed signals. You’ve likely heard of vias and traces laid out at right angles having an impact. But have you considered how the glass fabric weave in the board itself impacts a design? In this video I grabbed some of my fanciest test equipment and put these design assumptions to the test. Have a look and then join me after the break for more details on what went into this!
Debugging with printf is something [StorePeter] has always found super handy, and as a result he’s always been interested in tweaking the process for improvements. This kind of debugging usually has microcontrollers sending messages over a serial port, but in embedded development there isn’t always a hardware UART, or it might already be in use. His preferred method of avoiding those problems is to use a USB to Serial adapter and bit-bang the serial on the microcontroller side. It was during this process that it occurred to [StorePeter] that there was a lot of streamlining he could be doing, and thanks to serial terminal programs that support arbitrary baud rates, he’s reliably sending debug messages over serial at 5.3 Mbit/sec, or 5333333 Baud. His code is available for download from his site, and works perfectly in the Arduino IDE.
The whole thing consists of some simple, easily ported code to implement a bare minimum bit-banged serial communication. This is output only, no feedback, and timing consists of just sending bits as quickly as the CPU can handle, leaving it up to the USB Serial adapter and rest of the world to handle whatever that speed turns out to be. On a 16 MHz AVR, transmitting one bit can be done in three instructions, which comes out to about 5333333 baud or roughly 5.3 Mbit/sec. Set a terminal program to 5333333 baud, and you can get a “Hello world” in about 20 microseconds compared to 1 millisecond at 115200 baud.
Rotary encoders are critical to many applications, even at the hobbyist level. While considering his own rotary encoding needs for upcoming projects, it occurred to [Jan Mrázek] to try making his own DIY capacitive rotary encoder. If successful, such an encoder could be cheap and very fast; it could also in part be made directly on a PCB.
The encoder design [Jan] settled on was to make a simple adjustable plate capacitor using PCB elements with transparent tape as the dielectric material. This was used as the timing element for a 555 timer in astable mode. A 555 in this configuration therefore generates a square wave that changes in proportion to how much the plates in the simple capacitor overlap. Turn the plate, and the square wave’s period changes in response. Response time would be fast, and a 555 and some PCB space is certainly cheap materials-wise.
The first prototype gave positive results but had a lot of problems, including noise and possibly a sensitivity to temperature and humidity. The second attempt refined the design and had much better results, with an ESP32 reliably reading 140 discrete positions at a rate of 100 kHz. It seems that there is a tradeoff between resolution and speed; lowering the rate allows more positions to be reliably detected. There are still issues, but ultimately [Jan] feels that high-speed capacitive encoders requiring little more than some PCB real estate and some 555s are probably feasible.
When [JZSlenker] was challenged to find a creative way to destroy a bunch of compact discs that were burned incorrectly, he did not disappoint. He came up with a rather simple but fun contraption that launches the CD’s at high speeds and with a fast rate of fire. He doesn’t share many details about how this machine was built, but the 18 second video makes it pretty obvious how it works.
The CD gun is built mainly from a piece of plywood. This provides a flat base with which to mount the other components. A stack of compact discs is held in place by what appears to be a metal cage that was welded together. An inexpensive angle grinder is used as the propulsion mechanism. The grinding wheel is mounted just in front of the stack of CD’s in a vertical orientation. The wheel must be placed just high enough above the plywood base for a CD to fit in between the wheel and the base. This design is remarkably similar to the Sticker Gun which our own [Brian Benchoff] is building.
Some type of linear actuator is used as the firing mechanism. The actuator is hooked up to a thin piece of metal, cut into an L shape. It almost looks like a reaper tool. When a button is pressed, the actuator fires instantly. This pushes the metal hammer into the CD on the bottom of the stack. The CD is pressed forward into the grinder wheel which then shoots the CD into the air. Based on the below video, it looks like [JZSlenker] is able to fire at a rate of about three CD’s per second with this rig.
This has got to be a super-villain weapon for an upcoming movie, right? Maybe AOL-man?
In high speed digital circuits, fast doesn’t necessarily mean “high clock rate”. [Jack Ganssle] does an excellent job at explaining how the transition time of signals in high speed digital circuits is just as important as the speed of the signal itself. When the transition time is large, around 20 nanoseconds, everything is fine. But when you cut it down to just a few nanoseconds, things change. Often you will get a ringing effect caused by impedance mismatch.
As the signal travels down the trace from the driver and hits the receiver, some of the signal will get reflected back toward the driver if the impedance, which is just resistance with a frequency component, does not exactly match. The reflected signal then heads back to the driver where the impedance mismatch will cause another reflection. It goes back and forth, creating the ‘ringing’ you see on the scope.
[Jack Ganssle] goes on to explain how a simple resistor network can help to match the impedance and how these should be used in circuits with fast transition times, especially where you will be taking readings with a scope. As the scope probe itself can introduce impedance and cause the ringing.