Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    RRF 3.01-RC8/DWC 2.1.3/DSF 2.0.0: DWC state after emergency stop

    Scheduled Pinned Locked Moved
    Beta Firmware
    6
    9
    467
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ChrisPundefined
      ChrisP
      last edited by dc42

      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.
      2020-04-17.png

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by dc42

        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).

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • gloomyandyundefined
          gloomyandy
          last edited by

          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?

          1 Reply Last reply Reply Quote 0
          • tobias_munichundefined
            tobias_munich
            last edited by

            same issue after emergency stop with DWC 2.1.3.

            Hypercube-Evolution, Dual-Z, Nimble v2, Orion Piezo
            Duet3, DuetWifi, Raspberry Pi 4, 7 inch HDMI Display, Panel-Due
            Firmware: RepRapFirmware for Duet 3 MB6HC 'always the latest release'

            1 Reply Last reply Reply Quote 0
            • Herniczundefined
              Hernicz
              last edited by

              Same issue after config.g edit > Save > Reset.
              For me the machine name also defaults to "My Duet".

              There are known knowns and known unknowns, things we know that we don't know. But there are also unknown unknowns.

              dc42undefined 1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @Hernicz
                last edited by

                @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.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                Herniczundefined 1 Reply Last reply Reply Quote 0
                • Herniczundefined
                  Hernicz @dc42
                  last edited by

                  @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.

                  There are known knowns and known unknowns, things we know that we don't know. But there are also unknown unknowns.

                  chrishammundefined 1 Reply Last reply Reply Quote 0
                  • chrishammundefined
                    chrishamm administrators @Hernicz
                    last edited by

                    @Hernicz That bug has been fixed in DSF 2.1.0, consider upgrading.

                    Duet software engineer

                    Herniczundefined 1 Reply Last reply Reply Quote 0
                    • Herniczundefined
                      Hernicz @chrishamm
                      last edited by

                      @chrishamm Thanks.

                      There are known knowns and known unknowns, things we know that we don't know. But there are also unknown unknowns.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post
                      Unless otherwise noted, all forum content is licensed under CC-BY-SA