Let's try this:


When you added the jumper, did you add it with the *route* command, by =
stretching and rubberbanding the airwires, or did you add it by just =
drawing it or by using the wire command?  If it was the latter, EAGLE =
does not know it is part of the schematic yet.  I would still suggest =
unrouting or erasing the jumper, and redrawing it using *route*.  =20

-- Lawrence Lile, P.E.
Electrical and Electronic Solutions
Project Solutions Companies
www.projsolco.com
573-443-7100 ext 221
> -----Original Message-----
> From: Mohit Mahajan [mailto:biozen@SANCHARNET.IN]
> Sent: Tuesday, August 17, 2004 3:57 AM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: Re: ] Unrouted <-> Jumper (Eagle)
>=20
> Hi Lawrence,
>=20
> > 1. one of the wires shown in the picture ...
> It does touch. I've moved the jumper around in the schematic and the
> wires move along with it, confirming that they are connected.
>=20
> > 2. The jumper you show is not on the correct layer...
> Checked this, and the jumper is in the correct layer.
>=20
> > 3. Run an ERC and DRC on the board...
> Done this too and haven't found a warning/error that is about the
> jumpers.
>=20
> I've decided to go on with it as it is. Except for these airwires, the
> routes in the boards are correct, so am going to get it made anyway.
>=20
> I'd like to get to the root of the problem though.
>=20
> Thanks,
> Mohit.
>=20
> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@MITVMA.MIT.EDU] On Behalf Of Lawrence Lile
> Sent: Monday, August 16, 2004 6:35 PM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: Re: ] Unrouted <-> Jumper (Eagle)
>=20
>=20
> One of three things is happening:
>=20
> 1. one of the wires shown in the picture does not actually touch, =
making
> a break in the wire that is like 0.00001 mm long.  This can occur if =
you
> have ever changed grid settings.  I swore that I had not done this =
after
> the last time it occurred, but I found out it was generated by a =
custom
> part I had made with a goofy grid.  The solution is to rip up signals =
in
> that area and hand route them again, possibly with a grid size 1/2 or
> 1/10 of what you are using now.  Don't set grid to "finest", it causes
> more of this kind of trouble.
>=20
> 2.  The jumper you show is not on the correct layer.  This seems
> unlikely, but double check it anyway. Rip it up and start over with a
> correct layer.
>=20
> 3.  Run an ERC and DRC on the board.  It is possible you will see an
> error like "trace too close to pad" in an area that you believe should
> be connected.  Check your schematic for the same kind of off-grid
> problem. Move schematic components around and make sure they are =
really
> connected to the grids you think they are (hit escape and they will =
snap
> back where they belong)
>=20
> 4. If all else fails, alter your schematic and add a zero ohm resistor
> in this area for a jumper.
>=20
>=20
>=20
> -- Lawrence Lile, P.E.
> Electrical and Electronic Solutions
> Project Solutions Companies
> www.projsolco.com
> 573-443-7100 ext 221
>=20
> > -----Original Message-----
> > From: Mohit Mahajan [mailto:biozen@SANCHARNET.IN]
> > Sent: Friday, August 13, 2004 7:40 AM
> > To: PICLIST@MITVMA.MIT.EDU
> > Subject: [EE:] Unrouted <-> Jumper (Eagle)
> >
> > Hello,
> >
> > The attached file shows an unrouted airwire in red and a jumper (J2)
> > in an Eagle board.
> >
> > After autorouting this board this airwire was left unrouted. I added =
a
>=20
> > jumper J2 in the schematic where this airwire was, to complete the
> > route. The board shows the jumper and the signal is routed, yet the
> > airwire is still there. I've tried "Ratsnest" command, renaming the
> > net and signal command, but it remains.
> >
> > Doesn't Eagle recognise a jumper as the same electrical connection? =
Or
>=20
> > should one use some other component as jumper bridges?
> >
> > What should I do to remove these airwires (I have 3 such unrouted
> > airwire connections that also have a jumper)?
> >
> > Thanks,
> > Mohit.
> >
> > --
> > http://www.piclist.com hint: To leave the PICList
> > mailto:piclist-unsubscribe-request@mitvma.mit.edu
> >
> >
> >
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004
> >
> >
>=20
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004
>=20
>=20
> --
> http://www.piclist.com hint: The PICList is archived three different
> ways.  See http://www.piclist.com/#archives for details.
>=20
> --
> http://www.piclist.com#nomail Going offline? Don't AutoReply us!
> email listserv@mitvma.mit.edu with SET PICList DIGEST in the body
>=20
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004
>=20

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004
=20

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body