G84 tap cycle post help

[RC1]

Can a post be edited to output the peck depth I set in a tapping cycle as a new line with a G84 and a z depth?

 

my Post output is this...

 

%

O0000

G20

G0 G17 G40 G49 G80 G90

T3 M6

G0 G90 G54 X.986 Y-.6975 S150 M3

G43 H3 Z2. M8

G98 G84 Z-1.875 R.1 Q.025 F9.38

G80

M5

G91 G28 Z0. M9

M30

%

 

 

My Mill dont support the "Q" on a tap cycle.

 

I need this..

 

G90 G54 X1.5 Y-0.5

S450

G43 H01 Z1.0 M08

G84 G99 Z-0.1 R0.1 F22.5

G84 G99 Z-0.15 R0.1 F22.5

G84 G99 Z-0.2 R0.1 F22.5

G84 G99 Z-0.25 R0.1 F22.5

G84 G99 Z-0.3 R0.1 F22.5

G80 G00 Z1. M09

[crazy^millman]

Ok look at your parameters you have a .025 somewhere to the right on the drilling cycle and that should be why you are getting the Q. If not put up the tapping cycle out of the post and we can tell you how to delete that out of the post.

 

HTH

[john316]

.

 

It looks like you want to get a pecking tap cycle.

 

I don't know if Mcam has that built in.

 

You may have to create a custom drill cycle.

 

.

[Jack Mitchell]

I would suggest trying this approach instead.

Run it high as a test.

 

G90 G54 X1.5 Y-0.5

S450

G43 H01 Z1.0 M08

G84 G99 Z-0.1 R0.1 F22.5

Z-0.15

Z-0.2

Z-0.25

Z-0.3

G80 G00 Z1. M09

 

Regards, Jack

[Surface]

May I also suggest using a G code to disable the feedrate and spindle-speed override pot.

[RC1]

Crazy^Millman: Thats a tap cycle with a peck depth.

 

We had a hurco that supported that Q in a pecking tap cycle. The hurco post uses it like that in mastercam. We purchased a new Haas, and to get a pecking tap cycle it needs a G84 with every "z" depth, when it sees a new depth it automaticly chip breaks and goes to the new z depth. The problem is we do very deep tap cycles and to hand edit all those z depths would suck.

[Guest CNC Apps Guy 1]

Nevermind...

[crazy^millman]

Ok I went in a different direction. I will have think about it a little get back to you sorry about that.

[Guest]

I have worked out a peck tap cycle for a HAAS if anyone is interested. I am sure someone else has already done this but I Searched and could not find it. So I went to work. You set the number of pecks you want and the post does the rest.

 

in the pdrlcst$ section I have this

 

code:

---

pdrlcommonb

if drillcyc$ = 13,

[

numpeck = peck2$

peck_cnt = numpeck

initial_calc = (depth$ - tosz$) / peck_cnt

strt_depth = (tosz$ + initial_calc)

calc_depth = (depth$ - tosz$)

calc_peck = calc_depth / numpeck

"(PECK TAPPING CYCLE)", e$

pcan1, pbld, n$, *sgdrlref, *sg84, pdrlxy, *strt_depth, pcout,

prdrlout, *feed, strcantext, e$

count = peck_cnt - 1

pass = 1

WHILE count > 1,

[

sub_depth = strt_depth + (calc_peck * pass)

pbld, n$, *sub_depth, e$

pass = pass + 1

count = count - 1

]

pbld, n$, pfzout, e$

pcom_movea

]

---

In the pdrlcst2$ section I have this

 

code:

---

pdrlcommonb

if drillcyc$ = 13,

[

numpeck = peck2$

peck_cnt = numpeck

initial_calc = (depth$ - tosz$) / peck_cnt

strt_depth = (tosz$ + initial_calc)

calc_depth = (depth$ - tosz$)

calc_peck = calc_depth / numpeck

pcan1, pbld, n$, *sgdrlref, sg84, pdrlxy, *strt_depth, pcout,

*drdrlout, *feed, strcantext, e$

count = peck_cnt - 1

pass = 1

WHILE count > 1,

[

sub_depth = strt_depth + (calc_peck * pass)

pbld, n$, *sub_depth, e$

pass = pass + 1

count = count - 1

]

pbld, n$, pfzout, e$

pcom_movea

]

---

I have these variables defined

 

code:

---

fmt   4 count             # timing counter                         #Peck TAP CYCLE

fmt 4 peck_cnt #remaining no. of pecks #Peck TAP CYCLE

fmt 4 numpeck # No. of pecks #Peck TAP CYCLE

fmt 4 pass # pass counter use to calculate depths #Peck TAP CYCLE

fmt Z 2 sub_depth #subsequent depths #Peck TAP CYCLE

fmt Z 2 calc_depth # The total caculated cutting depth #Peck TAP CYCLE

fmt Z 2 calc_peck # the calculated peck amount #Peck TAP CYCLE

fmt z 2 strt_depth # the first tap depth #Peck TAP CYCLE

fmt Z 2 initial_calc # calculate the initial depth cut #Peck TAP CYCLE

---

And this in the drill cycle defs at the bottom where the .txt now resides

 

code:

---

[drill cycle 14]

1. "Peck Tap cycle"

2. ""

3. ""

4. ""

5. ""

6. ""

7. ""

8. "# of pecks"

9. ""

10. ""

11. ""

---

There might be a cleaner way to do it but it works.

 

If anyone has any suggestions as to how to make this cleaner, my ears are open.

 

Hope it helps someone.

 

[Guest]

whoops, change the small z to a capitol Z in this line

 

code:

---

fmt z 2 strt_depth        # the first tap depth                    #Peck TAP CYCLE

---

[crazy^millman]

Cool John that looks good.

 

[Guest]

I added to this peck tap cycle by giving it another option. You can set an initial depth which it will tap to, then it will begin a series of the peck taps.

 

code:

---

pdrlcommonb

if drillcyc$ = 13,

[

numpeck = peck2$,

stepeck = peck1$,

if stepeck = 0,

[

peck_cnt = numpeck

initial_calc = (depth$ - tosz$) / peck_cnt

strt_depth = (tosz$ + initial_calc)

calc_depth = (depth$ - tosz$)

calc_peck = calc_depth / numpeck

"(PECK TAPPING CYCLE)", e$

pcan1, pbld, n$, *sgdrlref, *sg84, pdrlxy, *strt_depth, pcout,

prdrlout, *feed, strcantext, e$

count = peck_cnt - 1

]

else,

[

peck_cnt = numpeck

strt_depth = (tosz$ + stepeck)

calc_depth = (depth$ - (tosz$ + stepeck))

calc_peck = calc_depth / numpeck

"(PECK TAPPING CYCLE)", e$

pcan1, pbld, n$, *sgdrlref, *sg84, pdrlxy, *strt_depth, pcout,

prdrlout, *feed, strcantext, e$

count = peck_cnt

]

pass = 1

WHILE count > 1,

[

sub_depth = strt_depth + (calc_peck * pass)

pbld, n$, *sub_depth, e$

pass = pass + 1

count = count - 1

]

pbld, n$, sg98, pfzout, e$

pcom_movea

]

---

I added one variable to the list above

code:

---

fmt    3 stepeck   #Inital step peck down increment from top of stock

---

And I added one more input box

 

code:

---

[drill cycle 14]

1. "Peck Tap cycle"

2. ""

3. ""

4. ""

5. ""

6. ""

7. "Inc. 1st step from TOS"

8. "# of pecks"

9. ""

10. ""

11. ""

---

[CNCGUY]

John,

 

This is for X?

 

Would you post a sample program with multiple, peck tap holes.

 

Thanks

[Guest]

Yes it was done in X, notice the $ at the end of the variables.

 

I'll dig around for the post I did this in tonight but I don't think I added this to the pdrill2 section which is all that would be required for multiple locations.

[Guest]

Here's how this coded out this is before the final change I noted above, mind you this isn't a post I used, only coded for someone. I had to dig to find it

 

code:

---

O0000 (T OP1)

N100 G00 G17 G20 G40 G80 G90

N110 T213 M06 ( 3/4-10 TAPRH)

N120 G00 G54 G90 X0. Y0. S356 M03

N130 G43 H0 Z2.

(PECK TAPPING CYCLE)

N140 G98 G84 Z-.0875 R.1 F35.65

N150 Z-.175

N160 Z-.2625

N170 Z-.35

N180 Z-.4375

N190 Z-.525

N200 Z-.6125

N210 Z-.7

N220 Z-.7875

N230 G98 Z-.875

N240 G80

N250 M05

N260 G91 G28 Z0.

N270 G28 Y0.

N280 G90

N290 M30

---

[CNCGUY]

Thanks John. I'll have to work on it and see if I can make it work!!!

[Bryan Johnson]

the link below is to a post on the FTP site that includes this option (repeat peck cycle for peck tap)

 

ftp://mastercam:[email protected]/Ma...ill_Haas_VF.PST

[TECHSERV]

I couldn't get into the FTP site where the new post is...any suggestions?

[seattlewa98]

Where do I add these infor

I have these variables defined

 

 

code:

--------------------------------------------------------------------------------

 

fmt 4 count # timing counter #Peck TAP CYCLEfmt 4 peck_cnt #remaining no. of pecks #Peck TAP CYCLEfmt 4 numpeck # No. of pecks #Peck TAP CYCLEfmt 4 pass # pass counter use to calculate depths #Peck TAP CYCLEfmt Z 2 sub_depth #subsequent depths #Peck TAP CYCLEfmt Z 2 calc_depth # The total caculated cutting depth #Peck TAP CYCLEfmt Z 2 calc_peck # the calculated peck amount #Peck TAP CYCLEfmt z 2 strt_depth # the first tap depth #Peck TAP CYCLEfmt Z 2 initial_calc # calculate the initial depth cut #Peck TAP CYCLE

 

--------------------------------------------------------------------------------

 

And this in the drill cycle defs at the bottom where the .txt now resides

 

 

code:

--------------------------------------------------------------------------------

 

[drill cycle 14]1. "Peck Tap cycle"2. ""3. ""4. ""5. ""6. ""7. ""8. "# of pecks"9. ""10. ""11. ""

[Guest]

As far as where you you define them.

 

I usually create a section at the top of the custom drill section where I add any definitions for variables that I have added in on my own.

 

It allows me to know what I have done and keep it separated from the main sections.