Corrupted project file?

Can't open most schematics created before Eagle 6.1   are you trying to load an older version of eagle produced file?

C

no, I have started to use v7.3 and created a new project. anyway found the root cause as one net have missing net names.

Thanks

I am having the same issue.   In my case it is a design created in Version 7.1, and I get the same errors if I try to open in either Version 7.1 or 7.5   I get similar warnings and errors for both the SCH and BRD files, line numbers are different buth they are both worried about an invalid/missing attribute.

Warning(s):

line 1285: invalid value '' for attribute 'name' in tag <signal>

Error:

line 1301, column 9: invalid/missing attribute 'name' in tag <signal>

Do I need to recreate the whole design from scratch, or can I salvage this?

On 7/01/2016 4:51 p.m., Mark Sauerwald wrote:

I am having the same issue.   In my case it is a design created in

Version 7.1, and I get the same errors if I try to open in either

Version 7.1 or 7.5   I get similar warnings and errors for both the SCH

and BRD files, line numbers are different buth they are both worried

about an invalid/missing attribute.

 

 

Warning(s):

 

line 1285: invalid value '' for attribute 'name' in tag <signal>

 

Error:

 

line 1301, column 9: invalid/missing attribute 'name' in tag <signal>

 

Do I need to recreate the whole design from scratch, or can I salvage

this?

 

Hi

You should be able to salvage.

For the Errors listed

Open the board file in a text editor

Go down to line 1301

There it has detected that the format of the line is unexpected.

It is expecting it to start like:

as the name should be made to

match those contacts on the schematic.

This should get you going but you will likely have consistency errors

between the board and schematic so you may have more work to do.

I would try to get either board or schematic opening by  them selves

first and then once that works open them both, then fix the

inconsistency errors to make them consistent. When you do this, work out

what you want to do to one of the files and close the other before you

do it.

HTH

Warren

Mark Sauerwald wrote on Thu, 07 January 2016 03:51

Do I need to recreate the whole design from scratch, or can I salvage

this?

Hi Mark,

Hopefully Warren's answer above should sort you out but just relating to

your final comment, it's always a good idea to keep backup's of earlier

version so if anything get's lost/corrupted you can always go to the last

backup. Since eagle now uses a text based rather than binary file format

you can do this nicely and track your changes with a version control

system. I use Git for all my projects and I check in regularly with a

description of exactly what I have changed so I can always go back and look

what I have done over the history of a design which can be really useful on

a big project with lots of changes. You then also have easy backups to

another machine or an off-site git server. You simply check in changes and

then push them to the remote location. Doing this means you'll never have

to ask the above question as you'll know you can always go back to the last

known good check in if something bad happens.

Best Regards,

Rachael

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Thank you for your advice Rachel and Warren for the suggestion.   I'll try the text editing suggestions out when I get home tonight - I use Eagle at home, and Altium at work, and there is always a transition period when I jump from one system to the other, but the text editing strategy looks like a good place to explore!   I was dreading having to redo this design from scratch, it is 10 sheets of schematic so it would have been some work!

At work, we use Perforce for version control and sharing - but I am not as diligent with my projects at home as I am at work.    I should look for a middle of the road solution and GIT looks interesting, I'll have to try that out.

Mark

On 07/01/16 17:06, Mark Sauerwald wrote:

At work, we use Perforce for version control and sharing - but I am not

as diligent with my projects at home as I am at work.    I should look

for a middle of the road solution and GIT looks interesting, I'll have

to try that out.

At work I have Visual Source (un)Safe inflicted on me but all my home

projects live in Subversion, at least partly because it's such a doddle

to administer.

Just to add a little, prompted by Rachael,s comment.

Eagle stores backups each time you save so the last of these may work for

you.

See the manual that explains the file naming of the saves and automatic

backups.

If you had done quite a bit of work since that last save maybe there's a

bit to much of a difference to use it and hence getting to work with the

text editor is the way to go.

What could be of value is, The backup may have exactly what you need to

repair the broken files so once you locate it, a simple cut and paste will

get you going and possibly the Schem and Board will be consistent.

Warren

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

I've worked extensively with a number of open-source source management

tools, including Subversion and GIT. For the home user I recommend

Subversion over GIT.

GIT is extremely powerful. It's designed explicitly to support massively

parallel development with very powerful branching and merging

capabilities. If you know how to use it it's great. However, it's also

cryptic, hard to learn for many people, and a real pain when it breaks.

Subversion is far more limited. It depends on having a central

repository for your projects. That's a bad thing if you're trying to

manage multiple parallel development efforts, but most basic users find

it easier to learn and use.

I spend much of my professional life developing Linux kernel code. That

means I have a fair bit of experience using GIT, and would consider

myself a fairly competent user. I also use GIT to manage my personal

projects, mainly because I was using GIT so much I found I was

forgetting how to do things with Subversion.

One of the keys to successful use of a source management system is

making sure the important stuff gets committed, and none of the garbage

gets committed. For example, Eagle creates "backup" files by renaming

the current version of its files to the "backup" name before creating

the new version. None of these "backup" files should ever be committed

to your source management system because they're basically useless

garbage you'll never want to use. If you find yourself thinking you

might want to go back to one of those older versions, that a sign you're

not committing your work often enough!

One of the ways to make this easier is to have the source management

system ignore the files you don't want to commit. To have GIT ignore the

"garbage" files Eagle creates, create a file called ".gitignore" in the

top directory of your project with the content between the lines of hashes:

###########################

.eaglerc

.cache/

.fontconfig/

.config/

*.b#[0-9#]

*.l#[0-9#]

*.s#[0-9#]

*.pro

###########################

The file name may be a bit different on Windows or Mac systems. I don't

use GIT on these systems.

You can do something similar with Subversion by setting the "svn:ignore"

property, or set the global-ignores option in its config.

On 01/07/2016 12:06 PM, Mark Sauerwald wrote:

Thank you for your advice Rachel and Warren for the suggestion.   I'll

try the text editing suggestions out when I get home tonight - I use

Eagle at home, and Altium at work, and there is always a transition

period when I jump from one system to the other, but the text editing

strategy looks like a good place to explore!   I was dreading having to

redo this design from scratch, it is 10 sheets of schematic so it would

have been some work!

 

At work, we use Perforce for version control and sharing - but I am not

as diligent with my projects at home as I am at work.    I should look

for a middle of the road solution and GIT looks interesting, I'll have

to try that out.

 

Mark

 

--

To view any images and attachments in this post, visit:

http://www.element14.com/community/message/170956

 

Thank you Warren

I was able to fix the files, and get my schematic and board layout back into sync.

Mark