MK3.5 - Calibration and tuning of X Y Z axis and E steps.
Just finished my MY3.5 upgrade, now wanting to calibrate and tune it.
I had only recently tuned my MK3S+ to correct some dimensional inaccuracies, and since then it had been printing spot on.
I did it in a hacky way, made a calibration cross (100x100x100), print, measure, do some math, then put:
M92 X100.4 Y100.3
in PrusaSlicer's Start G-code section, and my prints after that were bang on.
I've now done the same with my MK3.5, and would like to do it in a less hacky way I guess. Have printed a move advanced calibration cross, and have noticed I now have a slight Z deviation, where it was previously exact. I have also decided to tune the extrusion steps, and have determined that I need to update the values to;
X100.29 Y100.53 Z401.06 E???.?*1.0409
The issue I'm now having is, it appears I can't use the newly installed PrusaLink or Prusa Connect to do this? And when I searched for Pronterface, I find it was removed in 2.60. So, without Pronterface, is there any way to find out what E???.? currently is; then once I have, what's the least hacky way to send:
M92 X100.29 Y100.53 Z401.06 E???.?*1.0409
M500
to my MK3.5?
TIA! ❤️
RE: MK3.5 - Calibration and tuning of X Y Z axis and E steps.
Installed Pronterface, got the current E value, then discovered the 'super secret settings section'... (Goto settings, long press, get experimental settings)
So, for E steps, you can just go here, my default was 266, which was giving me 93.6mm. Even though I had changed and saved it in Pronterface, it didn't seem to take, so I changed it here. Bang on 100mm when I ask for it now. Hope this helps someone 🤙
Currently printing another calibration pyramid to see if the other changes saved properly.
RE: MK3.5 - Calibration and tuning of X Y Z axis and E steps.
For anyone playing at home, looks like you can't permanently change the XYZ steps, unless I was doing it wrong (highly likely).
Connected with Pronterface, ran values as above, M500 to save. Ran M92, returned the updated values. But seems to have reverted since a restart.