Altium DISCUSSION

Why did an Altium impedance-profile change leave the old routing limits?

Started by mojuba Altium Constraint Managerimpedance profilestrace widthlayer stackrouting rules
3 replies 248 views 4 participants
Latest activity · 27 Sep 2026

Why did an Altium impedance-profile change leave the old routing limits?

mojuba Altium Forum
#1

Altium's current Constraint Manager documentation notes a distinction between preferred trace width and the minimum and maximum limits when an impedance profile is refreshed.

If a fabricator changes the dielectric thickness and the calculated preferred width changes, what should be reviewed before routing continues? How can we check that the board is using the intended constraint rather than an older inherited value?

Reference: Altium: Constraint Manager (https://www.altium.com/documentation/altium-designer/sch-pcb/constraint-manager).

Community replies 3

Re: Why did an Altium impedance-profile change leave the old routing limits?

#2

Check the actual stackup values first: copper thickness, dielectric thickness and the material parameters agreed with the fabricator. Then refresh the relevant constraint data and inspect minimum, preferred and maximum widths together. A new preferred value outside the existing limits is an inconsistent rule. Save the constraint changes so the router can use them; a visible edit is not necessarily an applied edit.

Re: Why did an Altium impedance-profile change leave the old routing limits?

#3

Inspect the specific net or differential pair as well as its class. A more specific assignment can explain why one connection behaves differently from its neighbors. Also confirm the active routing layer and associated impedance profile. Keep a short test track on a copy of the board and inspect the applicable rule, rather than inferring rule selection only from the width shown in a toolbar.

Re: Why did an Altium impedance-profile change leave the old routing limits?

#4

Send the revised stack and nominal geometry back to fabrication for confirmation, including the required tolerance. A field-solver estimate depends on its material and geometry assumptions. Review already routed tracks separately; changing a rule does not mean every existing segment has been corrected. Run DRC, inspect affected nets and regenerate the release documentation after the stack and rules are settled.

TEP COMMUNITY