I did change them in the console, and even saved the gcode to see if it would be written, but it took no action. Even if Xtool locks the eeprom, it should still recognize the change, and run that code as easily as it does the movement.
I entered the code in the settings (see photo), but nothing. I have tailored Marlin firmware to run on all of my 3D printers, and am pretty good with gcode, and I DO NOT advise anyone to do this if you don’t know what it does to your machine.
As I said though. In 3D printing, I can change the values in PrusaSlicer if need be, but normally I lock them in through the firmware. It’s not like they need to be changed every day. My question is if I do change those two values in the console, they should have some effect. Also, when I save the gcode, and the values are saved, the M code should be read, and executed, but it’s being blocked somewhere. I can’t offer things to people that are to be a specific measurement if these companies building expensive machines don’t think we are capable enough to decide what we need. Are the two values that I marked the variables that change the x, and y steps?
If you have a choice in this I’d suggest going with a GRBL based solution over Marlin if at all possible. Marlin is currently much too varied and not particularly well supported. You’ll likely be changing one headache for another.