Zeroing During a Cut is Laggy (H5)

[GeckoSub]

Nothing urgent, more of a curiosity.
But since I now have the machine up and running (and with scales on both X/Z) I have noticed that if I am taking a cut and want to zero an axis during the cut, there can be a lag of a few seconds before the axis zeroes and sometimes not at all. If I am not running the spindle, it happens right away.
So, I speculate that the ESP32 is "too busy" doing other stuff. I haven't yet seen it resulting in losing sync so that's good.
But I wonder if this is normal for the stock H5 FW or whether my scales are pushing things over the edge...?

I bought my scales used and even though they are the same model numbers, one of the readheads sends out 1250 pulses/mm whereas the other is "just" 500 pulses/mm. But since I installed them randomly, the 1250 one ended up on the Z. So, I could possibly swap them around to help mitigate the issue. (I don't have a motorized X-axis so the X mostly stays stationary during cuts so no pulses are being sent).

[kachurovskiy]

The slowness of touch reactions when motor is running is caused by constant updates we have to make to UI due to changing angle. You can try reducing display update interval from 50ms to 100ms in https://github.com/kachurovskiy/nanoels/blob/main/h5/h5.ino#L1547 and seeing if it offers a better balance.

Keyboard doesn't suffer from this.

[GeckoSub]

The slowness of touch reactions when motor is running is caused by constant updates we have to make to UI due to changing angle. You can try reducing display update interval from 50ms to 100ms in https://github.com/kachurovskiy/nanoels/blob/main/h5/h5.ino#L1547 and seeing if it offers a better balance.

Keyboard doesn't suffer from this.

Ah, but I read that as good news - it's not like the ESP32 is getting stressed. So, it only affects the readout - not the actually processing for the cuts being done.
I'll try the update interval change. I feel like I can easily live with a slightly less responsive RPM/Angle/Turn readout.

Thanks Max:)

[GeckoSub]

The slowness of touch reactions when motor is running is caused by constant updates we have to make to UI due to changing angle. You can try reducing display update interval from 50ms to 100ms in https://github.com/kachurovskiy/nanoels/blob/main/h5/h5.ino#L1547 and seeing if it offers a better balance.

Keyboard doesn't suffer from this.

Made the change to 100ms and WOW, so snappy now:)
I can run the spindle at max speed and feed along the Z at a high feed (more pulses/sec on the Z scale) and still, I can zero the display instantanously now.
Unless it impacts other stuff, perhaps 100ms should possibly be the new default.

Thanks:)

[GeckoSub]

Hi Max,
I noticed that you may have set the default on this matter to 100 now.
But because of a recent issue I had on my custom FW, which Gemini suggested was because whole my display update is now pretty heavy - whereas yours is still light - I am now thinking that 50ms is possibly still totally fine on the stock FW/tft.

Anyways, just wanted to mention it.