element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Chat (English) How To Delete An Orphaned Trace
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 6 replies
  • Subscribers 175 subscribers
  • Views 1290 views
  • Users 0 members are here
Related

How To Delete An Orphaned Trace

Former Member
Former Member over 15 years ago

I found when I make a small modification to a project with schematic and

PCB, I'll sometimes end up with an orphaned trace. That is, a short trace

which doesn't go anywhere anymore.

 

I don't see a setting in the DRC rules to catch this. Is there a way to

automatically find and tag these so i can delete them? Sometimes, they are

short enough that my tired eyes miss them. I'm loathe to rip up and redo

the board as these are typically minor changes to isolated parts.

 

Thanks

 

David

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

 

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    Former Member over 15 years ago

    Peter Wilson wrote on Tue, 15 June 2010 00:13

    David Ingebretsen wrote:

    Jaya wrote on Mon, 14 June 2010 21:00

    >> On 15/06/2010 07:24, David Ingebretsen wrote:

    >> > I found when I make a small modification to a project with

    >> > schematic and

    >> > PCB, I'll sometimes end up with an orphaned trace. That is, a

    short

    >> > trace

    >> > which doesn't go anywhere anymore.

    >> >

    >> > I don't see a setting in the DRC rules to catch this. Is there a

    >> > way to

    >> > automatically find and tag these so i can delete them? Sometimes,

    >> > they are

    >> > short enough that my tired eyes miss them. I'm loathe to rip up

    and

    >> > redo

    >> > the board as these are typically minor changes to isolated parts.

    >> >

    >> > Thanks

    >> >

    >> > David

    >> Hi,

    >>

    >> Did you try applying the "Ratsnest" comand. Sometimes, it has helped

    me

    >>

    >> when i have unrouted connections on the board. Usually, such

    >> connections show up on the unrouted Layer 19. If you really want to

     

    >> check if there

    >>

    >> are any such connections present then you can switch off all the

    layers

    >>

    >> except Layer19.

    >>

    >> -Jaya

     

    Thanks Jaya. The problem is the traces are "routed" in a sense.

    For

    example, it I delete a component, the traces to that component are

    not

    ripped up. So, these orphaned traces are still connected to the

    proper net.

    A Ratsnest command doesn't show them and they are still on the top

    or

    bottom layer. It can also happen if I don't fully ripup a trace and

    miss a

    small piece sticking out from a pad.

     

    David

     

    What works for me is just dragging the end of the excess trace onto

    some

    other part of the trace signal that you do want to keep, Eagle culls

    the

    unnecessary length and the implied overlay or doubled segment and

    removes the excess or duplicated portion of the trace... not automatic,

     

    but it works fine for me.

     

    Peter

     

     

    Thanks Peter. Is there an easy or straightforward way to find these

    traces?

     

    David

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Former Member
    Former Member over 15 years ago

    Peter Wilson wrote on Tue, 15 June 2010 00:13

    David Ingebretsen wrote:

    Jaya wrote on Mon, 14 June 2010 21:00

    >> On 15/06/2010 07:24, David Ingebretsen wrote:

    >> > I found when I make a small modification to a project with

    >> > schematic and

    >> > PCB, I'll sometimes end up with an orphaned trace. That is, a

    short

    >> > trace

    >> > which doesn't go anywhere anymore.

    >> >

    >> > I don't see a setting in the DRC rules to catch this. Is there a

    >> > way to

    >> > automatically find and tag these so i can delete them? Sometimes,

    >> > they are

    >> > short enough that my tired eyes miss them. I'm loathe to rip up

    and

    >> > redo

    >> > the board as these are typically minor changes to isolated parts.

    >> >

    >> > Thanks

    >> >

    >> > David

    >> Hi,

    >>

    >> Did you try applying the "Ratsnest" comand. Sometimes, it has helped

    me

    >>

    >> when i have unrouted connections on the board. Usually, such

    >> connections show up on the unrouted Layer 19. If you really want to

     

    >> check if there

    >>

    >> are any such connections present then you can switch off all the

    layers

    >>

    >> except Layer19.

    >>

    >> -Jaya

     

    Thanks Jaya. The problem is the traces are "routed" in a sense.

    For

    example, it I delete a component, the traces to that component are

    not

    ripped up. So, these orphaned traces are still connected to the

    proper net.

    A Ratsnest command doesn't show them and they are still on the top

    or

    bottom layer. It can also happen if I don't fully ripup a trace and

    miss a

    small piece sticking out from a pad.

     

    David

     

    What works for me is just dragging the end of the excess trace onto

    some

    other part of the trace signal that you do want to keep, Eagle culls

    the

    unnecessary length and the implied overlay or doubled segment and

    removes the excess or duplicated portion of the trace... not automatic,

     

    but it works fine for me.

     

    Peter

     

     

    Thanks Peter. Is there an easy or straightforward way to find these

    traces?

     

    David

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube