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

    Firmware bundle 3.3beta2 released

    Scheduled Pinned Locked Moved
    Beta Firmware
    19
    49
    4.2k
    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.
    • Stephen6309undefined
      Stephen6309 @dc42
      last edited by

      @dc42 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.3beta2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-03-10 13:39:39
      Duet TOOL1LC firmware version 3.3beta2 (2021-03-10 10:06:22)
      Duet Web Control 3.3.0-b2
      PrusaSlicer 2.3.0 + win64

      Layer Chart, layer count and Time estimates don't update.

      droftartsundefined 1 Reply Last reply Reply Quote 0
      • droftartsundefined
        droftarts administrators @Stephen6309
        last edited by

        @Stephen6309 said in Firmware bundle 3.3beta2 released:

        @dc42 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.3beta2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-03-10 13:39:39
        Duet TOOL1LC firmware version 3.3beta2 (2021-03-10 10:06:22)
        Duet Web Control 3.3.0-b2
        PrusaSlicer 2.3.0 + win64

        Layer Chart, layer count and Time estimates don't update.

        Are you using SBC or stand alone mode? see https://github.com/Duet3D/DuetWebControl/releases/tag/v3.3-b2

        Rewrote backend for layers chart in standalone mode

        I don't think the SBC version has been updated yet, as there have been some changes in the firmware related to layer height since 3.2.2.

        Layer chart and layer count work for me as job progresses, in stand alone. However, estimations based on layer time (which was always the most inaccurate estimate), and the parsing of the file to count how many layers there are before printing, have been removed, because it was requiring more and more effort and memory to keep up with the ever-changing notation in slicers.

        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

        Stephen6309undefined 1 Reply Last reply Reply Quote 0
        • Stephen6309undefined
          Stephen6309 @droftarts
          last edited by

          @droftarts Yes, with PI 4, missed that. Update: time estimates are working on the current print. Layer count is the on the line above the layer chart, that shows the file progress.

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

            In 3.3beta2 the layer count and current layer time are only available if the GCode file being printed includes layer number comments.

            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

            DaveAundefined 1 Reply Last reply Reply Quote 0
            • Stephen6309undefined
              Stephen6309
              last edited by

              Duet 3 Mini, updated to 3.3beta3. No updating in Layer chart or file completion.

              1 Reply Last reply Reply Quote 0
              • DaveAundefined
                DaveA @dc42
                last edited by

                @dc42 My current file is printing without updating the layer chart. The file, from Simplify3D, has an entry such as ; layer 14, Z = 2.800 for every layer. Is there something else needed?

                DaveAundefined 1 Reply Last reply Reply Quote 0
                • DaveAundefined
                  DaveA @DaveA
                  last edited by

                  Something strange is happening. As I was typing my previous post I was seeing that the Layer Chart was not updating and the printer was on layer 7. I just checked back again and the layer chart has been filled from layer 2 with 0 time up to layer 10. Not sure what happened to layer 1.

                  Also noticed that the button option to show all layers or the lastnn is gone. Is this intentional?

                  droftartsundefined 1 Reply Last reply Reply Quote 0
                  • droftartsundefined
                    droftarts administrators @DaveA
                    last edited by

                    @Stephen6309 @DaveA Can you check you have updated DWC to Duet Web Control 3.3.0-b2? I had this when I was running previous RRF 3.3betas with DWC 3.2.2, but should be fixed in standalone DWC (I think not DWC SBC version, though). I got nice graphs from both simulation and real print.
                    Simulation:
                    Screenshot 2021-03-11 at 12.25.43.png
                    Same file, real print:
                    Screenshot 2021-03-11 at 12.54.46.png
                    These on Duet 2 Maestro (delta kinematics), Duet Web Control 3.3.0-b2 and RepRapFirmware for Duet 2 Maestro 3.3beta2 (2021-03-10)

                    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

                    DaveAundefined 1 Reply Last reply Reply Quote 0
                    • DaveAundefined
                      DaveA @droftarts
                      last edited by

                      @droftarts Settings General reports: Duet Web Control 3.3.0-b2
                      I'm going to start another print in the morning and pay closer attention.

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

                        @DaveA, if DWC isn't displaying layers you can send M409 K"job" during the print to check whether RRF knows the current layer number.

                        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
                        • tekkydaveundefined
                          tekkydave
                          last edited by tekkydave

                          RRF 3.3beta2 & DWC 3.3beta2 installed on Duet2 Wifi

                          Edit from the near-future: see my next post for the solution 😀

                          Note: I'm only testing this in simulation in case that makes a difference.

                          I'm not getting any layer counts or graph when slicing with PrusaSlicer 2.3. Works ok when tested with Cura (which I don't use anymore).
                          The PrusaSlicer gcode seems to be missing the

                          ;LAYER:0
                          

                          lines that Cura puts in.

                          and seems to have this at every layer change instead

                          ;LAYER_CHANGE
                          ;Z:0.3
                          ;HEIGHT:0.3
                          

                          These are my firmware settings in PrusaSlicer

                          Screenshot from 2021-03-12 10-33-24.png

                          Have I missed something on the PrusaSlicer config side or does it not support the necessary comments (yet).

                          ~ tekkydave ~
                          D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                          FreeCAD, PrusaSlicer

                          1 Reply Last reply Reply Quote 0
                          • tekkydaveundefined
                            tekkydave
                            last edited by

                            A simple workround for PrusaSlicer is to add a custom gcode to the Printer Settings:

                            Screenshot from 2021-03-12 10-52-33.png

                            ~ tekkydave ~
                            D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                            FreeCAD, PrusaSlicer

                            Stephen6309undefined 1 Reply Last reply Reply Quote 3
                            • droftartsundefined
                              droftarts administrators @DaveA
                              last edited by

                              @DaveA @Stephen6309 Apologies, I realise that I was running gcode sliced with Cura, which puts in:

                              ;LAYER_COUNT:125
                              ;LAYER:0
                              

                              at the first layer, and

                              ;LAYER:1
                              

                              etc at each layer change. If you use @tekkydave 's work around above for PrusaSlicer (and any other slicer that omits this) the layer count and chart should work correctly.

                              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 1
                              • deckingmanundefined
                                deckingman
                                last edited by deckingman

                                Just to add that the "before layer change" G-code section for Slic3R and it's variants like the Prusa edition, is under "Printer Settings". So if you have multiple printer profiles as I have (15 in my case) then you need to add that layer change g-code to all of them.

                                Oh and of course, if you want layer times and stats to show up on any parts that you've already sliced, then you'll have to re-slice them. Just sayin'....

                                Ian
                                https://somei3deas.wordpress.com/
                                https://www.youtube.com/@deckingman

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

                                  To complicate things further, some slicers (e.g. Cura, Ideamaker) count the first layer as 0, others (e.g. S3D) start from 1. Currently, if RRF sees ;LAYER n then it will assume layers start from zero and add 1 to n before storing it in the OM). If RRF sees ;layer n then it will assume that n starts from 1.

                                  I don't know whether PrusaSlicer starts from 0 or 1.

                                  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

                                  deckingmanundefined tekkydaveundefined oliofundefined 3 Replies Last reply Reply Quote 0
                                  • deckingmanundefined
                                    deckingman @dc42
                                    last edited by deckingman

                                    @dc42 said in Firmware bundle 3.3beta2 released:

                                    ............ I don't know whether PrusaSlicer starts from 0 or 1.

                                    I just tried it and can say that Prusa Edition starts with the first layer being 0.

                                    Edit. The "LAYER" is shown as upper case in the gcode file

                                    Ian
                                    https://somei3deas.wordpress.com/
                                    https://www.youtube.com/@deckingman

                                    1 Reply Last reply Reply Quote 0
                                    • tekkydaveundefined
                                      tekkydave @dc42
                                      last edited by

                                      @dc42 that explains why I don't see a layer 0 in DWC. Confused me a bit 😕

                                      ~ tekkydave ~
                                      D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                                      FreeCAD, PrusaSlicer

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

                                        @tekkydave I will clarify it in the upgrade notes. We'll also hide the layer chart in the next version of DWC when layer data is not 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

                                        tekkydaveundefined 1 Reply Last reply Reply Quote 0
                                        • tekkydaveundefined
                                          tekkydave @dc42
                                          last edited by

                                          @dc42 said in Firmware bundle 3.3beta2 released:

                                          @tekkydave I will clarify it in the upgrade notes. We'll also hide the layer chart in the next version of DWC when layer data is not available.

                                          Yes. I had noticed the layer chart persisted until the first layer change of the next print.

                                          ~ tekkydave ~
                                          D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                                          FreeCAD, PrusaSlicer

                                          1 Reply Last reply Reply Quote 0
                                          • Egrisundefined
                                            Egris
                                            last edited by Egris

                                            Tested fw 3.3 beta 2 on my rotary delta. Has there been a change to Segments per second for this kinematic? X/Y G1 moves look like there is a very low segments per second value usesd for straight lines.

                                            With the older 3.3 version its working fine

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