X axis adjustments

I have been on a CNC hiatus. Running an SO3 XXL with an HDZ. Just upgraded to latest CM version and now my X axis will not travel all the way left. Is there a way to adjust the bed size parameters in the new CM version?

Thanks

If you configured for an SO3 XXL w/ HDZ it should have gotten the extra X-axis movement distance right — if it didn’t, you can use the About menu’s button “Open Data Directory”, then edit the JSON file for your configuration to change the X-axis dimension.

Thank you. I went through the new machine setup twice to make sure I didn’t mess it up. Although it’s only a few cm, it messes up my waste board setup and fences location.

Quick follow up…. Found the .json file and tried to edit using notepad but it seems to revert back to the original X setting (-830.0). Any hints on how to make the modifications remain? I keep saving the file back to the original pathway (…\shapeoko.json) but seems to just go back to the default setting. I am sure I am missing some simple step.

Thank you for the help dusting the cobwebs off my brain! :slight_smile:

Possibly a permissions issue? Save the file to the desktop, verify the changes are there, then try backup up the original (say change its file extension from .json to .bak) then move the changed file to where the original was?

For a long time the machine setup included space for the Suckit dust shoe. The Suckit has wings that extend past the width of the Z. Not sure if they are still compensating for the Suckit wings but as @WillAdams gave instructions above about modifying the .json file.

After editing the json file, I think you need to go through the setup wizard and send the configuration to the machine. Or you can use mdi to modify the configuration on the machine directly. There are settings in GRBL for machine dimensions, soft & hard limits.

I have tried every way I can think of and still seems to revert back to the default settings after powering up. Miss the days when we could adjust this directly in CM.

I have not tried sending it via the command via MDI to GRBL just want it to persist after reboot / power up.

Seems like the allowance for the dust boot wing is hardwired now to the default configuration with no way to change it.

This topic was automatically closed after 30 days. New replies are no longer allowed.