InputShaping-Plugin-0.1.0-rc7 released (repacked)
-
@nightlonk42 Are you saying that if you do not install the input-shaper plugin (or disable it) that this problem does not happen?
-
This post is deleted! -
@gloomyandy said in InputShaping-Plugin-0.1.0-rc7 released (repacked):
@nightlonk42 Are you saying that if you do not install the input-shaper plugin (or disable it) that this problem does not happen?
That is correct
-
@fred-y @mfs12 I have to say, after using Klipper's system to "Autotune" this is bit archaic by comparison. I sure hope this will be continued to be improved upon as i think it has merit. WIthout having a huge understanding of the algorithms involved here let me take a stab at how i think your system could be improved to help the user make educated decisions on I.S. for their system.
1.) The Analysis graphing always defaults to displaying all 3 (X,Y,Z) axes simulataneously. This is overwhelming, the configuration dialog asks us to pick 1 axes to test, thus the accelerometer readings should only be recorded for this axis (or filtered after the fact) so as to not confuse the user.
2.) I have notice that my acclerometer testing file names are not being generate with the user selected (I.S. algo type, Frequency, Damping, axis desire, etc..) they simply get some random numbers & a date/time stamp... (Pic below)
Supposed to name:
Actual Name i get when CSV is saved:
So i have to go one-by-one, test, record, rename, update settings, repeat... very slow & frustrating simply to get my filenames correct so i can compare them....
3.) The analysis doesn't make any kind of recommendations for solving any of our variables.... The user must optimize 3-variables... not likely going to happen in any sort of quick situation. My recommendation would be for the system to take a standing still reading to account for environmental resonances (fans/etc...) and ignore these values when analyzing the accelerometer data. From there it should test increasing frequencies (Defined by user OR 0-150Hz F.E.) and then run that through solving for each I.S. type one-by-one to determine optimal frequency to cancel and maximum accel/decel & dampening at solved frequency...
This would, in effect, do exactly what Klipper I.S. does so well (and in mere minutes) but would give us a graphical representation of it simultaneously....I truly hope you keep at it and make some improvements to the system, I don't want this to sound like negative because this is great work so far, it just simply isn't complete yet, if you mission is to provide the user with "turnkey" information to improve their prints. I will keep playing with this and upgrading as beta's come out.
-
@jallen810 Work is still progressing.
-
@phaedrux said in InputShaping-Plugin-0.1.0-rc7 released (repacked):
@jallen810 Work is still progressing.
Looking forward to have it!
-
Hey @nightlonk42,
thanks for your feedback. I have no clue how inputshaping plugin would interferes with the other plugins or other functionality of the printer.
But as this plugin is still in a very early stage, please stop using it for now. We will keep an eye on this issue.
-
Hey @jallen810,
as @Phaedrux already stated the plugin is still in an early stage, but it will improve.
From what i understand your most missing features are
- displaying only the tested axis
- show inputshaping configuration and test parameters for each record
- get parameter recommendations
- speed things up
- do a completely automated calibration process
-
This post is deleted! -
Hi. I installed DWC 3.4b4 today.
Now I want to install the plugin,
but I get the message: Requirement DWC version 3.4.0-b4
-
A new version of input plugin was released.
Check https://forum.duet3d.com/topic/25306/inputshaping-plugin-0-2-0-pre3-released/1
