My Snapmaker U1 suddenly stopped working the way it should, and I can’t figure out what changed. I’ve checked the basic setup and still can’t get it running properly, so I need help troubleshooting the issue and finding out what to try next.
Start with the boring stuff, because on Snapmaker machines the boring stuff fixes a lot.
- Power off the U1 fully. Unplug it for 2 minutes.
- Reseat every cable. Power, toolhead, bed, limit switches, controller. One loose plug = weird behavior.
- Check the screen for any error code. Write the exact text.
- Home each axis one at a time. Watch which axis fails, skips, grinds, or moves the wrong way.
- Inspect rails and lead screws. Debris, dried grease, or a bent screw will stop motion fast.
- Try a factory reset, then reload firmware from Snapmaker’s site if your version is old or corrupted.
- If the bed or nozzle temps look wrong, test thermistor readings at room temp. A bad sensor often shows nonsense numbers.
- If prints start then fail, check slicer settings. Wrong toolhead, wrong start gcode, or bad accel values will do it.
If you post these, people can narrow it down fast:
- exact symptoms
- what changed before it broke
- firmware version
- photo of wiring
- video of startup/homing
If it died out of nowhere, my first bets are cable, firmware, or a failed module. Seen all 3. The loose cable one gets ppl every time.
I’d go a slightly different direction than @andarilhonoturno on one thing: I would not factory reset or flash firmware right away unless you already know the hardware is behaving. Firmware gets blamed for everything, but most “suddenly stopped working” cases are either a sensor reading wrong or one axis/module silently failing.
A few checks that help narrow it down fast:
- Does the machine fail at idle, during homing, or only when starting a job?
- In the controller menu, watch the live temp values before heating anything. If nozzle or bed is showing something crazy at room temp, stop there. That points to wiring/sensor, not setup.
- Use the touchscreen to jog each axis in small steps, like 1mm then 10mm. If manual jog works but prints don’t, that smells more like gcode/slicer/profile than machine hardware.
- If it homes but dimensions are off, put a mark on the coupler/lead screw and see if it slips under load. Set screws backing out can make it act haunted.
- Check whether a fan is dead. On some toolheads, one failed fan can trigger ugly behavior fast, especially if it starts normal then goes weird after a minute or two.
- If the touchscreen is laggy/freezing/rebooting, that can be controller-side rather than motion-side.
Also, “checked the basic setup” can mean 10 diff things, so post:
- exact model/toolhead
- what it does now vs before
- whether it powers on normally
- whether manual movement/heating works
- any noise, smell, or blinking lights
A short vid helps way more than ppl think. Without the symptons, everybody’s just guessing.
Try isolating the fault instead of testing every feature.
Power off and unplug the U1 for 10 minutes. Disconnect USB devices, camera, enclosure accessories, and any add-on modules. Leave only the stock hardware connected. Power it on and run one small built-in test print.
If it works, reconnect one item at a time and repeat the test. The item causing the failure becomes obvious. Also try a different wall outlet, without a power strip. Weak or unstable power causes odd, inconsistant faults.
If this started right after you moved the machine or bumped it, look at belt tension before anything else. The U1 is CoreXY, so both belts share the load on X and Y. One belt going slack throws off motion in ways that look like a dozen other problems, and it happens quietly. You won’t get an error code for it. Prints just start skewing or the head starts making that faint knocking sound at direction changes.
The isolation method @brighttiger1078 described is solid for accessory-related faults, and I’d run it if you’ve got the enclosure or extra modules hooked up. But I’ll push back gently on where everyone’s pointing. On these newer multi-material setups, the filament/material side causes a lot of ‘it just stopped’ reports. A jam or a feed sensor throwing a fault mid-job can halt everything and look like a controller problem when it’s really the loading path. Check whether it dies at the same point each time. Repeatable failure points usually mean feeding or gcode, not random hardware.
I’m with @sonhadordobosque on leaving firmware alone at first. Reflashing a machine you haven’t diagnosed just adds a variable. Get the exact behavior nailed down, cold temps readout, where in the process it quits, any sound. If manual jog and heating both work fine and it only breaks during a job, stop looking at the machine and start looking at your slicer profile and the filament path.