13
\$\begingroup\$

I recently came across the concept of "Pin 1 Problem" known in the pro-audio electronics. It seems straightforward at first, but becomes confusing when it comes to grounding. Let me describe the problem from the beginning.

Pin 1 Problem

Many audio engineers believe the Pin 1 Problem is the culprit of various EMI/EMC problems in audio.

Pin 1 Problem

Namely, the Pin 1, shield, of an XLR connector, is often connected to the circuit ground on the PCB. It is argued that a significant amount of RF energy will travel to the PCB and coupled into the circuit ground, rendering the shield/chassis ineffective, making the audio equipment more suspectable to interference problems.

Instead, the designer should try following the AES48 standard specified by Audio Engineering Society: At no circumstance the Pin 1 is allowed to connect the circuit ground (if there is a metal chassis). Instead, Pin 1 should be tied directly at the chassis. The circuit ground and the chassis is still bounded, but at a common star grounding point, not at the XLR connector.

For example, Jim Brown (Chair of the AES Technical Committee on EMC, who I believe is an expert on this topic), describes the problem in Pin 1 Revisited.

Pin 1: wrong example

Fig 1 – This is the classic RF pin 1 problem in a mic. The cable shield goes to the enclosure, but through a wire long enough to have significant inductive reactance at VHF. The drop across the inductance is coupled to the signal zero reference, where it is added to the signal.

Pin 2: correct example

Fig 2 – A circuit configuration that avoids a pin 1 problem. The shield goes directly to the shielding enclosure. Signal reference common also goes to the shielding enclosure, but there is no common impedance.

AES48-2005

I then started reading the full specification of AES48-2005 standard. The standard makes it clear,

AES48-2005

  1. Pin 1 should be tied directly to the chassis, not the circuit ground.

  2. Grounds of all EMI filter circuits that are responsible for blocking noises at the input/output connector (if there is any), should be tied directly to the chassis, not the circuit ground.

  3. The safety ground, chassis ground, and circuit ground is tied at a common star grounding point.

So far so good.

Contradiction

Until I found contradictory practices in digital system. When Henry Ott (The prominent EMC guru in the industry, who I believe is an expert on this topic) is asked about grounding and bounding, his answer was,

Q:

I. I am very much interested in the subject of the proper way to connect the circuit ground to the chassis. We usually have mounting screw holes on the board that connect to the chassis. Should I tie the mounting screw holes to the circuit ground plane or leave them as a chassis ground only and tie it to circuit ground at only one point, say at the power supply? If I connect them to the ground plane should I tie just one to the ground plane (if one, which one), or all of them to the ground plane?

II. A second question involves a mixed-signal PCB, should the chassis ground connect to the analog ground, the digital ground, or be left as a chassis ground and only tied at one point, say at the power supply ground?

A:

I: First I will tell you what you should not do, that is to make a single point connection between the circuit ground and the chassis ground at the power supply.

In most cases, the circuit ground should be connected to the chassis with a low inductance connection in the I/O area of the board. In some cases additional circuit to chassis connections may have to be made, but these are in addition to the one in the I/O area, not in place of it.

The best way to understand this is to consider the circuit ground as a noise voltage generator (as a result of the finite ground impedance and the logic currents flowing through the ground). This ground noise will drive a high-frequency common-mode noise current out the cables and cause them to radiate. If, however, the circuit ground is connected to the chassis in the I/O area, this noise current will be diverted to the chassis, and will not flow out on the cables. This circuit ground to chassis connection must be a very low inductance connection in order to divert the high-frequency noise currents–this usually requires multiple, short connections in the I/O area.

II. When a mixed-signal PCB is involved the circuit to chassis ground connection should normally be made in the digital section of the board, still following the procedure explained in 1.

(emphasis is mine)

Also, in the EE.SE question Should chassis ground be attached to digital ground?, the top answer is,

I've done it several ways, but the way that seems to work best for me is the same way that PC motherboards do it. Every mounting hole on the PCB connects signal gnd (a.k.a. digital ground) directly to the metal chassis through a screw and metal stand-off.

For connectors with a shield, that shield is connected to the metal chassis through as short of a connection as possible. Ideally the connector shield would be touching the chassis, otherwise there would be a mounting screw on the PCB as close to the connector as possible. The idea here is that any noise or static discharge would stay on the shield/chassis and never make it inside the box or onto the PCB. Sometimes that's not possible, so if it does make it to the PCB you want to get it off of the PCB as quickly as possible.

Let me make this clear: For a PCB with connectors, signal GND is connected to the metal case using mounting holes. Chassis GND is connected to the metal case using mounting holes. Chassis GND and Signal GND are NOT connected together on the PCB, but instead use the metal case for that connection.

My reasoning

It seems the grounding/bonding practices are very different in audio and digital systems. Experts from both systems acknowledge that a low-impedance bonding, free from inductive impedance, between the circuit ground and chassis ground is essential, but do not agree on its implementation.

