Printer Model: trident 350
MCU / Printerboard: rpi 3b+/Octopus 1.1/ SB2040 via canable pro clone (latest original canable fw 1000000) klippy_idle_shutdown.txt (352.1 KB)
klippy.log
Hi,
i’m experiencing random shutdowns of my printer, regardless of printing or not, hot or cold. At first I thought it was a canbus issue when I used the octopus in canbridge mode. So I got a canable pro clone to skip the bridge, which works fine. I can use the adxl on the toolhead board without issues now. On the bridge I had do reduce microstepping for x and y motors from 32 to 16 to get it work. But i still get a “timer too close” error when probing more than about 40 times in a row. Not a real problem, 7x7 works fine most of the time. The real issue is the random shutdown, i can’t find a hint in the klippy log. I booted the printer this morning an did a z_tilt. When i came back 6 houirs later, printer was up an running idle and then suddenly shutdown with lost comms to mcu (octopus) while I was checking the config in mainsail. Same happend yesterday while printing. Since then octopus is running USB only, no can bridge, I’m pretty sure the shutdown is not canbus related. When this error happens restart or restart_firmware do not bring back the printer, rebooting the pi also doesn’t work. Full powercycle brings it back to normal state. It then takes minutes or days to happen again.
any ideas what to check next?
Should I buy new PSUs? 24v an 5v?
Get a new Octopus? or other board?
are there any other logs I might check?
unfortunately a new pi is not an option at the moment, not going to pay the scalpers
Why aren’t you using the CAN bus interface built into the Octopus?
The rPi 3B should be fine in terms of power.
I’m using the Octopus’s CAN interface (with CanBoot) on two of my printers without any issues, one talking to an SB2040 Afterburner toolhead controller and one with a Mellow FLY SHT toolhead controller without any issues.
That’s exactly what I did. But since I installed the canbus i got the mcu shutdown errors. The errors indicated a problem with the canbus so my approach was to remove the octopus bridge to exclude the octopus. But the error remains, the "Timeout with MCU ‘mcu’ where MCU is the octopus which is connected USB to the pi. the MCU “crashes” somehow an can only be recovered witrh power on/of cycle, so no canbus involved now
You may use Sineos wonderful little webpage https://sineos.github.io that allows uploading a klippy.log and creating the graphs to analyze your log.
There is already something going on before the error occurs.
Maybe this goes down your alley CANBUS Communication timeout while homing Z.
I used the wires that came with the sb2040 an twisted the data lines myself, I tried not twisted, didn’t seem to make a difference. I got the jumper for the 120ohm resistor on the toolhead board an on the canable, measures around 60 ohm
I just “downgraded” to 32bit mainsailos. No more canbus errors , 0 invalid_bytes
thanks everybody. I’m going to print now to see if the octopus crashes again, maybe this was related to 64bit os too.
So my canbus problems are all gone, but the random shutdown persists: just happend again 3 minutes into the print, printed 11 hours with no issues before.
klippy_shutdown_print.log (1.8 MB)
I used sineos website as mentioned above but could not really find anything. For me it looks like the connection is gone and klipper goes into shutdown. It’s maybe a problem with the usb connection to the octopus or the octopus itself. It can only be recovered by powering off the octopus, all software restarts do not help, including rebooting the pi. I’ve ordered a new usb c cable, I’m using the one that came with to octopus
I had a similar issue, where the printer would randomely shut down during printing, 3 minutes in or 5 hours in, it was infuriating.
After searching the web, I found out that if the mainboard fw is not updated, sometimes things like this can happen (with different error messages). Try making sure that your raspberry pi firmware is up to date (just hit the check for new firmware button next to the different fw’s installed on your device. Then update the mainboard fw based on your updated pi fw.
I also had to fully restart my printer while this was happening btw. I am not using an octopus, but other people have had this same problem with their octopus’s. I am using a btt manta m8p, and the mainboard fw was wayyyyyyyyyyy out of date.
I changed the USB cable from pi to octopus, no shutdowns so far, I left it powered on day and night to see what happens and did some printing.Seems it was the cable
erm, no, like i said above I went from 64 bit mainsail to 32 bit, which solved my canbus problems but did NOT solve the random shutdown, THAT was resoveld by a new usb c cable
Have you been running 64-bit Mainsail on a 32-bit Raspberry Pi OS?
Could you please run the command “uname -a” and share the output?
I have also experienced sporadic disconnection issues and suspected it might be due to the known 64-bit issue. However, before downgrading to 32-bit, I would like to clarify the root cause of my problems.
Yes I’ve been running 64bit Mainsail OS directly downloaded in Pi Imager. That was the cause of several canbus related problem. All of the canbus problems went away after reinstalling the pi with mainsail OS 32Bit.
, 0 invalid_bytes