Basic Information:
Printer Model: Custom
MCU / Printerboard: OctopusPro 1.1
Host / SBC: OrangePi 5
[N/A] klippy.log
Why not save shaper calibration data inside printer_data folder?
I guess this is more of a convenience question rather than a problem.
A lot of times (including when I am right next to the printer) I can’t ssh to the host and I use my phone to control the printer, run tests, etc…
Why not simply save the PNG and csv files inside printer_data folder, instead of /tmp or make it configurable. It is always a pain in the ball bearing when I am working on calibration as I have to go back and forth.
I kind of found an in the middle solution: Klippain-ShakeTune plugin. Which is actually neat for some extra features, and it saves under printer_data, but it doesn’t update printer. cfg file automatically, which means I just run it twice using stock shaper calibration too, to update settings (not out of lazyness, but the way the output is presented, is the best way for me to make mistakes).
It’s a bit odd I get slightly different results even though it’s the same api. But I digress.
The point is, it makes no sense to me why require going through hops to see the results of what I triggered via Mainsail interface. I am willing to submit a PR if I get the blessings and pointers on where to look for the code
…