I moved my right side sensor, to allow more room for large workpieces on my XXL. Unfortunately, now when I initialize and setup my machine, the left side no longer goes all the way to the end of the gantry (where it used to go). My assumption is that I’m telling the shapeoko that it’s bed size is xxx and so, from the right side, it calculates where the left side should be. The problem is, I have over an inch of room to the left of where it’s willing to go now…and the gantry has PLENTY of space (it used to go all the way to the end.
How do I tell my XXL that it has more room on the bed, so that it takes advantage of the full length of the gantry?
They both should be persistent until you run the setup wizard again.
Yes, in the json file they are negative numbers measured from machine zero (in mm).
In GRBL they are positive numbers representing the total travel of each axis.
As others pointed the json file is written during configuration. That configuration limits jogging but does not limit movement during gcode cutting. If you write gcode that tries to send the X or Y a half a mile the machine will try until it hits the mechanical limits. Now the limiting of the jogging might cause problems if you are trying to use the lower left corner to set X and Y but the jogging limitations wont stop the machine from cutting past the jogging limits. Now you might get a warning about going beyond bounds but as long as you are not going past the physical limits you would be good.
I’ve got this thing working now. The key was editing the JSON file. Before that, changing 130 via MDI had no impact on the travel. It did not hit physical limits…it simply stopped where it “thought” the end was and would not let you jog any further than that (I wanted to jog over to set zero).
So…changing the JSON file and restarting CM did the trick. The full gantry is now available to me (34.21") - which is a God-send…because my files are almost exactly the width (and you can’t “Tile” horizontally)!