This is not my issue but it is a bug which could explain some odd behavior by many many users. I am also creating the discussion post to meet the criteria setout by the project moderator so it can get progressed. (edit: Beacon is not affected by this bug) Github Issues Link: [BUG] Accumulating micr…

This code is the particular kind of tricky that is most difficult to reason about: temporally tricky. I spent a lot of time reading the endstop and homing code for the load cell work. I have to agree with what kevin said: the Trigger Position and the Halt Position should not be the same. Since ENDST…

I’ve spent many hours researching this issue and unfortunately I am not able to reproduce a problem. In conversations with @Arksine , he has also spent time on this and is also unable to reproduce a problem. So, at this point, we need more information to track down the cause. I am definitely inter…

FYI, the mainline version of the Klipper code will now warn if it detects stepper motors getting out of sync after a probe attempt. If one sees a log message like Stepper 'stepper_z1' position skew after probe: pos -200631 now -200630 it is a result of this new check. If you do get the message, make…

For a long time I had issues with bed mesh and was thrown off to diagnose issues with inconsistent Z distances during print by many other factors: Temperature affecting readings of my inductive probe Thermal expansion inconsistent bed levelling Crappy lead screw nuts Probe movement on its fixation…

[image] tinkerman: So I increased the sampling and voila: What did you increase exactly? Was it the samples value in the probe section?: [probe] samples: 4 Could you follow the testing procedure with the macro and see if your setup is impacted?

[image] garethky: Was it the samples value in the probe section?: Yes, it wasn’t defined before, I have set it to 2. I have now increased it to 3 to reduce the odds of having adhesion issues. Probing speed is 5 mm/s (Z) [image] garethky: Could you follow the testing procedure with the ma…

If I understood the goal of the test correctly, then I got a reproducible result. I even had to reduce the samples in half because 70 would simply cause too big of a drift that was hitting retry limit. Initial zed positions: stepper_z:25.000081 stepper_z1:25.000081 stepper_z2:25.000081 MSCNT: 00…

Thanks. Your log does seem to indicate something incorrect occurred. However there were some code changes recently in this area (both mcu and host) that you don’t have on your install. Could you update to the latest code, reflash the micro-controllers, and retry? -Kevin

Hi Kevin, I have updated both Host and MCU and ran the test again (35 samples). Result: Before: stepper_z:83 stepper_z1:41 stepper_z2:56 After: stepper_z:83 stepper_z1:33 stepper_z2:48 This result make very little sense as this way too big of a difference, which I would be able to visually…

[image] tinkerman: This result make very little sense as this way too big of a difference, which I would be able to visually distinguish. Are you sure with these results? Are you able to reproduce and validate them? Side note: You can already see in the log the warning of the newly introduc…

[BUG] Accumulating microstep shift during probe moves related to endstop oversampling

General Discussion

Topic		Replies	Views
Z stepper microstep shift on multi-mcu homing / loadcell / ldc1612 General Discussion	26	1029	October 27, 2024
Z_tilt_adjust and bed mesh General Discussion	13	527	March 17, 2025
Need to discard the first probe - help me find the root cause Developers	30	3847	November 13, 2024
Impossible Bed mesh leveling - Cr10sPro V2 General Discussion	89	23184	January 2, 2024
BIQU MicroProbe V2.0 on Spider with Klipper? General Discussion	65	5540	February 15, 2024

[BUG] Accumulating microstep shift during probe moves related to endstop oversampling

Related topics