What would cause the console to not report data?
-
I had updated my duet3 + SBC to 3.01rc6 and when I do any command that should report back info, it doesn’t show up in the webpage. I repeatedly sent a G30 S-1 which should send back the z height it proved at, but it only shows a green bar with the command as executed but not the result. I get this with a number of commands. M122 and M115 still works to return data.
-
Have you also updated your DSF to the latest unstable? 1.3.1 I think?
-
@Nuramori There are known issues...
https://forum.duet3d.com/topic/15343/dsf-1-3-1-unstable-released -
@Phaedrux I did. I'm on the unstable branch, and I confirmed that I am on 1.3.1.
I'm not sure if it's related, but the system has emergency stopped more frequently than not ever since I moved to RC5 then RC6. I can't find a common thread to the issue of the random halt. At first I thought maybe the Pi was overheating, but I have a cooler, and as soon as it happened the last time, I checked and the temp was 38c. The temp of the cuet3 was 34c (I actively cool it.)
once I reboot everything, it will work fine, though if I reboot too soon, the Z axis refuses to home, or even move. Another reboot will free up the z axis.
The time before it halts has no time or layer correlation to anything I can find. -
DSF 1.3.1 is required for RRF 3.01-RC6 but IMHO 1.3.1 is not stable enough for anything other than testing 1.3.1.
-
Actually, you'd be better off disconnecting the Duet3 from the Pi and running the Duet3 in standalone mode.
-
I understand. I'm ok with helping provide feedback. I am conflating two issues, but the initial one is strange, where a command like G30 S-1 won't return the value I need to set the z probe. I ended up just looking at the dashboard to see the z value in the one part of the screen.
The other issue of random halting began with using RC5, so that was before RC6 and before using 1.3.1. That one is a bit more problematic.
