We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

From DC to RF...starting where?

00:00

Formal Metadata

Title
From DC to RF...starting where?
Subtitle
An analog engineer dives into RF circuits
Title of Series
Number of Parts
102
Author
License
CC Attribution 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
This talk will focus on learning and re-learning RF topics, from the perspective of a semi-experienced engineer. We will review rules of thumb, practical experience and the theory of RF and how it all fits together for your next PCB design. This will also be contrasted with best-practices for designing lower frequency circuits and how it all fits together. Starting my engineering career working on low level analog measurement, anything above 1kHz kind of felt like "high frequency". This is very obviously not the case. This talk will go over the journey of discovering and rediscovering higher frequency techniques and squaring them with the low level measurement basics that I learned at the beginning my career. The talk will include a discussion of Maxwell's equations and some of the assumptions that we make when we're working on different types of circuits. Attendees of this talk will find this information useful in the context of RF calculations around cellular, wifi, bluetooth and other commonly available communication methods. CCCamp attendees will walk away knowing a little bit more about how to interact with the elements that power their everyday projects.
29
30
Thumbnail
32:05
53
59
65
81
86
Thumbnail
1:42:59
95
96
Thumbnail
35:58
TelecommunicationChaos (cosmogony)MathematicsKeyboard shortcutSoftware testingMeasurementEuclidean vectorExt functorPacket Loss ConcealmentProduct (business)Rule of inferenceInheritance (object-oriented programming)ModemSource codeKolmogorov complexityFrequencyContent (media)Spectrum (functional analysis)Presentation of a groupRoundness (object)Real numberFrequencyTelecommunicationPhysicalismInformation technology consultingRevision controlLevel (video gaming)Focus (optics)Multiplication signTracing (software)Right angleConnectivity (graph theory)Square numberRule of inferenceGreatest elementDirection (geometry)MereologyCuboidModule (mathematics)Web 2.0PlanningProduct (business)BitSpeech synthesisElectronic design automationElectric power transmissionE-learningDifferent (Kate Ryan album)Cycle (graph theory)VoltmeterWhiteboardGoodness of fitProcess (computing)MathematicsMusical ensembleWindowSoftware testingRegulator geneMeasurementMicrocontrollerComputer hardwareComplex (psychology)ExergieSheaf (mathematics)Wave packetModemFunction (mathematics)Reading (process)2 (number)Connected spaceAnnihilator (ring theory)PlastikkarteNichtlineares GleichungssystemDomain nameGame controllerPower (physics)Ferry CorstenExtension (kinesiology)Operator (mathematics)Range (statistics)TransmissionskoeffizientTime domainArithmetic meanDistanceSimulationIntegrated development environmentOcean currentMobile appJSONXMLLecture/Conference
FrequencyBitCycle (graph theory)Time domainDomain nameRevision controlConnectivity (graph theory)InformationSquare numberDifferent (Kate Ryan album)Online helpMultiplication signRight angleTelecommunicationDiagram
Component-based software engineeringFrequencyMaß <Mathematik>Order of magnitudeOrder (biology)Scale (map)MeasurementLink (knot theory)Physical systemBitPower (physics)Function (mathematics)Order (biology)Connectivity (graph theory)Multiplication signOperator (mathematics)MultilaterationFrequencyTerm (mathematics)MathematicsTelecommunicationOrder of magnitudeAdditionScaling (geometry)outputGroup actionAnnihilator (ring theory)Level (video gaming)Game theoryOcean currentTable (information)Channel capacityPhysical systemRight angleConnected space
Link (knot theory)Power (physics)Wireless LANComputer-generated imageryMereologyPhysical systemTransmitterMeasurementWellenwiderstand <Strömungsmechanik>Maxima and minimaHeat transferSource codeFood energySpektrum <Mathematik>FrequencyMatching (graph theory)Condition numberBounded variationWhiteboardFood energyFunction (mathematics)FrequencyLink (knot theory)Insertion lossWellenwiderstand <Strömungsmechanik>MathematicsToweroutputLevel (video gaming)Noise (electronics)Physical systemSoftwareLogarithmRouter (computing)Scaling (geometry)Cellular automatonCuboidMatching (graph theory)BitMeasurementDifferent (Kate Ryan album)MetreDistanceNetwork topologySet (mathematics)Similarity (geometry)Integrated development environmentRight angleRoutingElectric generatorMassCounterexampleGame theoryDeclarative programmingCASE <Informatik>Point (geometry)Line (geometry)TransmissionskoeffizientSource codeMereologyVariable (mathematics)Source code
Band matrixFrequencySource codeComputer networkWechselseitige InformationSpectrum (functional analysis)MeasurementFunction (mathematics)Food energyFrequencyCalculationDomain nameDifferent (Kate Ryan album)Spectrum (functional analysis)Multiplication signTime domainBand matrixMeasurementSoftwareRevision controlBitRight angleCASE <Informatik>Source codeMathematicsQuicksortArithmetic meanGreatest elementLine (geometry)Computer animation
FreewareComputer networkMaxima and minimaMeasurementPlot (narrative)Smith chartFrequencyMeasurementScaling (geometry)MereologySoftware testingWellenwiderstand <Strömungsmechanik>Range (statistics)Structural loadRight angleReal numberSpecial unitary groupInsertion lossPoint (geometry)Smith chartGreatest elementVirtual machineBitMatching (graph theory)Degree (graph theory)Different (Kate Ryan album)Information overloadInheritance (object-oriented programming)Visualization (computer graphics)Source code
Smith chartComputer-generated imageryInsertion lossHeat transferPower (physics)Parameter (computer programming)Physical systemReflection (mathematics)Insertion lossCoefficientPower (physics)Smith chartScattering parametersLevel (video gaming)CurvatureRight anglePerspective (visual)Computer animation
Insertion lossCharacteristic polynomialGamma functionNichtlineares GleichungssystemParameter (computer programming)Food energySource codeMeasurementComponent-based software engineeringWhiteboardData storage devicePower (physics)Plane (geometry)FrequencyComputer-generated imagerySheaf (mathematics)Wellenwiderstand <Strömungsmechanik>Range (statistics)Complex (psychology)Clique-widthTrailRevision controlConnectivity (graph theory)Link (knot theory)Ocean currentInductive reasoningHookingField (computer science)Complex (psychology)CalculationDimensional analysisNichtlineares GleichungssystemGamma functionInformationMathematicsTracing (software)Greatest elementUltraviolet photoelectron spectroscopyCurvatureGroup actionBitMetrePower (physics)TrailMeasurementSurfaceCharacteristic polynomialPoint (geometry)Computer hardwareWhiteboardPer milStanding wavePerspective (visual)Sound effectOperator (mathematics)FrequencyTelecommunicationSpektrum <Mathematik>WordRight angleConstructor (object-oriented programming)Disk read-and-write headBuildingComputer animation
Wellenwiderstand <Strömungsmechanik>Clique-widthTrailNichtlineares GleichungssystemRange (statistics)Complex (psychology)Sound effectPlane (geometry)Data storage deviceComputer-generated imageryParallel portData storage deviceVery-high-bit-rate digital subscriber lineWellenwiderstand <Strömungsmechanik>Sound effectMetreDifferent (Kate Ryan album)Right angleCASE <Informatik>CalculationFrequencyTrailEquivalence relationPlanningGame controllerSeries (mathematics)Parallel portEndliche ModelltheorieInductive reasoningSoftware testingNeuroinformatikArithmetic meanBit ratePoint (geometry)Beat (acoustics)SurfaceChannel capacityXMLProgram flowchart
FrequencyPlane (geometry)LeakRight angleMixed realityTerm (mathematics)Bit rateInductive reasoningComplex (psychology)Channel capacityBlock (periodic table)Different (Kate Ryan album)Cartesian coordinate systemPlanningOcean currentFrequencyPhysicalismArithmetic meanBookmark (World Wide Web)Element (mathematics)MereologyMobile appLecture/ConferenceComputer animation
Drop (liquid)Function (mathematics)Power (physics)Level (video gaming)Normed vector spacePlane (geometry)Right angleFrequencyAreaFood energyElectric currentWellenwiderstand <Strömungsmechanik>Term (mathematics)MeasurementCellular automatonRevision controlTelecommunicationIRIS-TElectronic program guideMixed realityWhiteboardPlanar graphYouTubeComputer programSoftware-defined radioPresentation of a groupSlide ruleTwitterSmith chartCharacteristic polynomialDifferent (Kate Ryan album)Power (physics)Electronic program guidePresentation of a groupInterior (topology)Mixed realityRule of inferencePlanningWhiteboardField programmable gate arrayFood energyNoise (electronics)Field (computer science)DataflowTransmissionskoeffizientSpectrum (functional analysis)Sound effectInductive reasoningChainOcean currentOrder (biology)Point (geometry)Cellular automatonPhysical systemMusical ensembleSoftware-defined radioOpen setSheaf (mathematics)Right angleDebuggerYouTubeBand matrixMultiplication signDirection (geometry)Line (geometry)State of matterHeat transferCASE <Informatik>Hand fanSimilarity (geometry)SoftwareMathematicsStack (abstract data type)GSM-Software-Management AGInformationThermal radiationWide area networkShape (magazine)Film editingFrequencySource codeFunction (mathematics)LengthPerspective (visual)Generic programmingWellenwiderstand <Strömungsmechanik>Very-high-bit-rate digital subscriber lineSlide ruleResultantVideo gameTerm (mathematics)Goodness of fitEvent horizonHacker (term)BuildingUniverse (mathematics)Group actionPhysicalismWave packet1 (number)INTEGRALVideoconferencingWord40 (number)Arithmetic meanBit rateCycle (graph theory)BitLevel (video gaming)InternetworkingComputer animation
TransmissionskoeffizientRoundness (object)Lecture/Conference
VideoconferencingJSONComputer animation
Transcript: English(auto-generated)
for today is going to be about PCB design for RF circuits.
Our next presenter is going to be Chris Gamel. Please welcome him with a big round of applause. All right. Thanks for coming today. So let's talk about some goals to start with. I'm just going to talk about how I got
into the world of working with RF. I'm going to try not to bury you with math. I know that it's a hot summer day, and the last thing you want to do is look at math equations. And then finally, the main thing is to get you some resources as well so you can do what I did and make the mistakes I've made, hopefully a couple fewer. So let's talk about you. Who here has electronics experience?
OK, that's a good crowd. How about RF experience? Couple fewer, couple maybes. Any ham radio operators out there? OK. And then the main thing is you might have some more experience than I do. So that's kind of the main thing I was getting at here is that I want to talk about the struggles
that I've had as I've moved from DC to RF. That was kind of the genesis for this talk. And show you what I've been doing and show you some mistakes I made, and hopefully you make fewer mistakes than I did. So first off, who am I? My name is Chris. I've been doing electronics design for 15 years or so. And I've worked in a bunch of different industries,
semiconductor and industrial and stuff like that. And I really like the industrial side of things. You get to really dig into problems and you don't have the six month cycle that consumer does, although there's a lot of fun problems there too. I also host a show called The Amp Hour, it's an electronics podcast. Been doing that for about nine years now. And I teach people electronics. I obviously teach people the DC side of electronics.
I'm not teaching them RF because I'm learning RF. And that's called contextual electronics. So that's an online course where I teach people how to do some of this stuff. And my past though, I started by working on this. Anyone know what this is? Raise a hand if you know what this is. It's a electrometer. So this is used by material scientists.
Basically you push a thousand volts into a material and then you see how much leakage current's coming through it and it can do down to like femtoamps. So really cool thing. But the thing is it's really slow. Like it's really slow. 10 PLC power line cycles, means you're getting about six readings per second. And inside you're basically, you're integrating everything. And by integrating I mean you're integrating
your measurements over and over again and things are just going really slow. It's truly a DC measurement equipment. So not quite blazing. Of course there are microcontrollers in there. There are some higher speed signal things. But my focus when I got started in electronics, this is my first real electronics job, was doing this kind of thing. And so learning a lot of the DC measurement techniques.
Over time it's also morphed into working with sensors and other power supplies. Obviously everything is a switching regulator these days. But we're not talking about blazing speeds here. We're definitely not talking about RF level frequencies. So what really changed here? And what changed is the world around us. And you've probably all noticed this too, right? We're all wearing wristbands right now
that have Bluetooth on it. It's everywhere. Every product basically throws in a Bluetooth chipset for effectively free or it has some kind of connectivity method because that's a feature. And that means that every product is gonna have RF in it. RF's in everything. Of course RF is actually everywhere as well, right?
We're always surrounded by signals. But every product has it as well. And it's super cheap these days. And so this is the chip I've been talking about lately. This is like a little 433 megahertz transmitter. And it's 15 cents if you buy 100 of them. I mean like, these are levels of cheapness that are like, it's just you could throw it in anything. And so this was starting to motivate me.
And I assume that that's why you're sitting here as well or watching online. You're a little bit motivated as well by some of this stuff. And you don't, you wanna know what to do with it. So you're interested in making things. You're interested in this cheap, wonderful hardware. And you're wondering how to actually integrate it. So let me tell you about my story about how I started with my first RF design.
So the first thing I did was the most obvious thing, which was to copy the app note. And if you're talking to electronics designers, it's a very common thing. It's not, you know, when I started my career, I was always kind of worried about it. Like, oh, I'm just copying. I'm not doing anything original. But so much of electronics these days
is just re-implementing what's there because you're in a rush or you're losing what's working. And even if you put everything in exactly the same, there's still gonna be problems. And I always say that electronics designers, they make their payday by making things work even when they're supposed to be working. So I always guess about 80% or so of a circuit design might be,
you know, it's a reference design. You're copying a switching regulator. You're using a microcontroller and you're copying the stuff there as well. And you're just trying to get it to work. And so that's the first thing I did. And there's a great talk as well by Mike Osman who is here at this conference. He talks about this as well. This is a talk he gave back in 2015 with some rules about how to basically,
you know, copy RF circuit and go through this. So I kind of think about my talk as an extension of that talk. Some of his rules were using four layers, using integrated components, trying to get everything as 50 ohms, following the manufacturer recommendations that's effectively copying the example circuits, and then routing RF first. I think these are all really good rules here.
And I did a lot of these. And so let's talk about my first design. So my first design was a cellular module I was working on for a previous employer and had a little microcontroller, had a SIM card on it, and it worked, right? So not much of a story there. It just kind of worked. But why did it work?
That's kind of the main thing we're trying to get at here. Why did this just work out of the box and with simplicity that I was applying to it? You know, I applied those five rules that Mike was talking about. But the main things to know are the module on board, it was pre-matched with the antenna as well that it's plugging in. Effectively, the RF section that I was using was connecting the output of the cellular modem
to a UFL antenna connector. And then I was using an antenna that was already pre-characterized as well. So I had a very, very short distance where I was connecting the output to a port where I was gonna plug an antenna into. I basically minimized my interaction, I kept my RF trace short, and I didn't really worry about it past that
because this was just a test board, but it worked enough for me to be excited about it. You know, kind of keep trying and you need those dopamine squirts to kind of keep going. So can we do this all the time, right? Can we always just keep keeping traces really short? Can we just copy the data sheet? Can we follow those five rules? And the answer is, yeah, maybe. I mean, you might be able to.
You might be able to just integrate components like that, but it really depends on your design goals. It depends on what you're trying to get out of it. It depends on what you're trying to do with your end product. When you're starting to move into a more uncharacterized zone, right? Say you're making a PCB, you wanna make your own PCB antenna where the antenna is built into the board. That's gonna be a little bit harder, right?
You're gonna need to do a little bit more characterization and testing. If you're going from a differential to single-ended, you might have to do some more stuff there and do a bunch more math and use more components, but it's really the complexity of your circuit that's gonna have the most impact on your success in that realm if you're just trying to do that stuff.
Let's talk about, though, why I wanted to learn more about this in the first place. The first one is I'm a consultant. I do designs for people, and the thing that kept me up at night is I was going to just copy the data sheet, do this thing, but then I'm gonna get it to the bench, and it doesn't work, and there's nothing scarier than the thought of being there and just trying to hold your finger here,
and you hope that it works, and you open the window and hope that changes something, and you don't know what you're doing. You're basically cargo cult trying to impact your environment without actually having any control over it, and that was a big fear for me. I didn't wanna be in that situation. That's doubly true when I'm sitting at a compliance test lab, and they're charging $10,000 a day,
and I still don't know what I'm doing, so I wanted to basically be able to understand the underlying because that could really impact the ability to get a product out into the world, and then finally, it's kind of a feel-good one as well. I wanna make sure, obviously, FCC and CE compliance, these are things that, they're testing the same thing that you're not stomping on someone else's bandwidth,
or you're not operating out of range, but that's also something I don't wanna mess up someone else's day because I've got a poorly designed circuit, so a lot of people said that they had RF experience in their crowd, which is great, but I'm gonna assume not everybody does, so we're gonna go through some of the RF concepts that are kind of tricky, and stuff that still trips me up a little bit as well.
First off is the frequency domain. So this is a lot of the things we talk about when we're talking about RF and higher frequency things. We start moving from a time domain to a frequency domain, and this is a topic that I think there's a lot of math behind it, but I promise you not to get too much into it,
so some of it you're gonna have to take on faith. I'm gonna show you, this is a scope trace, so the top one is a square wave. You might have this as like a clock or a similar on-off signal, so you're blinking an LED on and off. What you have there though is you have different frequency components that actually exist within that, and so the bottom part is the actual frequency component
of that square wave, and that doesn't really mean much, and it's really tough when you look at them side by side. They look like they're on the same axis, but they're actually not, right? So take that a little bit on faith, but I also found a great animation, and we'll hope that this plays.
It looks like it's going to. I love this because it's basically showing you the components, is it playing? Yeah, it's playing. So it's showing you the components that actually exist and make up, they basically sum up and make a square wave, right? So this is a simplified version. They make up the square wave, and they exist in these different amounts, right? So the largest sine wave is the most, that's the main frequency that exists within it,
but then there's all these smaller frequencies as well, and you see how that kind of translated to be between the time domain and the frequency domain. We could basically, if we have this information, we can then go and perfectly replicate that same square wave by knowing the frequency information. So this is kind of a tough concept to get your head around, but it is one that will be very, very useful, and I'll talk a little bit more about an instrument
that kind of helps you to visualize this as well. I think that went through a full cycle. Another tricky topic is just kind of components, right? We're trying to squeeze a lot of electronics into a 45-minute talk here, but capacitors, basically, when you're at DC, they're blocking everything, right?
There's no signal that's gonna be going through. As you go up in frequency, the signal's going to basically be able to pass through the capacitor. Again, it's not physically passing through, but it's effectively passing through, and this is a really tough concept to get, but the main thing to know is that the transition between blocking and not blocking happens because of the value of the capacitor itself, right, the capacitance of that component.
In the inverse way, an inductor allows frequencies to pass through at the low frequency, or DC, and it blocks it at a higher frequency as you move up into the RF world, and so these two things kind of play off one another and they interact. Again, this is a lot of electronics theory trying to squeeze into a small talk, but hopefully you'll take some of it on faith.
Another thing is that in RF, a lot of times we're working in log scales, right? So you'll see a lot of decibels, or dB, and dBm, which is a more, dB is a ratio metric, and dBm is more an actual value. But the idea is here that we're operating in orders of magnitude, and that's really important. You'll see an example a little bit later here.
So you'll see a lot of things referred to in dB, and that can, again, be kind of hard to wrap your head around, but it's an important concept because the scale that we're working with of signals, when you transmit a signal and when you receive a signal, it's very, very different in terms of the magnitudes that you have there. As an added bonus, though, you basically,
when you're going through a system, you have different gains going through, right? If you have a 10X gain in something, you have a 20 dB addition to it, right? So if you're starting at a zero power signal and you go through a 10X stage, you have now 20 dB, you put it through another 10X stage, now it's 20 dB plus 20 dB, now you have a 40 dB signal at the output. And so that's kind of nice because it does simplify some of the math
once you get past the confusion thing. Oop, wrong way. Where'd it go? And that's the last thing about this is the power is how we're often gonna be talking about RF circuits is it's not just current, it's not just voltages, those obviously make up power together, but we're gonna be usually talking about power and so that's an important thing to know as well.
When we're looking at RF subsystems, what we're usually talking about is not degrading the signal, right? So if we have gain and that's something that we want to maintain over time, we wanna make sure that the signal is not being interfered with by the things that we introduced to it. So if we have a connector that has minus three dB
of gain, that means that we're making the signal worse on the other side of that connector and that's bad, we wanna make sure we're not doing that. Similarly, if we need to have a output and an input that are not well matched together, and we'll get to that here in a second, that also is gonna degrade some of the signal quality as well. So let's talk about what that signal path looks like here. So on the left side here, we have a TX, we have a radio,
it's transmitting, that's TX, going through a cable, going through an antenna, and yes, there is a little bit of gain in the antenna as well. But you see in the middle here, there's that red sloping line, that's basically as it's floating through the air and going from a CC camp cell tower to your crazy camp phone, there's actually some loss in that. And then again, it hits the antenna on your phone,
there's some gain there, and then there's a cable, and then it's at the receiver. All of these things basically say that you're gonna be either adding or removing a signal by going through these different stages. And the main thing is we wanna make sure that we're not adding any degradation or noise as we're going through our systems.
Just back to that, the logarithmic side of things. So again, to give you the scale difference here, so if you have a link budget that's 100 dB, and that means you have a signal, so what you do is you divide that by 20, there's a five there, you take that 10 to the fifth, I know that's math again, but basically we have a signal that's outputted, if we have one watt signal output at a transmitter,
that means we would be receiving one one hundred thousandth of that at the phone in this example that I gave. And so that's kind of like why we wanna not introduce any other degradation than that, because it's gonna make it less likely that we receive that signal at our phone. How do we get through this? So again, how do we make sure
we don't degrade unnecessarily? Well, what we do is we make sure that we're matching the impedance of these inputs and outputs so that we don't introduce signal degradation. Now this is a new concept when I was moving from DC to RF, now obviously it exists at lower frequencies as well, but we wanna basically, it's much more critical
I think at RF because you are playing with much different impedances as well. Now, one of the baseline things is that you need to have perfectly matched impedances, input and output, so your output might be an amplifier, your input might be an antenna.
You wanna make sure those things are as perfectly matched as you can so you're not introducing unnecessary degradation. So let's talk about a counter example. This would be a bad situation that you'd have here. So you have an ESP32, it's a little tiny Wi-Fi module, and then you have a PCB antenna on board. And those two things are not well matched together. When they're not well matched together,
what's gonna happen? Well, first off, it might not work at all, or you may perceive it not to work at all because you have a Wi-Fi router over here, you have your ESP32 over here, and it's not actually talking to your Wi-Fi router because there's no signal getting from one to the other. So without actually having measurement equipment, you won't actually know what's happening, but to your perception, it's not gonna work.
Another thing, though, is it may work, but it may not work as far as you want it to, right? So it only works if you're within a foot or within a meter, sorry. And it's only gonna, so it, and you expect it to work at 10 meters instead of one meter. And then finally, you're gonna have a less efficient system as well, right?
You're gonna have energy that gets either radiated locally on your board and not radiated towards your Wi-Fi router, or it's just gonna be dissipated as heat. So what is impedance, though, right? So I know I'm jumping around topics a lot here, but what we're trying to do is we're trying to get an output like an antenna, or sorry, an output like an amplifier and an input like an antenna, these two things to be kind of talking to one another.
And we want them to do that by matching their impedance. What is impedance, though? Impedance is basically the, how it lets, how it passes or blocks electromagnetic energy at various frequencies, right? So if we have a 2.4 gigahertz Wi-Fi thing like the ESP, we wanna know that our antenna
is accepting that energy at that frequency the same as our amplifier is outputting that energy at 2.4 gigahertz. You may be thinking, well, why do we have to do this at all, though? Why, shouldn't an antenna just work? Shouldn't all this stuff just work? And the answer is, yeah, it should just work, but that's not how the world works.
The world's imperfect, right? You may remember the iPhone, iPhone 4. It was a well-designed phone, I think it was the 4, but it was a well-designed phone, and when you held it in your hand, though, your hand basically interfered with the antenna. It was changing the impedance of that antenna, and so the matching was all messed up, and you didn't get the same kind of distance
to the tower as you thought you would. This is a similar kind of problem, obviously on a much larger scale. So it's not just a hand. It could also be, is it a more humid day? Is there other stuff in your environment? Is there a tree blocking it? Is there other things that, are you in a city? Are you in the woods? All of these things can basically impact your signal path,
and also on a much closer scale, how your antenna actually works. So even though you may have an antenna that comes out of the box that says, yes, this is definitely 50 ohms, you are good to go, there's manufacturing variability as well, and you basically, you wanna be able to not only measure what's happening, but also then go and modify it
so that they're well-matched up with one another. So as any simple example, a Pi network is one way to normalize your output and your input. In this case, a 1,000 ohm source, which is on the left here, and then you have your little networks of inductors and capacitors, and then your load, in this case, would be an antenna at 100 ohms. You wanna normalize these things at 50 megahertz
and a bandwidth of six megahertz. Basically, there's a bunch of calculations you could do. Again, we're skipping math, but a bunch of calculations you could do, and you can find values that allow you to match up your signal source, in this case, an amplifier, and your antenna, and they work better together. So it's gonna have the maximum output that you can have here.
Let's talk about some of the measurement tools that would get to this point and understand this in the first place. I had mentioned this a little bit, but a spectrum analyzer, this was, again, that animation showing going from a time domain to a frequency domain. So a spectrum analyzer just basically measures the frequency domain. So you put in a signal into your spectrum analyzer,
you're gonna see a chart of the frequencies. And this is really, really useful as you start to look at something like Bluetooth, where it's hopping over all these different frequencies and stuff like that. But really, anything that's outputting its own signal, right, a phone is going to generate its own signal, a, you know, again, a Wi-Fi chip is going to generate its own signal, you then could take that signal
and then look at what it's actually outputting in the spectrum and look at it on a spectrum analyzer. You could also do that, what we were looking at earlier was a slightly different thing, that was an oscilloscope. So that's showing the time domain, and then it has an FFT, which is a measure of the frequency, and it's basically a very tiny software version of what we're looking at here.
Another thing we can get is a VNA. So a vector network analyzer is something now where you're not just, so a phone might be outputting a signal on its own, right, it's got a battery, it's pumping out RF energy. But if you don't have a thing that's actually actively outputting energy and you wanna measure it, you wanna measure the characterization of an antenna by itself, you might want something like a VNA.
And this is where these things get really, really useful. So I've pulled in some of these low-cost VNAs here, and low-cost is very relative. On the top left there is the mini VNA tiny, that's 400 euro. Top right is pocket VNA tiny, 400 euro. And these are like some of the bottom of the line, not the lowest, but pretty low.
Then the depace is the bottom left, that's at 2K, HP 8753A starts at 2K and kinda goes up depending on what you have in there. And you're like, wow, that's really expensive. But, so I've been shopping around for all these things. I've been on eBay and I've been looking at all these different things. And I was really shocked to see a VNA that was about 550 euros. I saw it and I was so excited about it
and I was like, wow, this thing looks beautiful. Definitely gonna bid on it. And then I realized that I actually was looking at the wrong thing. This was $550,000. So, if I could borrow some money from people in the audience, we could definitely go in together on this thing. But what this really, the reason I'm putting this up on here is to show kind of the scale difference, right?
You can go from a 400 euro dollar thing all the way up to a $560,000 thing. And the thing that you're paying for between the two is the one that the 400 euro thing is gonna work more in the 200 megahertz to one gigahertz range. This is showing at a 67 gigahertz range.
It's super, super complicated. All of the things that happen in between, all of the losses that I've already talked about, basically everything has to be perfect in this machine. And I think it's a good example of showing kind of the scale of what has to happen. And what you're really paying for when you buy a VNA is the frequency range, right? It'll scale pretty linearly. As you move up in frequency range, your price is gonna move up as well.
So, personally, I'm targeting things a little bit lower. I wanna do things that are commercially available, 900 megahertz, 2.4 gigahertz, maybe five gigahertz, but those are the ranges that I wanna play with and maybe you wanna play with as well because I wanna play with all the radios that are out there that are cheap and abundant and kind of self-contained.
The last thing you might need is Calkit. And what this does is basically, it gives you an open, a short, and a known load. And basically, you can calibrate the equipment that you have that I showed, right? The VNA, you can go and calibrate that thing. And that's important not only because it gets warm, you're in a warm tent or you're out in the sun or something like that and you're using your VNA. You wanna make sure it's well calibrated at that point.
But you also might have cables in between. You might have a test setup where you have a cable from point A to point B and you wanna make sure that that cable isn't part of your measurement. And that's something that a Calkit can help with as well. So let's talk about some measurements real quick. Again, I know we're on a summer day, we're talking about measurements, how fun. But I think these are really important.
Smith charts are basically, it's basically a collection of measurements in a visualization tool. And so this has things like impedance and reluctance on it. And I'm gonna be honest here, I'm not using Smith charts all that much, but I didn't wanna show it because the VNAs kind of allow you to have these outputs, right? You can go and match things a little bit easier.
A lot of the, when I showed the Rs, sorry, the Cs and the inductors and capacitors that had different values, you can go and find those by using something like a Smith chart. And that's a really powerful thing. VNAs also show you things like S-parameters though. So return loss, insertion loss, power transfer and reflected power. These are all things that basically you can go and characterize your systems with.
So your antenna, your output, maybe you have gain stage. Basically you can use one or two port network analyzer to go and measure these different parameters and characterize your system. And that's really useful for when things don't work. And again, that was one of my big things. Return loss is a very common one.
So this is also known as a reflection coefficient. And basically this is something you might do when you might plug in an antenna here, right? So this is showing an antenna, right? And it's showing that it's reflecting power at most frequencies. And it's a little unintuitive from my perspective. When it's flat at the top, it's saying that's where it's reflecting most frequencies.
But at 2.4 gigahertz, it's actually, there's a bunch of power that's not being reflected back. And it's basically showing that it's tuned for this frequency. This is a way to show that this is a well-tuned antenna. And how narrow or wide that dip is is also gonna show how selective the frequencies are. This also plays into VSWR,
which is the voltage standing wave ratio. This is what a lot of ham radio people use as well when they're characterizing antennas that you can use a little bit more broadly. But here's an antenna here, sorry, here's an equation here. And you see the gamma that's in that equation, that's that funky looking R thing in the equation at the bottom. That is basically the last thing we were looking at here.
Sorry. That is the return loss. And that then plays into VSWR. And it's basically helping you figure out how well matched it is. So basically as you get a lower and lower VSWR, you have a better antenna. Okay, so that was kind of the measurement stuff.
We talked about some of the basics of RF. And now I wanted to kind of transition into like the title of the talk. We needed that build up, all that kind of background information here. But the reason I started thinking about all this in this first place is, why does DC end up kind of change
as you move towards RF? What are some of these assumptions that I've always had as I was doing specifically layouts and new designs and thinking about how I'm gonna put my different components together? How does it all play together? The first one is just that a wire is just a wire. So if I hook up a component over here at A and I put a piece of 24 AWG wire over to B,
that the signal's just gonna get there. And that's obviously not true with DC either. These are all very simplified versions. But it's definitely not true as you move up in the RF region, right? Because every wire is actually an inductor, especially as you move up into higher frequencies. Inductance comes from the magnetic fields that are happening.
As you pass current through a wire, you start to form these magnetic fields here. And it's basically the resistance of the magnetic field as you're moving current through it. So as you try and turn off the current, the magnetic field's now gonna push back and it's gonna spike the voltage effectively. And you may recognize the thing on the right here. If you've ever wrapped a piece of wire
around a screwdriver as a kid and then you attach it to a battery, you make an electromagnet. That's the same kind of idea here. If you look at a lot of inductors, what they look like is coiled wires around some kind of substrate as well. And so the main thing to know is that, yeah, a wire is not just a wire. At DC, it doesn't matter because usually the inductance is low enough
that it's not a huge deal. And there's a pretty practical example here that many people, especially getting started in electronics, will understand. As you're using a breadboard, breadboards usually operate fine. Even up to 10 megahertz, they're operating fine if you're blinking something at 10 megahertz. You're probably not seeing it. But say you're operating a clock at a ATmega328.
That works fine at eight megahertz. But if you're trying to pump it many, many more megahertz than that, you're gonna start to have degradation issues. And that's because of the inductance as you're starting to wire from one point to another. Basically, not just the wires that they show here, but then the strips of metal that are underneath the breadboard as well.
And that brings us to our next thing, which is in DC, of course, I never actually thought this when I was designing stuff in DC, but that PCB construction, the stuff that makes a printed circuit board, the fiberglass and the copper and stuff in there, aren't as important as the components that I put on there. So the resistance of a trace or the inductance of a trace isn't as important as the resistor
that I put on board there. And that is definitely not true as we move up in frequency. So this is a four-layer stack up here. This is showing how you, and it's kind of a side view, so it's kind of hard to see here. But you basically have four layers at the top. You're gonna run all your traces and you have your components actually soldered down on top. If you haven't been to the hardware hacking village,
you can go and see some of the surface mount stuff there. Highly recommend that. But you have traces on the top side. Inside, you should have a ground layer, which is usually the second layer. Then you have signal and power on the third layer. And then you can have more traces on the bottom and also some more ground. So these are kind of the normal stack ups here. But the stack up, the actual dimensions of that stack up, how far one thing is from another,
that's when it really starts to play together much more at high frequencies than it does at low frequencies. Again, these characteristics all exist at low frequencies, but you don't have to worry about them as much. Or you care about them in different ways, I suppose. So as you start moving up in frequencies,
you start to have some more complexities that kind of get introduced here. So this is pretty much the only math that we have to do here. But this is, and it's in a calculator too, so from online, and the links are all here. But say you have a trace that's four mils wide, or 0.1 millimeter. The track is about 50 millimeters long, or about two inches.
And your height above ground, right? So what we're saying is from the top top layer, layer one to layer two, I was looking up just a standard stack of it said it's about 0.2 millimeters. And so basically put all these things in there. That means that track has an impedance, an inductance rather, of 63 nanohenries. And if we take that at 2.4 gigahertz,
that's effectively a one kiloohm resistor, effectively. Again, this is operating at these different frequencies. But the idea here is that that actually is a more significant amount of impedance than you would have normally thought from just having a wire. If a wire was just a wire, that wouldn't be a problem, right? You assume that it's zero ohm, the ideal case.
It is definitely not the ideal case though. So first off, it's very important to note that yes, your ground plane should always be right below where you're running your RF signals. That's very, very important. You need to define that as well. And you need to pay attention when you're buying a PCB as well. So this is a stack up from JLC.
And this is showing that 0.2 millimeters between the top layer, the top layer copper, and the next layer down. And that's important to know that. Not only that, you also need to know the, I think the calculator I was using, it actually assumed the dielectric. But basically, you're setting up these two physical things in the real world, and you need to understand how those things play with one another.
Again, you needed to care about that at DC, but you really need to care about it as you're moving up in frequency for RF circuits. And not even just RF circuits, as you're doing high speed digital, you're also gonna have to worry about it there with controlled impedance and things like that. Okay, another assumption. Not, again, a very simplistic assumption for DC is that a capacitor's there to store charge.
And yes, that is true. But the idea here is that a capacitor isn't just a capacitor, right? And so these are a smorgasbord of different capacitors up on the top left. The top left is through-hole capacitors, and the top right is surface-mount capacitors. The top left, when you have through-hole capacitors, they actually have wires literally attached to them.
That is what those leads are. And again, we've already talked about this. Those are inductors, effectively. The same thing happens, though, at low frequency. You can never really get rid of that inductor. And what we have below there is the equivalent series inductance, the equivalent series resistance, parallel resistance, and then the actual capacitance itself. This is kind of a bulked model of what a capacitor is.
And what happens is, as you start to move up in frequency, you start to see effects that you wouldn't have seen at lower frequency. So at lower frequencies, it just acts like a capacitor, it charges up slowly as you move towards DC. At true DC, a capacitor is just a block in the road. In more practical terms, below 10 megahertz,
it's just gonna charge up at a different rate depending on its capacitance. Well, as you move up into higher and higher frequencies, that inductance starts to really matter. And what happens here is that the impedance, which is a complex mix of inductance and capacitance, that starts to invert as you move past this corner frequency. And so your capacitor, which you thought was a capacitor,
that blocking thing is now turning into an inductor, and that starts to really mess up some of your circuits. Your filter might change, your signal path might change, and you really just need to keep that in mind. Another, this is kind of what inspired a lot of thinking for this talk as well. I was looking at layout for how I would do layout for a really sensitive amplifier.
Maybe you wanna make sure that it's nice and you have ground planes around it, that's fine, that's a lot of RF as well. But we would actually cut out around the different circuit elements so you wouldn't have currents kind of creeping in, you wouldn't have these different things creeping into the circuit. And I say that with scare tags
because, I mean, yes, that is how it works at DC, but that's not really how it works as you move up in frequency again. So some of these are noise reduction techniques that you might use in analog. You might wanna try and isolate some of your parts of your circuit using physical means, but RF don't care. That's kind of the summary there.
So here's an app note from Hank Zumblin, one of my favorite applications engineers from Analog Devices. And this is what he's showing here. He's showing you basically, you cut out, you see that L there, you're cutting around the precision analog section. And that is less effective when you have high frequencies there. So you need to, basically at low frequencies,
the cutout means that the signals and the noise that you might be generating with a switching supply won't get around the cut. But it basically, as you start to move up in frequency, that same thing has other effects. And so that's like, at high speed, it will treat this as a capacitor and quote unquote travel through to the other side.
But what it's really doing is it's radiating. And what I'm showing here is an antenna that's actually made by cutting a slot in a plane, which is the same thing I was doing. So you could start to, as you cut slots on planes to isolate things, you could also be creating radiation points. You might be failing EMC. You might be pushing some energy into the R spectrum that you didn't think you were. And not necessarily the best idea.
Another assumption here, current follows the path of least resistance. This is kind of a well-known thing, I suppose. But it really is, is it cares about impedance. It doesn't care about resistance. And so what this is showing that, if you have a meandering path here, it's going in this squirrely trace
and it's going through a resistor. The current would flow back to the source directly. But what actually happens, so at DC what happens is that this is true, right? This is the path of least resistance. It might be flowing through a ground plane. It might be flowing through a VCC, something similar like that.
But as you start to move up in speeds, it starts to travel underneath the signal, underneath the trace itself, and that starts to have other impacts as well. So if you started to go through a region of your board that you weren't supposed to be going through, that could have some impacts. And the main thing to know is that, at higher speeds, it takes on complex terms, right?
So the inductance really starts to matter in this case. And so as the inductance matters more, where the signal's gonna travel is going to change as well. And this happens because as, so anyone in the audience remember the right-hand rule? Anyone, physics? Yeah, okay, I have a couple people. So basically this is the right-hand rule in action, right? So as you have current going through a wire, right?
The magnetic field's gonna curl around that wire. But the place where the inductance is gonna be lowest is where that cancels out. So if the current can flow anywhere in the universe, it's gonna wanna flow directly underneath that signal because flowing back underneath that signal,
it's gonna cancel out. I don't have two right hands, unfortunately. It's gonna cancel out the magnetic field as it was flowing that direction, and that's gonna be the best place. So it's gonna flow actually underneath, right underneath that line. Okay, so that was kind of the DC stuff. I had also promised in this talk, how does this all apply to Bluetooth and cellular
and Wi-Fi and LoRa and all the new features that kind of come out here? So I wanted to disambiguate all these things. Basically they're all the same thing. So all of these lessons that I've been learning and hopefully you'll be learning or you've already learned, they all apply because the RF energy, basically as you add antennas and as you add amplifiers and everything else,
they're gonna be operating at different frequencies, but they're going to have the same fundamental rules applied to them. The things that might change are the length of the antennas or the shape of the antennas or the amount of power that you have to put into the system and things like that. But a lot of them are really just brand names. And even more than that, a lot of them are actually software stacks that are on top of radios. That was something that took me a long time as well.
So Bluetooth and Wi-Fi are both 2.4 gigahertz radios. If you didn't know this, a lot of times your phone is actually using the same radio to do Bluetooth and Wi-Fi. That kinda blew my mind when I learned that. And if not the same radio, then possibly the same antenna. Anyways, I wanted to show just some of the frequency ranges we have here.
So again, Bluetooth is running 2.4 gig, Wi-Fi is 2.4 gig and five. LoRa and Sigfox, these are kinda low power wide area networks. 433, 915, 868, depends on where you are in the world and what you're using. GSM and cellular have these multiple frequencies here. But the idea is I wanted to show there's a bunch of set frequencies that you might be dealing with.
A lot of them are either, as GSM goes or cellular goes, a lot of them are spectrum that's been allocated by your local governing body, FCC in the US. Sorry, I don't know the European name here. But the idea is that those are kind of pre-allotted to these different technologies. But then there's the more open ones,
like 2.4 gigahertz and 915 in the states and ISM band and things like that. And the idea is that you're gonna be operating with all of these different frequencies, but the underlying things are the same. So let's talk about some resources that you might wanna look at in order to do what I did, I guess. Some of these are some books that I enjoyed.
A Practical Guide to RF and Mixed Signal. This is interesting because it's from the perspective that people were doing FPGAs for a long time, and now FPGAs have radios going on boards as well, right? And they're moving from an eight-layer board to a 16-layer board because they now need to have the interplay of these different layers. And so I'm coming at it usually from the low-level DC. They're coming at it from the high-speed digital,
and seeing the difference in RF characteristics and what they have to do to their boards is pretty interesting. The other one is just a generic RF circuit design. I enjoy this one. And then the final is Planar Microwave Engineering, Thomas Lee. Thomas is just like a famous guy in the industry. He's a microwave professor out at Stanford, and it's just a really approachable book,
even though there's a ton of math. There's lots of very funny footnotes that helps as you're crunching through math as well. Oh, sorry. Another one is YouTube. I love watching YouTube videos. I think that's kind of the highest bandwidth transfer of information. Alan Wolke is W2AEW. He's got a great channel. That's how I started learning Smith chart things,
and he's a ham radio operator. Tons of other great information there. And then Shahryar, who does the signal path. That's how I found out about one of those VNAs. He has a great review of those, and then he also looks at the 67 gigahertz, $500,000 ones. He, of course, has to give them back at the end. And then finally, a really accessible way to get started for a lot of this stuff,
I think are things like Mike Osman's Grayscott Gadgets HackRF. That's a SDR. And so you just kind of get a feel for what's out in the world. Another one is GNU Radio plus RTLSDR. That's like a $20 thing. And they're actually here somewhere in the camp. I think they're giving a workshop today too. And then there's Analog Devices Pluto.
These are all existing things. You're not gonna be building radios, but you're gonna be interacting with radios on the software side, and that'll probably get you more into the hardware side. So a quick thank you to Jeff Kaiser or Mighty Ohm. He helped me create these slides. And Derek Kozel, who's actually the GNU radio person, did this stuff. And thanks for coming.
So thanks to Chris for a very interesting talk. We have some time for questions. So if you have a question, there's a microphone right over here. You can step up and ask your question. But we also have a question from the internet, apparently.
No, no question from the internet. Okay, question here on the microphone. I have a question. Is it better to run RF through inner layers or outer layers? The question was inner layers or outer layers. I think the main thing is,
as long as it's referenced to ground is the main thing. Inner layers versus outer layers, you're gonna have different characteristics because it's basically an outer layer is dealing with the dielectric of the board and then dielectric of air. So it's gonna have different strip line characteristics. But usually, when I've done this so far at least, it's been real simple. It's been top layer.
Like Mike says in his presentation too, you do that first so nothing's in the way. Usually I think of inner layers. You're doing that because a lot of things are in the way. But I wouldn't wanna go through any vias or anything like that. I wanna just get it as close as possible to the output port and getting it there. So your mileage may vary. Yes, another question.
Yeah, thanks for the talk. Are you aware of any FPGA-like devices that use RF circuits? So the one that I was looking at was the, I think the zinc has an RF front end now. They're not gonna be cheap though. That's the main thing. So I would recommend that.
I'm a big fan of the open tool chain stuff that's happened with Ice 40s. I think there's some of that stuff. Go pop one of those 433 megahertz radios on there. Otherwise though, not really sure about anything. At a certain point though, so that was like a transmitter, right? You're basically pumping data to that. The fact of an FPGA working with a transmitter is,
it's just gonna be pushing data to it. You could do the same with a micro or you could key it in if you wanted, if it could go slow enough, of course. But the main thing is that the transmitter itself is gonna be usually separate from the FPGA. I don't know of any integrated ones, especially not at the lower end where I'm usually looking.
Any more questions? Final question? Okay, if not then please give Chris a big round of applause. Thank you. Thanks for coming.