InputShaping-Plugin-0.1.0-rc2 released
-
Hey,
to improve the input shaping calibration experience we want to introduce the Input Shaping Plugin. So far it is a standalone but might get merged into DuetWebControl at later point.
It is based on DWC's Accelerometer Plugin and brings the following features:
- setting parameters for recording accelerometer profile
- start recording accelerometer profile
- automated download and analysis of the recorder profile
- preset of ringing frequency with the maximum amplitude
- setting of input shaping parameters
As this plugin is still in an early stage any feedback, bug reports, feature requests or wishes is helpful. So don't hesitate and leave a comment. Enjoy printing...
Release Notes inputshaping-plugin-0.1.0-rc2
Features
- setting parameters for recording accelerometer profile
- start recording accelerometer profile
- automated download and analysis of the recorder profile
- preset of ringing frequency with the maximum amplitude
- setting of input shaping parameters
Bugs
Downloads
Downloads can be found at https://github.com/mfs12/DuetWebControl/releases/tag/inputshaping-plugin-0.1.0-rc2
-
@mfs12 Thanks for this tool, but I have an issue with it.
When i measure the acceleration with this tool, I get a high spike at 1 Hz in X and Y axis as shown in the following pictures
when i use my code :
G1 X-50 G4 S2 G4 P10 G1 X100 F20000 M400 M956 P0 S1000 A0
I don't have this spike
-
Hey @SIam, i think this is related to the different parameter used in the input shaping plugin for the M956.
Plugin is using A2 and not A0.
Check the documentation at
https://duet3d.dozuki.com/Wiki/Gcode#Section_M956_Collect_accelerometer_data_and_write_to_file
which basically means it measures during deceleration.
-
New release available... check https://forum.duet3d.com/topic/24605/inputshaping-plugin-0-1-0-rc3-released/1
-
@siam said in InputShaping-Plugin-0.1.0-rc2 released:
When i measure the acceleration with this tool, I get a high spike at 1 Hz in X and Y axis as shown in the following pictures
In inputshaping-plugin-0.1.0-rc4 the order of profiling commands was changed. This might fix the problem you observed.
Please check...
https://forum.duet3d.com/topic/24695/inputshaping-plugin-0-1-0-rc4-released
and drop a line if you got time.