InputShaping-Plugin-0.2.0-pre8 released

[mfs12]

This release contains only comsetic changes.

release notes for inputshaping plugin 0.2.0-pre8

This work is based on the original acceleration plugin. Input shaping plugin tries to take
the input shaping calibration to a next level.

The current state is still EXPERIMENTAL!!!

Although it's experimental it brings already some handy features which is why i
am doing this release. Therefore please comment, give feedback, report bugs and share your
ideas.

requirements

• Duet Web Control 3.4.0-b6
• RepRap Firmware 3.4.0-b6

features

• restructure plugin to use vue components
• added test configuration component
• added recorder component
• added chart component
• use object model to determine status of test
• added add/delete of algorithm configurations
• added add/delete/select of records
• added add/delete/select of sessions
• display test parameters in chart component
• allow records with differing samples rates of up to 1%
• cleaned up debugging output
• added localization
• home device only if not homed
• improved ui layout
• added component to manage multiple sessions
• added more parameter validation for test and algorithm
• disable tab record tab when no algorithms defined
• disable tab chart when no records available
• improved error reporting
• localized date-timestamps
• added integrals for each axis
• skip algorithm test which already have test record (speed improvement, easier understanding)
• improved editing note in configuration tab
• cleaned input fields (ids or not editable but only names)
• added recommendation support
• make deletion of accelerometer files configurable
• added tool offset to suggest start/stop position
• display overflows in analysis' table

bugs

• fixed initial filtering of records by axis
• fixed session cleanup when session is deleted
• fixed data handling when swapping sessions
• fixed can address handling (needs more testing)
• fixed record integrity when referenced algorithm is changed
• fixed CAN address handling when address is null
• fixed one-time homing for some machines
• fixed labeling of chart axes
• fixed chart's freq/time status handling

known issues

• parameter validation doesn't cover every situation

downloads

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

howto

prerequisites

• select a tool
• home printer
• bring axes into initial positions, especially important for not tested axes

initialize session

• switch to tab "initialize"
• create a new session or
• select an available session

configure session

• switch to tab "configure"
• configure your session session
• configure test parameters
• add as many input shaping algorithm configurations as you like
  • more than one per algorithm are allowed
  • this is good to compare different input shaping configuration of the same algorithm
• CAUTION: once a record in a session exists test parameters can't be changed anymore.

record profiles

• switch to tab "record profiles"
• press "run" button and wait until recording is done

frequency analysis

• switch to tab "frequency analysis"
• in "acceleration records" section you see a list of profiles recorded
  • clicking on the entry DELETEs it form the session!!! (it is lost!!!)
• in "filter" section the show/hidden graphs are displayed
  • un-checking an axis will hide or show all charts of an axis group
• in chart section
  • individual graphs can be shown or hidden by pressing the colour next to the name
• press "FFT" button to show FFT representation of the graph
• press "Time" button to show time representation of the graph

recommendations

• switch to tab "recommend"
• select a record of type "none" from the first table
• run recommendations, thism might take a while...
• sort second table with recommendations by integral
• ideally the record with the smallest integral should be provide the best configuration
• add configuration to session
• switch to tab "configure" to review added configurations
  • see section "configure session"

limitations

• currently no data is stored permanently!!!
• everything is volatile so avoid hitting browser's reload

what's next?

Potential next steps are

• store session in a local file or in browser's local storage or
• load session from local file or browser's local storage
• recommend input shaping parameters
• improve input validation
• add translations