#<holes> = 3 - Unexpected behaviour

Hmmm, I don't understand what is going on. This is what you should see:


It may be worth asking in a different forum section as a M67 issue, either Basic Configuration or Advanced Configuration as more folk will probably notice it. I am fairly certain that there is nothing we do which would affect M67 operations. In the meantime I will keep experimenting but not being able to replicate the issue makes it difficult.

I am probably barking up the wrong tree but could you try with the following lines disabled in their respective files:

I did some digging into this today.  I didn't see the issue on my system either, but I noticed I am up to date with all of the commits on master (QtPlasmaC version 008.048), whereas you are on 008.043.  That is from May 4, 2024.  I did some digging in to the commit history, as I vaguely remembered seeing something involving Motion, and I found this commit:

github.com/LinuxCNC/linuxcnc/commit/6598...13e27e03e792dc838c86

in the commit description, it solves some M67 issues.  Here is the issue it claims to have fixed:

github.com/LinuxCNC/linuxcnc/issues/2987

At any rate, I checked out the commit before this one (469ab15), and recompiled the project, and I see similar issues to what you are seeing.  M67 does not seem to be effective.  I think I can safely say this is the culprit.  It does beg the question as to how long it was broken, but nonetheless it seems to work again.

Long story short:  You need to update. 

Happy cutting.

 

I should caveat that the buildbot has been down, I think this change was built before it broke. But I’m sure this is the issue nonetheless.