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

    Firmware 2.02 Release candidate 3 now available

    Scheduled Pinned Locked Moved
    Firmware installation
    31
    104
    15.7k
    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.
    • dc42undefined
      dc42 administrators
      last edited by

      I've just released this at https://github.com/dc42/RepRapFirmware/releases/tag/2.02RC3. Highlights of this release include:

      • If a Duet WiFi running in client mode loses the connection to the access point, it retries the connection continuously
      • Fixed some serious issues with the 12864 display driver for the Duet Maestro

      There are many other improivements and bug fixes, see https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.

      If you are an experienced Duet user, please try this release and report your feedback (good or bad) in this thread. I intend this to be the final release candidate for the 2.02 release unless any major issues are found in it.

      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

      Danalundefined Adrian52undefined Drammyundefined 3 Replies Last reply Reply Quote 0
      • Danalundefined
        Danal @dc42
        last edited by Danal

        @dc42 said in Firmware 2.02 Release candidate 3 now available:

        • If a Duet WiFi running in client mode loses the connection to the access point, it retries the connection continuously

        YAY!!!

        Installed. No issues at install. Starting a 2day print on a large-ish delta.

        Firmware Name:	RepRapFirmware for Duet 2 WiFi/Ethernet
        Firmware Electronics:	Duet WiFi 1.02 or later
        Firmware Version:	2.02RC3(RTOS) (2018-10-17b2)
        WiFi Server Version:	1.21
        Web Interface Version:	1.22.4-b1
        

        A couple of hours, working fine, staying connected:

        
        Warm-Up Time	Current Layer Time	Last Layer Time	Job Duration
        01m 09s	        06m 12s	                n/a	        2h 43m 09s
        
                             Estimations
        Based on	Filament Usage	File Progress	Layer Time
        Time Left	54h 05m 48s	118h 09m 10s	167h 39m 59s

        Delta / Kossel printer fanatic

        kuhnikuehnastundefined 1 Reply Last reply Reply Quote 0
        • stewwyundefined
          stewwy
          last edited by

          Running well. No problems so far, just moved from 0.0 at center back to 0.0 at edge also been playing with extruder mA so I've redone config.g a couple of times. printing well

          1 Reply Last reply Reply Quote 0
          • 3DOesteundefined
            3DOeste
            last edited by

            I was going to post in the other thread, but I just finished a 27hr print with 2.02 RC 2 without issues.

            1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator
              last edited by

              M600: Filament change pause ¶
              This command is supported for compatibility with other firmwares. It behaves like M226 except that if macro file filament-change.g exists in /sys on the SD card, it is run in preference to pause.g.

              That's great. I did a filament swap last night and was wanting something exactly like this.

              Z-Bot CoreXY Build | Thingiverse Profile

              pro3dundefined 1 Reply Last reply Reply Quote 0
              • fmaundefined
                fma
                last edited by

                David, what does 'Implemented the object model framework and a few variables' mean? Is it internal dev stuff, or user features?

                Frédéric

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

                  @fma said in Firmware 2.02 Release candidate 3 now available:

                  David, what does 'Implemented the object model framework and a few variables' mean? Is it internal dev stuff, or user features?

                  The object model will underpin three features planned for forthcoming firmware revisions: conditions and loops in GCode, more flexible/more readable menu description files for the 12864 display on the Duet Maestro, and user-configurable fields in Duet Web Control. Currently it is only used in two places:

                  • The M408 P1 S"filter" command uses it to return values from the object model. It's not fully working because of a bug in the filter parser, however M408 P1 with no filter returns the complete object model. DWC will use a similar mechanism to retrieve values for user-specified fields.
                  • In a G- or M-code command, in place of a numeric parameter it should be possible to use an expression such as [gcodes.speedFactor]. But this isn't useful yet because so few variables are included in the object model, also it's not working because of the same bug in the filter parser.

                  The next step is to design the object model. Some of the existing module boundaries (gcodes, platform, move etc.) are not right for the object model, so some redesign/refactoring will be needed.

                  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
                  • Jacotheronundefined
                    Jacotheron
                    last edited by

                    Working on my CNC no issues detected.

                    The object model framework seems to be exactly what I sometimes need. Can't wait, and excited that it will be coming (specifically the conditionals and loops).

                    1 Reply Last reply Reply Quote 0
                    • incogizmoundefined
                      incogizmo
                      last edited by

                      Tested with Duet Maestro and LCD, no stutter or slowdowns on high detail areas like previously. A decent torture test seems to have been Slic3r Gyroid infill. Awesome work!

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

                        @incogizmo said in Firmware 2.02 Release candidate 3 now available:

                        Tested with Duet Maestro and LCD, no stutter or slowdowns on high detail areas like previously. A decent torture test seems to have been Slic3r Gyroid infill. Awesome work!

                        Thanks for confirming that it is fixed.

                        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
                        • fmaundefined
                          fma
                          last edited by

                          @dc42 said in Firmware 2.02 Release candidate 3 now available:

                          The object model will underpin three features planned for forthcoming firmware revisions: conditions and loops in GCode, more flexible/more readable menu description files for the 12864 display on the Duet Maestro, and user-configurable fields in Duet Web Control. Currently it is only used in two places:

                          • The M408 P1 S"filter" command uses it to return values from the object model. It's not fully working because of a bug in the filter parser, however M408 P1 with no filter returns the complete object model. DWC will use a similar mechanism to retrieve values for user-specified fields.
                          • In a G- or M-code command, in place of a numeric parameter it should be possible to use an expression such as [gcodes.speedFactor]. But this isn't useful yet because so few variables are included in the object model, also it's not working because of the same bug in the filter parser.

                          The next step is to design the object model. Some of the existing module boundaries (gcodes, platform, move etc.) are not right for the object model, so some redesign/refactoring will be needed.

                          Amazing! The future looks good ☺

                          Frédéric

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

                            Interesting thing I found about G30:

                            1. If you use:
                            G30 X20 Y20 
                            

                            to probe the bed at a specific point, you always have to calculate the offset of the probe, because the coordinates of the nozzle are used.

                            Whereas if you use 2:

                            G30 P0 X20 Y20 H0 Z-99999 
                            

                            the offset of the probe is already calculated and the real probe coordinates are used but not the "actually" coordinates of the nozzle

                            1. The H- parameter is still not taken into account when probing. Therefore, I performed a little test:
                            M561                                                    ; delete any bed transformation
                            G1 X45.457 Y8.602 Z10 F15000				; go to probing point on floating bed
                            G30 X45.457 Y8.602 H0 S-1   				; define this point as Z=0
                            
                            M561                                                    ; delete any bed transformation
                            G1 X45.457 Y8.602 Z10 F15000				; go to probing point on floating bed
                            G30 X45.457 Y8.602 H5 S-1   				; define this point as Z=0
                            
                            M561                                                    ; delete any bed transformation
                            G30 P0 X20 Y20 H0 Z-99999 S-1			        ; probe point P0
                            
                            M561                                                    ; delete any bed transformation
                            G30 P0 X20 Y20 H3 Z-99999 S-1			        ; probe point P0
                            
                            M561                                                    ; delete any bed transformation
                            G30 P1 X20 Y20 H3 Z-99999 S-1			        ; probe point P1
                            

                            This ended up in the results:

                            20:20:45G32 bed probe heights:, mean nan, deviation from mean nan
                            20:20:42G32 bed probe heights: 0.004, mean 0.004, deviation from mean 0.000
                            20:20:39G32 bed probe heights: 0.007, mean 0.007, deviation from mean nan
                            20:20:36Stopped at height 1.399 mm
                            20:20:31M98 P"0:/macros/Test H-Factor"
                            Stopped at height 1.399 mm
                            

                            So as the H-factor differs every probe, the results are all the same... 😕

                            greetings kuhni

                            1 Reply Last reply Reply Quote 0
                            • Adrian52undefined
                              Adrian52 @dc42
                              last edited by

                              @dc42 updated to 2.02rc3 and dwc 1.22.4-b1. Prints fine, but at the end of a print, the 'job status' does not seem to finish properly. Previously the 'print another' option would appear, but now I just get greyed out 'pause job' button. Using a Kossel delta. Can select and print another job from the g-code files tab.

                              Adrian52undefined BlueDustundefined chrishammundefined 3 Replies Last reply Reply Quote 0
                              • Adrian52undefined
                                Adrian52 @Adrian52
                                last edited by

                                @adrian52 previous version dwc seems to work fine with rc3

                                1 Reply Last reply Reply Quote 0
                                • pro3dundefined
                                  pro3d @Phaedrux
                                  last edited by pro3d

                                  @phaedrux
                                  Did you test M600 yet?

                                  Does it have pause and park feature or does this have to be macros on the side?

                                  /Roy

                                  Valkyrie DIY High Temp 3D Printer

                                  R&D - Engineering Designer - Viking 3D Printers
                                  https://vkingprinter.com/

                                  Phaedruxundefined 1 Reply Last reply Reply Quote 0
                                  • stewwyundefined
                                    stewwy
                                    last edited by

                                    Had a problem with the 1.22.4 web interface:

                                    Uploading a file the first time using the upload&print button was fine.
                                    However if I upload it again with the same filename, having made some slicer settings, and having paused and canceled the original it usually failed the re-upload.

                                    Just retrying with 1.22.3 and it works fine

                                    1 Reply Last reply Reply Quote 0
                                    • Phaedruxundefined
                                      Phaedrux Moderator @pro3d
                                      last edited by

                                      @pro3d it will run pause.g by default or filament-swap.g if present. So you have to customize the macro to your needs.

                                      Z-Bot CoreXY Build | Thingiverse Profile

                                      1 Reply Last reply Reply Quote 0
                                      • k3lagundefined
                                        k3lag
                                        last edited by

                                        @dc42 updated to 2.02rc3 and dwc 1.22.4-b1. Since upgrading whenever I scroll down in DWC it automatically scrolls back up a couple seconds later. Very irritating. I'm using Safari 12.0. This hasn't been a problem with any previous version. It seems to print fine however.

                                        dc42undefined Dougal1957undefined zerspaner_gerdundefined fmaundefined paulowiskundefined 5 Replies Last reply Reply Quote 0
                                        • dc42undefined
                                          dc42 administrators @k3lag
                                          last edited by

                                          @k3lag said in Firmware 2.02 Release candidate 3 now available:

                                          @dc42 updated to 2.02rc3 and dwc 1.22.4-b1. Since upgrading whenever I scroll down in DWC it automatically scrolls back up a couple seconds later. Very irritating. I'm using Safari 12.0. This hasn't been a problem with any previous version. It seems to print fine however.

                                          Which version of DWC were you using previously?

                                          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
                                          • Dougal1957undefined
                                            Dougal1957 @k3lag
                                            last edited by

                                            @k3lag I can't reproduce this in Safari 12.0 it appears just fine to me tho I normally use Chrome.

                                            Doug

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