InputShaping-Plugin-0.2.0-pre6 released

Stephen6309

@mfs12 How do you get those logs?

mfs12

in firefox you can open the browser's console "Ctrl-shift+j".
Then -> Right mouse button -> export log to file -> upload file here.

DuetWebControl -> open menu (left top) -> open console -> open console's menu (right top of the messages) -> download as file -> upload here.

For further details:

Check and search for "download". https://duet3d.dozuki.com/Wiki/Duet_Web_Control_v2_and_v3_(DWC)_Manual#Section_Console

More details about firefox' console. https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

Stephen6309

@mfs12
Currently printing something.

/rr_connect?password=reprap&time=2021-11-2T13%3A18%3A58:1 Failed to load resource: the server responded with a status of 404 (Not Found)
index.js:560 Plugin EndstopsMonitor not found
_callee11$ @ index.js:560
thinEngine.js:357 Babylon.js v4.2.0 - WebGL2 - Parallel shader compilation
/machine/directory/0%3A%2Fsys%2Faccelerometer:1 Failed to load resource: the server responded with a status of 404 (Not Found)
app.450a9c06.js:42 Uncaught (in promise) Error: Directory 0:/sys/accelerometer not found
   at new ExtendableBuiltin (app.450a9c06.js:42)
   at DirectoryNotFoundError._createSuperInternal (app.450a9c06.js:1)
   at new NetworkError (app.450a9c06.js:42)
   at DirectoryNotFoundError._createSuperInternal (app.450a9c06.js:1)
   at new DirectoryNotFoundError (app.450a9c06.js:42)
   at RestConnector._callee11$ (app.450a9c06.js:42)
   at tryCatch (app.450a9c06.js:24)
   at Generator.invoke [as _invoke] (app.450a9c06.js:24)
   at Generator.throw (app.450a9c06.js:24)
   at asyncGeneratorStep (app.450a9c06.js:1)
/machine/directory/0%3A%2Fsys%2Faccelerometer:1 Failed to load resource: the server responded with a status of 404 (Not Found)
vue.runtime.esm.js:1897 Error: Directory 0:/sys/accelerometer not found
   at new ExtendableBuiltin (app.450a9c06.js:42)
   at DirectoryNotFoundError._createSuperInternal (app.450a9c06.js:1)
   at new NetworkError (app.450a9c06.js:42)
   at DirectoryNotFoundError._createSuperInternal (app.450a9c06.js:1)
   at new DirectoryNotFoundError (app.450a9c06.js:42)
   at RestConnector._callee11$ (app.450a9c06.js:42)
   at tryCatch (app.450a9c06.js:24)
   at Generator.invoke [as _invoke] (app.450a9c06.js:24)
   at Generator.throw (app.450a9c06.js:24)
   at asyncGeneratorStep (app.450a9c06.js:1)
logError @ vue.runtime.esm.js:1897

DWC doesn't show anything other that the usual printing stuff.

Stephen6309

@mfs12 Ran a fresh one after exiting/restarting chrome. Looks like the last one was from when enabling the builtin accelerometer.

rr_connect?password=reprap&time=2021-11-2T14%3A43%3A27:1 Failed to load resource: the server responded with a status of 404 (Not Found)
index.js:560 Plugin EndstopsMonitor not found
_callee11$ @ index.js:560
Initialize.vue:71 Created new session
TestCommand.vue:158 axis changed Test
vue.runtime.esm.js:1897 TypeError: Cannot read properties of null (reading 'runs')
    at VueComponent.accelerometerRuns (Recorder.vue:96)
    at Watcher.get (vue.runtime.esm.js:4495)
    at Watcher.evaluate (vue.runtime.esm.js:4597)
    at VueComponent.computedGetter [as accelerometerRuns] (vue.runtime.esm.js:4851)
    at VueComponent.<anonymous> (vue.runtime.esm.js:503)
    at Watcher.get (vue.runtime.esm.js:4495)
    at new Watcher (vue.runtime.esm.js:4484)
    at VueComponent.m.$watch (vue.runtime.esm.js:4961)
    at createWatcher (vue.runtime.esm.js:4921)
    at initWatch (vue.runtime.esm.js:4903)
logError @ vue.runtime.esm.js:1897
Recorder.vue:109 run tests
Recorder.vue:120 run tests Session
Recorder.vue:132 starting tests
Recorder.vue:87 axis not homed:  Array(3)
Recorder.vue:137 home all axis
Recorder.vue:269 homing all axis G28 M400
Recorder.vue:273 
Recorder.vue:160 configuring algo Algorithm
vue.runtime.esm.js:1897 TypeError: Cannot read properties of null (reading 'runs')
    at VueComponent.accelerometerRuns (Recorder.vue:96)
    at Watcher.get (vue.runtime.esm.js:4495)
    at Watcher.evaluate (vue.runtime.esm.js:4597)
    at VueComponent.computedGetter [as accelerometerRuns] (vue.runtime.esm.js:4851)
    at _loop$ (Recorder.vue:162)
    at tryCatch (runtime.js:63)
    at Generator.invoke [as _invoke] (runtime.js:294)
    at Generator.next (runtime.js:119)
    at tryCatch (runtime.js:63)
    at maybeInvokeDelegate (runtime.js:357)
logError @ vue.runtime.esm.js:1897

DWC console:
11/2/2021, 2:43:28 PM Connected to cxy-msv1.local

mfs12

@Stephen6309,

something looks weird. The http requests basically all fail.

Please check and provide the exact versions of:

DWC
RRF
TBC
InputShaping Plugin

Can you record data with the accelerometer plugin? it is an internal plugin.

And please provide the complete logs. If there's something logged, please share it. Because more information helps to understand the complete situation.

Stephen6309

@mfs12 The firmware on the tool board actually wasn't updated. M997 B121 fixed it. It just homed and moved and it says recording. Now finished has has a nice graph.

You might want to add an error check for the actual firmware on the toolboard.

cbrunnem2

does seem the plugin or input shaping in general helps me. has this been seen before? the frequency peaks do not change when i change the movement speed so i dont think its stepper noise.

any thoughts?

2021-11-02 22_49_14-My Printer.png
2021-11-02 22_49_24-My Printer.png

dc42

@cbrunnem2 do you have any signs of ringing (ghosting) on your prints? What sort of printer is it?

Did you have any fans running during the accelerometer data collection? One user had a peak, somewhat above 100Hz AFAIR, which disappeared when he turned the fan off.

cbrunnem2

@dc42 it is a cartesian printer. homemade basically. x and y slide on linear MGN-12H rails. dual Y motors, single x motor, and a direct drive extruder.

there is some ghosting at 125mm/s. at 250 mm/s its more noticeable. i can get pictures tonight.

fans are NOT off during this so i will try that tonight.

cbrunnem2

@dc42 turned off my fans and.... hmmm not really any strong modes and trying to damp any of them doesn't work. i assume this is just something i cant benefit from?

PS. 136hz mode was my 5050 cooling fans and the 195hz mode was my extruder fan. not sure why i didnt think to turn them off....

joeko

the line are not realy flat
i am confused. when i look to other curves and see my than i think something is wrong. it is an vcore corexy.
has someone an idea what is going on ?
and this with zvd

mfs12

New release out now... locking this thread...

https://github.com/mfs12/DuetWebControl/releases/tag/inputshaping-plugin-0.2.0-pre7