You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The feedback you get from running the SHAPER_CALIBRATE gcode command comes from Klipper. I would suggest opening a thread on the Klipper discourse to report this issue.
What happened
The SHAPER_CALIBRATE post-processing phase returns inconsistent data compared to manually running the python script
Client
Mainsail
Browser
Microsoft Edge
How to reproduce
Run SHAPER_CALIBRATE using a Flying ADXL345
Additional information
The following is what I get by running the X axis calibration by SHAPER_CALIBRATE and waiting for the output:
This is instead the output by using the same collected CSV data, but manually executing the klipper calibrate script:
The text was updated successfully, but these errors were encountered: