Topics

UnDoo problems #eagle

Vaughn
 

Made a schematic and then tried the board. Gave autoroute a go and got a reasonable board.

Problem is there are areas I have made errors on both the board and schematic. Trying to undo and go back I nowe have a error stating the changes on either will not update the other. e.g. changes on the schematic will not be shown on the board.

Any ideas how to fix this or do I start from scratch?

Thanks Vaughn

Drago
 
Edited

Hi, first of all, you have to check if f/b annotation is active or severed (almost sure is severed), to fix that you have to back to schematic or board (this time just open one of two files) (that error was occurred by changing one file without the another one opened, like adding or deleting parts, changing names and so on) once have you thought returned to active state open the other file to make sure they has.

for more information check this links

http://forum.arduino.cc/index.php?topic=238509.0

https://www.lucidar.me/en/eagle/eagle-tutorial-part-3-board-editor/

http://web.mit.edu/xavid/arch/i386_rhel4/help/321.htm

https://electronics.stackexchange.com/questions/176807/eagle-cad-method-of-re-linking-schematic-and-board

Best regards

Harvey White
 

On Sun, 26 Aug 2018 01:47:56 -0700, you wrote:

Made a schematic and then tried the board. Gave autoroute a go and got a reasonable board.

Problem is there are areas I have made errors on both the board and schematic. Trying to undo and go back I nowe have a error stating the changes on either will not update the other. e.g. changes on the schematic will not be shown on the board.

Any ideas how to fix this or do I start from scratch?
You must have both the board and schematic open at the same time. Make
changes on the schematic, and the board will follow, ditto with adding
or deleting parts. However, when you rewire something in the
schematic, you will find stubs for former connections. Since you used
the autorouter for everything, just ripup all the tracks (default
ripup) and try again. If you use a ground pour polygon, delete those
polygons first since the autorouter is not happy with existing
polygons, it will not route all the wires in that case. Give it a try
to see if this is the case for your board.

Each time you save the board, you will find that eagle keeps backups
in the form of name.b#n and name.s#n. If you have edited the board
separately from the schematic, then the dates and times of the
existing .brd and .sch file will not match. Go back (.b#1 is the most
recent) and rename name.b#1 (for example) name01.brd, do the same with
the schematic. Open both, and then run consistency checks. You'll
have your work before you made the separate changes. If this doesn't
work, then go back and look at name.b#2, .b#3, etc.

Harvey



Thanks Vaughn

Harvey White
 

On Sun, 26 Aug 2018 01:47:56 -0700, you wrote:

Made a schematic and then tried the board. Gave autoroute a go and got a reasonable board.

Problem is there are areas I have made errors on both the board and schematic. Trying to undo and go back I nowe have a error stating the changes on either will not update the other. e.g. changes on the schematic will not be shown on the board.

Any ideas how to fix this or do I start from scratch?
No, but you will need to go back and try to match the version of the
board file that doesn't have your changes.

In Eagle, you cannot change the board without changing the schematic
and vice versa.

At some point, you had a board or schematic file open without the
corresponding other file. This gives Eagle severe heartburn (and
then.... you).

Eagle keeps backup files of both schematic and board, so you can try
to match them up. If the board wasn't too complicated, you can lay it
out again by moving all the .brd or .br# files into a separate folder
where Eagle can't find it (note that you're not destroying
information, just making it invisible).

Then create a board and go from there.

otherwise, you will have to try to match things up.

In my version (7.x) there's a big nasty yellow and black striped
banner telling you that changes in one will not be reflected in the
other when both files are not open.

Harvey


Harvey



Thanks Vaughn