Rule category: Electrical
Rule classification: Binary
This rule defines the minimum clearance allowed between any two primitive objects on a copper layer. Either a single value for clearance can be specified, or different clearances for different object pairings, through use of a dedicated Minimum Clearance Matrix. The latter, in combination with rule-scoping, provides the flexibility to build a concise and targeted set of clearance rules to meet even the most stringent of clearance needs.
The rule scope returns a set of objects, the constraints detailed below are then applied to that set of objects:
Different Nets Only- constraint is applied between any two primitive objects belonging to different nets (e.g. two tracks on two different nets).
Same Net Only- constraint is applied between any two primitive objects belonging to the same net (eg, between a via and pad on the same net, or two track segments in the same net).
Any Net- constraint is applied between any two primitive objects belonging to any net in the design. This is the most comprehensive of the three options and covers the possibility of the objects belonging to the same net, or different nets.
► Learn more about Differential Pair Clearance Checking
For many users, there is no great difference between Track and Arc primitives. And when it comes to Fill, Region, and Polygon objects, most users just see these as more 'copper.' With this in mind, the minimum clearance matrix for the Clearance rule has been enhanced to operate in two modes:
Definition of clearance values in the matrix can be performed in the following ways:
With the required selection made (either a single cell or multiple cells), making a change to the current value is simply a case of typing the new value required. To submit the newly entered value, either click away on another cell, or press Enter. All cells in the selection will be updated with the new value.
Designers can check clearances between the edges of drill holes and neighboring copper objects on signal layers. This is particularly beneficial in preventing the routing of track too near to a drilled hole, which could otherwise suffer from any potential wandering of the drill during board fabrication. The row at the bottom of the Clearance rule's minimum clearance matrix is used to define the desired clearances.
Designers can also check clearances between split plane regions on internal plane layers. How clearance is defined depends on the mode in which you are using the minimum clearance matrix:
A violation will appear in the form:
Clearance Constraint: (<CurrentClearance> < <DefinedClearance>) Between Split Plane (<NetName>) on <InternalPlaneLayerName> And Split Plane (<NetName>) on <InternalPlaneLayerName>,
Clearance Constraint: (32.36mil < 34mil) Between Split Plane (GND) on Internal Plane 1 And Split Plane (NetC6) on Internal Plane 1
Differential pairs present unique design challenges, often requiring a specific
within-pair clearance as well as a
pair-to-pair clearance, and potentially a third rule to control the
pair-to-all other nets, clearance. To support this, the Constraints region includes the dropdown where you can choose
Same Differential Pair and
Different Differential Pair options.
For example, if the nets within the differential pairs require a tighter clearance than the general board clearance, this can be achieved by using the
Same Differential Pair constraint option, as shown below. Note that even though the rule scope applies to
All net objects in the design, the Constraint setting restricts it to only apply to objects in the
Same Differential Pair.
This result could also be achieved by scoping the rule to only apply to differential pair objects (eg,
InAnyDifferentialPair), as shown below. Note that this rule would also apply between a net in a differential pair to any other net object in the design, so this approach should only be used if you have other higher priority rule(s) that define the
DiffPairNet-to-Any requirements. If this approach is used, the Priority of the differential pair rules must also be configured correctly, with the rule with a tighter clearance requirement having a higher priority.
A similar approach can be used to control the clearance between differential pairs. The image below shows how the
Different Differential Pair constraint can be used to achieve this.
As with the previous example, it could also be achieved using the rule scope, instead of the
Different Differential Pairs constraint. Remember that the rule priorities must be configured so the rule with the tighter clearance requirement has a higher priority.
To define a different clearance from a differential pair net to any other net object, the following rule could be used.
This could be further refined so that it only applies between differential pair objects and non-differential pair objects, as shown below.
► Learn more about scoping Differential Pair design rules
► Learn more about Differential Pair Routing
All rules are resolved by the priority setting. The system goes through the rules from highest to lowest priority and picks the first one whose scope expressions match the objects being checked.
Online DRC, Batch DRC, interactive routing, autorouting, and during polygon placement.
Different Nets Only. An example of when
Same Net Onlyor
Any Netcould be used is to test for vias being placed too close to pads or other vias on the same net, or any other net.
InPoly) should be included in the Full Query in this case, instead of
IsPoly). The specific polygon clearance rule must also be given a higher priority than any general clearance rule, if it is to have any effect.
Valid students can get their very own 6-month Altium Designer Student License for FREE! Just fill out the form below to request your Student License today.