[request] Knowledgebase: Klippy's timing variables

[naikymen]

Klipper has a lot of timing variables in Klippy, and so far three of them are described: Code overview - Klipper documentation

Timing is central to Klipper, and minimal descriptions of the related variables and constants would be very helpful.

I’d like invite the wise and interested parties to comment on the timing variables in Klippy, including but not limited to:

• LOOKAHEAD_FLUSH_TIME
• flush_time, flush_timer
• MIN_KIN_TIME
• MOVE_BATCH_TIME
• SDS_CHECK_TIME
• DRIP_SEGMENT_TIME
• DRIP_TIME
• buffer_time_low, buffer_time_high, buffer_time_start
• move_flush_time
• print_time
• idle_flush_print_time
• kin_flush_delay
• kin_flush_times
• force_flush_time
• last_kin_move_time
• stall_time

This information will be very helpful for new contributors studying the source code, and is a good candidate entry for the knowledgebase category.

Best
N.

[hcet14]

I second this request.

Kind regards, hcet14

[Maas]

I’ve written a bit in my post:

Moonraker websocket to klipper, changing the size of the buffer

For future reference; Was able to solve by going into the klipper firmware directly; Through ssh on the py, ~nano ~/klippy-env/bin/python ~/klipper/klippy/toolhead.py did the trick. In the file klipper/klippy/toolhead.py There are two main settings; BUFFER_TIME (high low and start) → this determines how much seconds of future g-code is allowed to enter the buffer. And the LOOKAHEAD_FLUSH_TIME G-code is loaded in small batches, the batch size determined by time (0.25s of gcode by default) ca…

If you need more info let me know, I do not know much more than the outcome of my code implementations.

[EmperorArthur]

Might be worth it to submit a pull request with the source code documented.

It would certainly help me when reading through it, and the documentation generators can pick it up automatically in the future.