What Every PCB Designer Needs To Know About Track Impedance With Eric Bogatin

PCB design starts off being a relatively easy affair — you create a rectangular outline, assign some component footprints, run some traces, and dump out some Gerber files to send to the fab. Then as you get more experienced and begin trying harder circuits, dipping into switching power supplies, high speed digital and low noise analog, things get progressively more difficult; and we haven’t even talked about RF or microwave design yet, where things can get just plain weird from the uninitiated viewpoint. [Robert Feranec] is no stranger to such matters, and he’s teamed up with one of leading experts (and one of this scribe’s personal electronics heroes) in signal integrity matters, [Prof. Eric Bogatin] for a deep dive into the how and why of controlled impedance design.

RG58 cable construction. These usually are found in 50 Ω and less commonly these days 75Ω variants

One interesting part of the discussion is why is 50 Ω so prevalent? The answer is firstly historical. Back in the 1930s, coaxial cables needed for radio applications, were designed to minimize transmission loss, using reasonable dimensions and polyethylene insulation, the impedance came out at 50 Ω. Secondarily, when designing PCB traces for a reasonable cost fab, there is a trade-off between power consumption and noise immunity.

As a rule of thumb, lowering the impedance increases noise immunity at the cost of more power consumption, and higher impedance goes the other way. You need to balance this with the resulting trace widths, separation and overall routing density you can tolerate.

Another fun story was when Intel were designing a high speed bus for graphical interfaces, and created a simulation of a typical bus structure and parameterized the physical constants, such as the trace line widths, dielectric thickness, via sizes and so on, that were viable with low-cost PCB fab houses. Then, using a Monte Carlo simulation to run 400,000 simulations, they located the sweet spot. Since the via design compatible with the cheap fab design rules resulted often in a via characteristic impedance that came out quite low, it was recommended to reduce the trace impedance from 100 Ω to 85 Ω differential, rather than try tweak the via geometry to bring it up to match the trace. Fun stuff!

We admit, the video is from the start of the year and very long, but for such important basic concepts in high speed digital design, we think it’s well worth your time. We certainly picked up a couple of useful titbits!

Now we’ve got the PCB construction nailed, why circle back and go check those cables?

Continue reading “What Every PCB Designer Needs To Know About Track Impedance With Eric Bogatin”

A Basketball Hoop That Never Lets You Brick

With none of the major leagues in any team sport currently meeting, sports fans have a huge void that has to be filled with something. For [Shane Wighton], the machine shop is the place to go when sports let you down, and the result is this basketball backboard that lets you sink every shot every time.

When we first saw this, we thought for sure it would be some overly complicated motorized affair that would move the hoop to catch the basketball, sort of like the dart-catching dartboard we featured some time ago. And while that would be awesome and somebody should totally build that so we can write it up, [Shane]’s hoop dream is a lot simpler mechanically, even if the math needed to determine the proper shape for the backboard was complex. He wrote software to simulate throws from hundreds of positions to determine the shape for the board, which ends up looking like a shallow elliptic paraboloid. The software created a mesh that was translated into CNC tool paths in Fusion 360, and the backboard was carved from blocks of softwood.

The first tests were disappointing; instead of landing every shot, the board seemed to be actively denying them. [Shane] had to puzzle over that for a while before realizing that he didn’t account for the radius of the ball, which means the centroid never actually contacts the backboard. Rather than recalculate and create a new backboard, he just shifted the hoop out from the backboard by a ball radius. With that expedient in place, the setup performed exactly as calculated.

[Shane] may have taken the long road to hoops glory, but we appreciate the effort and the math lesson. And the fact that this ends up being the same shape as some antennas is a plus.

Continue reading “A Basketball Hoop That Never Lets You Brick”

Archimedes Would Have Known Better If He Could Count To A Million

Today is March 14th, or Pi Day because 3.14 is March 14th rendered in month.day date format. A very slightly better way to celebrate the ratio of a circle’s circumference to its diameter is July 22nd, or 22/7 written in day/month order, a fractional approximation of pi that’s been used for thousands of years and is a better fit than 3.14. Celebrating Pi Day on July 22nd also has the advantage of eschewing middle-endian date formatting.

But Pi Day is completely wrong. We should be celebrating Tau Day, to celebrate the ratio of the circumference to the radius instead of the diameter. That’s June 28th, or 6.283185…. Nonetheless, today is Pi Day and in the absence of something truly new and insightful — we’re still waiting for someone to implement a spigot algorithm in 6502 assembly, by the way — this is a fantastic opportunity to discuss something tangentially related to pi, the history of mathematics, and the idea that human knowledge builds upon itself in an immense genealogy stretching back to the beginning of history.

This is our Pi Day article, but instead of complaining about date formats, or Tau, we’re going to do something different. This is how you approximate pi with the Monte Carlo method, and how anyone who can count to a million can get a better approximation of one the fundamental constants of the Universe than Archimedes.

Continue reading “Archimedes Would Have Known Better If He Could Count To A Million”

A Spreadsheet For Guesswork

Ever wish you could guess more precisely? Or maybe just make your guesses look confusingly legitimate? Guesstimate could help.

It uses Monte Carlo simulations to add some legitimacy to the ranges given to it. For example, if you say the cost of lumber for your next project could be between 2 and 8 dollars a piece, you don’t typically mean that it’s equally likely to be any of those numbers. Most people mean that the boards are most likely to be around 3-5 dollars and everything lower or higher is less probable. Using different shaped distributions, Guesstimate can help include this discrepancy of thought into your pseudo-calculations.

It’s a neat bit of code with a nice interface. There is a commercial side to the project for those who want to collaborate openly or pay someone to host it privately. It has a few neat example models for those interested.

Does anyone use anything like this in their daily lives? Is there another similar project out there? This kind of thing is pretty cool!