Timer too close only when print is finished

General Discussion
5

Hmmm, something strange, it always dies on the:
queue_digital_out oid=22 clock=445285424 on_ticks=0

Sent 99 5504.017080 5504.017080 13: seq: 1c, queue_digital_out oid=22 clock=1014871658 on_ticks=0
Dumping receive queue 100 messages
...
Receive: 99 5504.017496 5504.017080 12: seq: 1d, shutdown clock=1040419231 static_string_id=Timer too close
...
Sent 99 9953.251806 9953.251806 13: seq: 18, queue_digital_out oid=22 clock=445285424 on_ticks=0
Dumping receive queue 100 messages
Receive: 96 9953.159649 9952.943025 15: seq: 18, analog_in_state oid=18 next_clock=563659008 value=29975
Receive: 97 9953.169607 9952.943025 15: seq: 18, analog_in_state oid=19 next_clock=568859008 value=30702
Receive: 98 9953.229677 9952.943025 15: seq: 18, analog_in_state oid=25 next_clock=600059008 value=27446
Receive: 99 9953.252281 9953.251806 12: seq: 19, shutdown clock=459527199 static_string_id=Timer too close

(I suspect it is a fan, because there is not a lot of such cmds in the queue, and the last one is: queue_digital_out oid=22 clock=1039342246 on_ticks=1)

Something from this:

[gcode_macro _END_PRINT]
gcode = 
	G91
	G1 Z10
	G1 E-5 F3000
	
	G90
	G1 X0 Y0 F5000
	
	M84
	M106 S0
	M104 S0
	M140 S0
	SET_FAN_SPEED FAN=exhaust_fan SPEED=0.0
	
	_SET_FLAP_ENABLED ENABLED=0

Does that.

Probably it is one of the fans.

This sounds quite strange.

If you can reproduce this reliably (I suspect you don’t have to really print something, just dummy print and then end macro).
You can try to perform the: Klipper Versioning, Downgrading, and Bisecting

To find where it has been broken.

It is possible that recent refactoring introduced a bug with Pin PWM scheduling.

Thanks.