MACH3 - How to I remove G43 from post?

[Anonymous]

Hey guys, 

Im struggling hard core with G43, it keeps messing with me if I forget to go back through all my code and delete them all. I hand load my machine for every operation so I really dont make use of any tool offsets. 

I simply load the needed tool, bring Z down to stock top, zero it out and move on with life. Nothing fancy. 

Is there a way to disable G43 from Mach3's post? I actually run Mach4 but they read the same way. 

[LibertyMachine · Accepted solution]

Navigate to this section of code:

if (!machineConfiguration.isHeadConfiguration()) {
      writeBlock(
        gAbsIncModal.format(90),
        gMotionModal.format(0), xOutput.format(initialPosition.x), yOutput.format(initialPosition.y)
      );
      writeBlock(gMotionModal.format(0), gFormat.format(43), zOutput.format(initialPosition.z), hFormat.format(lengthOffset));
    } else {
      writeBlock(
        gAbsIncModal.format(90),
        gMotionModal.format(0),
        gFormat.format(43), xOutput.format(initialPosition.x),
        yOutput.format(initialPosition.y),
        zOutput.format(initialPosition.z), hFormat.format(lengthOffset)

And make these changes (in RED)

if (!machineConfiguration.isHeadConfiguration()) {
      writeBlock(
        gAbsIncModal.format(90),
        gMotionModal.format(0), xOutput.format(initialPosition.x), yOutput.format(initialPosition.y)
      );
      //writeBlock(gMotionModal.format(0), gFormat.format(43), zOutput.format(initialPosition.z), hFormat.format(lengthOffset));
    } else {
      writeBlock(
        gAbsIncModal.format(90),
        gMotionModal.format(0),
        gFormat.format(43), xOutput.format(initialPosition.x),
        yOutput.format(initialPosition.y),
        zOutput.format(initialPosition.z), hFormat.format(lengthOffset)

[Anonymous]

Thank you, that worked but now I notice in the Mach3 post, it only loads one tool per setup? Why wont it throw out a M6 every time it needs a new tool? I have Mach4 configured so it automatically stops and waits for me to change out the tool and re-zero before clicking cycle start which then continues on along milling. I have my tool table setup and each tool has its own number. But from one op too the next it doesnt throw out a M6.  

[Anonymous]

Cancel that, I figured it out. I had manual load checked and for some reason that cancels the M6 ops after the first one.  

[daniel_lyall]

@Anonymous What is the G43 doing is it some funny non commanded moves and just going to random spot or is just stuffing up the tool offsets.

There is a bug what I have never been able to find if, it causes Mach3 and 4 to goto random places at tool change time and at restart of the G Code after a tool change.

[Anonymous]

I hand load my machine, so the tool offset is never the same. So with that being the case, I would zero the machine out with a tool, G43 would add a tool offset on top of the zero, then it would try to go drilling too china. 

[daniel_lyall]

Yep that's the offset bug the only way to get rid of it is to type G40 and G49 into the mdi after you load the gCode, haveing it in the safe conditions does nothing to get rid of it.

It gets even worse If you run a program from V carve pro after a fusion G code.

[grURN8F]

@LibertyMachine Made the change in red. Works great for me, thank you!

However: From time to time my change seems to be overwritten. I only notice that as mostly the optional stop option (in post process), which I usually have set to "no", is set to "yes" at the same time. May be due to a Fusion update?

Is there a way to permanently keep the changes?

Thanks & cheers

Gregor

[seth.madore]

When making changes to the post, one thing that you REALLY need to be doing is saving that copy to a local folder that doesn't get overwritten each update. Save it to a folder you create in your Documents, or even better, enable Cloud Libraries in Fusion and upload it to there.

https://knowledge.autodesk.com/support/fusion-360/learn-explore/caas/sfdcarticles/sfdcarticles/How-t...

[grURN8F]

Well - mostly as I suspected then. Did not know a post could be stored in and loaded from the cloud library, though. Great advice and thanks for the how to! 😀