-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Not an issue, but an idea about autocalibrating switch_offset value #42
Comments
I was just thinking the same thing, but a step further: if we probe the two end stops right on top of each other as you describe, then we don't need to probe the body of the mag probe at all. Thoughts? |
I'm sorry, this will not work! Please read the switch section. I had this discussion already many times! |
I had the same idea, but just because the Z Endstop's switch triggers, doesn't mean that it doesn't travel further down after being triggered - potentially falsifying the actual travel distance. Same for the magprobe. Depends on who triggers easier. This would (maybe) work if both switch trigger and have 0 travel of the switch actuator afterwards... or not, i need to read up on that again. ;-) |
Correct! And, even if there would be no overtravel, the probe has to trigger before the endstop - reliably! The latter one could be achieved by a sexbolt endstop with a spring... |
Hi,
I successfully use your code on my Voron2 equipped with a klicky probe.
Manual calibration of the switch_offset works fine, but is still a hassle.
I recently had to change my klicky probe to a spare one, and unfortunately, the switch_offset wasn't the same on the 2nd microswitch.
This gave me an idea on a possible way to try, and maybe achieve autocalibration of the swith offset:
On a voron we have to "endstops" being the z_endstop end the probe.
If we probe the magprobe two times, we could maybe get the relative distance travelled by the microswitch.
I'll try to explain my idea further with the description of a calibration sequence:
We should now have the means to compute both relative distances between all required values.
Unofrtunately, I lack the base knowledge on klipper to implement this idea, and would appreciate your insights
The text was updated successfully, but these errors were encountered: