RRF 3.01-RC8/DWC 2.1.3/DSF 2.0.0: DWC state after emergency stop
-
DWC fails to reload tools, temperature chart and machine movement controls (there should be a U, V and W axis too on the screenshot) after pressing Emergency Stop. Pressing the reset button on on the D3 resolves the issue. Restarting DCS does not.
-
Thanks for your report. I have amended the title of this thread to flag it as an issue with the new release bundle.
I have reproduced it on a system running Duet 3 + RPi but I don't see it on either of my machines running in standalone mode (one Duet 2, one Duet 3).
-
I don't want to confuse issues with possible non Duet problems but I've seen the same thing on an LPC based system when using an attached SBC. It looks to me as if the config.g file is not being executed. I think this may be related to the new reset mechanism that restarts DCS on M999. If I change the setting NoTerminateOnReset (in the dsf config file) so that DCS is not restarted then things seem to work fine.
I've not investigated fully but could it be that the DCS is not running when the firmware asks it to execute config.g?
-
same issue after emergency stop with DWC 2.1.3.
-
Same issue after config.g edit > Save > Reset.
For me the machine name also defaults to "My Duet". -
@Hernicz said in RRF 3.01-RC8/DWC 2.1.3/DSF 2.0.0: DWC state after emergency stop:
Same issue after config.g edit > Save > Reset.
For me the machine name also defaults to "My Duet".Regardless of this bug, after saving config I think it would make sense for DWC to send M999 with the parameter that causes only the Duet to be reset, so that DCS is not reset.
-
@dc42 I didn't have this issue on RC5 with DSF 1.2.4. It worked like it would without SBC. A new flag for M999 might fix this but it seems to be just a shortcut.
The strange thing is after I updated my config.g and ended up with this issue I pressed emergency stop and DWC shown my custom machine name for a moment before it shown "My Duet".
So it seems like the config gets loaded but then it gets unloaded for some reason. -
@Hernicz That bug has been fixed in DSF 2.1.0, consider upgrading.
-
@chrishamm Thanks.