Home > Community > Forums > PCB Design > About eco.txt

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 About eco.txt 

Last post Tue, Nov 20 2007 1:02 AM by archive. 3 replies.
Started by archive 20 Nov 2007 01:02 AM. Topic has 3 replies and 1018 views
Page 1 of 1 (4 items)
Sort Posts:
  • Tue, Nov 20 2007 1:02 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    About eco.txt Reply

    As we know, there is a log file which named eco.txt in physical folder. It's generated by the action, Export physical and update PCB. It reports the details of design modification.

    Now my problem is how to keep the multiple version for the eco.txt in one file?
    Because the general eco.txt will be overwritten by the new version, during exporting physical.
    I needĀ a kind of multiple eco.txt, it can record all the history for modification in one log file.

    How can I get the solution? Thanks.

    My CadenceĀ version is still 15.5.1.


    Originally posted in cdnusers.org by leonlee
    • Post Points: 0
  • Mon, Dec 3 2007 3:50 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: About eco.txt Reply

    Hi Leonlee,

    the previous version ov eco.txt will be renamed to eco.txt,1 and so on. so what ever latest changes is imported to layout will be in eco.txt. If you want a consolidated eco.txt report only way is to use a skill program if available / import the final schematic with all the changes to the old file so that all the changes are logged into single eco.txt file. This is only for documentation.


    Originally posted in cdnusers.org by eswar
    • Post Points: 0
  • Mon, Dec 3 2007 5:33 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: About eco.txt Reply

    Yes, I have tried to solve it by SKILL. Copy the original eco.txt, and read the new eco.txt line by line, then write them to a consolidated eco.txt together.Just for documentation only.


    Originally posted in cdnusers.org by leonlee
    • Post Points: 0
  • Mon, Dec 3 2007 5:47 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: About eco.txt Reply

    Hi Leonlee,

    I've done this a couple ways, and still do:

    1) Document EVERY single change that comes in. Date; Engineer; change requested; etc.
    2) Keep the very first board you started, with the original netlist imported. When someone wants all the changes, take that file and read in the latest netlist. IT WILL SHOW ALL THE CHANGES to date. :) This helps cover your butt. It's especially enlightening for management when they look at COMPONENT ADDITIONS. :) When the eco.lst file gets more than 10 pages long, people tend to disappear. :)

    Good day.
    Mitch


    Originally posted in cdnusers.org by cadpro2k
    • Post Points: 0
Page 1 of 1 (4 items)
Sort Posts:
Started by archive at 20 Nov 2007 01:02 AM. Topic has 3 replies.