Inconsistent state of printer with SBC
-
@Phaedrux sure.
-
@gnydick It would be helpful to inspect the journal of DuetControlServer (
sudo journalctl -u duetcontrolserver -e, then scroll up). Can you see any unusual log entries there? If not, please share your config file and daemon.g so I can attempt to reproduce it. -
@chrishamm nothing useful in the logs and hasn't happened again.
-
@gnydick I have identified a possible cause and prepared a solution in RRF (although I believe it's unlikely to happen). If this problem occurs again, please open the JS console by pressing F12 and check potential errors in there, too.
-
@chrishamm will do. Can you describe what it is? I'm a software engineer among other things, so you can be as technical as you need.
-
@gnydick I think I could reproduce this problem today, it doesn't look like my previous idea was the cause. I have prepared fixes for 3.5-b1 and backported it to our v3.4 branch. That bug fix will be included in 3.5-b1 and 3.4.6.
At first I thought the response of an object model request could be too long which would result in endless resends of the OM request. This (yet unlikely) bug is now fixed. The other issue I found today could only occur if an OM request was sent from DCS to RRF and RRF lost connection afterwards due to a timeout. Then DSF would not invalidate the pending OM request so it could not be retried. In this scenario the UI would display "disconnected" all the time and no more updates would be processed, although the response of G/M/T-codes could still be seen in the console. That's now fixed, too.
-
@chrishamm that behavior seems exactly like what I experienced. It still interacted some, but still showed Disconnected. It was resolved by restarting duetcontrolserver. Does that match the bug you fixed, in terms of at least working as a recovery step?
-
@gnydick Yes, that's right. Emergency Stop usually restarts DCS, too.
-
@chrishamm emergency stop hasn't resolved things for me. It seems to be the frequent cause of these issues.
-
Here's another occasion. Yesterday, I noticed I could not reach the DWC, so used the PanelDue + M586 and saw the http was disabled. So I enabled it there. I then used the printer as usual.
Today, I went to use the printer and saw the screen attached after submitting a print from my slicer, but the DWC is stuck at a "Paused" state, again with no tools, sensors, etc.
Here are log files. It's actually a zip file, but it wouldn't let me upload a zip.
