trouble with z probe offset
-
I have the bltouch probe and probe works great. height map stored and slicer writes g29 code for print run. duet board uses the file during print run. however duet refuses to use the probe offset stored in config.g. this is intermittent problem. problems like this come and go without any config change. too many to list.
-
@sjason1377 said in trouble with z probe offset:
I have the bltouch probe and probe works great. height map stored and slicer writes g29 code for print run. duet board uses the file during print run. however duet refuses to use the probe offset stored in config.g. this is intermittent problem.
This has been covered before. When using older firmware versions, clear bed compensation before homing Z.
problems like this come and go without any config change. too many to list.
If you don't list them, we can't help you to resolve them.
-
what firmware should i be using?
-
And why would i clear a good a good compensation file if it's correct. I only run that once every 10 prints or so. it's a thk linear square rail machine that doesn't change and head will take milling forces. there is never more than a .02 mm difference between probe runs. I only home z because manually setting it takes more time. This sounds like you are saying to run new bed probe every print?
-
There was a bug in an older firmware that would under certain conditions apply the offset more than once. Would need to re read the release notes to tell you which one though.
You can disable the map without deleting it and reload it again later. You don't need to rerun the whole probing routine.
-
@sjason1377 said in trouble with z probe offset:
what firmware should i be using?
I suggest either 2.0 or 2.0beta1.