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 engineering bench in India, illustrating the hardware a developer can act on today, supported by GSAS
Technical Guides Arm

Arm's Agentic AI Push: What Indian Embedded Teams Can Actually Use Today

Arm has set out its platform strategy for the agentic era, putting inference everywhere it has compute. Indian embedded teams can start on that direction this quarter with the Cortex-M toolchain they already own: Helium, CMSIS-NN, Ethos-U and Vela, on boards you can order today.

13 Sept 2026 · 7 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