Hotend heating without control

General Discussion
1

Basic Information:

Printer Model: Kobra2
MCU / Printerboard:Pad7
Host / SBC Trigorilla B
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Funny Problem since today
After a normal print this morning, i realized a shutdown because the Heater is going above 275 degrees. After a few tries the issue remains. Thinking about a faulty Board.
To test that, i installed the original Anycubic FW and this runs as expected.

So, whenever i start the Printer, as soon as Klipper is running, the Hotend start to heat. The Temp sensor is reading the correct Temperature.
I am not able to say if i made a Update - so maybe.

I realized in the klippy.log at the end its always tells the following and the temp is continuing to rais:
klippy1407.log (4.7 MB)

Stats 71.4: gcodein=0 mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=1159 bytes_read=6276 bytes_retransmit=9 bytes_invalid=0 send_seq=142 receive_seq=142 retransmit_seq=2 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997907 pad_7: temp=43.9 heater_bed: target=0 temp=23.7 pwm=0.000 sysload=2.53 cputime=3.784 memavail=659956 print_time=60.794 buffer_time=0.000 print_stall=0 extruder: target=0 temp=69.9 pwm=0.000

Has anyone a idea what can cause this?

2

This looks like some severe hardware issue. On the one hand, we have:

Stats 3578.6: gcodein=0  mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=3561215 bytes_read=745871 bytes_retransmit=272 bytes_invalid=363 send_seq=67943 receive_seq=67943 retransmit_seq=65848 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997418  pad_7: temp=50.5 heater_bed: target=0 temp=41.8 pwm=0.000 sysload=0.15 cputime=139.300 memavail=658888 print_time=3486.724 buffer_time=0.000 print_stall=0 extruder: target=0 temp=268.1 pwm=0.000
Stats 3579.6: gcodein=0  mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=3561221 bytes_read=745974 bytes_retransmit=272 bytes_invalid=363 send_seq=67944 receive_seq=67944 retransmit_seq=65848 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997417  pad_7: temp=51.1 heater_bed: target=0 temp=41.7 pwm=0.000 sysload=0.15 cputime=139.319 memavail=658888 print_time=3486.724 buffer_time=0.000 print_stall=0 extruder: target=0 temp=270.3 pwm=0.000
Stats 3580.6: gcodein=0  mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=3561227 bytes_read=746091 bytes_retransmit=272 bytes_invalid=363 send_seq=67945 receive_seq=67945 retransmit_seq=65848 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997414  pad_7: temp=50.8 heater_bed: target=0 temp=41.7 pwm=0.000 sysload=0.15 cputime=139.338 memavail=658888 print_time=3486.724 buffer_time=0.000 print_stall=0 extruder: target=0 temp=272.5 pwm=0.000
Stats 3581.6: gcodein=0  mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=3561233 bytes_read=746200 bytes_retransmit=272 bytes_invalid=363 send_seq=67946 receive_seq=67946 retransmit_seq=65848 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997412  pad_7: temp=50.2 heater_bed: target=0 temp=41.6 pwm=0.000 sysload=0.15 cputime=139.359 memavail=658888 print_time=3486.724 buffer_time=0.000 print_stall=0 extruder: target=0 temp=275.5 pwm=0.000
Transition to shutdown state: MCU shutdown
Dumping gcode input 0 blocks
...
MCU 'mcu' shutdown: ADC out of range

grafik
grafik539×807 8.18 KB

As you can see, the temperature is increasing, ALTHOUGH Klipper commanded pwm=0.0, which effectively means no power to the heater. The board seems to ignore this.

On the other hand, there are multiple:

Timeout with MCU 'mcu' (eventtime=95.867656)
Transition to shutdown state: Lost communication with MCU 'mcu'
Dumping gcode input 0 blocks

See Timeout with MCU / Lost communication with MCU. In the context we see here, it could mean that your board crashed somehow and is no longer talking to the Klipper host on the Pad7.

Hard to diagnose remotely, but my money goes to a defect board or a severely messed up installation. The latter would not surprise me as well, given that we talk about a Kobra 2.
This printer uses a heavily modified Klipper version and already from this aspect no meaningful support can be provided.

Make sure that you do not burn down your home.

3

Thanks a lot for your reply!

First, it is an Kobra2, not a pro, witch means it runs Marlin out of stock. I use a BTT Pad7 with a USB Connection to run Klipper.

Second, and that is really confusing, if i load the Anycubic FW on this machine, everything runs fine.

And it runs for month since this morning :frowning:

4

Do I understand you right? With marlin your printer is working fine?

5

Yes, i was already looking for a spare Board and thought - give it a try.

6

So, it’s not your hardware!

Did you try the Marlin approach with another SDcard?

7

if i am running Marlin, there is no need for an SD Card. So no. Do you mean it can be caused by Klipper itself?

8

No! Not at all.

Please forget

What is your Klipper source? This GitHub - ANYCUBIC-3D/Kobra2?

9

Ok, thanks for your help, but i think the Board has issues. Still not able to print with original Marlin FW installed. Anycubic is not willing so send me a spare for free but i like the printer. Bord costs 60€…

2 Likes
10

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