The digital world believes the circuit ground and the chassis should be bounded with a connection in the I/O area of the board, because this connection would be a low-impedance connection. It stops noise radiation, because the noise will be diverted to the chassis. Digital designers also believes one can get the best result using a mesh ground, one can get the best result by using multiple mounting screws to bound the circuit ground to the chassis, and forms a very low impedance connection.

The audio world believes the the circuit ground and the chassis should never be bonded at the audio connector, because this connection would be a high-impedance connection, or create a common impedance path, the existence of this common impedance path makes the device ineffective from shielding itself from high frequency noise. Audio designers also believes one can get the best result using a star ground to eliminate any difference of ground potential.

It seems the frequency of the systems operating on, is the cause of the contradiction. An audio system focus on shielding itself from external interference, and avoiding hum and buzz, but a digital system emphasize on shielding the outside world from its own interference. Thus, low-frequency analog systems should follow the audio EMC practice, but high-speed digital system should follow the digital EMC practice?

Question

  1. Is my own analysis correct?

  2. The AES48 standard only mentions star ground: protective ground of the mains, circuit ground and the chassis should be connected at a common star grounding point. What would happen when I use a mesh ground (like a computer motherboard) to bond the chassis and the circuit ground , is it considered good or bad in audio?

  3. Things are not black-and-while. Nowadays, a professional audio system often contains a high-speed digital system inside as well. In this case, one is forced to choose breaking either the recommended practice of audio system or the digital system. What should I do? Perhaps the digital ground and the analog ground, with their respective connectors, can be treated separately, each follows the best practice of their own world?

Can anyone who have professional experience on both analog/audio and digital system help shedding some light on this problem?

\$\endgroup\$
3
  • 1
    \$\begingroup\$ You need to analyse solutions in the context of the problem they're trying to solve. In audio system, the board is the victim, and there are aggressor signals outside. In the digital world, the board is the aggressor, and the outside world is the victim. Notwithstanding reciprocity between transmitting and receiving gain, does that make a difference? Note also that audio is balanced, but digital systems are single ended. \$\endgroup\$
    – Neil_UK
    Sep 30, 2019 at 11:37
  • 1
    \$\begingroup\$ Don't forget the AES54-1-2008 standard, which says "There shall be no DC connection between the designated shield contact and any conductive shell." 🤦 (It says to make an RF connection between shell and shield, but not a DC/audio/60 Hz connection.) \$\endgroup\$
    – endolith
    Jul 13, 2022 at 18:48
  • 1
    \$\begingroup\$ @endolith That's right. After reading Henry Ott, I think I fully understood it now. Analog audio is low level and low-frequency, hence: (1) Due to 50/60 Hz ground loops, a multiple-point ground is undesirable. (2) It's possible to make LF current to follow your trace. Thus, star ground. Digital logic is high-level, high-frequency, so (1) ground loop is not a major concern, and (2) it's NOT practical to route RF current, only to reduce the return path impedance, thus, mesh ground. Finally when you have both AF & RF, you can use many capacitors to create a DC open & RF short, the AES approach. \$\endgroup\$ Jul 14, 2022 at 2:31

3 Answers 3

1
\$\begingroup\$

I hate the word 'ground', it covers sooo many slightly different things!

What the audio guys mean by 'ground' at least within the main doings of a board is really 'signal reference', which may or may not be the same as chassis ground, but which almost certainly should not be carrying current from cable screens or forming loops with the chassis. The problem is that with say 2V audio level, if you want a noise floor 100dB down you are looking at trying to have less then 20uV of noise on that net, which means you cannot have much current flowing. Smart audio people do all sorts of pseudo differential games by being very selective about exactly where reference connections are made.

At the edge of the board you typically have your RFI filters and such which DO need a direct connection to chassis (Ideally to the connector shell), but if you share this connection with the signal reference then you inherently have a little piece of copper carrying cable screen current and defining the reference net potential relative to chassis, that bit of copper has inductance so the screen current develops voltage across it, the reference net has capacitance to the case, so you end up with rf flowing in the reference net (Which is typically very short at audio frequency, 2.4GHz not so much!).

The digital guys mostly don't care about uV level noise getting into their nets (Ground bounce on the chips amounts to way more then that!). So for them tie everything to everything else and make lots of small loops that have little area is a massive win, reduces radiation also reduces coupling.

Incidentally, OUTSIDE of the board reference net, mesh is a net win for audio as well, you just got to keep the screen currents away from producing voltage drops in the internal audio reference net. See for example Tony Walderons papers on designing interference free audio systems, lots of loops of low impedance.

As to what to do on a mixed signal board? Decisions, decisions... Generally I favour a single ground plane and do the hierarchical grounding thing if there is sensitive audio in play, sometimes a plane with a slit, but NO trace is allowed to cross the slit, think in terms of the fact that current flows in loops in the ratio of the conductance and you wont go too horribly wrong.

