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

    No output from G32 on DSF 1.2.4 / DWC 2.07

    Scheduled Pinned Locked Moved
    Duet Web Control
    14
    64
    2.9k
    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.
    • chas2706undefined
      chas2706
      last edited by

      @chas2706 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

      Hi, I mentioned in another post that since upgrading to RRF3.01_RC1 I too do not get any output from G32. I have Duet3 with raspberry pi.

      @dc42 Do you have any suggestions.
      Also I noticed that when I enter any command in the console it does not work first time I have to enter twice! I am running RRF3.0.2_RC1 DWC2.0.7 DSF1.2.4.0 on Duet 3 board with SBC.

      dc42undefined 1 Reply Last reply Reply Quote 0
      • Danalundefined
        Danal
        last edited by

        Yeah, I don't see anything in those logs that looks wrong.

        I am well and truly stumped. The "must send twice" is equally weird.

        Delta / Kossel printer fanatic

        1 Reply Last reply Reply Quote 0
        • chas2706undefined
          chas2706
          last edited by

          @Danal said in No output from G32 on DSF 1.2.4 / DWC 2.07:

          Yeah, I don't see anything in those logs that looks wrong.

          Yes it is both weird and annoying.
          The bed levelling must be working because my prints are still good but its not right that you get no feedback.
          Do you think that the two issues may be linked?
          i.e. there's no bed deviation result because it was only reported once?

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

            @chas2706 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

            @chas2706 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

            Hi, I mentioned in another post that since upgrading to RRF3.01_RC1 I too do not get any output from G32. I have Duet3 with raspberry pi.

            @dc42 Do you have any suggestions.
            Also I noticed that when I enter any command in the console it does not work first time I have to enter twice! I am running RRF3.0.2_RC1 DWC2.0.7 DSF1.2.4.0 on Duet 3 board with SBC.

            One for @chrishamm I think, because in standalone mode I don't see any of these issues, and neither have I seen any reports of them. So I suspect it is a DSF issue, or a DSF/RRF interaction.

            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
            • chas2706undefined
              chas2706
              last edited by

              @dc42 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

              One for @chrishamm I think, because in standalone mode I don't see any of these issues, and neither have I seen any reports of them. So I suspect it is a DSF issue, or a DSF/RRF interaction.

              dc42 How do I roll back to Duet Software Framework 1.2.3.0 so I can go back to RRF3.0.1_beta2 and DWC2.06 because it was definitely working on that firmware setup.

              Danalundefined 1 Reply Last reply Reply Quote 0
              • richardmckennaundefined
                richardmckenna
                last edited by

                I’m not seeing any output from G32 either.

                Duet3+Pi 3B+
                Duet Web Control: 2.0.7
                Board: Duet 3 MB6HC (MB6HC)
                DSF Version: 1.2.4.0
                Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0 (2020-01-03b3)

                1 Reply Last reply Reply Quote 0
                • Danalundefined
                  Danal @chas2706
                  last edited by

                  @chas2706 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

                  @dc42 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

                  One for @chrishamm I think, because in standalone mode I don't see any of these issues, and neither have I seen any reports of them. So I suspect it is a DSF issue, or a DSF/RRF interaction.

                  dc42 How do I roll back to Duet Software Framework 1.2.3.0 so I can go back to RRF3.0.1_beta2 and DWC2.06 because it was definitely working on that firmware setup.

                  sudo apt-get install duetsoftwareframework=1.2.3.0

                  Delta / Kossel printer fanatic

                  1 Reply Last reply Reply Quote 0
                  • chas2706undefined
                    chas2706
                    last edited by

                    @Danal said in No output from G32 on DSF 1.2.4 / DWC 2.07:

                    sudo apt-get install duetsoftwareframework=1.2.3.0

                    Thanks for that.

                    mvieleersundefined 1 Reply Last reply Reply Quote 0
                    • mvieleersundefined
                      mvieleers @Danal
                      last edited by

                      @Danal Just to be sure: this is my bed.g logs for completeness. Don't believe there's much to go on in there. (by the way, I had upgraded to 3.01-RC2 before.)
                      duetcontrolserver:
                      Feb 18 20:30:45 duet3 DuetControlServer[352]: [info] Executing nested macro file bed.g on channel HTTP
                      Feb 18 20:30:46 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
                      Feb 18 20:30:53 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
                      Feb 18 20:30:53 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:30:54 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
                      Feb 18 20:30:54 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
                      Feb 18 20:31:01 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
                      Feb 18 20:31:01 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:02 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
                      Feb 18 20:31:02 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:02 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file retractprobe.g
                      Feb 18 20:31:04 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
                      Feb 18 20:31:11 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
                      Feb 18 20:31:11 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:12 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
                      Feb 18 20:31:12 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
                      Feb 18 20:31:19 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
                      Feb 18 20:31:19 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:20 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
                      Feb 18 20:31:20 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:20 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file retractprobe.g
                      Feb 18 20:31:23 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
                      Feb 18 20:31:30 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
                      Feb 18 20:31:30 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:31 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
                      Feb 18 20:31:31 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
                      Feb 18 20:31:38 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
                      Feb 18 20:31:38 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:39 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
                      Feb 18 20:31:39 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:39 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file retractprobe.g
                      Feb 18 20:31:42 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
                      Feb 18 20:31:49 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
                      Feb 18 20:31:49 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:50 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
                      Feb 18 20:31:50 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
                      Feb 18 20:31:57 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
                      Feb 18 20:31:57 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:58 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
                      Feb 18 20:31:58 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
                      Feb 18 20:31:58 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file retractprobe.g
                      Feb 18 20:31:58 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file bed.g

                      duetwebserver:
                      Feb 18 20:30:44 duet3 DuetWebServer[463]: info: DuetWebServer.Controllers.MachineController[0]
                      Feb 18 20:30:44 duet3 DuetWebServer[463]: [DoCode] Executing code 'G32'
                      Feb 18 20:31:58 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
                      Feb 18 20:31:58 duet3 DuetWebServer[463]: Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
                      Feb 18 20:31:58 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
                      Feb 18 20:31:58 duet3 DuetWebServer[463]: Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 73655.5472ms
                      Feb 18 20:31:58 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
                      Feb 18 20:31:58 duet3 DuetWebServer[463]: Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
                      Feb 18 20:31:58 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
                      Feb 18 20:31:58 duet3 DuetWebServer[463]: Request finished in 73656.4125ms 200 text/plain; charset=utf-8
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: Request starting HTTP/1.1 POST http://duet3.local/machine/code text/plain;charset=UTF-8 3
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[4]
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: CORS policy execution successful.
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: Executing endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: Route matched with {action = "DoCode", controller = "Machine"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] DoCode() on controller DuetWebServer.Controllers.MachineController (DuetWebServer).
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: info: DuetWebServer.Controllers.MachineController[0]
                      Feb 18 20:33:05 duet3 DuetWebServer[463]: [DoCode] Executing code 'G32'
                      Feb 18 20:34:19 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
                      Feb 18 20:34:19 duet3 DuetWebServer[463]: Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
                      Feb 18 20:34:19 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
                      Feb 18 20:34:19 duet3 DuetWebServer[463]: Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 73870.6134ms
                      Feb 18 20:34:19 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
                      Feb 18 20:34:19 duet3 DuetWebServer[463]: Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
                      Feb 18 20:34:19 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
                      Feb 18 20:34:19 duet3 DuetWebServer[463]: Request finished in 73872.5775ms 200 text/plain; charset=utf-8

                      1 Reply Last reply Reply Quote 0
                      • mvieleersundefined
                        mvieleers @chas2706
                        last edited by

                        @chas2706 Please note, to make this work, you cannot be on a release of Reprapfirmware that requires DSF 1.2.4.

                        1 Reply Last reply Reply Quote 0
                        • gtj0undefined
                          gtj0
                          last edited by

                          There are issues with the latest DSF and getting responses sent to the correct (or any) location. For instance, if I run G32 in one instance of the UI the response used to show up on all instances connected but now it seems to show up only on the one that issued the command (but not always even there).

                          I started looking in the source for the issue to see if I can fix it myself but haven't really had time to dig into it as deep seems to be needed.

                          1 Reply Last reply Reply Quote 0
                          • Danalundefined
                            Danal @Danal
                            last edited by

                            @Danal said in No output from G32 on DSF 1.2.4 / DWC 2.07:

                            After an apt-get sequence, I still get it just fine.
                            Duet Web Control 2.0.7
                            Board: Duet 3 MB6HC (MB6HC)
                            DSF Version: 1.2.4.0
                            Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0 (2020-01-03b3)
                            Chrome browser, if that makes any difference.
                            2/15/2020, 7:14:53 PM G32
                            Leadscrew adjustments made: 0.118 0.120 0.109, points used 3, deviation before 0.115 after 0.000

                            Ok, this is weird. Right in the middle of working on some other things, I stopped getting responses to G32.

                            I had them earlier. I ran three G32 and watched the actual result get better and better. Later in the evening, suddenly, no output. Between those two, several e-stops (I'm working on probes that jam). Pi was up all the time.
                            Certainly no release changes, etc.

                            So far, I haven't been able to get it back.

                            • Reboot of Pi, still no output.
                            • E-Stop of firmware, still no output.
                            • Power Cycle, still no output.

                            That last one baffles me to no end. Power cycle?

                            Delta / Kossel printer fanatic

                            mvieleersundefined 1 Reply Last reply Reply Quote 0
                            • mvieleersundefined
                              mvieleers @Danal
                              last edited by

                              @Danal Well that's strange behaviour. I'm losing the console output immediately, as soon as DSF 1.2.4.0 is installed.
                              I really am confident it is the DSF, as I am now running on standalone mode with same firmware and same DWC version without issues.

                              Hopefully @chrishamm will get around to looking into this.

                              1 Reply Last reply Reply Quote 0
                              • stonewaterundefined
                                stonewater
                                last edited by

                                I'm glad it's not just me. This started as soon as I moved to Duet 3 h/w. If I press the level button on the panel due - then I get the expected output in both console and web interface via the pop up.

                                If I run G32 via the web console then the printer does run the macro as expected but I don't get any output.

                                Did anyone find a solution to this?

                                1 Reply Last reply Reply Quote 0
                                • chas2706undefined
                                  chas2706
                                  last edited by

                                  @chas2706 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

                                  @Danal said in No output from G32 on DSF 1.2.4 / DWC 2.07:

                                  Yeah, I don't see anything in those logs that looks wrong.

                                  Yes it is both weird and annoying.
                                  The bed levelling must be working because my prints are still good but its not right that you get no feedback.
                                  Do you think that the two issues may be linked?
                                  i.e. there's no bed deviation result because it was only reported once?

                                  I am still experiencing these problems on the latest build.
                                  The G32 reporting mostly does not work although on odd rare occasions it does! and the fact that I still have to enter gcode commands twice in the console before they work is really annoying.

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

                                    As a temporary workaround until this is fixed, you can display the G32 deviation by running M409 K"move.calibration". tested using RRF 3.01-RC4 (recommended DSF version for this release is 1.2.5).

                                    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 1
                                    • chas2706undefined
                                      chas2706
                                      last edited by

                                      @dc42 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

                                      As a temporary workaround until this is fixed, you can display the G32 deviation by running M409 K"move.calibration". tested using RRF 3.01-RC4 (recommended DSF version for this release is 1.2.5).

                                      Ok thanks for that.

                                      1 Reply Last reply Reply Quote 0
                                      • richardmckennaundefined
                                        richardmckenna
                                        last edited by

                                        Has development stopped on DSF? Not seen any commits on the repo since January. Is @chrishamm ok?

                                        Danalundefined 1 Reply Last reply Reply Quote 0
                                        • Danalundefined
                                          Danal @richardmckenna
                                          last edited by Danal

                                          @richardmckenna said in No output from G32 on DSF 1.2.4 / DWC 2.07:

                                          Has development stopped on DSF? Not seen any commits on the repo since January. Is @chrishamm ok?

                                          The Dev branch of https://github.com/chrishamm/DuetSoftwareFramework contains commits by chrishamm made 7 days ago. They were not packaged into a release on github; however, they do seem to have been used to build the 1.2.5 DSF release that is currently on the package server.

                                          So he is around somewhere.

                                          At the same time, may I make a plea for Duet to be more transparent about the roadmap? DC42 is doing an excellent job of communicating "next steps" for the firmware on the boards. However, the D3+Pi roadmap still seems vague.

                                          Delta / Kossel printer fanatic

                                          1 Reply Last reply Reply Quote 2
                                          • chrishammundefined
                                            chrishamm administrators
                                            last edited by

                                            Hi everyone, I am sorry for being unavailable for so long. Primarily this is because I've been designing a new machine which will be based on the Duet 3. That will allow me to replicate different operation modes and to replicate certain configurations and/or issues that have been very tricky to test.

                                            As you may suspect I have prepared a new DWC version, which adopts David's new object model from RRF and likewise DSF has been improved, too. I'll release a new DSF version later this week which will also feature conditional G-code. Once these new versions are out, I'll be happy to provide support again.

                                            Again, sorry for the inconvenience!

                                            Duet software engineer

                                            Danalundefined mvieleersundefined 3 Replies Last reply Reply Quote 3
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA