Ender 3 v2 steppers stopped moving

General Discussion
1

Basic Information:

Printer Model: Ender 3 v2
MCU / Printerboard: V4.2.2 with GD32F303 chip
Host / SBC: RaspberryPi 3b
klippy (3).log (573.5 KB)

klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Hello! I have recently decided to try and wring out more out of my ender 3 v2 by upgrading the firmware. When I opened it I unfortunately found out that my board mounts the infamous GD32F303 chip. I didn’t manage to make marlin work on it, but I had better success with klipper after trying out some of the proposed solutions I’ve found on this forum. Before these issues I’ve ran all the configurations checks and the calibrations I thought relevant to me, with everything apparently working fine and printing with moderate improvements for 40 odd hours…

At least until recently, when I started inconsistently getting the “Lost connection with MCU” error, which would only disappear after multiple reboots and some time.
While trying to gather logs and info about this issue, I managed to make a longer print work until I ran into another issue: the motors stopped moving mid print (Mainsail interface showed that it still sending commands) and even days later Klipper still can’t make them move. When i try to home the axis the steppers get locked in position and then don’t move. Since the printer isn’t homed i couldn’t send single move commands, so I’ve tried enabling [force_move] and using the FORCE_MOVE command, but still no movement.

Hotend and bed can still heat up, so it doesn’t seem to be a power supply issue.

Since the printer worked fine for quite a bit, what could it be?

2

Welcome Lord_Pi.

I wouldn’t push that aside.

From your log

Attempting MCU 'mcu' reset command
Attempting MCU 'rpi' config_reset command
b'Got EOF when reading from device'
webhooks client 548354216672: Disconnected

I think that’s a power drop.

How old is your power supply? How much did it run?

3

All the electronics, apart from the Raspberry, are stock, so both the power supply and printer are two years old. I don’t have a hard number on the print hours, but i would estimate somewhere between 700 and 900 hours.

4

I was about to try and flash the default creality firmware to check if it was an hardware or software issue, when I tried one last time to see if the problem persisted still.
With no heating on, the axis moved correctly, and as soon as i tried to move them while heating the hot end and the bed the raspberry lost connection to the MCU as it has happened before. Resetting the firmware can’t manage to re-establish the connection, only rebooting both printer and Raspeberry works, but the behavior doesn’t change. I’ve attached the Klippy log.
klippy (4).log (71.1 KB)

I thought it might have been a stepper driver issue, but you might be right on the PSU.
How could I go on and test it?

5

Well…

I don’t know. Your Klipper setup was working and you finished prints. Maybe a 3D-friend has a PSU to borrow, which you could try?

6

Is that really a lot? I know creality machines aren’t known for build quality, but this felt like mild use over only two years.

I’ll try and ask, we’ll see.
Thank you for all the input.

7

The power supply outputs 12v or 24v. The 5v powering the arduino is normally
derived from a 5v buck converter on the mainboard which is supplied 12v/24v however unlike skr or mks boards theres no switch disable the pi ‘backpowering’ the creality board.
I’d suggest you turn on the printer then 20 seconds or so later power the pi but you may just have a broken mainboard.
SKR mini v3 is a great mainboard

8

Still cheap Chinese consumer stuff. Nobody knows where the power supplies come from :wink: You could have one of a bad batch.

9

I’ve finally managed to find another power supply on loan! After an unnecessary and long detour where I tried to downgrade back to vanilla firmware and then botched the klipper reinstall (I had to reflash both raspberry and printer), I can finally confirm it’s not a power supply issue.
At this point physical damage to the board seems the probable culprit. Thank you everyone for the support.
I’ll decide if I’d rather spend the money on a new board or put it torward a new machine (I wouldn’t mind getting my hands on an idex).

10

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.