\$\endgroup\$
7
  • \$\begingroup\$ Why does the voltage of the circuit signal reference relative to the chassis matter? \$\endgroup\$ Oct 6, 2021 at 0:49
  • \$\begingroup\$ Because usually the input and output stages have limited common mode range? \$\endgroup\$
    – Dan Mills
    Oct 6, 2021 at 13:39
  • \$\begingroup\$ How does a voltage difference between the signal ground/cable shield and the chassis at that point translate to a common-mode voltage w.r.t. the signal ground? The receiver in that example is referenced to signal ground, not (directly) to the chassis. \$\endgroup\$ Oct 7, 2021 at 0:58
  • \$\begingroup\$ @hddh, receivers have finite common mode range, the cable screen ties the two chassis together, and you want to place the receiver internal reference somewhere close to the transmitters common mode output so as to maximise available voltage swing, connecting it to chassis does this. Also this low Z connection minimises capacitive coupling from the case to the reference net. \$\endgroup\$
    – Dan Mills
    Oct 7, 2021 at 10:28
  • \$\begingroup\$ I agree re capacitive coupling. And I agree that receivers have a finite common mode range. I'm just not clear on why a voltage of signal ground and cable shield w.r.t. chassis will translate into a common-mode voltage w.r.t. signal ground. To be clear, I'm referring to this image \$\endgroup\$ Oct 8, 2021 at 2:22
1
\$\begingroup\$

Is my own analysis correct?

Looks good to me. I agree with your analysis. Usually the design rules from one system will not work with a different system with different goals.

Electromagnetic Compatability is an art, not a science. It's an art because many times many parameters are not measurable (mostly due to time constraints) on vastly different systems with different requirements. A designer uses best practices on a very complex system, it would be difficult for any one rule to determine the design.

The AES48 standard only mentions star ground: protective ground of the mains, circuit ground and the chassis should be connected at a common star grounding point. What would happen when I use a mesh ground (like a computer motherboard) to bound the chassis and the circuit ground , is it considered good or bad in audio?

The problem with mesh grounds (I have found) is it makes it really difficult to control currents, or know where they are coming from. With a single point ground, you can dissconnect cables and find the source easily.

Things are not black-and-while. Nowadays, a professional audio system often contains a high-speed digital system inside as well. In this case, one is forced to choose breaking either the recommended practice of audio system or the digital system. What should I do? Perhaps the digital ground and the analog ground, with their respective connectors, can be treated separately, each follows the best practice of their own world?

Depends on the cost of the system, in higher end systems (where cost isn't as much of an issue) isolation can be employed to stop currents from creating problems. If isolation can't be used, then best practice EMC could be used.

Many times currents on a PCB can be directed by good component placement (if you have a single ground)

\$\endgroup\$
1
\$\begingroup\$

I spent some years in pro-audio (at the time when systems were starting to contain more and more digital blocks, both for DSP and for control) and I never really came across a clear or definitive answer to this.

In building large systems (by which I mean a central equipment rack with anything from 10 to several hundred external units, which were often powered by the central rack), for major broadcast and theatres who had experience of such things, the basic practices I learned were:

  1. keep chassis and technical ground separate everywhere. Shields were generally connected to chassis.
  2. Provide multiple places where the two could be connected, at least at the central PSU and each external module. When the system was tested and signed off, you might start with everything joined, and if there are specific problems, experiment to find a local solution.
  3. In a pro system, you do not send unbalanced audio between equipment! In addition there may well be high quality audio transformers which not only give excellent CMR, but also provide a lot of protection against damage from transients, human error, and so on. This makes the problem far less severe than it seems initially.

I must say that the first analysis given (regardless of the pedigree of its author) seems a little fishy to me. Why did the capacitance from circuit to case suddenly vanish in the second diagram? All that has really happened here is that the connection point from tech 0V to chassis has moved a bit, but without any physical, real-world details, this seems meaningless. (Of course in practice there can be many XLR's, or perhaps multiway connectors with many balanced signals on them, so the diagram is not of much use anyway.)

Note that in the modern world, analogue signals are not getting routed between equipment much, anymore, unless you are an old-school analogue recording studio (they do still exist). These days, when you go to see a band at a festival, the signals from stage to sound desk are likely going over ethernet, quite possibly fibre, using Dante or similar. (I know that this is off the topic of the question, but just pointing out that to some extent, this discussion has become rather academic. Once you go from analogue to digital audio signal transmission, your requirements for noise immunity ease by several orders of magnitude.)

Finally, it's worth noting that, in a mixed signal system, where a microcontroller lives alongside analogue audio, the problems of keeping digital noise out of the analogue locally are significant. These days, again this gets easier as your "digital" block may be only one or two ICs. In the days when this was not so (e.g. early digital reverbs) many tricks, such as syncing the sampling frequency to power supply switching and opto isolated inputs/outputs to converters, were employed - and a LOT of physical metal and air between blocks.

\$\endgroup\$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.