Closed TypQxQ closed 6 years ago
@TypQxQ As dc42 told me yesterday, please post your findings on https://forum.duet3d.com/ since most people are looking there for further information / discussion etc. (I have no affiliation with duet, just trying to keep my main man dc42 focused on the development of the firmware ;-) )
Configure long running commands or increase communication timeout Seems more like an octoprint related issue. Have you tried to do that in octoprint?
Thankyou, found the answer on the forum:
There is a limit on the response length for normal replies. You can use M915 D0, M915 D1 etc. to get status for individual drives.
That's why it crashes the Print function and everything in OctoPrint.
The output is getting truncated, and I suspect that Octoprint is timing out waiting for the end-of-line character. I will change the command either to require that the D parameter is present, or to use a different output method that is suitable for long responses.
I'm setting my M915 like this:
M915 X Y S8 R1 F1
M915 E S5 R1 F1
M915 Z S7 R1 F1
When I issue a M915 in "G-Code console" the output gets clipped:
I have my Duet connected to OctoPrint and issuing the same command gives me:
I'm using: Duet WiFi 1.02 or later 2.02RC2(RTOS) (2018-09-07b2)
Using the 2.01 gave e same results.