-
-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code issue in clearance variable #130
Comments
...and the log seems to show it's a casting error
|
Hi, this is the default from the documentation. You need to define a (float) number if you want a different value. And please use the safe_z_height property since clearance is already deprecated. |
Should this value be picked up automatically by default or do you need to explicitly set it? |
If you do not include this property in your config file, the default will be used (in this case two times the z_offset of your probe ...or 3mm if your probe does not have a z_offset). Or it is the value that you use with this property. |
I am receiving an issue from Klipper
Unable to parse option 'clearance' in section 'z_calibration'
In the autoz.cfg file the line is
clearance: 2 * z_offset from the "probe:z_offset" section
I am using a euclid probe. I am not sure if this matters but he euclid probe include (which contains the z_offset value) precedes the autoz.cfg include.
I did just notice that all the text after clearance is lt blue instead of the orange
I suspect this is a python spacing issue but I am not sure what it should be.
The text was updated successfully, but these errors were encountered: