alchemyEngine

@Scroey It looks like to me like it's just a problem with [calculation of the remaining time to print.](https://github.com/alchemyEngine/measure_thermal_behavior/blob/0098166fe155e64352bd6d7eef2f6a1a1760725b/measure_thermal_behavior.py#L404). Did it actually run beyond the expected completion time, or did...

Ideally this would be implemented by allowing arbitrary equations in `temp_coeff` or an optional alternative `equation` config parameter. This would need to be parsed for Z height and temperature variables....

Somehow this flew under my radar back in the summer. Sorry for that. I'd love to ditch numpy as a requirement, it's the source of most issues that have come...

> I am running into a bug where I am getting the following error after some time: > > `!! Toolhead stopped below model range` Nothing in my code throws...

That line does not appear anywhere in the Klipper code base either. It seems like it may be an issue in the probe software?

The measurement script simply sends the `MEASURE_GCODE` that you configure in the script, so if what you're using there is throwing errors then I would start be investigating that gcode....

I checked out the log and unfortunately I can't give you any new insight. As I said, the measurement script does not hook into Klipper at all, but just sends...

Hi all, sorry for the delay on my end. @garethky Really cool feature! Thank you for this, I think this functionality would be extremely beneficial to those using nozzle probes....

> Then the nozzle heats up to printing temp for the print. At that time, print time, the module is automatically compensating for the nozzle expansion. Of course, that makes...