First longer print attempted, printer stops after 1 hour

I suspect it is something with the raspberry pi Previously i got these two warnings and kind of ignored them for now: Previously Under-Volted rPI supply voltage dropped below 4.65V at least once since the last power-on. Previously Throttled rPI ARM core(s) were throttled down at least once since last power-on. A little background, rpi is connected with 2x dupont for + and 2x dupont for -, with octopus pro. BUT when I was putting it all together, i burned one dupont wire because it was wired incorectly. I was following guide for octropus 1.1, and these two have uart pins differently. So i then wired everything correctly, changed the burned out dupont wire, and off we went calibrating. Now i attempted first longer print. The way i see it, it is probably rpi. maybe the dupont wire also burned connector somewhere. or maybe other three dupont wires were also damaged from when the melting was on the 4th wire. but i inspected them and it was only 4th wire. Maybe the pins are bad. I have multimeter. I'd have to check guides online how to measure if pins are good on rpi/octopus. It is very sus that i am getting under volting warning on rpi, since its connected with 4 dupont wires like its suppose to be. so i think i have to inspect that thoroughly. also to note, yesterday evening i plugged in logitech webcam, trying to get monitoring setup... so i think that also took some juice from it? I attached klippy log
Solution:
I would go over all your wiring and components, something else might have gotten damaged from wiring up the pi wrong
No description
Jump to solution
11 Replies
Bizilux
BiziluxOP8mo ago
this is the screenshot that i got when it just died again right now...
No description
Bizilux
BiziluxOP8mo ago
part cooling fan started blazing, like when on startup of the printer it starts blazing until klipper starts up... so i think something resets the printer :S
Bizilux
BiziluxOP8mo ago
i think on the new log i found where it crashed. now why it crashed is a different story... lines 19160
Bizilux
BiziluxOP8mo ago
its a whole line of NUL... but why that happened?
Bizilux
BiziluxOP8mo ago
got a clean klippy log of just the error... i tried a new gcode if that was the problem, but its not... like 4517 has nul all over it
blacksmithforlife
I would get a dedicated power supply for the pi to rule out the connection from octopus. It is normal for the fan to go to 100% when klipper restarts as that is a safety precaution
Bizilux
BiziluxOP8mo ago
I disconnected the 4 duponts and connected power supply to rpi. Now i got the error TMCuart_response timeout... I guess those 4 dupont wires need to stay connected? I thought USB is enough between octopus pro and rpi I'll try with those 4 wires in as well
blacksmithforlife
They're unrelated. The pi doesn't use UART to power itself
Bizilux
BiziluxOP8mo ago
After connecting 4 dupont wires to uart as well as separate power to rpi, i get this error
No description
Solution
blacksmithforlife
I would go over all your wiring and components, something else might have gotten damaged from wiring up the pi wrong
No description
Bizilux
BiziluxOP8mo ago
I checked and the mains power cable was somehow hanging halfway out... So I'm trying again now I did leave 4 dupont wires still connected now. As well as power supply to rpi I'm hoping that was a problem before too. Always worked for like an hour, but then after first layer when print speed went up, it maybe shook the power cable just a bit more out to lose contact
No description
Want results from more Discord servers?
Add your server