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

    Continue blocking during printing.

    Scheduled Pinned Locked Moved
    My Duet controlled machine
    5
    15
    529
    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

      Power up your printer, then send the M350 command. It will report what microstepping is selected.

      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

      Fedekossel1undefined 1 Reply Last reply Reply Quote 0
      • Fedekossel1undefined
        Fedekossel1 @dc42
        last edited by

        @dc42 I just did the M350 command. Oddly enough, it gives me this result

        Microstepping - x:256, y:256, z:256, e:16:16

        In my configuration posted above I clearly put 16 interpolated microsteps at 256, excluding extruder that I will now also put at 256 interpolation,

        1 Reply Last reply Reply Quote 0
        • AndreSundefined
          AndreS
          last edited by

          check your config-override.g

          Fedekossel1undefined 1 Reply Last reply Reply Quote 0
          • Fedekossel1undefined
            Fedekossel1 @AndreS
            last edited by

            @AndreS
            ; config-override.g file generated in response to M500 at 2020-03-10 10:27
            ; This is a system-generated file - do not edit
            ; Delta parameters
            M665 L360.270:360.270:360.270 R185.353 H364.129 B150.0 X0.229 Y0.060 Z0.000
            M666 X1.793 Y-1.094 Z-0.699 A0.00 B0.00
            ; Heater model parameters
            M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
            M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            G10 L2 P1 X0.00 Y0.00 Z0.00
            G10 L2 P2 X0.00 Y0.00 Z0.00
            G10 L2 P3 X0.00 Y0.00 Z0.00
            G10 L2 P4 X0.00 Y0.00 Z0.00
            G10 L2 P5 X0.00 Y0.00 Z0.00
            G10 L2 P6 X0.00 Y0.00 Z0.00
            G10 L2 P7 X0.00 Y0.00 Z0.00
            G10 L2 P8 X0.00 Y0.00 Z0.00
            G10 L2 P9 X0.00 Y0.00 Z0.00

            1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk
              last edited by

              @Fedekossel1

              Try sending

              M350 X16 Y16 Z16 E16 I1
              

              Once the machine has started up. Then resend M350 and make sure it reports back 16 microsteps for each axis.

              If it does, it means that a file somewhere still has incorrect values for M350, causing the wrong values to be loaded on start up

              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

              Fedekossel1undefined 1 Reply Last reply Reply Quote 0
              • Fedekossel1undefined
                Fedekossel1 @jay_s_uk
                last edited by

                @jay_s_uk
                I just tried, I always 256 microsteps, besides the config are in other places the parameters of microsteps?

                dc42undefined 1 Reply Last reply Reply Quote 0
                • Fedekossel1undefined
                  Fedekossel1
                  last edited by

                  I found inside config.g.bak all the steps at 256 microsteps, I change them to 16?

                  jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                  • jay_s_ukundefined
                    jay_s_uk @Fedekossel1
                    last edited by

                    @Fedekossel1

                    config.g.bak doesn't get loaded at system start up

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

                      @Fedekossel1 said in Continue blocking during printing.:

                      @jay_s_uk
                      I just tried, I always 256 microsteps, besides the config are in other places the parameters of microsteps?

                      That's the problem! Change XYZ to x16 microstepping with interpolation. If your E steps/mm is 400 or above, set that to x16 with interpolation too. If it is less than 400, set E microstepping to x64.

                      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

                      Fedekossel1undefined 1 Reply Last reply Reply Quote 0
                      • Fedekossel1undefined
                        Fedekossel1 @dc42
                        last edited by

                        @dc42
                        I fixed, it's normal that it doesn't tell me giving the command M350 "example" X:16 (on),
                        ?
                        From config I put
                        M350 X16 Y16 Z16 E16 I1

                        Typing the M350 command gives me this result

                        M350
                        Microstepping - X:16, Y:16, Z:16, E:16:16```

                        dc42undefined 1 Reply Last reply Reply Quote 0
                        • Fedekossel1undefined
                          Fedekossel1
                          last edited by

                          I just set all the axes correctly to 16 microsteps interpolated to 256, with the same gcode that froze, now goes without stopping. I keep you updated these days if I get problems or blocks during printing. At the moment I thank everyone!

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

                            @Fedekossel1 said in Continue blocking during printing.:

                            @dc42
                            I fixed, it's normal that it doesn't tell me giving the command M350 "example" X:16 (on),
                            ?
                            From config I put
                            M350 X16 Y16 Z16 E16 I1

                            Typing the M350 command gives me this result

                            M350
                            Microstepping - X:16, Y:16, Z:16, E:16:16```

                            Check that you have entered the I1 parameter correctly. That's letter i followed by digit 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

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