M956 "collect accelerometer data", specify output filename
-
As the title says - it'd be useful (for me, for my specific current goals - I recognize I don't speak for everyone X) ) to be able to specify the output filename that M956 writes to, similar to how M374 works (https://duet3d.dozuki.com/Wiki/Gcode#Section_M374_Save_height_map ). The "P" parameter is already in use for M956, so "F" is probably my vote for the parameter code, and of course for backwards compatibility and ease of use, no specified "F" value means "use the default timestamp output name".
In addition/alternatively, it'd be useful if the accelerometer output file had more information about the machine state when the file was recorded - at the very least if there were any input shapers enabled, and if so, their configuration for the recorded test. That would make it a lot easier to compare the results of different tests, without needing to take notes on the arbitrary filenames generated, or to uniquely name each file (which yes is my first suggestion here, but for plenty of people and uses, that'd be overkill; it also doesn't help if you want to go back and look at your tests that you didn't think at the time were worth documenting thoroughly).
-
@mgjosh I have added these to the firmware wish list.
