Random Shutdown

General Discussion
1

Basic Information:

Printer Model: Custom Cross Gantry
MCU / Printerboard: Manta M8P V1.1 + Ebb42 over CAN
Host / SBC: BTT CB1
klippy.log
klippy.zip (849.1 KB)
dmesg.txt (91.4 KB)

Describe your issue:

Total print time around 1400 hours and always smoothly. Since past week started shutting down randomly, during prints and even when idle.

No message appears when it fails, the printer just stops, shuts downs all heaters/fans/motors and mainsail stops working. Most often ssh still works, but in some occasions it also shut down.

Most of the klippy logs would just end up like this here attached, suddenly. But in some cases Missed scheduling of next digital out event, MCU shutdown(Main and EbbCan) and Timer too Close also showed up.

Some things that i tried to verify were:

  • Updated everything, including the CB1 OS, MCU and EBB firmware
  • Checked for Unstable Voltages
  • Changed the SD 3 times, twice from the same “batch/manufacturer” and the third from a different one
  • Redid the CAN wire harness and checked the rest of the power connections
  • Checked for BRLtty / ModemManager - Services Interfering with Klipper
  • Removed and reinstalled Klipper/Mainsail/Moonraker
  • Changed the Power Supply for the Manta/CB1 (This printer got another power supply for the ebb and the Bed, both are 24V)

As anything that stays for long, the MCU got some dust, is it possible that this can be causing trouble? (The USB ports are facing up and close to a fan)

Thank in advance for all

2

Well, your dmesg log is full of errors. Likely, the issue is related to the CB1:

  • Defective CB1
  • Corrupted Linux installation on the board
  • Dying SD / storage
3

Tried installing 2 diferent versions of the CB1 OS in diferent SD cards but kept having problems. Was kinda reluctant to believe that it was the CB1 before, but will just order another one now.
Thank you Sineos!

4

Before ordering a new CB1, you might read MCU 'EBBCan' shutdown: Timer too close.

You mentioned

I wanted to post in above mentioned topic this link MCU 'mcu' shutdown: Timer too close still present ¡ Issue #124 ¡ Frix-x/klippain-shaketune ¡ GitHub I stumbled over when I was reading about Klippain (GitHub - Frix-x/klippain: Generic Klipper configuration for 3D printers), but the topic was already closed.

5

Of course, reading relevant information always makes sense. In this case, the dmesg output clearly shows hardware and kernel-related errors that must not be present for a stable system.

@hcet14, please make sure to avoid distracting from such discussions without first assessing and understanding the relevant information.

1 Like
6

My post from above was addressed to @Valgautr.
For those who are hard of understanding.

@Frix-x found out, that the CB1 might overheat and start throttling because it is getting too hot.
This can of course lead to “hardware and kernel-related errors”.

@Valgautr said there was some dust on his CB1, this reduces the heat exchange of the CB1 controller to the circulating air.

Maybe his CB1 overheated?

7

Thank you for the further information.
There was indeed some dust, but the temp didn’t ever go above 55, as it has some cooling, so it didn’t seem to be related to this problem.
I ended up getting another CB1, replaced it a few days ago and it seems to be working nicely so far.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.