Gregory's Serverhowever, higher frequencies will see your puny disconnected shield and (due to parasitic capacitance) jump right across anyway!
|
24 comments
 having an RF current flowing isn't necessarily bad. because of the skin effect, this noise current flows on the outside of the braided shield in the cable while your common mode signal current flows on the inside of the braided shield, and they don't interact (at high frequencies) but if you really don't want those RF currents (perhaps your cable just happens to be the right length to form a monopole antenna to radiate interference) you can add a ferrite bead around the cable. this causes common mode currents to see a higher impedance at high frequencies, and this reduces the current. in my experience with complex interconnected systems, this can turn into a game of whack-a-mole as the RF return current will find a path back (oh yes it will!) using a different route--and it may be a less desirable one! what about the thing with the shield ground tied with an inductor in series? this is part of a *system* of multiple units connected together, and it's called a hybrid ground. with a capacitor in series for each device, your grounding system allows RF return currents to take the shortest path but forces lower frequency currents to go through some other path, presumably a single point ground (audio folks like this!) the inductor approach is less common because RF currents like to couple through parasitic capacitances (as we discussed before), so it's tough to control, but this method gives you a multipoint ground at low frequencies and a single point ground at high frequencies. say we've connected the shield to our board ground. we can still improve on this! page 486 of the book sets up a nice concept relevant to our problem at hand. create a "clean" I/O ground area on the PCB that acts like an extension of the chassis. put your EMI filter parts here. the idea is to direct any EMI on the signals ➡️ to the shield ground return. incidentally this approach does another good thing -- putting all the connectors on one side of the board. we're trying to build a circuit that plugs into a USB jack, not a dipole antenna! here's a fantastic real-world example of this design technique. here's a Macintosh 512K motherboard. with a bright light behind it, you can see the divide between the "clean" IO ground and the "dirty" logic ground. (they did break the rule slightly with the keyboard connector on the front, but they've also extended the cut in the ground plane along the right edge of the board.) naturally the topic gets even more complex when you add in ESD protection. some folks mentioned adding a "bleeder" resistor in parallel with the coupling capacitor. i'm leery of adding series impedance to limit the current, typically you want that ESD out of there without giving it opportunities to current share with sensitive signal returns. also it turns out that many resistors can get destroyed by an ESD pulse, so there's another good reason to avoid this approach. you might be OK if you add a shield ground ring around the board, near any gaps in your enclosure, so that ESD strikes will hit that rather than your main board ground. you should also protect any buttons or switches. for example, some tact switches come with a shield ground ring that goes to a 5th pin, which should be tied to your shield ground. earlier i said that the tl;dr for hobbyists is to just tie the shield to your board ground. for professionals who aren't experts in EMI but work for big companies who have EMI folks on staff, you might just want to add a generic "series component" between the two grounds and populate it with a 0 ohm jumper. the EMI people (during precompliance testing) may need to play around with that connection, and this makes it easy. @tubetime  @tubetime Ooooh, that's what these lines on PCBs are for. Makes sense.  @tubetime I honestly think this is ill-advised, because it makes the very signal lines whose signal we did this whole connection for cross reference levels and hence become noisy at the receiver. That's not really an option for single- ended signals, and the differential ones you would encounter today would be very unhappy about the break in impedance and the complete loss of current return path (much more energy in the E-field between diff traces and their joint adjacent ground plane than … @funkylab yeah the book advises building a ground "bridge" directly underneath high speed traces that cross over. they have high frequency return currents that take the path of least inductance (directly underneath) and if you have a ground cut underneath then the loop area increases, and you start radiating... @tubetime @funkylab I think you’re right. Just remember that “low frequency” that does cross the ground plane better have very slow rise/fall times. I could not find the >1GHz EMI that was radiating from my board. Long story short, it was a 32kHz oscillator with a 800fs rise/fall time. In the oscillator manufacturers defense, the datasheet only had a maximum rise time spec. But who would have thought the edges would be that sharp! @MarkAtMicrochip @funkylab you can sorta cheat a bit with high slew rate signals if they have a very long period and if you quasipeak during the EMI scan, but yeah usually high slew rate signals are a problem.  @tubetime Signals crossing a split plane in that example are firing all kind of alarms in my brain. Even if the signal is low freq, rise/fall times in todays electronics can cause EMI problems.   @tubetime Does it ever make sense to add a ferrite bead to 50 ohm coax? For context: I'm a ham. @profoundlynerdy sure, if you're having trouble with common mode noise currents going between equipment. i've had to do it before. it's tough to do it right because usually the RF noise finds another path. |
you'll get this same effect when you connect a capacitor between the shield ground and the board ground. you're now just *choosing* where that RF current will go.