Altium NEXUS Documentation

Working with the Un-Routed Net Design Rule on a PCB in Altium NEXUS

Created: November 21, 2018 | Updated: July 29, 2020
All Contents

Rule category: Electrical

Rule classification: Unary

Summary

This rule tests the completion status of each net that falls under the scope (full query) of the rule. If a net is incomplete then each completed section (sub-net) is listed along with the routing completion. The routing completion is defined as:

(connections complete / total number of connections) x 100

The PCB Editor's Design Rule Checking system typically sees a net as being routed if all nodes in that net (component pads) are connected through the use of net-aware design objects (tracks, arcs, pads, vias, and polygons). These objects are considered connected if they touch each other. However, while simply touching makes a perceived connection to the software, when it comes time to fabricate the board, the fragility of some of these 'connections' can cause critical issues, especially where the objects - for example two contiguous track segments, or a track entering a pad/via - are only slightly touching. Such connections are often referred to as 'Bad Connections', 'Poor Connections', or 'Incomplete Connections'. This rule can also be configured to test for such poor connections.

All design rules are created and managed within the PCB Rules and Constraints Editor dialog. For a high-level view of working with the design rules system, see Constraining the Design - Design Rules. For detailed information regarding how to target the objects that you want a design rule to apply to, see Scoping Design Rules.

Constraints

Default constraints for the Un-Routed Net rule.Default constraints for the Un-Routed Net rule.

Check for incomplete connections - with this option enabled, the following additional checks on connectivity between applicable design objects are made:

  • Track/Arc to Track/Arc - checking that the centerlines, or centers of the ends of the connecting track/arc segments, coincide.
  • Track/Arc to Via - checking that the centerline, or center of the end of a track/arc segment, is placed on the shape of the via.
  • Track/Arc to Pad - checking that the centerline, or center of the end of the track/arc segment, is placed on the shape of the pad.
  • Via to Pad - checking that the center of the via is placed on the shape of the pad.
  • Via to Via - checking that the centers of the two vias coincide.
  • Polygon to Track/Arc - checking that the center of the end of a track/arc segment is overlapped by the polygon.
  • Polygon to Pad/Via - checking that the center of the Pad/Via is overlapped by the polygon.

How Duplicate Rule Contentions are Resolved

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 expression matches the object(s) being checked.

Rule Application

Batch DRC.

Tips

  1. A poor connection will be flagged in the workspace using the detailed violation marker,, with a corresponding message appearing in the Messages panel.
  2. Where applicable, a connection line will be drawn between unconnected objects in the net, with data regarding the un-routed net length reflected in the PCB panel (in Nets mode).
  3. Some split plane DRC checks require the Un-Routed Net rule to be Batch-enabled for them to work.
  4. In Printed Electronics, layer transitions do not require a via, the net analyzer will recognize that the net is not broken if a via is removed from a routed net. A board is defined as Printed Electronics when the Printed Electronics option is enabled in the Layer Stack Manager. Learn more about Printed Electronics.

 

Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

お問合せ

お近くの営業所にお問合せください。

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: