Open Surax98 opened 1 month ago
The SHAPER_CALIBRATE post-processing phase returns inconsistent data compared to manually running the python script
Mainsail
Microsoft Edge
Run SHAPER_CALIBRATE using a Flying ADXL345
The following is what I get by running the X axis calibration by SHAPER_CALIBRATE and waiting for the output:
Recommended shaper_type_x = zv, shaper_freq_x = 54.2 Hz To avoid too much smoothing with '3hump_ei', suggested max_accel <= 0 mm/sec^2 Fitted shaper '3hump_ei' frequency = 48.0Hz (vibrations = 11.3%, smoothing ~= 0.497) To avoid too much smoothing with '2hump_ei', suggested max_accel <= 0 mm/sec^2 Fitted shaper '2hump_ei' frequency = 41.0 Hz (vibrations = 12.3%, smoothing ~= 0.456) To avoid too much smoothing with 'ei', suggested max_accel <= 0 mm/sec^2 Fitted shaper 'ei' frequency = 50.4 Hz (vibrations = 22.2%, smoothing ~= 0.221) To avoid too much smoothing with 'mzv', suggested max_accel <= 0 mm/sec^2 Fitted shaper 'mzv' frequency = 33.0 Hz (vibrations = 18.3%, smoothing ~= 0.297) To avoid too much smoothing with 'zv', suggested max_accel <= 2400 mm/sec^2 Fitted shaper 'zv' frequency = 54.2 Hz (vibrations = 34.8%, smoothing ~= 0.142)
This is instead the output by using the same collected CSV data, but manually executing the klipper calibrate script:
~/klipper/scripts/calibrate_shaper.py /tmp/calibration_data_x_20240514_135758.csv -o /tmp/shaper_calibrate_x.png Fitted shaper 'zv' frequency = 55.4 Hz (vibrations = 35.7%, smoothing ~= 0.057) To avoid too much smoothing with 'zv', suggested max_accel <= 12000 mm/sec^2 Fitted shaper 'mzv' frequency = 33.2 Hz (vibrations = 18.5%, smoothing ~= 0.185) To avoid too much smoothing with 'mzv', suggested max_accel <= 3200 mm/sec^2 Fitted shaper 'ei' frequency = 50.4 Hz (vibrations = 22.2%, smoothing ~= 0.127) To avoid too much smoothing with 'ei', suggested max_accel <= 4700 mm/sec^2 Fitted shaper '2hump_ei' frequency = 43.2 Hz (vibrations = 13.3%, smoothing ~= 0.289) To avoid too much smoothing with '2hump_ei', suggested max_accel <= 2000 mm/sec^2 Fitted shaper '3hump_ei' frequency = 51.0 Hz (vibrations = 12.4%, smoothing ~= 0.315) To avoid too much smoothing with '3hump_ei', suggested max_accel <= 1800 mm/sec^2 Recommended shaper is zv @ 55.4 Hz
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.
SHAPER_CALIBRATE
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: