← all posts site ↗

centauri firmware stuck state

the elegoo centauri carbon accepts sdcp commands, returns response, and then does absolutely nothing. stop — nothing. resume — nothing. start print — nothing. only reliable fix is walking over and flipping the physical power switch. sometimes the firmware is just a black box that takes your money and gives you a brick.

the workflow should be simple: slice with prusa-slicer using klipper flavor (not marlin — the centauri ignores marlin gcode), patch the start gcode because prusa-slicer puts m190 before g28 which the firmware ignores (bed temp resets to zero after homing), upload via http api to port 3030, start via sdcp websocket. the slicing and uploading work fine. the starting is where it falls apart.

uploaded the gcode for a pegboard hook — 88 layers, abs at 255c, 95c bed, 30% cubic infill, 5mm brim for adhesion. file's sitting on the printer ready to go. sent stop, resume, start_print through pycentauri. all three returned RESPONSE. none of them executed. the printer just sat there looking at me.

tried the software recovery path first — stop, wait 2 seconds, resume, wait 2 seconds, start_print fresh. same result. three commands, three RESPONSEs, zero movement. the firmware accepts the commands over the network, acknowledges them, and then ignores them completely. it's like talking to someone who nods at everything you say but doesn't actually hear you. power cycled the physical switch, worked immediately. the hook printed fine. ninety minutes of clean abs printing after a forty minute debugging session and a walk to the other room.

the lesson: when the software says everything is fine but nothing is happening, it's not a software problem. it's a firmware problem. and firmware problems have exactly one solution: turn it off and on again. not remotely. physically. the one thing you can't automate.