Have a Support question entered, but wanted to question the group.
New XXL with Z Plus install. I created a waste board file in V Carve Pro.
.75 material with a .85" cut depth.
Machine is zeroed properly.
When it machines, the cut depth is 1.27 - and sounds like it is bottoming out Z Plus. My bit height is fine and bit is tight - checked that several times and no movement.
I did a Zero of the bit on the waste board, and placed it next to a block that was 19.8mm in thickness. Raised Z and read change off of Jog screen - set in mm it traveled 12.421 mm.
So it looks like the steps per mm is not correct.
I am not familiar with entering commands directly - how would I correct.
The GRBL param $102 is 200 for a Z-plus, and 320 for an HDZ.
It looks to me like you have the HDZ configuration set in GRBL instead of the Z-plus, because 12.4mm / 19.8mm = 0.63, and 200/320 = 0.625
You can verify this by opening the log, going to the MDI window, sending $$, and then checking in the log what the value of $102 is.
EDIT: and then again, it would have had the opposite effect, or my brain is too tired
EDIT2: my brain was mush indeed. Since you were jogging manually, each time you jogged by say 1mm, it actually jogged by 1.6mm, therefore it took less jog steps to reach the top of the block, therefore in the end the jogged distance was much lower than 19.8mm. It all matches.
Interesting - The overview screen called for Z Plus, but when I went into the setup screen it called for HDZ. I resent the configuration, and checked against the test block - moved correct z that time.
Going to keep an eye on it as I know that I set the Z Plus option, and it did show as the one programmed.
Running up to date version of CM 4.
I did some searching, but I am not experienced in using the MDI interface and reading the log file. I was able to open the log, but did not wee the $102 command.
Is there some additional info or a tutorial?
Thanks for pointing me in the right direction!!! Going to try another test run.
There’s nothing special to know about the log and using the MDI commands, the only catch is that depending on the version of CM you are using, you may or may not have to checkbox to filter out status messages that keep getting displayed continuously in the log window, and it makes it hard to catch the output of the $$ command. You can either upgrade to that CM version (I can’t remember, maybe it’s only in the latest CM 5.x beta), or just do a copy of the full log window content, paste that in a file editor, and look for the $$, and then to each $xxx param being printed out, and you should find your $102.
But if distance is now correct, you can be sure $102 has properly been (re)set to 200 steps/mm.