Topics created by Michel000

its running for 5 hours now and still no AJAX errors.

So im happy i can print again, but if its not fixed , im stuck with old firmware….

Unless you have installed the Duet WiFi in an enclosed space with no ventilation, or right next to your heated bed, it is unlikely to need any active cooling with motor currents up to about 1.8A. You can read the CPU temperature on the web interface, but you need to calibrate it as described in the wiki. Even if the board was overheating, it is unlikely to slow down. I think it's more likely that the Duet is receiving an abnormally high rate of interrupts from one of it input sources, such as the WiFi module.

A feature that automatically applies toolhead offsets. It sounds like G1 R2 will work if I update to t 1.19 beta. I will try that. Thanks

You should configure just fan 1 to be the thermostatic one (which it is by default anyway) and leave fan 0 as the print cooling fan. If you have 2 hot ends each with a hot end fan, either use fan 1 and 2 outputs to control them, or connect them both in parallel to fan 1 output.

Hi DC42
I took a look add the code and i think it should be something like this:

From this function:
bool GCodes::DoSingleZProbe(GCodeBuffer& gb, StringRef& reply, bool reportOnly, float heightAdjust)

Call :
float m[DRIVES];
float offs[DRIVES];
reprap.GetMove()->GetCurrentMachinePosition(m, false);
offs[Z_AXIS] = m[Z_AXIS]
Tool::SetOffset(const float offs[MAX_AXES])