Restart forced after prime blob
Midway through a print my printer haulted and seemed to do a firmware restart, gcode fans stopped, unable to connect to the web interface exc. Now whenever I start a print it gets to the prime blob and then haults. I reverted back to my earlier config, updated everything and checked my wiring with nothing unusual happening. Attached is my klipper log and a download of my gcode file. I'm inexperienced with klipper but I don't see anything unusual. No error is thrown it just restarts.
My heaters still work, all my endstops, probes and sensors work fine and motion seems to be working perfectly fine. I have no idea what would be going on. My setup is mostly unmodified with a btt octopus pro f446 and a raspberry pi 4b powered off the rgb header of the board.
28 Replies
This looks really strange, everything just dies. If i had to guess i'd say it looks power related. the Octopus 446 stalls and then the RPi dies. It might be a short caused by a loose connection that only triggers at specific points on the bed, or a brown out. Try powering the pi with 2 x 5v and 2x gnd off the Raspberry Pi header and make sure the 5V USB Jumper isn't in place (needs to be taken out).
like-gold•2y ago
5v usb power wasn't in place and I swapped my wiring to match the diagram but the problem persists. I'm going to change the usb cable next but I doubt that's the issue
If the pi actually shuts down, i can't think of anything else than something power related. Really odd.
Unless it's a thermal shutdown
check if there's anything in /var/log/syslog
like-gold•2y ago
I'll give it a shot, pi temp never reads more than 50c I'll put a fan over it and see what happens. It looks exactly like a firmware restart, everything clearly still has power but all the outputs on the board shut off.
I couldn't find any file named syslog but I'm not very experienced with Linux file structures. There was a mainsail error file from last night but it looks like my wifi just blipped for a minute.
So the pi is still on?
like-gold•2y ago
The pi is still receiving power at very least. I'll take a video of what happens when it shuts down
like-gold•2y ago
like-gold•2y ago
Everything comes back on after around 2 minutes
I’ve never seen anything like it
like-gold•2y ago
Figures I'd run into an issue like this. Are there any files I should post? I've plugged the printer into different breakers and tried externally powering the pi with no success. I might set bed temp to zero and see if that changes anything.
After that I'm just going to reinstall ratos
like-gold•2y ago
I downloaded my cfg file and reinstalled the v1.2.4 latest non prerelease firmware and it seems to be working. Attached is my cfg file in case any clues could be in there. My ratrig is custom designed so the sizing is a little weird, assuming that is not the problem.
That is one of the most vanilla printer.cfg's i've seen in a while, nothing sticks out. Makes no sense to me that a reinstalled worked. Best i can think of is file corruption or something, but i can't imagine how that wouldn't fail on startup. The weird part about your log is that there's a whole bunch of null bytes inserted when it happens, no errors or anything.
Happy you got it working though
like-gold•2y ago
I jinxed myself it happened again
Oh no
So not file corruption then
Have you tried reslicing?
Is it the same .gcode file you're printing each time?
like-gold•2y ago
It's happening now when I try to turn on part cooling. Does part cooling blip on during the start print macro?
It does during primeblob
Try disconnecting your part cooling fan
Maybe it's shorting
like-gold•2y ago
I'm going to swap my hotend and par cooling fan to see if it's the board or the fan
If you just disconnect the part cooling fan on the board, that would be faster
At least then you can rule that out
If it then still does weird stuff when enabling the part cooling fan it's something on the board
like-gold•2y ago
Alright definitely the fan. Weird it was working earlier
Must've died
Or the wires are damaged
What fan is it?
like-gold•2y ago
I do have a btt piggyback running 2 maglev 5015 fans so it could be a short on the piggyback
Definitely possible
Time to bust out the multimeter 😄
like-gold•2y ago
I'm going to unplug one fan then the other and see if that's the issue then check continuity on the ground control
I'm glad I have a spare of the fan and the toolboard
Thanks for your help, this was definitely a weird problem
You're welcome 🙂
If you decide you want to do multipin instead of piggyback the fans you can look at my config
GitHub
myKlipperFiles/vcore3-printer.cfg at main · jscancella/myKlipperFiles
Contribute to jscancella/myKlipperFiles development by creating an account on GitHub.
like-gold•2y ago
There must be some kind of short in the fan because I swapped in my replacement and it's running good now
I'm not familiar with multipin is that a different toolboard?
No, it is a configuration that allows you to use two ports to control two fans as if they were one fan