How to interpret Timer too close error message dump

Hi @koconnor ,
thanks for the pointer. I see that the script in fact rearranges the log entries (attached) from the earliest to the latest, which helps a little… but I still miss some foundational knowledge to be able to find a lead through the log. Here my questions:

  • does each line corresponds to a command processed by the MCU? or the host?
  • I see 3 types of entries, sent, receive, stats… who is the reporter there? in other words who is the sender of a “sent”? who is the receiver of a “receive”?
  • each command seems to have 2 time tags? is it print time? why 2?
  • are sent/receive matched by looking at the seq: number?

finally and most importantly, how close is Too close? or if you will, which 2 timetags should I compare and how much the time difference should be?

thanks for your valuable help

cheers,
stef

klippy-dev.gcode00146.log (134 Bytes)
klippy-dev.shutdown00146.log (42.6 KB)