I have an SO3 XXL and created a spoilboard considerations document a while back. Please review it and see if you can use any of the contents. My spoilboard is slightly smaller than the cutting area specifically so I can level my spoilboard edge to edge. The original spoilboard that C3D supplied was bigger than the actual cutting area and that would live a ridge at the back and left side of the spoilboard. In those days that was not a problem but since they added tiling a ridge on the back would be a problem.
spoilboard_considerations.pdf (1.3 MB)
Additionally the jogging bountries that are set when doing the initial configuration are less than the capability. You dont want to physically hit the left rail but usually you can increase your jogging area slightly by modifying your shapeoko.json file. This will allow you to jog slightly more than the standrd configuration. When you send a file there is nothing stopping your SO3 from slamming into the physical stops. However during jogging there are limits. To find your shapeoko.json file open Carbide Create and then on the Help menu and About choose Open Data Directory. Under the Carbide Motion folder you will find the shapeoko.json file. You can open the file in a text editor such as notepad on Windows. Be sure to save as a text file. The parameters you want to look is the X.
Here is what my shapeoko.json file looks like. Do not duplicate my .json because I have an xxl. However you can increase slightly, power off SO3 and restart CM. CM only ready the shapeoko.json when started.
{
“bitRunnerEnabled”: true,
“bitSetterEnabled”: true,
“bitSetterX”: -25.5,
“bitSetterY”: -786.5,
“bitZeroType”: 1,
“connection”: 1,
“hasLaser”: false,
“lastConfigSent”: 2,
“lastProbeIndex”: 0,
“lastSizeOption”: 0,
“odometer”: [
{
“cleared”: false,
“minutes”: 12.259400000000024,
“startDate”: “2025-10-15”,
“travelX”: 16095.225025177002,
“travelY”: 16658.60024547577,
“travelZ”: 1656.600022315979
}
],
“showCarbideRouterRpm”: true,
“spindleType”: 0,
“travelX”: -830.0,
“travelY”: -850.0,
“travelZ”: -140.0,
“version”: 0,
“webhooks”: ,
“workOffsetX”: 714.2999877929688,
“workOffsetY”: 583.9749755859375,
“workOffsetZ”: 16.64999999999999
}
Specificaly change the
“travelX”: -830.0,
The number is in metric and negative from the homing position set during initialization.
Happy machining.