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

    [3.3RC3] Missed stepps or overdue moves

    Scheduled Pinned Locked Moved Unsolved
    Beta Firmware
    4
    27
    1.3k
    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 @TypQxQ
      last edited by dc42

      @typqxq those lines in the M122 B1 report indicate that the expansion board reset at some point. We need to establish whether that happened during the print, or a long time ago. If it did occur during the print, that would account for the maxOverdue value being so high.

      Please do the following:

      1. Upgrade the main board and expansion board firmwares to the versions at https://www.dropbox.com/sh/nmpsl9a3jfsumm5/AAA6adSjEcd1AM_j5_tVberGa?dl=0. Ignore the .map files.
      2. Send M122 B1 P1004.
      3. Run M122 B1 and check that the M122 report shows the software reset reason as "deliberate HardFault zeroDiv".
      4. Reset the main board.
      5. Try a print.

      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

      TypQxQundefined 1 Reply Last reply Reply Quote 0
      • TypQxQundefined
        TypQxQ @dc42
        last edited by

        @dc42 Made the above steps and I can't see any change. Here is the new logs event_rc3+1.txt . It's too long for the post limit.

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

          @typqxq thanks, I will try to replicate your setup today.

          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
          • dc42undefined
            dc42 administrators @TypQxQ
            last edited by

            @typqxq said in [3.3RC3] Missed stepps or overdue moves:

            Here is a link to the configuration and a test gcode file https://we.tl/t-DQueVGrH61

            Unfortunately that .link has expired. Please provide a new link to your files.

            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

            TypQxQundefined 1 Reply Last reply Reply Quote 0
            • TypQxQundefined
              TypQxQ @dc42
              last edited by

              @dc42 Here is a new link: https://www.dropbox.com/sh/yfjwidhzvlxk8k2/AAAQd95XneD8zUVNV8VnNO3ya?dl=0

              dc42undefined 2 Replies Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @TypQxQ
                last edited by dc42

                @typqxq thanks.

                I have spotted an error in your configuration, in file custom/tool_1.g:

                ; Create Heater
                	M308 S2 P"2.temp1" Y"thermistor" T100000 B4725 C0.0000000706 A"T1 Heater"	; configure sensor 2 as thermistor on pin temp1
                	M950 H2 C"2.out1" T2											; create nozzle heater output on out1 and map it to sensor 2
                	M143 H2 S300													; set temperature limit for heater 1 to 300C (e3d v6 all metal)
                	M307 H2 B0 S1.00												; disable bang-bang mode for heater  and set PWM limit
                
                ; Create Part Fan
                	M950 F3 C"2.out4"	                            ; Define Part Cooling fan on out4 (4pin)
                	M106 P3 C"Part Cooling T1"						; Setup Part Cooling Fan as Part Cooling T1
                
                ; Create Hotend Fan
                	M950 F4 C"1.out7"	                            ; Define Hotend Fan on out7 (2pin)
                	M106 P4 S255 T45 H2                             ; Setup Hotend Fan for thermal control, full on when H2 reaches 45C
                

                You create the sensor and heater on board 2, but the fan on board 1. RRF has the following documented limitation:

                A thermostatically-controlled fan on an expansion board can only be controlled by a temperature sensor on the same expansion board.

                Did you perhaps mean to use port 2.out7 for the fan?

                I don't know whether this is relevant to the problem of maxOverdue being much too large and the associated print issues. I will change the config to use port 2.out7 and try running your print.

                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

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

                  @typqxq I have reproduced the problem on my bench system so I am now able to investigate it.

                  For future reference, it would be easier for me to use your configuration files if instead of using M98 P"/sys/custom/xxx" in many places, you used M98 P"custom/xxx". This is because I have your configuration in a subfolder of /sys.

                  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
                  • TypQxQundefined
                    TypQxQ @dc42
                    last edited by

                    @dc42 Thank you, I found and fixed it last week. It had no effect from what I can see.
                    This are the configuration files as of when I reported the problem.

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

                      @typqxq please try the new firmware binaries at https://www.dropbox.com/sh/xfsvscbaab0dtzl/AACCcSeiTNINZL-xbs6IhC4Ja?dl=0. Ignore the .map files.

                      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

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

                        @TypQxQ have you had a chance to try the new firmware? We're waiting to release 3.3 stable but I would like to know whether this issue is resolved first.

                        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

                        TypQxQundefined MaxGyverundefined 2 Replies Last reply Reply Quote 0
                        • TypQxQundefined
                          TypQxQ @dc42
                          last edited by

                          @dc42 Sorry but I have left on vaccation and won’t be able to test it until I get back.
                          Have a great summer!

                          1 Reply Last reply Reply Quote 0
                          • MaxGyverundefined
                            MaxGyver @dc42
                            last edited by

                            @dc42 I had the same problems described by @TypQxQ after upgrading from RC3.2 to RC3.3.
                            The new binaries fixed the issue.

                            Cheers
                            Max

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

                              @maxgyver said in [3.3RC3] Missed stepps or overdue moves:

                              @dc42 I had the same problems described by @TypQxQ after upgrading from RC3.2 to RC3.3.
                              The new binaries fixed the issue.

                              Cheers
                              Max

                              Thanks for confirming that!

                              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
                              • MaxGyverundefined MaxGyver referenced this topic
                              • MaxGyverundefined MaxGyver referenced this topic
                              • MaxGyverundefined MaxGyver referenced this topic
                              • MaxGyverundefined MaxGyver referenced this topic
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA