Actions
Forum Thread Details
  • Replies 12 replies
  • Subscribers 183 subscribers
  • Views 2067 views
  • Users 0 members are here
Related

drill data generation & update

autodeskguest

When processing drill data in preperation to generate gerber outputs, I have

not yet found a way to automatically update the drill table in Options ->

Set -> Drill.   Clicking the "SET" button on the Drill table does

automatically extract drill sizes from the current project, but does not

sort them in increasing diameter (I would prefer it did).  But even if it

did sort them, it is still a manual process.  I can't even find a way to

execute that "SET" button command through a .ULP script.

 

Am I missing something?   Seems that matching the Drill Table

(options->set->drill) with the ULP-generated Drill Legend should be a

single-step process, right?

 

I'd be happy to update the drill-legend ULP to do this, but can't find any

ULP hooks to do it.

 

thanks,

..dane

 

 

 

Parents

  • However it is useful on the FAB drawing. This is used for the FAB house

    to quote, and check the board.

     

    I've never had a complaint or a problem getting a quote when I sent just

    sent the normal .drl, .drd, and .dri drill files to a board house.

     

    We, too, send the normal .drl/etc files to the fab house, but also include a

    reference drawing layer that includes the board outline and symbolic drill

    data (with a legend).

     

    Whether or not this is absolutely necessary is somewhat beside the point;

    the fact that some companies (like the one I work for) have this data

    generated as a part of the procedure is a reality.  Whether or not this file

    is used in today's environment I cannot answer.  It may be there for

    historical purposes, but it is there nonetheless.  That may seem like a

    silly answer to some, but those who work for companies with set procedures

    acknolwedge that reality.

     

    It is also part of the documentation that I deliver to my customers.

     

    Just give them the .dri file if they even care.  There is advantage in not

    having redundant information in different places and different formats.

    First, they could get out of sync by accident.  Second, someone on the

    other end has to worry about which is the real data, and possibly check

    that the multiple specs match.

     

    It seems you are making this too complicated.

     

    Which is why a single ULP that does both drill rack and drill legend is

    useful.  No more out-of-sync data.  We don't use the DRILLCFG.ULP that you

    describe.  Up until last night we have used Christian Bohrer's DRILEGEND.ULP

    (v2.01), which did both the drill rack and the legend, but admittedly was a

    headache to constantly have to get Eagle's drill table (option>set>drill) in

    the proper sorted sequence..  I've simply updated Christian's old script to

    fix some problems with the legend generation aspect.  Very useful for us,

    and I suspect for a few others also.

     

    cheers,

    ..dane

     

     

     

Reply

  • However it is useful on the FAB drawing. This is used for the FAB house

    to quote, and check the board.

     

    I've never had a complaint or a problem getting a quote when I sent just

    sent the normal .drl, .drd, and .dri drill files to a board house.

     

    We, too, send the normal .drl/etc files to the fab house, but also include a

    reference drawing layer that includes the board outline and symbolic drill

    data (with a legend).

     

    Whether or not this is absolutely necessary is somewhat beside the point;

    the fact that some companies (like the one I work for) have this data

    generated as a part of the procedure is a reality.  Whether or not this file

    is used in today's environment I cannot answer.  It may be there for

    historical purposes, but it is there nonetheless.  That may seem like a

    silly answer to some, but those who work for companies with set procedures

    acknolwedge that reality.

     

    It is also part of the documentation that I deliver to my customers.

     

    Just give them the .dri file if they even care.  There is advantage in not

    having redundant information in different places and different formats.

    First, they could get out of sync by accident.  Second, someone on the

    other end has to worry about which is the real data, and possibly check

    that the multiple specs match.

     

    It seems you are making this too complicated.

     

    Which is why a single ULP that does both drill rack and drill legend is

    useful.  No more out-of-sync data.  We don't use the DRILLCFG.ULP that you

    describe.  Up until last night we have used Christian Bohrer's DRILEGEND.ULP

    (v2.01), which did both the drill rack and the legend, but admittedly was a

    headache to constantly have to get Eagle's drill table (option>set>drill) in

    the proper sorted sequence..  I've simply updated Christian's old script to

    fix some problems with the legend generation aspect.  Very useful for us,

    and I suspect for a few others also.

     

    cheers,

    ..dane

     

     

     

Children
No Data