Comments (12)
This should not be caused by any update. But, it's hard to say. May be you have plastic left on the nozzle or your switch is somehow damaged?
from klipper_z_calibration.
I am also facing the same issue. Sometimes the first layer is perfect while sometime its too squished but I know for sure this issue is happening after update 1.0
from klipper_z_calibration.
Strange, I've had the same problem the last few times. But for me it was the very first time. It has nothing to do with the update. I had blamed it on the fact that I had printed PLA for the first time, which was very ooze. However, the error only seemed to go away after a Klipper restart 🤔
The typical Omron switch can develop a drift over time. I have had fewer problems with this so far, but some people have reported it.
from klipper_z_calibration.
I did try with Omron and Other switches as well but still I see the issue. Earlier my Z-offset was 0.65 for 0.4 nozzle and 0.63 for 0.8 Nozzle and that would work everytime. but not for 0.4 nozzle even 0.17 does not work.
Not sure what is causing the issue but everytime I need to look for the squeeze.
Just some results below with different z offset, first time it comes very well, then it gets squeezed.
Z-CALIBRATION: probe=6.007 - (switch=8.556 - nozzle=2.582 + switch_offset=0.190) --> new offset=-0.156250
Z-CALIBRATION: probe=6.042 - (switch=8.592 - nozzle=2.581 + switch_offset=0.190) --> new offset=-0.158750
Z-CALIBRATION: probe=6.030 - (switch=8.576 - nozzle=2.574 + switch_offset=0.190) --> new offset=-0.162500
Z-CALIBRATION: probe=6.052 - (switch=8.599 - nozzle=2.575 + switch_offset=0.190) --> new offset=-0.161250
Z-CALIBRATION: probe=6.246 - (switch=8.781 - nozzle=2.740 + switch_offset=0.180) --> new offset=0.024750
Z-CALIBRATION: probe=6.245 - (switch=8.772 - nozzle=2.743 + switch_offset=0.180) --> new offset=0.036000
from klipper_z_calibration.
more results below, this is after I start the printer, give it a print then I see the squeeze is too much, so cancel the print and restart the same print and again issue .
Z-CALIBRATION: probe=6.242 - (switch=8.748 - nozzle=2.745 + switch_offset=0.180) --> new offset=0.058500
Z-CALIBRATION: probe=6.197 - (switch=8.738 - nozzle=2.747 + switch_offset=0.180) --> new offset=0.026000
from klipper_z_calibration.
OK, the result is still consistent for me. There were really only a few exceptions. If you have constantly changing values, then there is something mechanically wrong with your printer. E.g. crooked/wobbling magnets, loose pulleys, wobbling print head, oozing nozzle.... just to name a few. Is your PROBE_ACCURACY consistent?
from klipper_z_calibration.
Yes prob accuracy is was consistent, very slight variation which I expect it. but rest it was good. I need to check other mechanical parts. but for sure they are not an issues.
from klipper_z_calibration.
Z-CALIBRATION: probe=5.332 - (switch=7.511 - nozzle=1.444 + switch_offset=0.250) --> new offset=-0.984272
Z-CALIBRATION: probe=5.334 - (switch=7.511 - nozzle=1.447 + switch_offset=0.250) --> new offset=-0.979272
Z-CALIBRATION: probe=5.333 - (switch=7.509 - nozzle=1.449 + switch_offset=0.250) --> new offset=-0.976772
these were my prob calibration reults
from klipper_z_calibration.
These values look pretty good. Now tune your switch_offset to barely touch the bed with the nozzle (the real z=0 position and no paper or something). Then test it again. And maybe even restart Klipper and test it again. Be careful with meshes if you use it. Start without a mesh and recalibrate it after you have calibrated your z...
from klipper_z_calibration.
Yes the calibration values are good, I did a slight change in my Start gcode, that was to move the z calibration before mesh, and I think i am starting to get good results. but still the values are not that stable. Tomorrow will check mechanical parts.
once more thing I observed was that on PEI smooth bed the results are very good, but on texture its not that stable.
from klipper_z_calibration.
Ok, on textured PEI the consistency depends on the switch and how fine the texture is. Unfortunately, there aren't that many plates that really have a fine texture.
from klipper_z_calibration.
I basically have the same problem as @jinnn1989. I dialed in the offset many times. Sometimes the print turns out really good, next print I get an elephant foot or the filament doesn't stick to the buildplate at all.
I already checked the mechanical parts and found no issues.
When I deactivate Auto Z and dial in my Offset manually I get perfect and consistent results.
I've read somewhere that this could have something to do with me using KAMP but even when I restart Klipper, clear the mesh, home the printer and then do a calibrate_z the results vary and my nozzle doesn't touch the buildplate or dives right into it.
from klipper_z_calibration.
Related Issues (20)
- Wiki Changelog describes need to change "safe_z_home" instead of "safe_z_height" HOT 1
- Probe trigger height being used as Zero position HOT 1
- [Feature suggestion] Nozzle wipe on Endstop HOT 3
- Do I need to move xy to a safe position myself after G28? HOT 2
- Tap compatibility HOT 1
- Move out of range during Calibrate_Z HOT 3
- Voron Tap support HOT 3
- Z Calibration Off, Printing Above plate HOT 13
- klippy/extras/z_calibration.py untracked HOT 3
- Bed Distance Sensor Support
- Code issue in clearance variable HOT 4
- calibrate_z crashes printhead into bed HOT 1
- If no Bed Mesh, it uses Z endstop height as Zero Position HOT 1
- Is it possible to have a dedicated Z Switch pin instead of just using the Probe Pin? HOT 10
- Automatic detection of the offset between nozzles of different tools. HOT 1
- At end of calibration i get a "unknown command" HOT 2
- [FR] Support for IDM Scanner HOT 7
- Perform Auto Z at KAMP Center HOT 1
- Move from clearance to safe_z_home when no [probe] section defined HOT 1
- Potential issues with oldham couplers HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from klipper_z_calibration.