Skip to main content
Altium Designer 20 transmission-line impedance calculator powered by the SIMBEOR engine, showing differential pair geometry and target impedance profiles for high-speed PCB routing

Transmission Line Impedance Calculation with Altium Designer 20

GSAS Engineering · · 1 min read

Transmission Line Impedance Calculation With Altium Designer 20

Today’s PCBs contain many transmission lines. Combine this with increased clock frequencies and data rates and the result is a critical challenge to high speed design. Neglecting these dynamics can undermine product development by compromising performance, power consumption, EMC/EMI compliance, and more, leading to delayed design cycles and opening gaps that can be exploited by your competition.

Hone your high-speed design skills by joining us as we discuss the typical transmission lines encountered in today’s designs, the PCB variables that affect impedance, as well as how to create, calculate, and design transmission lines in Altium Designer. Learn how to maximize the built-in SIMBEOR® engine by Simberian to craft impedance profiles and manage transmission lines in your designs.

Timing

Thursday, 25 June 2020 | 11:00 AM to 12:00 PM

ATTEND THIS LIVE RELEASE WEBINAR COVERING THE FOLLOWING:

  • Current trends in electronics development
  • PCB transmission line model and impedance calculations
  • Defining impedance profiles
  • Routing transmission lines to a specified target impedance
  • Live Q&A Session

Don’t pass up on this opportunity!

REGISTER NOW

LEARN MORE ABOUT ALTIUM DESIGNER

Why impedance accuracy matters more than ever for Indian high-speed teams

Indian PCB teams pushing into DDR5 (3200-6400 MT/s), PCIe Gen5 (32 GT/s), 100G/400G Ethernet (PAM4), USB4, and mmWave 5G FR2 are running into channel budgets where 1-2 ohm impedance variation is the difference between first-pass success and an expensive respin. Altium 20’s SIMBEOR-engine impedance calculator is a step up from older 2D field solvers, but it still operates on the stack-up in isolation from the routed channel.

How Siemens Xpedition + HyperLynx Z Planner go further

GSAS Micro Systems is an authorized engineering partner in India. The Xpedition stack-up flow integrates with HyperLynx Z Planner, Siemens’ production-grade impedance and SI tool, and that pairing gives Indian high-speed teams three things SIMBEOR-in-Altium does not:

  • Pre-layout topology exploration: sweep stack-up choices against impedance, insertion loss, dielectric absorption, and crosstalk targets before committing to a fabricator. The same engine validates the routed channel post-layout, so there is no manual re-entry between pre-layout and sign-off.
  • Material-library accuracy: HyperLynx Z Planner ships with measured material data from major fabricators (Rogers, Isola, Panasonic, Shengyi, ITEQ), at the frequency points that matter for mmWave 5G and 28G+ SerDes. Indian teams designing X-band radar and 5G FR1/FR2 systems work from the same library Western teams do.
  • Channel-level sign-off, not just impedance: for DDR5 and PCIe Gen5 the deliverable to the silicon vendor is a full channel report (insertion loss, return loss, eye height/width, jitter budget), not just “controlled impedance traces.” HyperLynx generates that report. SIMBEOR-in-Altium does not.

For Indian high-speed teams sizing the toolchain decision, see our Altium Designer vs Siemens Xpedition Standard for Indian PCB teams comparison and HyperLynx product overview.

Compare with HyperLynx Z Planner →

Also appears in:

Need embedded development 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

Storage sizing ladder for automotive data logging: four rungs stepping from an aggregate link rate of 1 Gbit/s to 125 MB per second, then 450 GB per hour, then 3.6 TB per eight-hour shift, then 18 TB per five-day week, in decimal units, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Data Loggers: Capture Without Loss

Search for an automotive data logger and the results split into cheap OBD dongles at one end and enterprise ADAS recorders at the other, with nothing in between explaining the engineering that decides whether you lose frames. This is the loss budget end to end: mirror oversubscription upstream of the logger, encapsulation overhead on the capture path, sustained write rate against burst rate, rotation stalls, and storage arithmetic worked in full so you can redo it with your own numbers instead of trusting ours. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read
The bench to harness adapter path drawn left to right: the ECU connector, a test lead, a media converter or pluggable T1 module, RJ45, and the host, showing where each connector family sits between the device under test and the laptop, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Connectors: H-MTD, MATEnet, MQS

An ECU arrives on the bench with a connector nobody has a mate for, and the day is gone. Search the family names and you get connector product pages that describe their own part and stop there. This article puts the families side by side in one table using only what their public pages state, then makes the point those pages leave out: the IEEE link segment definition, not the connector, is what sets reach and loss limits, and shielding is a channel decision rather than a preference. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read
Two test paths leaving the same device under test, one into a conformance suite that returns a passed report and one into a partner node that surfaces a field defect, showing why an ECU can clear a published suite and still fail in a vehicle, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Conformance: TC8 and Testing Above It

Summarising TC8 as a layer 1 to layer 4 suite is wrong in both directions. The public OPEN Alliance ECU test documents run from transmitter distortion up to a SOME/IP chapter with its own standardised test stub, and they contain exactly one time synchronisation test case. This is what those documents enumerate, chapter by chapter, what genuinely lives above their boundary, why a passing ECU can still fail against a partner node, and how much pre-compliance work a Tier-1 in India can honestly do in-house before a test house visit. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read