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

Side by side comparison of a 10BASE-T1S multidrop mixing segment, one balanced pair with four nodes on short stubs and a termination at each end, against a point to point star of four separate links into switch ports, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

10BASE-T1S and PLCA: Multidrop Ethernet Explained

10BASE-T1S is the one member of the T1 single-pair Ethernet family that keeps a shared medium, and PLCA is the reconciliation sublayer that stops the nodes on it from colliding. This article covers what IEEE 802.3cg standardises, how the beacon and transmit opportunities schedule a cycle, the node count and segment length figures the OPEN Alliance interoperability test suite works to, and the failure modes that put a segment quietly back into contention while every link still looks up. Written by the GSAS Micro Systems engineering team in India for teams bringing up multidrop segments on the bench.

29 Aug 2026 · 12 min read
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
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