Post process 126 holes into separate files

[LazyRiverLife]

I have created a wasteboard that has a grid pattern of 126 holes where I have put in screw inserts.   The pattern was done in F360 and I drilled them all at one time.   So far so good.

Now, I want to generate a separate gcode file for each hole that I can use to pre-drill into my materials what I will be using to hold them down and (hopefully) name them as  DrillR1C1, DrillR2C1, DrillR2C1, DrillR2C2, etc. etc.

This way I don't have to go back to F360 all the time for every piece I work on.   I can just call up the gcode for that hole position and it will peck drill it out.   

I am trying to be lazy and somehow generate this rather than selecting each hole one by one and post processing it.

Any ideas?

[CAMtech_Software]

With Selection mode, you can select it by giving a diameter range if you want. If you don't like this, the Select Same Diameter option will keep all the hole diameters you selected first.

 

 

[LazyRiverLife]

Thanks for the reply, but my question is more around how to generate separate post process files (one for each hole) rather than how to select all of them in order to post process.  

[CAMtech_Software]

I slightly changed the example I prepared for you. I got a separate line for each hole but in a single coordinate system. If you want, you can reproduce this with multiple wcs, but you will need to constantly get offset on your machine.

 

[LazyRiverLife]

Hmmm....I'll take a closer look at that.   The holes I am creating are using a pecking process and then a contour so it generates a lot more code and uses relative positioning, making it complicated to generate a single file and cut/paste the blocks for each hole.  This is why I wanted to actually generate separate post processing files.

For now, I have been generating the ones that I need as I go.   Eventually I might end up with all 126 holes, but for now I have about 20 or so.   It just would be nice to pull up a r2c3 and a r5c12 without having to go back to the computer.   

[programming2C78B]

if youre on a true grid, make a code that does 1 single hole on center of your g54. Manually move there relative to your table or part 0 and just run it however times is needed. 

[LazyRiverLife]

Yeah thought about that, but that means I have to recall/write down a list of all the locations of each hole.   It is a tedious task to do it one by one, but once I get my library setup, I can do all kinds of things just by specifying a row and column.

For a straight peck drill (with no contour), I created a parameter based gcode that lets me plug in my row and column, and that works great, but anything that goes into more complicated moves, it becomes tricky.    On top of that, Onefinity doesn't support prompting for parameters, so I have to set a global gcode value in one screen and then run the peck drill on another; hoping that I remembered to set the global gcode values properly.   So far it has been ok, but I know one day I am going to forget a step and drill a hole in the wrong place or break a bit....just a matter of time, I guess.

Anyway, I appreciate your suggestions!   Thank you.  😁