Spontaneous heating shutdown at the beginning of printing

General Discussion
1

Hello everyone!

I have a “floating” issue: at the beginning of printing (within a couple of minutes from the start), sometimes Klipper (or someone else) sends a command to turn off the heating (sets the target nozzle and bed temperatures to 0 degrees).

Some nuances:
This happens only at the beginning of printing: if i “catch” the Klipper command to turn off the temperature and set it to the desired temperature afterwards, such an error does not occur.
I set the temperature and “run” the printhead across the entire bed - the temperature holds steady (checked for the possibility of a circuit)
With the same G-code, this can happen, or it may not.
PID calibration has been performed.
The MCU firmware has been updated.

I’m asking for help from those who know how to read logs (I can’t figure it out myself).

Thank you in advance for your help!

Printer Model: K3D Vostok (CoreXY/2 custom idex printer)
MCU / Printerboard: Spider 446 v2.2 / Orange Pi 3 LTS
all logs: Klipper Log Parser
Error time: nearly 19:13 today

2

Please upload a log showing the error here and refer to the relevant error.

All I can see in the log is that apparently Extruder1 is activated but Extruder is heated up and a print start it attempted with the cold extruder.

3

@Sineos thanks u for attention)

The events occurred as follows:

  1. The file was sent to print.
  2. The print head was sent home and the nozzle and table heating were turned on.
  3. Printing started.
  4. After 2 minutes of normal printing, klipper received a command to set the temperature to 0 degrees.
  5. Half a minute later, the temperature dropped below the minimum and the print was automatically turned off.

This algorithm occurs in 50% of print starts (maybe with the same gcode).
If after such a one-time failure you manually set the normal print temperature, the error will not repeat until the end of the print.
Setting the temperature before printing also does not help.

I can’t understand which of the logs to look at and where the error is reflected: after the error actually occurred (after 5 minutes) I made these logs, but could not find any indication of any errors in them. Could you tell me which of the logs is needed to search for the error?

4

IMO, your IDEX config / macros are messed up and at least I will not start to debug this.

Just from your klippy.log:

  • There are macro errors like Unknown command:"SET_DUAL_CARRIAGE_MODE" → In fact Klipper does not know this command natively and it is not defined anywhere as a macro
  • It seems the active extruder is always Extruder1 and this one is cold, i.e. never has been heated up → Extruder 'extruder1' now syncing with 'extruder1'
  • It further seems you are partially using Klipper’s own IDEX capabilities, but mix it up with some macros of unknown origin

All I can recommend is to start clean based on klipper/config/sample-idex.cfg at master · Klipper3d/klipper · GitHub

1 Like
5

Thanks a lot for the tip! I’ll start looking for problems in macros

6

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