Skip to main content
Altium Designer PCB layout with multiple polygon pours, plane islands, and stitching vias on a multi-layer high-density board

Efficient Polygon Practice in Altium Designer

GSAS Engineering · · 1 min read

Efficient Polygon Practice in Altium Designer

Creating, Deleting, and modifying the polygon pours on your board is something you do everyday but are you doing it in the quickest most efficient way?

The copper pours you place on your board can make or break your product. You need to make sure you’re handling not only Analog and Digital power but signals as well.

Timing

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

JOIN THE WEBINAR TO DISCOVER:

  • How to create polygons
  • How to merge polygons
  • How to modify polygon outlines

REGISTER NOW

LEARN MORE ABOUT ALTIUM DESIGNER

Why polygon discipline matters

Polygon shapes carry the bulk of return current on most modern Indian PCB designs, power planes, ground planes, and the local copper pours under high-current loads. Get the polygon strategy wrong and the symptoms surface late: thermal hotspots that only show up under load, EMC test failures, voltage drop at distant loads, return-path discontinuities under high-speed signals. Get it right and the rest of the layout work becomes far less constrained, since signal layers no longer fight the power-plane geometry for via stitching and clearance budgets.

How Siemens Xpedition handles polygons

GSAS Micro Systems is an authorized engineering partner in India. Xpedition Standard and Xpedition Enterprise approach polygon pours through the same constraint-driven framework that governs the rest of the layout, clearances, antipads, stitching rules, and pour priorities live in the design rules and propagate consistently across every layer of the stack. The constraint-aware sketch router respects polygon priorities while routing high-speed signals through plane gaps, which is exactly the failure mode (signal-on-plane-with-wrong-priority) that costs Indian engineering teams hours of manual rework on Altium’s per-polygon priority model.

Xpedition Enterprise adds PI-DC analysis through the HyperLynx PI integration, the same polygon shapes routed in layout simulate as the actual power network, surfacing voltage drop and current density problems while the design is still mid-layout rather than waiting for prototype thermal-camera evidence.

For a topic-by-topic comparison of how each tool handles routing, polygons, and signal integrity workflows, see our Altium Designer vs Siemens Xpedition Standard for Indian PCB teams guide.

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

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
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
Ladder chart of the T1 single-pair Ethernet family by data rate: 10BASE-T1S (802.3cg), 100BASE-T1 (802.3bw), 1000BASE-T1 (802.3bp), 2.5/5/10GBASE-T1 (802.3ch) and 25GBASE-T1 (802.3cy), one balanced pair across five IEEE standards, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

The T1 Family Explained: 10BASE-T1S to Multi-Gig 802.3ch

The T1 family is the set of single-pair Ethernet physical layers used in vehicles, and every member is documented separately inside a different datasheet. This guide puts all of them in one table with rate, symbol rate, line code, specified reach and cabling traced to public IEEE task force documents, then answers the two questions that keep coming back: why 100BASE-T1 has no auto-negotiation, and why one end has to be master. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read