Skip to main content
PCB cross-section showing copper trace geometry and impedance relationship

Controlled Impedance and Plating Uniformity: The Connection Most PCB Designers Miss

GSAS Engineering · · 5 min read

Controlled-impedance PCB design is a discipline that most high-speed design engineers understand well. Trace width, dielectric thickness, copper thickness, and dielectric constant determine the characteristic impedance of a transmission line. Signal integrity tools like HyperLynx compute the required trace geometry for target impedance values, 50 ohms single-ended, 100 ohms differential, and the designer routes traces at those widths with precise stackup control.

What many designers overlook is that the copper thickness in the impedance calculation is not the nominal foil thickness, it is the final copper thickness after plating. And plating is not uniform. The same trace can be 30 micrometres thick at one end of the panel and 40 micrometres thick at the other, depending on its position relative to the anodes and surrounding copper features. This 10-micrometre variation changes the trace cross-section geometry and shifts the impedance.

How Plating Variation Affects Impedance

The characteristic impedance of a microstrip or stripline is a function of the trace width (w), copper thickness (t), dielectric thickness (h), and dielectric constant (Er). For a typical inner-layer stripline at 50 ohms:

  • A 5-micrometre increase in copper thickness reduces impedance by approximately 1-2 ohms
  • A 10-micrometre increase reduces impedance by approximately 2-4 ohms

For designs with tight impedance tolerance bands (50 ohms +/- 5%), a 10-micrometre plating variation can consume half the available tolerance budget, before accounting for dielectric thickness variation, etch factor, and other manufacturing variables.

The problem compounds for differential pairs, where impedance depends on both the individual trace dimensions and the coupling between traces. Plating variation that affects both traces equally shifts the differential impedance. Plating variation that affects one trace more than the other (possible if the traces are in different current density regions) creates an impedance imbalance between the positive and negative traces.

Where Plating Variation Is Worst

Not all regions of a PCB panel experience the same plating variation. The electrochemistry creates predictable patterns:

Panel edges vs centres. Edge traces plate 30-50% thicker than centre traces in a typical vertical plating cell. A controlled-impedance trace near the panel edge may be 38 micrometres while the same trace near the panel centre is 28 micrometres.

Near pours vs isolated. Traces adjacent to large copper pours compete for plating current with the pour. The pour, with its large surface area, draws current away from the narrow trace, resulting in thinner copper on the trace. The impedance shifts upward (thinner copper = higher impedance for striplines).

Near vias. Regions with many plated-through vias draw current vertically through the panel, locally reducing the current available for surface trace plating.

The Simulation Solution

Elsyca PCBBalance and PCBPlate address the plating variation that compromises impedance control:

PCBBalance equalises the copper density across each layer, reducing the gross variation in current distribution that causes thick-edge/thin-centre patterns. By adding simulation-optimised copper thieving, PCBBalance narrows the plating thickness window across the panel.

PCBPlate provides the quantitative prediction, the actual copper thickness at each controlled-impedance trace location. The designer or fabricator can then:

  1. Verify that plating variation stays within the impedance tolerance budget
  2. Adjust trace widths to pre-compensate for predicted plating variation (wider traces in thick-plating regions, narrower in thin regions)
  3. Optimise panel layout to place impedance-critical traces in regions of uniform plating

This simulation-informed approach is more effective than the traditional method of adding impedance test coupons to the panel border and hoping that the coupon measurement represents the actual trace conditions across the board.

Integration with Signal Integrity Workflow

For Indian design teams using Siemens EDA tools (Xpedition, HyperLynx) for signal integrity analysis, the Elsyca plating simulation adds the manufacturing dimension that SI tools assume is constant. The workflow:

  1. HyperLynx determines required trace geometry for target impedance
  2. PCBBalance optimises copper balance for uniform plating
  3. PCBPlate predicts actual copper thickness at impedance-critical locations
  4. HyperLynx re-evaluates impedance with predicted (not nominal) copper thickness

This closed-loop approach catches impedance problems that originate in manufacturing, problems invisible to the signal integrity tool that assumes uniform copper.

For teams in Bengaluru, Pune, Chennai, Hyderabad, Mumbai, and Delhi NCR designing DDR5 memory interfaces, high-speed SerDes channels, and RF circuits where impedance tolerance is tight, the Elsyca simulation provides the manufacturing fidelity that signal integrity analysis requires.

Why Buy from GSAS

GSAS provides both the Elsyca PCB plating simulation tools and the Siemens EDA signal integrity tools in India, a unique combination that bridges PCB design and PCB manufacturing simulation under a single engineering partner. Contact us from Bengaluru, Hyderabad, Chennai, Pune, Mumbai, Delhi NCR, or Visakhapatnam.

Explore Elsyca Products → | Request a Quote →

Interested in Elsyca tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Horizontal stacked bar showing where an ADAS test vehicle's bandwidth budget is spent, split into cameras, lidar, radar and bus traffic, with the logger uplink limit drawn as a vertical rule crossing the bar, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

ADAS Sensor Data Logging: Bandwidth Budgets That Add Up

Every page that tells you an ADAS test vehicle produces terabytes a day states the headline and skips the arithmetic, so you cannot redo it for your own sensor set. This article publishes the arithmetic instead: one formula, every table row derived on the page, a worked eight-hour drive that chains those rows into a sustained write rate, a media count and an offload window, and the five places bandwidth budgets go wrong. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 15 min read
Split panel diagram comparing one control message on a shared multidrop CAN bus with one sensor stream on a switched point to point Ethernet link, labelled shared bus arbitration, node, point to point link, switch, control message and sensor stream, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

CAN vs Automotive Ethernet: When to Use Each

CAN and automotive Ethernet answer different questions, so the useful comparison is a decision table rather than a winner. This guide from GSAS Micro Systems sets CAN and CAN FD figures from CAN in Automation next to the IEEE 802.3bw objectives for 100BASE-T1, covers arbitration against switch queues, cost and harness consequences, failure modes on both sides, and what changes on an India bench team's setup when a project adds Ethernet next to the CAN it already runs.

29 Aug 2026 · 14 min read
DoIP handshake sequence between tester and DoIP entity: vehicle identification, TCP connect, routing activation request and the accept-or-reject response code with its denial causes, then diagnostic messages, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

DoIP Routing Activation Failures: The Response Code Table

A DoIP routing activation denial is one byte, and that byte names the cause exactly. This article puts every published response code in one table, cross-checked across the AUTOSAR Classic Platform DoIP specification, the Wireshark dissector and two open-source client libraries, then gives the order a DoIP entity applies its checks so you can read a denial backwards to the configuration value that produced it. Written by the GSAS Micro Systems engineering team in India for diagnostics and validation benches in Bengaluru, Pune, Chennai and Hyderabad.

29 Aug 2026 · 13 min read