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

Duet Web Control 2.1.2 released

Scheduled Pinned Locked Moved
Duet Web Control
12
46
1.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.
  • undefined
    ChrisP
    last edited by 15 Apr 2020, 14:17

    @chrishamm @dc42
    Thanks both for looking into this.

    I'll have a go at running in standalone later but for now, as per @dc42 original request. Here are two further logs with details of what state things show.

    • Immediately after a print finished, M701 DWC and filaments.csv all correctly show that filament is loaded (I'm certain that at the start of the print DWC and .csv were wrong, but I didn't see when it changed - presumably during the print, but I don't know why).
    • I then used the drop down option on DWC to unload the filament and immediately copied the log: 4.txt
    • At this point DWC incorrectly shows filament loaded, M701 is correct and filaments.csv is incorrect
    • Since M701 was showing correctly that there was no filament loaded, I used it again with the S parameter to manually load the next filament. Immediately after pressing enter on this in the console i noticed DWC corrected itself to showed no filament loaded checking .csv also showed that had now updated - I did this while waiting for heat up so at this point the new filament hadn't loaded.
    • After filament load, DWC incorrectly shows filament not loaded, M701 is correct again and .csv is incorrect. HEre is the log immediately after the load: 5.txt
    • Started the next print with DWC showing no filament loaded, but something clearly knows it is at it used the filaments config file during the print's start code.

    Hope this helps. As i said, I'll try standalone later, but if there's anything else you want me to try, just let me know.

    1 Reply Last reply Reply Quote 0
    • undefined
      garyd9 @chrishamm
      last edited by 15 Apr 2020, 14:22

      The issue of fans not working properly in DWC when the fan was configured with an "X" parameter is confirmed resolved with DWC 2.1.2. Thank you.

      "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

      1 Reply Last reply Reply Quote 0
      • undefined
        jay_s_uk
        last edited by 15 Apr 2020, 16:11

        @chrishamm

        Simulation times for me aren't getting shown in the jobs list once the simulation is completed. This was on a duet 3 with SBC running RC7 and DSF 1.3.2

        I haven't tried on a duet 2 yet.

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        undefined undefined 2 Replies Last reply 15 Apr 2020, 16:15 Reply Quote 0
        • undefined
          droftarts administrators @jay_s_uk
          last edited by 15 Apr 2020, 16:15

          @jay_s_uk Simulation times show for me on Duet 2 Wifi and Duet 2 Maestro (RRF 3.01-RC7, DWC 2.1.2).

          Ian

          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

          1 Reply Last reply Reply Quote 0
          • undefined
            garyd9
            last edited by 16 Apr 2020, 00:59

            @chrishamm

            DWC 2.1.2 running in Chrome under Win10 w/ Duet3 (standalone) 3.0.1 RC7:

            I'm finding at times that the "last layer time" isn't being updated on the status page under some conditions.

            One place I think replicates this is if the computer running DWC goes into standby, and then I wake the machine while I print is in progress. The status page layer times runs "catchup" for a second, but the "last layer time" gets stuck at some time that seems to be similar to the "Job Duration" time.

            At that point, the "current layer time" updates as expected, and goes back to zero on layer changes, but the "last layer time" never changes.

            The "layer chart" also appears to get out of whack.

            (I'm really hoping you can replicate this, because I'm at a loss for words to describe it properly.)

            If I refresh the browser window, everything starts working again.

            "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

            undefined 1 Reply Last reply 16 Apr 2020, 08:45 Reply Quote 0
            • undefined
              chrishamm administrators @garyd9
              last edited by 16 Apr 2020, 08:45

              @garyd9 Thanks for reporting this, I suspect one place in DWC2 that could cause this behaviour. Can you please test this new build and let me know if the problem is gone? https://www.dropbox.com/s/znzevo862ny7kr6/DuetWebControl-SD.zip?dl=0

              Duet software engineer

              undefined 2 Replies Last reply 16 Apr 2020, 13:02 Reply Quote 0
              • undefined
                dc42 administrators @jay_s_uk
                last edited by dc42 16 Apr 2020, 08:50

                @jay_s_uk said in Duet Web Control 2.1.2 released:

                @chrishamm

                Simulation times for me aren't getting shown in the jobs list once the simulation is completed. This was on a duet 3 with SBC running RC7 and DSF 1.3.2

                I believe @chrishamm said it's a known issue that DSF doesn't yet write the simulated time to the end of the GCode file.

                EDIT: it's listed at https://github.com/chrishamm/DuetSoftwareFramework/tree/dev#known-issues.

                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

                undefined 1 Reply Last reply 16 Apr 2020, 10:37 Reply Quote 0
                • undefined
                  jay_s_uk @dc42
                  last edited by 16 Apr 2020, 10:37

                  @dc42

                  Thanks for that. Didn't realise there was a separate known issues list.
                  It would be helpful if a central list was maintained.

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  undefined 1 Reply Last reply 16 Apr 2020, 11:08 Reply Quote 1
                  • undefined
                    dc42 administrators @jay_s_uk
                    last edited by 16 Apr 2020, 11:08

                    @jay_s_uk said in Duet Web Control 2.1.2 released:

                    @dc42

                    Thanks for that. Didn't realise there was a separate known issues list.
                    It would be helpful if a central list was maintained.

                    Yes it is a bit hard to find. We're going to standardise release documentation so that known issues are always easy to find.

                    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
                    • undefined
                      garyd9 @chrishamm
                      last edited by 16 Apr 2020, 13:02

                      @chrishamm said in Duet Web Control 2.1.2 released:

                      @garyd9 Thanks for reporting this, I suspect one place in DWC2 that could cause this behaviour. Can you please test this new build and let me know if the problem is gone?

                      Uploaded to my duet3. Will try to keep an eye out for the issue and ping back.

                      "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

                      1 Reply Last reply Reply Quote 1
                      • undefined
                        ChrisP @dc42
                        last edited by 16 Apr 2020, 14:48

                        @dc42 said in Duet Web Control 2.1.2 released:

                        Thanks. As you have been resetting DCS in this sequence, I'm not clear whether this is an issue with RRF after all. You could try to replicate the problem in standalone mode if you wish; otherwise I'll wait to see what @chrishamm says.

                        So having just tried this in standalone mode, I cannot find a way to replicate the issue this way.

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          c310
                          last edited by 16 Apr 2020, 15:18

                          what is the way to add duet driver temperature to the chart?

                          this successfully adds MCU

                          M308 S2 Y"mcu-temp" A"CPU" ; CPU temp sensor

                          but this does nothing

                          M308 S3 Y"drivers" A"drivers" ; drivers temp sensor

                          i tried M308 S21 Y"drivers" A"Duet_drv" too with no luck

                          how to get drivers temperature visible?

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            Danal
                            last edited by 16 Apr 2020, 17:54

                            If I recall, TMC drivers don't actually report temperature. They just report OK vs Nearly too hot vs Too Hot. (or conceptually similar).

                            So they can't be graphed. (usefully)

                            Delta / Kossel printer fanatic

                            ? 1 Reply Last reply 16 Apr 2020, 17:58 Reply Quote 0
                            • ?
                              A Former User @Danal
                              last edited by 16 Apr 2020, 17:58

                              So they can't be graphed. (usefully)

                              true story, you'll just get 0C, 100C and 150C but it'll be in the extra tab or what its caled.

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                garyd9 @chrishamm
                                last edited by 16 Apr 2020, 19:25

                                @chrishamm said in Duet Web Control 2.1.2 released:

                                @garyd9 Thanks for reporting this, I suspect one place in DWC2 that could cause this behaviour. Can you please test this new build and let me know if the problem is gone? https://www.dropbox.com/s/znzevo862ny7kr6/DuetWebControl-SD.zip?dl=0

                                While I haven't (yet) replicated the original reported problem, here's a new one with the DWC drop your dropbox. In the image below, notice the "current layer time" of 0. (It's currently printing the first layer, so the "last layer time" is shown as I'd expect.)

                                Here's also the output of a M409 query. It's possible this is a case of RRF 3.0.1 RC7 reporting bad data in the object model. If so, please forward the issue to dc42. (layerTime is 0 in the json)

                                M409 K"job"
                                {"key":"job","flags":"","result":{"build":{"currentObject":6,"m486Names":false,"m486Numbers":false,"objects":[{"cancelled":false,"name":"Object 2","x":[-94.4950027,55.1020012],"y":[0.0820000,24.5779991]},{"cancelled":false,"name":"Object 4","x":[-58.9290009,90.6679993],"y":[18.8269997,43.3219986]},{"cancelled":false,"name":"Object 6","x":[-86.8740005,62.7229996],"y":[42.3479996,66.8420029]},{"cancelled":false,"name":"Object 6(1)","x":[-74.8000031,74.7979965],"y":[67.8170013,92.3130035]},{"cancelled":false,"name":"Object 1","x":[-54.9140015,94.6839981],"y":[-25.0049992,-0.5110000]},{"cancelled":false,"name":"Object 3","x":[-89.4520035,60.1459999],"y":[-43.9399986,-19.4440002]},{"cancelled":false,"name":"Object 5","x":[-29.9820004,55.7639999],"y":[-63.2210007,-52.2210007]}]},"duration":1682,"file":{"filament":[7095.3],"fileName":"0:/gcodes/PETG/No Fan/8x Surgical_Mask_Ear_Strain_Relief (faster).gcode","firstLayerHeight":0.20,"generatedBy":"Cura_SteamEngine 4.5.0","height":1.60,"lastModified":"2020-04-15T12:11:50","layerHeight":0.20,"numLayers":8,"printTime":7591,"simulatedTime":8855,"size":4515762},"filePosition":526940,"firstLayerDuration":1682,"lastFileName":"0:/gcodes/PETG/No Fan/8x Surgical_Mask_Ear_Strain_Relief (faster).gcode","layer":1,"layerTime":0,"timesLeft":{"filament":11079,"file":12736},"warmUpDuration":0}}

                                1c3a3120-4d3e-4a8f-ad2e-e27c6489614f-image.png

                                "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

                                undefined 1 Reply Last reply 16 Apr 2020, 19:48 Reply Quote 0
                                • undefined
                                  dc42 administrators @garyd9
                                  last edited by dc42 16 Apr 2020, 19:48

                                  @garyd9 said in Duet Web Control 2.1.2 released:

                                  here's a new one with the DWC drop your dropbox. In the image below, notice the "current layer time" of 0. (It's currently printing the first layer, so the "last layer time" is shown as I'd expect.)
                                  Here's also the output of a M409 query. It's possible this is a case of RRF 3.0.1 RC7 reporting bad data in the object model. If so, please forward the issue to dc42. (layerTime is 0 in the json)

                                  Thanks for reporting this, it's a bug in RRF. Should be fixed in the internal build at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

                                  EDIT: the fix is included in RRF 3.01-RC8.

                                  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
                                  • undefined
                                    smoki3
                                    last edited by 18 Apr 2020, 08:44

                                    M122 does not output anything on my Duet 2 Wifi

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      jay_s_uk
                                      last edited by 18 Apr 2020, 08:54

                                      @smoki3

                                      Try DWC 2.1.3 which was released yesterday

                                      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                      1 Reply Last reply Reply Quote 0
                                      • undefined
                                        dc42 administrators
                                        last edited by 18 Apr 2020, 09:11

                                        I'm locking this thread because DWC 2.1.3 is now available.

                                        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
                                        37 out of 46
                                        • First post
                                          37/46
                                          Last post
                                        Unless otherwise noted, all forum content is licensed under CC-BY-SA