That would make sense except for the tool path that doesn't exist in the g code that can be seen in both occasions that this has occurred.

Okay I get it, I just need you to test for me if you would please . if you can make it happen without making a part I can then get your profile from you and test it here. I want to fix this but I can 100% tell you that I am not having this on my system. There are many ways to make this happen and I just want to make sure we are looking for the correct one. We will get this.

Sure, thanks. I will give it a shot tonight

Do you have any code in your M6 macro?

No, I don't have any code in the m6 macro. I have 4 PMC scripts. When this issue started I reinstalled mach 4 and setup a new profile and reconfigured everything to make sure it wasn't my profile causing it. For some reason a couple of the PMC scripts no longer work. (Not sure if this is relevant)

1. Turns the optional stop on as soon as the system is enabled. (Working)
2. Feed hold button (Not Working)
3. Cycle start button (Not working)
4. I can't remember the fourth but will edit once I get to my computer tonight.

Do you have a tool changer or a tool setter?

No, I don't have any code in the m6 macro. I have 4 PMC scripts. When this issue started I reinstalled mach 4 and setup a new profile and reconfigured everything to make sure it wasn't my profile causing it. For some reason a couple of the PMC scripts no longer work. (Not sure if this is relevant)

1. Turns the optional stop on as soon as the system is enabled. (Working)
2. Feed hold button (Not Working)
3. Cycle start button (Not working)
4. I can't remember the fourth but will edit once I get to my computer tonight.

Correction. None of these scripts were active during the issue

Do you have a tool changer or a tool setter?

No. All manual.

I have some gcode to bore 4 holes. I will run it tonight in air and see if I can replicate the issue.

Hi all,

I ran the 4 boring operations gcode (see attached - Boring op test part). It was supposed to bore 4 holes. Initial generation of the tool path looks great. As soon as it started to move to the first hole location, the tool path window changes and there is this new magical tool path that does not exist in the code which it follows(See attached Boring four Holes test 1&2).

I then reset everything and after trying a few things I cannot get it to repeat the same behavior. Got to love intermittent problems