Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    M566 Command Seemingly Not Respected

    Gcode meta commands
    2
    8
    75
    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.
    • dzg7pl
      dzg7pl last edited by

      Hi Everyone,

      I am trying to remove ghosting from my prints and the M566 command is one of the ways I am trying to achieve this. Unfortunately, no matter what values I try, my Duet WiFi does not seem to want to apply them. I have tried setting the command in config.g and also in the print file, without success. An example of what I have tried is: M566 X150 Y150 Z12 E9000 P1. I have tried without P1 and also had X/Y down as low as 1 - nothing makes a difference (that I am able to observe anyway). I have also tried using M205.

      What obvious thing am I missing?!

      Cheers

      Tim

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

        When are you sending m566? Only in config.g or during a print?

        It's possible you are using cura and there is an m205 in the start gcode overriding your config.g setting when the print starts.

        Send m566 by itself during a print to see what the current value is. Same for m205

        1 Reply Last reply Reply Quote 0
        • dzg7pl
          dzg7pl last edited by

          @Phaedrux said in M566 Command Seemingly Not Respected:

          When are you sending m566? Only in config.g or during a print?

          It's possible you are using cura and there is an m205 in the start gcode overriding your config.g setting when the print starts.

          Send m566 by itself during a print to see what the current value is. Same for m205

          Hi, thanks for the reply and sorry for not coming back sooner (my printer belt snapped and haven't used it since early Dec). I have tried the M566 command in both config.g and my gcode files, but neither appear to work. I'm printing the XYZ calibration cube and running M566/M205 during the print does show the correct values, but whatever I set them to, there is no distinguishable effect on the speed of the print/direction changes (I've even set to as low as M205 X0.1 Y0.1).

          I'm using PrusaSlicer if that has any bearing on this.

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

            What values are you trying to use? There is a minimum. What are you expecting to happen?

            Please share the rest of your config.g as well as your firmware version and some basic print settings.

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

              @Phaedrux said in M566 Command Seemingly Not Respected:

              What values are you trying to use? There is a minimum. What are you expecting to happen?

              Please share the rest of your config.g as well as your firmware version and some basic print settings.

              From what I understand, these settings are used to reduce the speed around sharp changes in direction (e.g. corners). My understanding is that the lower the values are for these commands, the slower the changes in direction should be. This is one way to remove ghosting from prints. Based on this understanding, I have been expecting prints of the cube to be slower as the printer is not allowed to reach the max speed (80mm/s) I have set as the M566/M205 settings constrain the speed it is able to achieve before it needs to slow down for the corners.

              I know I've missed something simple/obvious, but can't work it out.

              config.g

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

                M566 X150 Y150 Z12 E9000 P1

                Those values are very very low, and if you were trying to go lower, you're not likely to see any difference.

                https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M566_Set_allowable_instantaneous_speed_change

                The units for M566 is mm/min and the lower limit is 0.1mm/s or 6mm/min.

                So 150mm/min = 2.5mm/s.

                Are you also setting M205 anywhere?

                I would start with M566 X600 Y600 Z60 E6000 P1

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

                  @Phaedrux said in M566 Command Seemingly Not Respected:

                  M566 X150 Y150 Z12 E9000 P1

                  Those values are very very low, and if you were trying to go lower, you're not likely to see any difference.

                  https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M566_Set_allowable_instantaneous_speed_change

                  The units for M566 is mm/min and the lower limit is 0.1mm/s or 6mm/min.

                  So 150mm/min = 2.5mm/s.

                  Are you also setting M205 anywhere?

                  I would start with M566 X600 Y600 Z60 E6000 P1

                  Thanks for the reply. I've tried all sorts of values with no visible impact on the print speed etc. I've even gone down to the minimum allowed values of X/Y6 with no effect. I am not aware I am setting M205 anywhere - it's not in the gcode files I am generating.

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

                    What firmware version are you using and can you share a sliced gcode file so we can see your print settings.

                    How fast are you printing?

                    What kind of printer is this?

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