You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a fairly large machine, my X is over 1100mm of travel. In going through detailed calibration after moving house and taking the machine apart, I discovered I needed to adjust my ganged Y axis homing offset to -5 mm to get back in to square. The firmware currently limits that value to +/- 2mm. It appears a lot of my error is derived from hand made sensor mount brackets.
It would be good to support a wider range of values, I suggest +/- 10.xxx mm for that variable to allow for errors that may exist in larger machines or and made machines/sensor brackets.
While there is the potential to rack the gantry if a high value is used here incorrectly, there are various ways a person can rack or damage a machine if they set incorrect values and this is largely a one-time calibration value that is not in the normal workflow so I can't think of any reason not to increase the allowable range.
In the end I needed 2.88 on my particular build, but this is a helpful change for larger format machines. Closing since it has completed and is in the release.
I have a fairly large machine, my X is over 1100mm of travel. In going through detailed calibration after moving house and taking the machine apart, I discovered I needed to adjust my ganged Y axis homing offset to -5 mm to get back in to square. The firmware currently limits that value to +/- 2mm. It appears a lot of my error is derived from hand made sensor mount brackets.
It would be good to support a wider range of values, I suggest +/- 10.xxx mm for that variable to allow for errors that may exist in larger machines or and made machines/sensor brackets.
While there is the potential to rack the gantry if a high value is used here incorrectly, there are various ways a person can rack or damage a machine if they set incorrect values and this is largely a one-time calibration value that is not in the normal workflow so I can't think of any reason not to increase the allowable range.
core/settings.c
Line 508 in e3e7484
(Thanks to Andrew Marles for making me a quick build to test it).
The text was updated successfully, but these errors were encountered: