[Bug]: Long homing moves can cause HeatTaskStuck software reset

[gloomyandy]

A long homing move that results in the total number of steps exceeding 0x7ffffff can cause the processor to reset with a HeatTaskStuck reason. See this thread: https://forum.duet3d.com/topic/37165/issue-with-szp-on-secondary-idex-toolhead and also tests run by Jay when testing a mainboard in expansion mode.

This report was created at the request of DC42. His comments:

"moves that exceed 2^31 steps will cause problems, and probably always have although the symptoms may have changed. I guess we should add a check on the move length in G0 and G1 commands."

All of the examples I have seen have been as the result of a long homing move (often on Z as this tends to have a high step/mm). I suspect that in most cases other moves will have the length limited by axis length, but perhaps this is not being applied to "special" moves. It may also be possible to hit this problem with very long extrusion moves, not sure if we currently apply any sort of limit to them.

[github-actions]

This issue has been automatically closed because it does not originate from a Duet3D administrator.
Please create a discussion on https://forum.duet3d.com first and fill out the corresponding GitHub template if the bug or feature request is acknowledged.