deep hole drilling...subsequent pecks?

[Jammer™]

Let's say I am drilling a hole 2" deep with a short drill, then taking it to 5" deep with another drill. I peck drill my first hole at .125 a peck. I want my second drill to start at -2" on the first peck and each subsequent peck to be .125 down to my -5" depth. I can post this with a hurco post and it reads out three different z depths, and works fine. But when I use my okk post it puts in a z-5.000, my reference height value, and a Q2.000 Well that wants to drill 2" deep on the first peck, and 2" deep on every other subsequent peck as well. My okk post reads like this:

fmt Q 2 peck1 #first peck increment (pos)

fmt 2 peck2 #second or last peck (pos)

fmt Q 2 shftdrl #fine bore tool shift

fmt R 2 refht_a #reference height

fmt R 3 refht_i #reference height

 

Do I need to add a letter on that second line (where the Q's and R's are)for it to pick up my second peck increment? And if I do, will the machine read it? I don't know if this can be fixed through Mastercam, or do I need to call OKK? Thanks for any input.

[Roger Martin from CNC Software]

Jammer,

 

Question #1 is...

 

Does your OKK even HAVE subsequent peck capability? Is there a word address in the programming manual for a subsequent peck parameter?

If so, it is an easy post change.

[Jammer™]

I don't believe that they support subsequent pecking. As far as I can tell from the books and trying dry runs on the machine anyway. I have sent our okk rep an e-mail, but I haven't heard anything yet. If they don't support it, is there a way to make it happen, either thru mastercam or by altering the post? I have used my top of stock parameter, but It wants to rapid to my initial depth, and I don't like that.

[steve f]

Jammmer,

 

your post can output drilling cycles in long code which would give you what you want (at the expense of a short program), although I don't know off hand where to find it in your post. Maybe someone'll chime in soon and tell you where to look,

 

Steve

[Roger Martin from CNC Software]

If your Pecking Cycle doesn't support a Subsequent Peck parameter -

you will need to turn off canned cycle output for Peck Drilling.

 

Find in your PST->

usecanpeck : yes #Use canned cycle for Peck

 

Change to ->

usecanpeck : no #Use canned cycle for Peck

 

 

Now the 1st Peck, Subsequent Peck and Peck Clearance values

are used when generating LONG HAND output (using G0 & G1 moves).

 

That may not sound too appealing, ALL your peck drilling in long hand format?

If you sometimes want the G83 canned cycle and sometimes need to go to the

long hand output to use Subsequent Peck, etc - there is a way.

You can add some logic in the PDRILL0 postblock like shown below...

 

Now if you program a Peck Cycle and specify ZERO for the Subsequent Peck value,

you will get a G83 canned drilling cycle call. But if you enter a NON-ZERO value

for the Subsequence Peck the post will change over to long hand output.

 

 

code:

---

pdrill0         #Pre-process before drill call

sav_dgcode = gcode #Capture gcode for 5 axis drill

 

#Added (2/19/2003) -->>

if drillcyc = 1, # Peck Cycle is programmed

[

if peck2 = 0,

usecanpeck = yes #Use canned cycle for Peck

else,

usecanpeck = no #Use canned cycle for Peck

]

---

[steve f]

...and output the long hand code as a sub program. Then you can see what it's doing instead of sifting through 30 miles of g-code. Might be worth a try anyway...

[Rick Damiani]

quote:

---

I have used my top of stock parameter, but It wants to rapid to my initial depth, and I don't like that.

---

Set the feed plane for that operation to the real top of stock. That will force the initial plunge to happen at the feed rate, followed by peck drilling starting at the correct depth.

[Jammer™]

Thanks alot for the help guys. That is exactly what I need to do. Roger, could I send you a copy of my post? I went to the section where it says "pdrill0" and it doesn't look anything like your example. Being the "non-post editor" that I am, I am afraid of messing something up.

[?Mark]

I've been searching for an easy way to switch between canned cycle and long hand without doing custom drill cycle and looks like I found it...but it's old...

 

 

quote:

---

Now if you program a Peck Cycle and specify ZERO for the Subsequent Peck value,

you will get a G83 canned drilling cycle call. But if you enter a NON-ZERO value

for the Subsequence Peck the post will change over to long hand output.

---

Roger, It's a great way of setting conditional long or canned cycle depending on the "Subsequent Peck value".

 

Can it be done in current mpfan post with

pchpbrk$ #Canned Chip Break Cycle

 

???

 

Regards, Mark

[HEAVY METAL]

Hi roger

I'm trying to get this to work in the mpmaster post. I have replaced the pdrill0 section with the above code. i had to add the peck2 to the ppeck section but it does not seem to be switching between the two formats when i enter a subsequent peck value? i know i'm leaving something out. any ideas

thanks heavy

[?Mark]

Heavy, it's almost 4 year old thread

 

I stumbled upon it while searching for an easy way to switch between canned and long hand cycle...

Looks like a sweet way to do it.

Hopefully Roger will chime in

[Roger Martin from CNC Software]

mark,

 

To do the same the ChipBreak you should be able to use the same type of logic.

 

** You'll need to append the '$' sign on all these variables if running X !

code:

---

      #Added (2/19/2003) -->>

if drillcyc = 1, # Peck Cycle is programmed

[

if peck2 = 0,

usecanpeck = yes #Use canned cycle for Peck

else,

usecanpeck = no #Use canned cycle for Peck

]

 

#Added (11/15/2006) -->>

if drillcyc = 2, # ChipBreak Cycle is programmed

[

if peck2 = 0,

usecanchip = yes #Use canned cycle for Chip Break

else,

usecanchip = no #Use canned cycle for Chip Break

]

---

-----

Heavy,

 

mpmaster post

 

Sorry, I can't help you there...

Try getting In-House's attention or one of the (many) MPMaster experts on the fourm to assist.

[Allan Brown]

Roger's code is for V9. Not X or X2 - missing $ signs after all the pre-defined variables.

 

Another caution - I'd edit your Control Def, Machine Cycles, Mill, Long code option, Percent of subsequent peck distance. Change to 100. 60 results in reams of code, in my opinion.