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
  • 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) Airwire/Ratsnest problem with jumper
  • 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 8 replies
  • Subscribers 177 subscribers
  • Views 558 views
  • Users 0 members are here
Related

Airwire/Ratsnest problem with jumper

autodeskguest
autodeskguest over 16 years ago

I don't have very much experience with Eagle so I think there may be a

simple solution for this. It is a project for school. If you open the

picture attached you can see that after adding a jumper, that airwire

seems to have forgotten where it belongs.

 

Wayland

 

  • Sign in to reply
  • Cancel
  • autodeskguest
    autodeskguest over 16 years ago

    not sure what your question is. maybe you need to click "ratsnest" to

    recalculate the wires? or your jumper is defined as 2 different pins on

    different nets so they no longer connect?

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 16 years ago

    Wayland Bugg wrote:

    Sorry, I thought it was obvious. In the picture attached, I have

    highlighted an airwires with "Show objects" to demonstrate that the

    highlighted portion is no longer considered by Eagle to be part of what

    I am now guessing is called a net. Ratsnest will not calculate the

    shortest path. You can see that it is a much shorter path to go from

    R2/R3 to C2, instead of all the way over to C1. I used "Wire" and not

    "Net" to create the schematic. I added the jumper after creating the

    schematic by deleting a section of wire and re-wiring through the jumper.

     

    Wayland

    Try to bottom post. Each side of the jumper is a different net since you

    broke the net and inserted the jumper. So the rats nest air wires look

    correct to me. Highlight the other side of the jumper and see what

    should be connected. Also do the same in the sch.

    Paul R.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 16 years ago

    Paul Romanyszyn wrote:

    Wayland Bugg wrote:

    Sorry, I thought it was obvious. In the picture attached, I have

    highlighted an airwires with "Show objects" to demonstrate that the

    highlighted portion is no longer considered by Eagle to be part of

    what I am now guessing is called a net. Ratsnest will not calculate

    the shortest path. You can see that it is a much shorter path to go

    from R2/R3 to C2, instead of all the way over to C1. I used "Wire" and

    not "Net" to create the schematic. I added the jumper after creating

    the schematic by deleting a section of wire and re-wiring through the

    jumper.

     

    Wayland

    Try to bottom post. Each side of the jumper is a different net since you

    broke the net and inserted the jumper. So the rats nest air wires look

    correct to me. Highlight the other side of the jumper and see what

    should be connected. Also do the same in the sch.

    Paul R.

     

    This worked perfectly on at least 5 other jumpers but not this one. How

    do I get the jumper to be part of the net? Whats the right way to add a

    jumper?

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 16 years ago

    On Tue, 24 Mar 2009 21:56:16 -0400, Wayland Bugg

    <theguy@waylandbugg.com> wrote:

     

    This worked perfectly on at least 5 other jumpers but not this one. How

    do I get the jumper to be part of the net? Whats the right way to add a

    jumper?

     

    It may not be the way you added the jumper.  It might be the way you

    added traces.  It seems the only way to get Eagle to recognize a trace

    as part of a net is to add it using the "Route" funciton.  If you add

    a trace using the "Add Trace" funciton, Eagle does not count it when

    computing where to put airwires.  You can tell if the trace was added

    correctly by trying ot delete it (using Delete, not Rip-up).  If you

    try to delete a trace that was added with Route, then Eagle will not

    let you do it.  It will say you can't do this in the board.  Do it in

    the schematic instead.  But if Eagle lets you delete a trace without

    complaint, either you are not editing with a consistent schematic, or

    the trace was put there some way other than with the Route function.

     

     

     

     

    Robert Scott

    Real-Time Specialties

    Ypsilanti, Michigan

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 16 years ago

    Robert Scott wrote:

    On Tue, 24 Mar 2009 21:56:16 -0400, Wayland Bugg

    <theguy@waylandbugg.com> wrote:

     

    This worked perfectly on at least 5 other jumpers but not this one. How

    do I get the jumper to be part of the net? Whats the right way to add a

    jumper?

     

    It may not be the way you added the jumper.  It might be the way you

    added traces.  It seems the only way to get Eagle to recognize a trace

    as part of a net is to add it using the "Route" funciton.  If you add

    a trace using the "Add Trace" funciton, Eagle does not count it when

    computing where to put airwires.  You can tell if the trace was added

    correctly by trying ot delete it (using Delete, not Rip-up).  If you

    try to delete a trace that was added with Route, then Eagle will not

    let you do it.  It will say you can't do this in the board.  Do it in

    the schematic instead.  But if Eagle lets you delete a trace without

    complaint, either you are not editing with a consistent schematic, or

    the trace was put there some way other than with the Route function.

     

     

     

     

    Robert Scott

    Real-Time Specialties

    Ypsilanti, Michigan

     

    Thanks for the post. I am at Mich. Tech. and surprisingly, nobody has

    been able to help me out with this yet. Ok. When I try to delete the

    airwire or routes it tells me that I must do it in schematic. ERC

    doesn't report any inconsistency between the board/schematic. I suppose

    I could start over. Is there a way to generate a new board from a

    schematic? Would that fix anything?

     

    Wayland

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 16 years ago

    Hi Wayland,

     

    If you want that the net name is the same on both sides of the jumper, you

    just have to re-connect an airwire between its two pins.

     

    It seem that you want to route a single side (on bottom only), but you can

    avoid to add jumpers in schematic in using the top layer instead: simply add

    two vias of the same diameter as your jumper wire and add a trace on the top

    layer between theses two vias.

    So you can keep the continuity of the net.

     

    Christian Bohrer

     

    "Wayland Bugg" <theguy@waylandbugg.com> a écrit dans le message de news:

    gqdgcg$4i2$2@cheetah.cadsoft.de...

    Robert Scott wrote:

    On Tue, 24 Mar 2009 21:56:16 -0400, Wayland Bugg

    <theguy@waylandbugg.com> wrote:

     

    This worked perfectly on at least 5 other jumpers but not this one. How

    do I get the jumper to be part of the net? Whats the right way to add a

    jumper?

     

    It may not be the way you added the jumper.  It might be the way you

    added traces.  It seems the only way to get Eagle to recognize a trace

    as part of a net is to add it using the "Route" funciton.  If you add

    a trace using the "Add Trace" funciton, Eagle does not count it when

    computing where to put airwires.  You can tell if the trace was added

    correctly by trying ot delete it (using Delete, not Rip-up).  If you

    try to delete a trace that was added with Route, then Eagle will not

    let you do it.  It will say you can't do this in the board.  Do it in

    the schematic instead.  But if Eagle lets you delete a trace without

    complaint, either you are not editing with a consistent schematic, or

    the trace was put there some way other than with the Route function.

     

     

     

     

    Robert Scott

    Real-Time Specialties

    Ypsilanti, Michigan

     

    Thanks for the post. I am at Mich. Tech. and surprisingly, nobody has been

    able to help me out with this yet. Ok. When I try to delete the airwire or

    routes it tells me that I must do it in schematic. ERC doesn't report any

    inconsistency between the board/schematic. I suppose I could start over.

    Is there a way to generate a new board from a schematic? Would that fix

    anything?

     

    Wayland

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 16 years ago

    On Wed, 25 Mar 2009 10:51:10 -0400, Wayland Bugg

    <theguy@waylandbugg.com> wrote:

    ... When I try to delete the

    airwire or routes it tells me that I must do it in schematic. ERC

    doesn't report any inconsistency between the board/schematic.

     

    That is all good.

     

    I suppose

    I could start over. Is there a way to generate a new board from a

    schematic? Would that fix anything?

     

    No, probably not.  I'm still not clear what is broken.  I guess this

    the heart of what you are doing:

     

    ..R3 to C2, instead of all the way over to C1. I used "Wire" and not

    "Net" to create the schematic. I added the jumper after creating

    the schematic by deleting a section of wire and re-wiring through the jumper.

     

    This is still not clear.  When you delete a section of wire in the

    schematic, the schematic assigns a new random name to one of the

    resulting nets.  Then when you add a jumper, I assume you are

    connecting one of those nets to one pin and the other net to the other

    pin.  If you want to back up and give it another try, go back to the

    schematic and delete both the wires to the jumper.  Then use the

    "info" tool to determine the net name for both nets that you had

    connected to the jumper.  Those names had better be different, or else

    something is wrong with your schematic.  Then re-connect the jumper in

    the schematic.  Again check the net names on both sides of the jumper

    to make sure that are still different.  Then go to your board.  There

    should be an airwire to each pin of the jumper.

     

     

     

    Robert Scott

    Real-Time Specialties

    Ypsilanti, Michigan

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 16 years ago

    On Tue, 24 Mar 2009, Wayland Bugg wrote to us saying :

    This worked perfectly on at least 5 other jumpers but not this one. How

    do I get the jumper to be part of the net? Whats the right way to add a

    jumper?

     

    Why do you want to add a jumper?

     

    There are two possible reasons I can think of.

     

    First reason is that you want to be able to isolate part of the circuit

    by removing the jumper from the board. In this case, the two sides of

    the jumper are explicitly separate nets and MUST NOT be connected any

    other way. Eagle is behaving correctly for this case.

     

    The second reason (and I suspect this is the case) is simply that when

    laying out your single-sided board, you are unable to achieve all the

    links you want. In this case, I'd suggest the jumper is NOT WHAT YOU

    WANT. It's not really part of the circuit, it's just an implementational

    anomaly. What I recommend you do, if this is the case, is not show it on

    the schematic at all, nor even on the board directly. Design the board

    using a short bit of track on the top side (i.e. as a double sided

    board). I know you aren't going to etch it as a double sided board, but

    if the top copper contains only three or four short links you can just

    etch the bottom side and treat the top side as a guide to where the wire

    links need to be fitted.

    --

    Rob Pearce                       http://www.bdt-home.demon.co.uk

     

    The contents of this | Windows NT crashed.

    message are purely   | I am the Blue Screen of Death.

    my opinion. Don't    | No one hears your screams.

    believe a word.      |

     

    • 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.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube