I can't get g94 or g95 out of a post.

[HayreAss]

I'm tweaking on a post for a buddy that I occasionally work for, and I just cant seem to get it to post G94, or G95.

The last post I worked on for him, in X5, worked just fine.

He convrted it up to X8, and it works fine...

However, we want to play with the Renishaw probing cycles, and the old post does not support that.

So we are trying to get up and running with the provided post,

Generic Haas 3X Mill.pst

 

I have been monkeying with it for a few hours, and I can't seem to get it to post either G94 or G95.

 

I understand that G94 is likely the default, so it's likely not required to call it out at the beginning, but we did it before, it worked, and there's never been a crash.

It got posted on every tool change, right before the first feed move.

 

I like to program rigid tapping with IPR, rather than IPM, and I can't seem to find the correct toggles to do that.

No matter what I do, I get IPM programming.

 

There's never a G94 or G95 in the posted Gcode.

 

In the old post, I could toggle use_pitch to change results, but that is not there in this new post, and I am unclear about what replaced it.

 

It's likely an easy fix, but it's eluding me.

 

Anybody have a solution?

[HayreAss]

Dang, I figured somebody would have an idea by now!

 

I sussed out the logic that does it in the old post, but it's an old mpmaster post, and the logic on the new post is different.

[Dave Allen]

do you want a G94 @ all the toolchanges.

and a G95 on the tap cycle line.

[HayreAss]

That would be outstanding, yes.

 

I hadn't looked at it that way either, because I suppose I could figure out how to force g94 at every tool change,  and likely figure out how to force g55 for a tap.
Post it along with  g84 or something.

 

Though if you already have a solution in mind, I am eager to hear it.

[HayreAss]

Well actually no, that wouldn't work, because it needs to post the feed in pitch, not IPM...

 

Forcing it to just post G95 without the correct feed would be catastrophic.

 

Though a blanket G94 at every toolchange would be OK, providing it changes to G95 when required.

[HayreAss]

Right now, my old post puts the G94 at the first Z feed of every toolchange that will use it.

 

G94 G01 X-.5027 Z.0195 F200.

 

And a G95 on the line before the tapping cycle.

 

%

O00000 (2X4 TOP 2 UP)

(POST - HAAS)

(SEPTEMBER-26-2014  5:03 PM)

(T5 -  NO. 10-32 TAPRH     - H5   - D0.1900")

G00 G17 G20 G40 G80 G90

G91 G28 Z0.

T5 M06 ( NO. 10-32 TAPRH)

G00 G17 G90 G54 X-.4724 Y.1575 S600 M03

G43 H5 Z1.

G95

G99 G84 Z-.5 R.1 F.0313

G80

M05

G91 G28 Z0.

G28 Y0.

G90

M30

%

[Dave Allen]

Yes that is the idea, So all you need is to figure out how to output the thread pitch right.

[HayreAss]

Upon further reflection, I think G94 will not only be OK for tapping, but probably even more accurate.

Rounding errors in the decimal will be per minute, not per revolution.

[Dave Allen]

This is a copy of the  ptap$ in a fadal post that outputs the pitch in the feed.

of course you only need the else portion of the formula.

 

 

ptap$            #Canned Tap Cycle - G84/G74
      pdrlcommonb
      if tap_format = 2,
        [
        feed = (1 / n_tap_thds$) * speed
        pcan1, pbld, n$, *sgdrill, *sgdrlref, pfxout, pfyout, pfzout, pcout,
          prdrlout, *feed, dwell$, strcantext, e$
        ]
      else,
        [
        feed = speed
        thread_lead = 1 / n_tap_thds$
        pcan1, pbld, n$, *sgdrill, *sgdrlref, pfxout, pfyout, pfzout, pcout,
          prdrlout, *feed, *thread_lead, dwell$, strcantext, e$
        ]
      pcom_movea