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
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • 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 182 subscribers
  • Views 1599 views
  • Users 0 members are here
Related

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

Former Member
Former Member over 14 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
Parents
  • Former Member
    Former Member over 14 years ago

    The gpi files are generated for each job. Normally you see only the last

    job's gpi file cause the others are overwritten. The filename of the info

    file can be altered (look for "%I" placeholder in the manual). I use

    ".[ext]%I{.info}" for my cam data file name, so I get an info file for each

    job, and it also shows you explicitly that the "xxx.yyy.info" file belongs

    to the "xxx.yyy" cam data. This removes the gpi related questions from the

    manufacturer.

     

    Now, this filename ought to be the standard filename in the cam files that

    comes with eagle so that people learn how to use it.

     

    Also I agree with you that the info file should not be written unless you

    use the %I placeholder.

     

     

    "James Morrison" <james@eaglecentral.ca> wrote in message

    news:ih51qv$cl$1@cheetah.cadsoft.de...

    >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.

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Former Member
    Former Member over 14 years ago

    The gpi files are generated for each job. Normally you see only the last

    job's gpi file cause the others are overwritten. The filename of the info

    file can be altered (look for "%I" placeholder in the manual). I use

    ".[ext]%I{.info}" for my cam data file name, so I get an info file for each

    job, and it also shows you explicitly that the "xxx.yyy.info" file belongs

    to the "xxx.yyy" cam data. This removes the gpi related questions from the

    manufacturer.

     

    Now, this filename ought to be the standard filename in the cam files that

    comes with eagle so that people learn how to use it.

     

    Also I agree with you that the info file should not be written unless you

    use the %I placeholder.

     

     

    "James Morrison" <james@eaglecentral.ca> wrote in message

    news:ih51qv$cl$1@cheetah.cadsoft.de...

    >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.

     

     

     

    • 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 © 2025 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