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) Re: Need a Way to Get Rid of CAM .GPI Files
  • 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 191 subscribers
  • Views 2289 views
  • Users 0 members are here
Related

Re: Need a Way to Get Rid of CAM .GPI Files

e14 Contributor
e14 Contributor over 15 years ago

On 1/18/2011 1:48 PM, James Morrison wrote:

I know this has come up before but I'm having to delete a lot of these

lately and it is annoying.

 

I have no use for the .gpi files that are generated when creating

gerbers. We need a way to add a tab to the CAM file (last one I would

think) that

can specify a system command to run. Then users could do all kinds of

things for production file generation, including running a command line to

remove those silly .gpi files.

 

I can't count how many thousands of those files I have deleted--that is all

wasted time that I'll never get back. And I don't want to have to go to a

command line to do it manually--the tool should allow a way to clean up

automatically.

 

James.

thought I was the only one...why not just make their generation

optional? or get rid of it? I don't find them useful, does anyone?

 

  • Sign in to reply
  • Cancel
  • rachaelp
    rachaelp over 8 years ago in reply to hbridge99

    hbridge99  wrote:

     

    Oh nice! A reason to upgrade I guess.

     

    I just read your earlier post from 2015 about creating the directories specified on the fly. The latest CAM processor will also create any directories you specify in the output file paths so you don't have to do it manually.

     

    It also supports Gerber X2 format and deals with polygons properly so rather than creating polygon fills in the gerbers with lines they are using the proper polygon support in the gerbers which makes them a lot smaller and the output speed of the CAM is massively improved.

     

    hbridge99  wrote:

     

    It's great to see Autodesk actually fixing some of the dumb stuff in Eagle.

    There's lots of dumb stuff to fix.

     

    There's a lot that's not dumb too and they've added a massive amount of new features in the last year. It's worth a look if you haven't already. The latest releases have Push&Shove routing, Live DRC (which is actually really useful), SPICE integrated right into EAGLE and not by calling an external SPICE tool. There is also integration with Fusion360 which is great except it's not 100% reliable yet and relies on the managed libraries feature which I do not want to use.

     

    Another thing that's been added recently which has been asked about MANY times is a flip board view, i.e. a proper one which just shows the view from the reverse. The old mirror board ULP actually changed your data so wasn't really useful but now we have a true bottom side view while in the layout.

     

    They've also added what is called a "Manufacturing flyoff" which gives an image of what the board will look like, stats about the board, allows the image, dxf's etc to be exported. It's very useful too.

     

    They still have a lot of work to do to add in all the features and improvements that people have been asking for over the years, it's a long list because of how resource starved they were for a long time. Now Autodesk are investing heavily into EAGLE and it's improving rapidly.

     

    Best Regards,

     

    Rachael

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hbridge99
    hbridge99 over 8 years ago in reply to rachaelp

    Oh nice! A reason to upgrade I guess.

    Thanks for the reply.

    It's great to see Autodesk actually fixing some of the dumb stuff in Eagle.

    There's lots of dumb stuff to fix.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • rachaelp
    rachaelp over 8 years ago in reply to hbridge99

    hbridge99  wrote:

     

    Still undone 02/2018?

     

    How hard is it to suppress the output of file?

     

    There is a completely new CAM in 8.6.0, I've just checked explicitly for this file but it is not being generated by the new CAM. There is a .gbrjob file exported now but in the main Gerber section you can uncheck a box to turn that off. The output now simply contains the specified Gerber and Excellon files, nothing else.

     

    Best Regards,


    Rachael

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hbridge99
    hbridge99 over 8 years ago

    Still undone 02/2018?

     

    How hard is it to suppress the output of file?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hbridge99
    hbridge99 over 11 years ago in reply to e14candies

    chuckling - it's the Eagle way!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14candies
    e14candies over 11 years ago

    that is all wasted time that I'll never get back. And I don't want to have

    to go to a command line to do it manually

     

     

    There is probably a ULP to retrieve your time image

    --

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

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hbridge99
    hbridge99 over 11 years ago in reply to e14 Contributor

    Users have been asking for this functionality for 10 years I bet, but at least for five revisions / versions. How hard can this be fix?

    It would also be nice to be able to do some simple OS commands like make a new folder, so Gerber folders could be made automatically.

     

    CadSoft development remains a divine mystery.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14 Contributor
    e14 Contributor over 15 years ago in reply to e14 Contributor

    Olin wrote on Wed, 19 January 2011 08:11

    Quote:

    They are small but it doubles the numbers of files for absolutely

    now reason.  If there was a value then it might be different but to

    this point no one can tell me why I'd ever want them.

     

    I don't see a value in them either, but I also don't see how they

    double the number of files.  I get one per CAM run, which is to say one

    per board.

     

     

    I get one per layer.  I use .grb as the file extension for my gerber files

    and I get a .gpi file for every .grb file.

     

    James.

    --

    James Morrison  ~~~  Stratford Digital

     

    Specializing in CadSoft EAGLE

    • Online Sales to North America

    • Electronic Design Services

    • EAGLE Enterprise Toolkit

    --

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

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14 Contributor
    e14 Contributor over 15 years ago in reply to e14 Contributor

    James Morrison wrote on Tue, 18 January 2011 18:24

    The reason I specifically delete them is because I was asked a few

    times by different manufacturers about those files--they seemed to

    confuse them.  So to reduce the confusion I stopped sending them.  Now no

    one complains.

     

    I've probably never had that problem because of the readme file I always

    include with the package of board files.  For example, here is the

    README_FAB.TXT file for a sample 4 layer board:

     

     

    File names:

      .plc  -  Top silk screen

      .stc  -  Top solder mask

      .cmp  -  Top copper

      .ly2 to .lyN  -  Inner layers from top to bottom

      .sol  -  Bottom copper

      .sts  -  Bottom solder mask

      .pls  -  Bottom silk screen

      .drl  -  Drill sizes

      .drd  -  Drill data

      .out  -  Board outline

      .dri  -  Human readable drill information

      .gpi  -  Human readable photoplotter informationThis is all automatically

    generated by the script that picks up the various CAM processor output

    files and builds the ZIP file that board houses all want to see.  The

    script knows certain files are optional, and if they aren't present it

    doesn't add a entry for them in the list above.  It can also pick up a

    notes file, the contents of which it will append after this list.

     

    My process is that I run the ULPs and CAM processor jobs (that part could

    be automated better) that creates the various Eagle output files.  Then I

    run my script EAGLE_PCB, which picks up all the files, figures out what's

    in this board, builds the readme file, adds the notes if present, and zips

    up everything ready to plunk on just about any board house in the world.

    Each released version of every board gets its own subdiretory, so the .GPI

    file may be a waste of space, but a very minor one, and nothing I ever have

    to manually deal with.

     

    In case anyone is interested, the EAGLE_PCB script and a lot of other Eagle

    tools is in my free http://www.embedinc.com/pic/dload.htm.

     

    Quote:

    They are small but it doubles the numbers of files for absolutely now

    reason.  If there was a value then it might be different but to this

    point no one can tell me why I'd ever want them.

     

    I don't see a value in them either, but I also don't see how they double

    the number of files.  I get one per CAM run, which is to say one per

    board.

     

    Quote:

    A good tool should clean up after itself.

     

    I do agree that it's inconsistant that Eagle always creates the .GPI file

    without you enabling that or not specifically disabling it.  Everything

    else is selectable.

     

    Quote:

    And being able to run arbitrary commands from the CAM processor would

    be very useful in general, this would just be one use of that.

     

    Agreed.  I'd probably have it run my EAGLE_PCB script when done making the

    board fab files.

     

    I also have a EAGLE_ASSY script that does something similar for assembly

    files as apposed to board fab files.

    --

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

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14 Contributor
    e14 Contributor over 15 years ago in reply to Richard_H

    Richard Hammerl wrote on Wed, 19 January 2011 02:01

    Am 19.01.2011 00:24, schrieb James Morrison:

    Olin wrote on Tue, 18 January 2011 17:56

    >> James Morrison wrote on Tue, 18 January 2011 16:48

    >> > I know this has come up before but I'm having to delete a lot of

    >> > these lately and it is annoying.

    >>

    >> They are generally small, so what's the big deal just leaving them

    >> there?  My automated script that makes the ZIP file for board fab

    >> includes the GPI file, although I don't know if any board house has

    ever

    >> looked at it.  I figure if it resolved even one confusion once it

    will

    >> have been worth it.  It really takes no extra time to deal with

    since

    >> it's all automated.  The README file that the automated script

    creates

    >> lists the GPI file as "Human readable photoplotter information", so

    it

    >> can be easily ignored by anyone that doesn't care.

     

    Hi Olin,

     

    The reason I specifically delete them is because I was asked a few

    times by

    different manufacturers about those files--they seemed to confuse

    them.  So

    to reduce the confusion I stopped sending them.  Now no one

    complains.

     

    They are small but it doubles the numbers of files for absolutely

    now

    reason.  If there was a value then it might be different but to

    this point

    no one can tell me why I'd ever want them.

     

    A good tool should clean up after itself.

     

    And being able to run arbitrary commands from the CAM processor

    would be

    very useful in general, this would just be one use of that.

     

    James.

     

    James,

     

    you could use a simple batch file that executes

     

    DEL /S *.gpi

     

    for example when you are starting Windows.

    It would also be possibe to start EAGLE with a batch file that deletes

    theses files before.

     

     

    Yes I know Richard.  I can do that.  I do something similar but it uses a

    GUI instead.

     

    The point is that the tool should allow a way to do this automatically.

    Those files cause confusion with manufacturers because no other CAD tool

    that I know of produces them.

     

    From a manufacturer's point of view I understand.  If they don't make

    exactly what the customer wants the won't get paid.  So they look at every

    file that gets sent and if they don't know then they ask.  I would do the

    same and I expect that from all my PCB suppliers.   So these extra files

    cause extra work for them too and delay PCB manufacturing.

     

    In the close to 1000 PCB's that I have done with EAGLE I have never had a

    use for these files.  And no one has ever asked for them.  And no one

    (CadSoft or a user)has ever given me one reason for keeping them here in

    the forums.  That tells me they are useless.  Useless files that only

    hinder or confuse manufacturers.

     

    So why would EAGLE want to keep them?

     

    But in the end, I'm a user telling you a small, easily fixable, frustration

    that I need a way for the tool to NOT create these.  Isn't that enough?

    Others have chimed in saying the same thing.  Give us a box or something to

    stop this or another way to have the tool cleanup after itself.  Those who

    want the current way (and remember, no one has ever stated that they use

    these files as far as I can tell) can keep it.

     

    James.

    --

    James Morrison  ~~~  Stratford Digital

     

    Specializing in CadSoft EAGLE

    • Online Sales to North America

    • Electronic Design Services

    • EAGLE Enterprise Toolkit

    --

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

     

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