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
  • 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) Downgrading brd/sch from V5 -> V4
  • 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
  • Replies 15 replies
  • Subscribers 181 subscribers
  • Views 1061 views
  • Users 0 members are here
Related

Downgrading brd/sch from V5 -> V4

nickds1
nickds1 over 17 years ago

I've been playing with V5, and very nice it is too! (thanks guys).

 

However, I publish a few designs on the web & elsewhere, and the bottom line

is that very few Eagle users will be on V5 for some time, especially as its

a cost-option and V4.16r2 is pretty stable.

 

So, can I save/export a V5 project in V4 format, such that V4 users can work

with it? Even MS Word allows this sort of functionality. A ULP that stripped

all the V5 extras (attributes etc.) would probably be the route to take...

 

Is this possible/has it been done?

 

Thanks

 

Nick

 

 

 

  • Sign in to reply
  • Cancel
Parents
  • Richard_H
    Richard_H over 17 years ago

    James Morrison schrieb:

     

     

    Hi Richard,

     

    Would it not be possible to include "Save As..." with an option to store in

    an older file formats (3.5, 4.0, 4.1)?  Almost every program I know allows

    for this.  Even Microsoft, the king of forced upgrades for little value has

    this feature.  Given the code exists already it doesn't appear to be

    technically infeasible.  I suppose it would increase the code size somewhat

    but it can't be that different.  Even if it was would it matter?

     

     

     

    One the one hand I support your point. Of course it would be nice

    to have the possibility to design a board in EAGLE 5 and save it

    in EAGLE 4.1 data format, or as you propose even in 4.0 or 3.5.

    So far so good. To have such an option would be very nice.....

     

    ...but what if the quality of the board in EAGLE 4.1 or 4.0

    is not the same as in EAGLE 5?

    Let's take ARCs, for example:

    Now they can have signals, in EAGLE 4.0 they can't. Suddenly

    you will get lots of DRC errors, RATSNEST tells you something

    about unrouted airwires. Or for example a polygon: It can have

    a round shape. This is not possible in EAGLE 4. It can't be

    displayed anymore in the layout.

    Or an example from version 5 to 4.1:

    Define attibutes for your components. All this information would

    be lost... Yes I know, we could write it in a layer as simple

    text, so not everything would lost.

    Or, for example, make a partlist with a bom.ulp that exports

    attributes. The partlist made with EAGLE 4.1 of the same board/

    schematic would be different. Again arcs: Now the can have

    rounded ends and Gerber export uses an aperture that has

    the same diameter as the arc's width. Go back to EAGLE 4.1 and

    you will have arcs with flat ends. Gerber will use a fine

    width for emulating the arcs. In the worst case the arc is not

    visible on your board.

    And now let's assume your partner (the one with EAGLE 4.1)

    changes something in the board and you want to load it again

    EAGLE 5. I think I can foresee that this might end up in a kind

    of desaster. Not in all cases, sure. I admitt, I am painting

    black here. But I know Murphys law....

     

    Wouldn't a customer expect that the conversion in the older data

    format is without loss withour changes in his design?

    Ich think he would, and I think he is right with his expectation.

    But I see a lot of obstacles and traps for such a function.

     

    Nevertheless I will discuss your proposal with our development

    people.

     

     

    --

    Mit freundlichen Gruessen / Best regards

    Richard Hammerl

      CadSoft Support -- hotline@cadsoft.de

      FAQ: http://www.cadsoft.de/faq.htm

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Richard_H
    Richard_H over 17 years ago

    James Morrison schrieb:

     

     

    Hi Richard,

     

    Would it not be possible to include "Save As..." with an option to store in

    an older file formats (3.5, 4.0, 4.1)?  Almost every program I know allows

    for this.  Even Microsoft, the king of forced upgrades for little value has

    this feature.  Given the code exists already it doesn't appear to be

    technically infeasible.  I suppose it would increase the code size somewhat

    but it can't be that different.  Even if it was would it matter?

     

     

     

    One the one hand I support your point. Of course it would be nice

    to have the possibility to design a board in EAGLE 5 and save it

    in EAGLE 4.1 data format, or as you propose even in 4.0 or 3.5.

    So far so good. To have such an option would be very nice.....

     

    ...but what if the quality of the board in EAGLE 4.1 or 4.0

    is not the same as in EAGLE 5?

    Let's take ARCs, for example:

    Now they can have signals, in EAGLE 4.0 they can't. Suddenly

    you will get lots of DRC errors, RATSNEST tells you something

    about unrouted airwires. Or for example a polygon: It can have

    a round shape. This is not possible in EAGLE 4. It can't be

    displayed anymore in the layout.

    Or an example from version 5 to 4.1:

    Define attibutes for your components. All this information would

    be lost... Yes I know, we could write it in a layer as simple

    text, so not everything would lost.

    Or, for example, make a partlist with a bom.ulp that exports

    attributes. The partlist made with EAGLE 4.1 of the same board/

    schematic would be different. Again arcs: Now the can have

    rounded ends and Gerber export uses an aperture that has

    the same diameter as the arc's width. Go back to EAGLE 4.1 and

    you will have arcs with flat ends. Gerber will use a fine

    width for emulating the arcs. In the worst case the arc is not

    visible on your board.

    And now let's assume your partner (the one with EAGLE 4.1)

    changes something in the board and you want to load it again

    EAGLE 5. I think I can foresee that this might end up in a kind

    of desaster. Not in all cases, sure. I admitt, I am painting

    black here. But I know Murphys law....

     

    Wouldn't a customer expect that the conversion in the older data

    format is without loss withour changes in his design?

    Ich think he would, and I think he is right with his expectation.

    But I see a lot of obstacles and traps for such a function.

     

    Nevertheless I will discuss your proposal with our development

    people.

     

     

    --

    Mit freundlichen Gruessen / Best regards

    Richard Hammerl

      CadSoft Support -- hotline@cadsoft.de

      FAQ: http://www.cadsoft.de/faq.htm

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube