<p>This is a theoretical assumption, but I suppose that your steps/mm values are now wrong in the EEPROM - specifically that they are set to 0 (<strong>zeroed steps per mm</strong>)? Could you please use the LCD and navigate to <em>Configuration &gt; Advanced Settings &gt; Steps per mm</em> and check what values are set there? If there are zeros, could you set them to positive values (e.g. =80) and check homing again? Then save the changes using <em>Configuration &gt; Store Settings</em>.</p>
<p>I just made the following test proving that this may be the cause. I set steps per mm for X=0 (executed G-Code: <code>M92 X0</code> from serial terminal) and tried to move X. The stepper motor was enabled (quiet noise or hiss), but it didn't move at all. There was no additional feedback e.g. on LCD. Pretty similar.</p>
<p>If this is not the only broken setting, then option <em>Configuration &gt; Restore Defaults</em> should reset the EEPROM to values defined in Marlin's configuration. I needed to perform <em>Configuration &gt; Store Settings</em> to make it persistent. But this will reset many other values, so I would suggest writing down all current values from LCD before doing the reset, for reference in future (in case they were valuable). And you still may not see all of the settings on the LCD, therefore I would use G-code for this operation - see below.</p>
<p>These operations can be also performed from a serial terminal using G-Code commands: <a href="https://marlinfw.org/docs/gcode/M503.html" rel="nofollow noreferrer">M503</a> to verify and copy the current configuration, and <a href="https://marlinfw.org/docs/gcode/M502.html" rel="nofollow noreferrer">M502</a> followed by <a href="https://marlinfw.org/docs/gcode/M500.html" rel="nofollow noreferrer">M500</a> to perform a factory reset.</p>

CC BY-SA 4.0
2021-01-15T03:09:35.280Z
2023-06-06T07:13:05.007Z
2023-06-06T07:13:05.007Z
octopus8
<p>In your platformio.ini file check the <code>default_envs</code> variable if it's <code>mega2560</code> set it to your board type, <a href="https://youtu.be/S0epn4ANJlo?t=187" rel="nofollow noreferrer">this</a> video from ruiraptor explains how to get your board type. It fixed it for my Ender 3.</p>

CC BY-SA 4.0
2023-09-22T20:34:51.387Z
2023-09-22T20:34:51.387Z
Leo Aqua
<p>I've recently updated my Ender 3 Pro to the latest Marlin 2.0 firmware and when I press autohome or try to move the axis, I hear a very quiet noise from the motors trying to move and then they just don't. I did get an error message about EEPROM when I first booted the printer after flashing but I just pressed reset and the issue hasn't come back even after trying multiple different firmware versions.</p>

CC BY-SA 4.0
2021-01-13T22:32:26.190Z
Hi, welcome to 3DPrinting.SE! This could we'll be related to an incorrectly configured configuration file, it is very hard to guess what is causing this with this little information.
0scar
CC BY-SA 4.0
2021-02-02T04:38:25.563Z
Jacob, were you able to resolve your issue with steppers movement? If my response below helped you (and you can accept it to close question)? Or do you have any other explanation to share, like stepper driver settings in firmware? I am very curious of the actual reason. Also let us know if you still struggle with this.
octopus8
<creality-ender-3><firmware>
No stepper motor movement on Ender 3 Pro
Jacob Durbin
# No stepper motor movement on Ender 3 Pro

(Asked by: username_0 on 2021-01-13)

I've recently updated my Ender 3 Pro to the latest Marlin 2.0 firmware and when I press autohome or try to move the axis, I hear a very quiet noise from the motors trying to move and then they just don't. I did get an error message about EEPROM when I first booted the printer after flashing but I just pressed reset and the issue hasn't come back even after trying multiple different firmware versions.

**Tags:** creality-ender-3, firmware

> **Comments:**
> **username_1**: Hi, welcome to 3DPrinting.SE! This could we'll be related to an incorrectly configured configuration file, it is very hard to guess what is causing this with this little information.  
> **username_2**: username_0, were you able to resolve your issue with steppers movement? If my response below helped you (and you can accept it to close question)? Or do you have any other explanation to share, like stepper driver settings in firmware? I am very curious of the actual reason. Also let us know if you still struggle with this.  

---

## 2 answers

### Answer by username_2 on 2021-01-15. Score: 1

This is a theoretical assumption, but I suppose that your steps/mm values are now wrong in the EEPROM - specifically that they are set to 0 (**zeroed steps per mm**)? Could you please use the LCD and navigate to *Configuration > Advanced Settings > Steps per mm* and check what values are set there? If there are zeros, could you set them to positive values (e.g. =80) and check homing again? Then save the changes using *Configuration > Store Settings*.

I just made the following test proving that this may be the cause. I set steps per mm for X=0 (executed G-Code: `M92 X0` from serial terminal) and tried to move X. The stepper motor was enabled (quiet noise or hiss), but it didn't move at all. There was no additional feedback e.g. on LCD. Pretty similar.

If this is not the only broken setting, then option *Configuration > Restore Defaults* should reset the EEPROM to values defined in Marlin's configuration. I needed to perform *Configuration > Store Settings* to make it persistent. But this will reset many other values, so I would suggest writing down all current values from LCD before doing the reset, for reference in future (in case they were valuable). And you still may not see all of the settings on the LCD, therefore I would use G-code for this operation - see below.

These operations can be also performed from a serial terminal using G-Code commands: [M503](https://marlinfw.org/docs/gcode/M503.html) to verify and copy the current configuration, and [M502](https://marlinfw.org/docs/gcode/M502.html) followed by [M500](https://marlinfw.org/docs/gcode/M500.html) to perform a factory reset.


---

### Answer by username_3 on 2023-09-22. Score: 0

In your platformio.ini file check the `default_envs` variable if it's `mega2560` set it to your board type, [this](https://youtu.be/S0epn4ANJlo?t=187) video from ruiraptor explains how to get your board type. It fixed it for my Ender 3.


---

