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

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
The AUTOSAR network management state ring: Bus Sleep, Repeat Message, Normal Operation, Ready Sleep and Prepare Bus Sleep, with the wake transition marked; the governing timers for each exit are named in the article's sourced state table, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

ECU Testing over Ethernet: Startup, Shutdown and Wake

A bench that powers the ECU, waits for it to settle and then starts capturing has already skipped three of the four phases where integration defects live. This is the lifecycle version of ECU testing over Ethernet: what a ping does not prove, the AUTOSAR network management state set and the timers that govern it read out of the public specifications, why one node holds a whole cluster awake, and a phase-by-phase table of stimulus, observable, pass criterion and capture method you can write test cases from this week. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read