Printer completes start macro, and then won't print

General Discussion
1

Basic Information:

Printer Model: Troodon CoreXY
MCU / Printerboard: Stock troodon motherboard
klippy.log
klippy.log (830.1 KB)

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:

…
Strange issue, was working fine earlier but now after starting print it runs through the start macro, does the bed mesh, heats up, and then does nothing. Just sits there maintaining heated temp and never moves.

start gcode:
START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]

klippy.log attached.

2

From your log:

...
MCU 'rpi' shutdown: Command request
clocksync state: mcu_freq=50000000 last_clock=112274439459 clock_est=(2224.972 110846774260 49998729.758) min_half_rtt=0.000059 min_rtt_time=790.330 time_avg=2224.972(843.484) clock_avg=110846774260.724(42173140335.283) pred_variance=5317370.244 clock_adj=(8714.405 49998971.250)
Dumping serial stats: bytes_write=14430 bytes_read=46379 bytes_retransmit=0 bytes_invalid=0 send_seq=2377 receive_seq=2377 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0
Dumping send queue 100 messages
...

...
Shutdown due to webhooks request
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
...

You may note this:

If you done that on purpose, you may can post (compressed/zipped) the gcode file you want to print

3

That is probably when I hit ESTOP, because that’s the only way I could cancel the print. if i hit pause it also just sits there forever.

I attached the gcode.

cube.gcode (874.8 KB)

4

So tit seems to be this:

M109 S205 ; set temperature and wait for it to be reached

I noticed in the log, that the extruder temp is about 10°C above the target temp.
Klipper like to have the temperature quite spot on. 10°C is way too much deviation.

Ave you already run a PID tune?

https://www.klipper3d.org/Config_checks.html#calibrate-pid-settings

5

hmm interesting, I thought I did but maybe it didn’t save. I see what you mean about the extruder temp being higher now.

PID tune just started, let’s see if that fixes it.

1 Like
6

PID tune finished and it did fix the issue of temp being higher, but it’s still doing the same waiting behaviour

klippy(1).log (2.5 MB)

edit, ok so it sat there for another 2-3 minutes and THEN it started to print. But it’s strange because it did sit at the correct temp for the entire time.

7

Maybe the the MCU goes into throttled mode.

It gets quite warm at about 60°C. Do you have a cooler for the pi?

8

no cooling, but i can easily add it. I have some heatsinks here. But if it were throttling would I receive an error on the mainsail UI? I dont see any throttle warnings.

9

What I find odd:
grafik

Your temperature readings seem very unstable. Within 1 second it jumps from 204.3 to 206.1 and back to 204.6
I could imagine that Klipper waits until it has stable readings. However I do not know how long it needs to be stable and with which tolerance.

In any case, these jumps are not normal.

10

Yeah, I was watching the temp and I don’t understand why it fluctuates like that. Any tips for better calibration? or could this be a result of a loose connection?

I am using a Bambulabs hotend. I should note I have another printer using bambu hotend on klipper and temp is rock solid.

11

Hard to say. I doubt that this is a calibration or PID effect, as temperature cannot “jump” according to well established physics.

I’d rather believe there might be an issue with the thermistor.

1 Like
12

I replaced the thermistor, I think that was the issue. the fluctations seem more reasonable now

klippy(2).zip (843.6 KB)

1 Like
13

Did it also solve your “waiting printer problem”?

14

I tried only two prints so far after, but yes it seems better. It waits for only maybe 5-10 seconds and then starts to print.

I also added Pi Heatsink and mini fan, which brings the MCU temp to 50c while under load. Hopefully that will help any possible throttling.

1 Like
15

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