toolhead: Don't report buffer_time stat during homing
The buffer_time info is misleading during a homing operation - just report zero instead. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
parent
503891cd0e
commit
e1919e3731
|
@ -461,6 +461,8 @@ class ToolHead:
|
||||||
m.check_active(self.print_time, eventtime)
|
m.check_active(self.print_time, eventtime)
|
||||||
buffer_time = self.print_time - self.mcu.estimated_print_time(eventtime)
|
buffer_time = self.print_time - self.mcu.estimated_print_time(eventtime)
|
||||||
is_active = buffer_time > -60. or not self.special_queuing_state
|
is_active = buffer_time > -60. or not self.special_queuing_state
|
||||||
|
if self.special_queuing_state == "Drip":
|
||||||
|
buffer_time = 0.
|
||||||
return is_active, "print_time=%.3f buffer_time=%.3f print_stall=%d" % (
|
return is_active, "print_time=%.3f buffer_time=%.3f print_stall=%d" % (
|
||||||
self.print_time, max(buffer_time, 0.), self.print_stall)
|
self.print_time, max(buffer_time, 0.), self.print_stall)
|
||||||
def check_busy(self, eventtime):
|
def check_busy(self, eventtime):
|
||||||
|
|
Loading…
Reference in New Issue