Skip to content
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

Weird acceleration values by running SHAPER_CALIBRATE #896

Open
Surax98 opened this issue Aug 10, 2024 · 1 comment
Open

Weird acceleration values by running SHAPER_CALIBRATE #896

Surax98 opened this issue Aug 10, 2024 · 1 comment
Labels
not moonraker reported issue with other software

Comments

@Surax98
Copy link

Surax98 commented Aug 10, 2024

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:

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
@Surax98 Surax98 added the bug Something isn't working label Aug 10, 2024
@Arksine Arksine added not moonraker reported issue with other software and removed bug Something isn't working labels Aug 10, 2024
@Arksine
Copy link
Owner

Arksine commented Aug 10, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not moonraker reported issue with other software
Projects
None yet
Development

No branches or pull requests

2 participants