Navigation

    Duet3D Logo

    Duet3D

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

    M572 ignored by RRF

    Tuning and tweaking
    3
    5
    66
    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.
    • war4peace
      war4peace last edited by

      Hi everyone,

      It's me again 😞 with another fresh issue from today.
      My config.g has M572 D0 S0.16 since the first time I tuned the printer (V-Core 3 with Duet 3 6HC, RRF 3.2.2) and the filament I am using (DevilDesign Black PETG). The same command is in both the filament config itself and in config.g and it had been working well with no problems.
      ...Until today.
      I started a print as I always do, left it alone and minded my own business. After it finished, I came to realize there was layer shifting starting with layer 4, something which had never happened before. I started printing the same model again, and I quickly realized Pressure Advance was no longer applied. This resulted in thicker extrusions where the bottom layer full infill was meeting the perimeters, raising the layer enough to snag the nozzle after a few layers and create layer shifting.

      If I enter the command manually in the console while printing is in progress, it works and it is applied correctly.
      Correct filament is loaded (it's the only one I've been using, there is one filament folder), config.g has no errors.

      Question is: why is M572 being ignored unless I enter it manually, despite it existing both in config.g and filament configuration file?

      dc42 Phaedrux 2 Replies Last reply Reply Quote 0
      • dc42
        dc42 administrators @war4peace last edited by

        You can check the current pressure advance settings by sending M572 with no parameters. If it reports zero, then most likely your M572 command in config.g is not being acted on. One possible reason is that it is earlier in config.g than the M584 command that creates the extruder drive.

        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

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

          @dc42
          The M572 command is at the bottom of the file. Here's the tail of the config.g:

          G31 P500 X-28 Y-28 Z2.22    ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed
          
          ; Pressure Advance
          M572 D0 S0.16
          
          ;Taper Height
          M376 H20
          
          ; PanelDue 5i for Duet 3 6CH
          M575 P1 S1 B57600
          
          T0
          
          

          After a full shutdown (power off) and a restart (power on), M572 is working again. However, since a few days ago (could be a week), PanelDue is stuck "Connecting". It used to work intermittently, not anymore.

          I'll create a macro to check all these settings upon boot.

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

            @war4peace said in M572 ignored by RRF:

            The same command is in both the filament config itself and in config.g

            Is there an error in the command in one of the other locations? OR is there a setting in the slicer overriding it? Search a sliced gcode file for M572

            Z-Bot CoreXY Build | Thingiverse Profile

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

              @phaedrux
              No, that is not the case. I have verified by running g-code files from yesterday and the same issue was still occurring.
              Nothing overrides M572 for a very simple reason: my slicers are always kept free of extra G-Code with very specific exceptions (Temp Towers and PA calibration, which are in their own separate profiles).

              There are several unexpected behaviors leading me to believe the Duet + SBC don't really like reboots using power-off from outlet. Could be the 24V PSU not being the best (Weho 350W). I will replace it with a Mean Well 240W and see what happens.

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