Printer Shutting down while printing at random

General Discussion
1

Basic Information:

Printer Model: Voron V0
MCU / Printerboard: BTT Manta M4P
Host / SBC: CB1
klippy.log

I’ve been trying just about everything to try and get a simple print out of my printer. I just upgraded to an EBB36 connected to my Manta M4P using the IO2CAN I’m having a problem where it randomly stops printing and won’t let me get into mainsail without power cycling the printer. I have checked all the power connections and they appear all fine I’ve checked all the crimps and fixed my CAN_H wire and that still didn’t fix it so I reinstalled Klipper on everything and that also didn’t fix it. So I replaced the EBB with a spare. I’ve made sure the baud rate is the same between both are is 500000. I’m also not really sure what the exact error msg is because I can’t see it before it kicks me out of mainsail. I have also tried turning off all unnecessary features like my bed and toolhead LEDs and aux and chamber fans. I also tried changing the psu incase it was drawing to much for the stock psu
klippy.log (4.6 MB)
moonraker.log (259.3 KB)

2

The problem, where you can’t access mainsail, is hard to debug by klippy logs.
Most probably it is a Linux issue, Network and/or sort of hardware.

About the only error that is present in this log.

Stats 1019.0: gcodein=0  mcu: mcu_awake=0.031 mcu_task_avg=0.000034 mcu_task_stddev=0.000042 bytes_write=2254186 bytes_read=395690 bytes_retransmit=9 bytes_invalid=0 send_seq=40494 receive_seq=40494 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=23 upcoming_bytes=807 freq=64000754
...
MCU 'mcu' shutdown: Missed scheduling of next digital out event
clocksync state: mcu_freq=64000000 last_clock=65488368732 clock_est=(990.799 63655920428 64000753.867) min_half_rtt=0.000085 min_rtt_time=320.436 time_avg=990.798(845.839) clock_avg=63655920428.736(54134322478.707) pred_variance=4065493.568
Dumping serial stats: bytes_write=2275596 bytes_read=598865 bytes_retransmit=9 bytes_invalid=0 send_seq=41795 receive_seq=41795 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0
...
Sent 94 2988.490621 2988.490621 16: seq: 1d, queue_digital_out oid=14 clock=2550270975 on_ticks=2935866
Sent 95 2989.390893 2989.390893 16: seq: 1e, queue_digital_out oid=14 clock=2607870976 on_ticks=2605660
Sent 96 2993.290568 2993.290568 16: seq: 1f, queue_digital_out oid=14 clock=2857470976 on_ticks=2975109
Sent 97 2994.190604 2994.190604 16: seq: 10, queue_digital_out oid=14 clock=2915070976 on_ticks=2348769
Sent 98 2994.490791 2994.490791 16: seq: 11, queue_digital_out oid=14 clock=2934270975 on_ticks=2752127
Sent 99 2998.690527 2998.690527 16: seq: 12, queue_digital_out oid=14 clock=3203070976 on_ticks=2704088
...
Receive: 94 3003.453039 2998.690527 14: seq: 13, stats count=158 sum=97315 sumsq=432977
Receive: 95 3003.490192 2998.690527 15: seq: 13, analog_in_state oid=13 next_clock=3509758976 value=23990
Receive: 96 3003.510142 2998.690527 14: seq: 13, analog_in_state oid=15 next_clock=3511038976 value=7850
Receive: 97 3003.790138 2998.690527 15: seq: 13, analog_in_state oid=13 next_clock=3528958976 value=23990
Receive: 98 3003.810126 2998.690527 14: seq: 13, analog_in_state oid=15 next_clock=3530238976 value=7846
Receive: 99 3003.991327 2998.690527 12: seq: 13, shutdown clock=3523071130 static_string_id=Missed scheduling of next digital out event

Hmmm,
Basically, by some reason, klippy does not send a new PWM in time.
I can’t spot anything suspicious.

I may only suggest to just update the Klipper host and CAN mcu and reproducing the issue.

Hope that helps.

3

They should have been up to date. But that hopefully doesn’t matter for the moment I finally went ahead and changed the CB1 out for one from another printer and had a successful dry print so now I’m going to try a full print

4

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