On Saturday, Dec 13, 2003, at 15:57 US/Pacific, Tal wrote:

> now I wire some wires on TOP layer and connect between the auto route
> wires
> (2 separate net$) (bottom) with *TOP* wires that are NOT exist in the
> schematic (reason: the auto can't handle it) for each wire the eagle
> ask to
> which net$ to connect the "manual" wire I respond and continue to
> connect
> the other "manual" wires.

So I think you have let your board and your schematic become
"inconsistent", which is a pretty bad thing in eagle.

Probably the easiest way to fix this is to go back the to schematic
and run the ERC (rule check.)  It will complain about the problems.
Then add the wires manually to the schematic (that you already added
to the board) and re-run the ERC until it no longer complains about
any inconsistencies.

Eagle is pretty insistent that "nets" (NOT wires) be added in the
schematic only unless you are making a bare board.  The board has
airwires and routing for random connections, but the schematic
needs to have the lines placed manually and would quickly become
an awful mess if eagle tried to do it automatically.  Not being
able to route some signals is a lousy reason for not putting
those signals in the schematic...

If you want to control which layer a signal will be routed on
as you are drawing the schematics, you can probably use some
variation of "class."  I don't remember whether the autorouter
will route one class at a time, but it DOES route thicker traces
first, so if you make the bottom class slightly thinner than the
top class, route only the top (the thick traces will route first),
and then route only the bottom to pick up the rest.

BillW

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads