@dc42 I wondered, is it possible that the error is not exactly an error? I mean, when this disconnection-reconnection routine starts, is the number of interactions it performs too high and too concentrated? What if we reduced the speed of reconnection attempts and the number of attempts?

Hello there! I would like to use the stallguard of Z axis in order to calculate with a macro the offset of the probe (super pinda). The problem is that the macro doesn't allow to use variables, and so that become a bit difficult. I won't change the endstop mechanism and i wanna use the super pinda for mesh level and homing, i just wanna use a macro in this way, go homing and then down untill the probe detect the plate, after that continue slowly untill the stallguard hit gently the plate and return the value inspected (so later you can use the G31 command). I would like to have a macro like this, becouse i change plate continously, and a macro that helps me with the z offset would be pretty nice. Any suggestion on how i can do without using variables?

@Exerqtor I had the same errors with 3.4.5 - 3.4.6 and 3.5 Rc 1 with a duet 2 wifi.
I never had this kind of errors, it started to happen when i used a smartphone as a router. I suspected from the beginning, that the error was caused due to the continuous connect/reconnect. I "solved" (it is a workaround not a fix) using a PC as an Hotspot instead the phone and the crash never happened again. Later i inspected a bit, and with almost every phone or pad i used as an hotspot will cause connection-disconnection-reconnection continously and crashes.