Skip to main content
Rigid-flex PCB layout in Altium Designer showing the rigid-to-flex boundary, bend region, and coverlay transitions for a compact medical wearable design

Rigid-Flex Design in Altium Designer

GSAS Engineering · · 1 min read

RIGID-FLEX DESIGN IN ALTIUM DESIGNER

Rigid-flex PCB technology offers a tremendous amount of benefits, including reduced weight, space, increased durability, and reliability. Today’s small, lightweight mil-aero, medical, and consumer electronics products are best implemented with rigid-flex technology. However, not every PCB design tool offers the capabilities necessary for achieving successful rigid-flex PCB designs on time.

Timing:

Thursday, 03rd December 2020 | 02:30 PM to 03:30 PM

Here are just some key points you can expect to walk away with:

  • Why Rigid-Flex
  • Flex Materials
  • Routing Tips
  • Polygons Placement

Event Completed

LEARN MORE ABOUT Altium Tools

Recorded Live-webinar

What rigid-flex really demands from a PCB tool

Rigid-flex isn’t just about drawing flexible sections in the layer stack. The tool needs to model bend regions, stagger transitions through coverlays correctly, route across the rigid-to-flex boundary without DRC false-positives, handle variable layer counts in different zones of the board, and produce manufacturing data that the fabricator can build from without back-and-forth queries. Indian medical-wearable, defence, and aerospace teams adopting rigid-flex hit each of these stress points within the first few projects.

How Siemens Xpedition handles rigid-flex

GSAS Micro Systems is an authorized engineering partner in India. Xpedition Enterprise treats rigid-flex as a first-class design intent rather than a layered drawing exercise, bend regions, coverlay transitions, and per-zone stack-up changes are modelled in the design database, propagated through routing rules, validated against fabricator capabilities through Valor NPI sign-off, and rendered correctly in the 3D view that ECAD/MCAD co-design relies on. Xpedition Standard offers rigid-flex via its token-based add-on for individual engineers and small teams.

The choice for an Indian rigid-flex team usually comes down to project scale: Xpedition Standard with the rigid-flex token covers the typical 4-6 layer rigid section + 1-2 layer flex section that most consumer-electronics and IoT wearables ship. Xpedition Enterprise becomes the right answer when a programme has multiple boards interconnected through rigid-flex (military electronics, advanced medical instruments, satellite payloads), multiple geographically distributed designers on one design, or HyperLynx SI sign-off requirements on the routed product.

For a deeper head-to-head, see our Altium Designer vs Siemens Xpedition Standard for Indian PCB teams comparison.

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

Embedded verification and unit test workflow, illustrating the economics of finding defects early, supported by GSAS Micro Systems in India
Technical Guides

Verification Economics: What a Late Defect Actually Costs, and What the Evidence Really Says

Finding a defect in month 2 instead of month 14 is a budget decision before it is a quality decision. This sets out what the published evidence supports, what it does not, including the 100x multiplier that traces back to a course handout rather than a study, and how an Indian embedded team builds the case on its own numbers.

21 Sept 2026 · 14 min read
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