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
    About the element14 Community
  • 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) Can't Load Old Schematic
  • 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
  • State Not Answered
  • Replies 14 replies
  • Subscribers 189 subscribers
  • Views 1950 views
  • Users 0 members are here
  • message
  • error
Related

Can't Load Old Schematic

e14 Contributor
e14 Contributor over 12 years ago

I have a schematic I did 2 years ago and now want to edit, but when I try to load it I get this error message: line 16474, column 66: redefinition of name 'SUPPLY1' in tag <part>. How can I fix this (or bypass it)?

 

Thanks,

Greg

  • Sign in to reply
  • Cancel
Parents
  • AnalogNotes
    0 AnalogNotes over 12 years ago

    Opening my mouth where I might not know what I'm talking about, but here goes anyway!  image

     

    If you open that file with a text editor, do you find "SUPPLY1" listed twice in that part?  It may be as easy as using your editor to change that name, or delete the extra definition line.

     

    Make a backup first...  image

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • e14 Contributor
    0 e14 Contributor over 12 years ago in reply to AnalogNotes

    Doug, I actually tried that right after I posted the question.  In the first attempt it just went to another error involving the same signal, so I deleted that line also.  The schematic now loads and looks correct, but I'm sure there are missing connections.  A better 'hack' at this might be to change the signal name on these 2 lines to some new, unique name.  I haven't tried that yet.

     

    The 2nd error message is: <instance part="SUPPLY1" gate="GND" x="332.74" y="172.72"/>.  Note that this has coordinates in it, which I presume would indicate where the particular connection to this signal occurs, but what coordinate system is it?  I can only set the grid to 'normal' units such as inches or millimeters.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • autodeskguest
    0 autodeskguest over 12 years ago in reply to e14 Contributor

    On 1/03/2014 6:48 a.m., Greg Marshall wrote:

    Doug, I actually tried that right after I posted the question.  In the

    first attempt it just went to another error involving the same signal,

    so I deleted that line also.  The schematic now loads and looks correct,

    but I'm sure there are missing connections.  A better 'hack' at this

    might be to change the signal name on these 2 lines to some new, unique

    name.  I haven't tried that yet.

     

    The 2nd error message is: <instance part="SUPPLY1" gate="GND" x="332.74"

    y="172.72"/>.  Note that this has coordinates in it, which I presume

    would indicate where the particular connection to this signal occurs,

    but what coordinate system is it?  I can only set the grid to 'normal'

    units such as inches or millimeters.

     

     

     

    The coordinate system for sch file is millimeters

     

    You can verify this for your self. Set the sch grid to MM. next locate a

    part on the schematic, say R1 and view its INFORMATION. Record its xy

    location

     

    Now look for the part in the file in the 'instances> instance' section.

    It will be towards the bottom. It will have the same XY there.

     

    Quickest way to find the right line is search in the file for "x="60.96"

    inserting the x you noted from INFORMATION. THere will likely only be

    one fine result, the one you want.

     

    Setting the grid to inches, performing a save and then inspecting the

    file again, there will be no change to the xy location of the part

    proving it's mm.

     

    HTH

    Warren

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • autodeskguest
    0 autodeskguest over 12 years ago in reply to e14 Contributor

    On 2/03/2014 1:05 p.m., Greg Marshall wrote:

    Warren,

     

    Below is the <parts> section with most of it snipped out. Note

    occurrences of "SUPPLY1" near the beginning and end:

     

    <parts>

    <part name="D1" library="diode" deviceset="1N4004" device=""/>

    <part name="FRAME1" library="frames" deviceset="FRAME_B_L" device=""/>

    <part name="C3" library="rcl" deviceset="C-US" device="025-025X050"

    value="0.1uF"/>

    <part name="C4" library="rcl" deviceset="C-US" device="025-025X050"

    value="0.1uF"/>

    <part name="C6" library="rcl" deviceset="C-US" device="025-025X050"

    value="0.1uF"/>

    <part name="C7" library="rcl" deviceset="C-US" device="025-025X050"

    value="33pF"/>

    <part name="C8" library="rcl" deviceset="C-US" device="025-025X050"

    value="33pF"/>

    <part name="SUPPLY1" library="supply2" deviceset="GND" device=""/>

    <part name="SUPPLY2" library="supply2" deviceset="GND" device=""/>

    <part name="SUPPLY3" library="supply2" deviceset="GND" device=""/>

    .

    .

    .

    <part name="U2" library="uln-udn" deviceset="ULN2068B" device="N"/>

    <part name="C16" library="rcl" deviceset="C-US" device="025-025X050"

    value="0.1uF"/>

    <part name="SUPPLY1" library="supply2" deviceset="GND" device=""/>

    <part name="F1" library="ptc-ntc" deviceset="B57164" device=""/>

    <part name="C17" library="rcl" deviceset="CPOL-US" device="E2-5"

    value="33uF"/>

    <part name="J1" library="GBM" deviceset="PWR-JACK-2.5MM" device=""/>

    </parts>

     

    And here is a similarly edited part of the <instances> section:

     

    <instances>

    <instance part="D1" gate="1" x="60.96" y="251.46"/>

    <instance part="FRAME1" gate="G$1" x="0" y="0"/>

    <instance part="FRAME1" gate="G$2" x="325.12" y="2.54"/>

    <instance part="C3" gate="G$1" x="111.76" y="233.68"/>

    <instance part="C4" gate="G$1" x="195.58" y="198.12"/>

    <instance part="C6" gate="G$1" x="330.2" y="116.84"/>

    <instance part="C7" gate="G$1" x="101.6" y="106.68"/>

    <instance part="C8" gate="G$1" x="116.84" y="106.68"/>

    <instance part="SUPPLY1" gate="GND" x="53.34" y="215.9"/>

    <instance part="SUPPLY2" gate="GND" x="109.22" y="91.44"/>

    .

    .

    .

    <instance part="U2" gate="A" x="330.2" y="147.32"/>

    <instance part="C16" gate="G$1" x="332.74" y="182.88"/>

    <instance part="SUPPLY1" gate="GND" x="332.74" y="172.72"/>

    <instance part="F1" gate="1" x="38.1" y="251.46" smashed="yes"

    rot="R90">

    <attribute name="NAME" x="40.132" y="253.7206" size="1.778" layer="95"/>

    <attribute name="VALUE" x="43.307" y="253.492" size="1.778" layer="96"

    rot="R90"/>

    </instance>

     

    Does this tell you anything?

     

    Greg

     

    --

     

     

    Thanks Greg

    The XML looks well formed. For some reason Eagle permitted a part of the

    same name or made an error when writing out during the save, Anyway your

    solution is fine.

     

    Since about v6.5 Jorge reports there have been more checks made when a

    board loads so maybe this is why it has shown up now.

     

    All the best

    Warren

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • autodeskguest
    0 autodeskguest over 12 years ago in reply to e14 Contributor

    On 2/03/2014 1:05 p.m., Greg Marshall wrote:

    Warren,

     

    Below is the <parts> section with most of it snipped out. Note

    occurrences of "SUPPLY1" near the beginning and end:

     

    <parts>

    <part name="D1" library="diode" deviceset="1N4004" device=""/>

    <part name="FRAME1" library="frames" deviceset="FRAME_B_L" device=""/>

    <part name="C3" library="rcl" deviceset="C-US" device="025-025X050"

    value="0.1uF"/>

    <part name="C4" library="rcl" deviceset="C-US" device="025-025X050"

    value="0.1uF"/>

    <part name="C6" library="rcl" deviceset="C-US" device="025-025X050"

    value="0.1uF"/>

    <part name="C7" library="rcl" deviceset="C-US" device="025-025X050"

    value="33pF"/>

    <part name="C8" library="rcl" deviceset="C-US" device="025-025X050"

    value="33pF"/>

    <part name="SUPPLY1" library="supply2" deviceset="GND" device=""/>

    <part name="SUPPLY2" library="supply2" deviceset="GND" device=""/>

    <part name="SUPPLY3" library="supply2" deviceset="GND" device=""/>

    .

    .

    .

    <part name="U2" library="uln-udn" deviceset="ULN2068B" device="N"/>

    <part name="C16" library="rcl" deviceset="C-US" device="025-025X050"

    value="0.1uF"/>

    <part name="SUPPLY1" library="supply2" deviceset="GND" device=""/>

    <part name="F1" library="ptc-ntc" deviceset="B57164" device=""/>

    <part name="C17" library="rcl" deviceset="CPOL-US" device="E2-5"

    value="33uF"/>

    <part name="J1" library="GBM" deviceset="PWR-JACK-2.5MM" device=""/>

    </parts>

     

    And here is a similarly edited part of the <instances> section:

     

    <instances>

    <instance part="D1" gate="1" x="60.96" y="251.46"/>

    <instance part="FRAME1" gate="G$1" x="0" y="0"/>

    <instance part="FRAME1" gate="G$2" x="325.12" y="2.54"/>

    <instance part="C3" gate="G$1" x="111.76" y="233.68"/>

    <instance part="C4" gate="G$1" x="195.58" y="198.12"/>

    <instance part="C6" gate="G$1" x="330.2" y="116.84"/>

    <instance part="C7" gate="G$1" x="101.6" y="106.68"/>

    <instance part="C8" gate="G$1" x="116.84" y="106.68"/>

    <instance part="SUPPLY1" gate="GND" x="53.34" y="215.9"/>

    <instance part="SUPPLY2" gate="GND" x="109.22" y="91.44"/>

    .

    .

    .

    <instance part="U2" gate="A" x="330.2" y="147.32"/>

    <instance part="C16" gate="G$1" x="332.74" y="182.88"/>

    <instance part="SUPPLY1" gate="GND" x="332.74" y="172.72"/>

    <instance part="F1" gate="1" x="38.1" y="251.46" smashed="yes"

    rot="R90">

    <attribute name="NAME" x="40.132" y="253.7206" size="1.778" layer="95"/>

    <attribute name="VALUE" x="43.307" y="253.492" size="1.778" layer="96"

    rot="R90"/>

    </instance>

     

    Does this tell you anything?

     

    Greg

     

    --

     

     

    Thanks Greg

    The XML looks well formed. For some reason Eagle permitted a part of the

    same name or made an error when writing out during the save, Anyway your

    solution is fine.

     

    Since about v6.5 Jorge reports there have been more checks made when a

    board loads so maybe this is why it has shown up now.

     

    All the best

    Warren

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
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.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube