Added Generic Commands to CAM Processor

James Morrison wrote on Thu, 11 November 2010 11:10

With all these changes the CAM processor would really become "Export

Manager" or something like that.

One other use of this is would be to run a script to delete those really

annoying .gpi files that are created for the gerbers.  They confuse board

houses when you send them and they have no use that I've ever seen.  So I

always just delete them.  But it's an unnecessary step that I should be

able to get EAGLE to do somehow.   A cleanup script to run as the last

section of a CAM job would be a good place to do 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.

On 11/12/2010 08:28 AM, James Morrison wrote:

James Morrison wrote on Thu, 11 November 2010 11:10

>> With all these changes the CAM processor would really become "Export

>> Manager" or something like that.

>

One other use of this is would be to run a script to delete those really

annoying .gpi files that are created for the gerbers.  They confuse board

houses when you send them and they have no use that I've ever seen.  So I

always just delete them.  But it's an unnecessary step that I should be

able to get EAGLE to do somehow.   A cleanup script to run as the last

section of a CAM job would be a good place to do it.

 

James.

James,

This is an excellent suggestion.  Two additional sections could be added

to the cam file - one for PRE-CAM actions, and one for POST-CAM actions.

    Description="..."

    Section=camprep

    Section=TopScreen

    ...

    Section=Drill

    Section=campost

    ULP="drillcfg.ulp"

    ULP="genxydata.ulp"

    ...

    ULP="cam-wrapup.ulp"

    ULP="/usr/local/lib/my-cam-stuff.ulp"

We're all familiar with drillcfg.ulp, but it could be modified to

automatically save without mods in inches.  "cam-wrapup.ulp" can launch

a shell to run a shell script.  It could also produce the x-y data,

clean up the .gpi files, and zip everything together to send to the fab

house.

The CAM processor would recognize the exit status of the ULP.  If

non-zero, stop the job.

The capabilities are interesting with an added feature like this.

On 11/12/2010 08:28 AM, James Morrison wrote:

James Morrison wrote on Thu, 11 November 2010 11:10

>> With all these changes the CAM processor would really become "Export

>> Manager" or something like that.

>

One other use of this is would be to run a script to delete those really

annoying .gpi files that are created for the gerbers.  They confuse board

houses when you send them and they have no use that I've ever seen.  So I

always just delete them.  But it's an unnecessary step that I should be

able to get EAGLE to do somehow.   A cleanup script to run as the last

section of a CAM job would be a good place to do it.

 

James.

James,

This is an excellent suggestion.  Two additional sections could be added

to the cam file - one for PRE-CAM actions, and one for POST-CAM actions.

    Description="..."

    Section=camprep

    Section=TopScreen

    ...

    Section=Drill

    Section=campost

    ULP="drillcfg.ulp"

    ULP="genxydata.ulp"

    ...

    ULP="cam-wrapup.ulp"

    ULP="/usr/local/lib/my-cam-stuff.ulp"

We're all familiar with drillcfg.ulp, but it could be modified to

automatically save without mods in inches.  "cam-wrapup.ulp" can launch

a shell to run a shell script.  It could also produce the x-y data,

clean up the .gpi files, and zip everything together to send to the fab

house.

The CAM processor would recognize the exit status of the ULP.  If

non-zero, stop the job.

The capabilities are interesting with an added feature like this.