HAAS GR712 Post

[connor_kilgour]

Hi Everyone,

First of all, sorry for any lack of knowledge on my behalf. New to Fusion and post editing. Completely self taught.

We have a HAAS GR712 Router (PRE-NGC) currently running a custom mastercam post. From my understanding, I should be able to use the HAAS (PRE-NGC) mill post in the fusion library? 

We also have a custom hood attachment to remove any dust from the material, therefore after a tool change is completed, the machine needs to Z0. before moving any other axis. This is to avoid colliding with the tool setter. This is what the custom post writes:

(12.7 ONSRUD)

T5 M06

G00 G28 G91 Z0.

G00 G90 G54 X-137.5 Y361.68 S9900 M03

Saying I use the Fusion mill post, what would I have to write and where to give me the same result?

Any help is appreciated.

Thank you,

Connor

[serge.quiblier · Accepted solution]

Hello @connor_kilgour 

If you edit your post, you can find the onSection function.

And search inside it here is a snippet of code with the addition:

    skipBlock = !insertToolCall;
    writeToolBlock(
      "T" + toolFormat.format(tool.number),
      mFormat.format(6)
    );
    writeRetract(Z);  // Depending on the safe PositionMethod post property G53 or G28 is used
    if (tool.comment) {
      writeComment(tool.comment);
    }
    if (measureTool) {
      writeToolMeasureBlock(tool, false);
    }
    if (insertToolCall) {
      forceWorkPlane();
    }

Line 7 in this piece of code is the change for forcing retract after the tool change.

Regards.

______________________________________________________________

If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!

[connor_kilgour]

Awesome! Thank you so much. I have inputted this into the post and it works perfectly. I did do a work around where it would just writeBlock but this method is much better.

Appreciate your help

Thank you,

Connor

[serge.quiblier]

Hi @connor_kilgour 

it's cleaner to do it that way, because we are tracking if we are retracted or not.

So, if for whatever reason we might have to call the writeRetract twice successively, it won't be outputted twice.

It will also force the output of the retracted axes on the next move.

Glad you are happy with the fix.

Regards.