MK3S Custom Firmware DEFAULT_AXIS_STEPS_PER_UNIT
I need to change the distance per step on a MK3S Z-axis due to using aftermarket z-axis threaded rods with different thread pitch.
I'm following the steps specified in the README.md on the official GitHub Prusa Firmware repository.
I found the file ...Prusa-Firmware\firmware\variants\MK3S.h, where there is a line:
// Steps per unit {X,Y,Z,E}
#define DEFAULT_AXIS_STEPS_PER_UNIT {100,100,3200/8,280}
I have changed the default 3200/8 to the calculated value for my Z-axis threads, rebuilt the firmware with VSCode according to the steps in the repository README.md, and flashed the .HEX to the printer. Unfortunately, the printer's z-axis behavior is not changed, which means this isn't the correct way to do this.
I'm unable to find instructions on this exact mod. Can someone tell me how to incorporate the revised DEFAULT_AXIS_STEPS_PER_UNIT numbers into the .HEX build?
Thanks in advance.
RE: MK3S Custom Firmware DEFAULT_AXIS_STEPS_PER_UNIT
Hi,
I think you can use G-code to change the Steps per unit value. For example: M92 Z300 will change Steps per unit for Z axis to 300, them use M500 to store the change to EEPROM.
RE: MK3S Custom Firmware DEFAULT_AXIS_STEPS_PER_UNIT
The answer was the M commands, thanks for replying.
Prusa customer support explicitly refused to provide any information when asked. This, in combination with locking out MK4S and Core One firmware (making mods impossible), has permanently harmed Prusa's reputation in my eyes. Pretty much leaves no reason to prefer Prusa over their competitors.
RE: MK3S Custom Firmware DEFAULT_AXIS_STEPS_PER_UNIT
The answer was the M commands, thanks for replying.
Prusa customer support explicitly refused to provide any information when asked. This, in combination with locking out MK4S and Core One firmware (making mods impossible), has permanently harmed Prusa's reputation in my eyes. Pretty much leaves no reason to prefer Prusa over their competitors.
CORE One FW code is still open, and AFAIK, was never locked. Details here: https://www.prusa3d.com/page/open-source-at-prusa-research_236812/
And the code itself is on GitHub, as always: https://github.com/prusa3d/Prusa-Firmware-Buddy
Yes, you have to break away the appendix on the board to flash it, but it's hardly a lock - rather a safety feature.