element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • 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 & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • 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
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • 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 Support (English) Trace lock and re-optimization
  • 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 3 replies
  • Subscribers 188 subscribers
  • Views 671 views
  • Users 0 members are here
Related

Trace lock and re-optimization

e14 Contributor
e14 Contributor over 14 years ago

It would be nice to be able to lock traces the way components are

locked. This would allow experimenting with routing on one part of the

board, issuing a global 'ripup' command, without worrying about ripping

up existing traces.

 

If this feature is implemented it would also allow for another feature

I've always wanted: re-optimization. Imagine running Autoroute but

without the routing pass. That is, only the optimization passes are run.

This would be very helpful to clean up a manual routing job.

 

In re-optimization, any trace that is not locked is fair game for the

autorouter to re-route according to existing costs (without changing the

connectivity). Of course, locked traces remain untouched.

 

Andrew.

 

  • Sign in to reply
  • Cancel
  • e14 Contributor
    e14 Contributor over 14 years ago

    Am 06.09.2011 23:42, schrieb Andrew Sterian:

    It would be nice to be able to lock traces the way components are

    locked.

     

    Yes, please! (see also my post from 2010-07-19)

     

    Some additional wild thoughts on that subject:

      1. Locked/unlocked parts can easily be distinguished by their

         diagonal vertical handles. Other objects should stay as they

         are now if unlocked. If locked, I'm not really sure how to

         display that:

          - Vias COULD get a diagonal cross if locked.

          - Wires, polygons etc. COULD get diagonal crosses at each

            ent point if locked.

          - Or one just does NOT show the 'locked' status at all

            (because screen display could get quite messy)

      2. At the moment, grouping some area and moving it only a bit

         MIGHT result in DRC errors: If the user doesn't know that

         the group contains locked objects, everything else is moved,

         the locked objects aren't, and the resulting mess might not

         be so bad as to be seen immediately.

      3. Other programs don't show the lock status at all, BUT warn

         the user when changing the board: 'This group contains

         locked objects. Do you want to proceed with moving?' If the

         user selects YES, the board might be messed up due to some

         objects moving and others staying, but at least the user

         was warned that things might happen. Selecting NO aborts

         the moving.

      4. At least the following behaviour is possible when trying

         to move (or otherwise change) locked objects:

          - Notify the user ('You must first unlock the objects')

            and do nothing.

          - Notify the user ('Locked objects will not be processed')

            and proceed only with the unlocked objects.

          - Notify the user ('Even locked objects will be processed')

            and proceed with the action as if the objects were

            NOT locked.

          - Ask the user what to do ('Locked objects: Process them,

            Ignore them, Cancel').

     

    I don't really care WHICH of the above would be implemented (they all

    have advantages and disadvantages), but being able to lock ALL object

    types and being notified if things might go wrong would be just spiffing...

     

    Andreas Weidner

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14 Contributor
    e14 Contributor over 14 years ago

     

    "Andrew Sterian" <a.sterian@emsyde.com> wrote in message

    news:j4644n$dlo$1@cheetah.cadsoft.de...

    It would be nice to be able to lock traces the way components are locked.

    This would allow experimenting with routing on one part of the board,

    issuing a global 'ripup' command, without worrying about ripping up

    existing traces.

     

    If this feature is implemented it would also allow for another feature

    I've always wanted: re-optimization. Imagine running Autoroute but without

    the routing pass. That is, only the optimization passes are run. This

    would be very helpful to clean up a manual routing job.

     

    In re-optimization, any trace that is not locked is fair game for the

    autorouter to re-route according to existing costs (without changing the

    connectivity). Of course, locked traces remain untouched.

     

    Andrew.

     

    +1

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14 Contributor
    e14 Contributor over 14 years ago

    Andrew Sterian wrote on Tue, 06 September 2011 17:42

    It would be nice to be able to lock traces the way components are

    locked. This would allow experimenting with routing on one part of the

     

    board, issuing a global 'ripup' command, without worrying about ripping

     

    up existing traces.

     

    If this feature is implemented it would also allow for another feature

     

    I've always wanted: re-optimization. Imagine running Autoroute but

    without the routing pass. That is, only the optimization passes are

    run.

    This would be very helpful to clean up a manual routing job.

     

    In re-optimization, any trace that is not locked is fair game for the

    autorouter to re-route according to existing costs (without changing

    the

    connectivity). Of course, locked traces remain untouched.

     

     

    I agree Andrew, this could be useful.  Even if just to protect a highly

    optimised section of the layout (like a power supply for instance).

     

    Cheers,

     

    James.

    --

    James Morrison  ~~~  Stratford Digital

     

    Specializing in CadSoft EAGLE

    • Online Sales to North America

    • Electronic Design Services

    • EAGLE Enterprise Toolkit

    --

    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
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 © 2026 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.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube