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

    Error in Docs for M591

    Scheduled Pinned Locked Moved
    Filament Monitor
    3
    5
    345
    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.
    • tfjieldundefined
      tfjield
      last edited by

      Re: filament-error#.g usage help? Avoid pausing on sensorerror?

      I think there is an error in the docs for M591. It currently says:

      In RRF 3.4 and later, the action on a filament error is to:

      • run filament-error#.g if available, where # is the extruder number
      • failing that run filament-error.g if available

      But the upgrade notes say:

      • The handling of filament errors have changed. When a filament error occurs, an event is created. To handle the event, RRF runs macro file filament-error.g without appending the extruder number to the file name and without pausing the print first. The extruder number is passed as param.D along with some other parameters. If filament-error.g is not found then the print is paused (running pause.g) and the error is reported.

      I've looked through the code and I don't think filament-error#.g is ever called.

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

        @tfjield thanks for pointing this out. I have amended the documentation.

        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

        tfjieldundefined ComedianTF2undefined 2 Replies Last reply Reply Quote 2
        • tfjieldundefined
          tfjield @dc42
          last edited by

          @dc42 Thank you!

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

            @dc42 Do you have an example of the param.D being used?

            1 Reply Last reply Reply Quote 0
            • tfjieldundefined
              tfjield
              last edited by tfjield

              @comediantf2
              This is what I put in filament-error.g so that it would work with both 3.3 and 3.4+:

              M25				; first, pause the print as pre-RRF 3.3 did
               
              if {param.D == 0}		; now call the right pre-RRF 3.4 subroutines.
              	M98 P"filament-error0.g"
              elif {param.D == 1}
              	M98 P"filament-error1.g"
              
              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Unless otherwise noted, all forum content is licensed under CC-BY-SA