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

    Code change for RF3

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    4
    8
    461
    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.
    • zerspaner_gerdundefined
      zerspaner_gerd
      last edited by

      I am considering how to change my filament changing macro to the behavior of RF3 without losing any feature.

      Ask:

      • Can you stop the E axis in RF3 via an end stop? My reading something like that.

      G1 H1 E moves (stopping on motor stall) are now implemented

      What does the endstop configuration look like?

      M574 E2:2 S1 P"!e0stop"
      

      That doesn't seem to work because M574 doesn't print anything.

      M574
      Endstop configuration:
      X: low end switch connected to pin !xstop
      Y: high end switch connected to pin !ystop
      Z: high end switch connected to pin !zstop
      

      Or do I have to use an additional axle again?

      • My biggest problem is, how can I manage two functions on E0 ("e0stop") endstop?
        In RF2 I deactivated the trigger with M581 E0 S-1 T0, how do I do this with RF3?
        The PIN ("! E0stop") had two functions for me, the emergency stop and the filament change to stop the feeder

      Best regards

      Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

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

        The only type of "endstop" for extruder drivers supported at present is a stall detection endstop. I find that this works very well for filament loading, using this macro:

        ; Load T0 with PLA
        G10 P0 S200 R160    ; set temperatures for PLA
        T0                  ; select tool
        M915 E0 S3          ; set stall sensitivity
        M400
        M913 E30            ; motor current to 30%
        M83                 ; relative extrusion
        G1 H1 E800 F6000    ; feed up to 800mm until stall
        M400
        M913 E100           ; restore normal motor current
        G1 E50 F120         ; extrude 50mm @ 2mm/sec
        

        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

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

          @dc42
          That won't bring me anything for my variant.

          My filament load looks like this:

          1. Turn the feeder slowly when the filament is at the mark, confirm the button G1 H1 A700 F200
          2. Then comes the fast charging G1 A670. F2700
          3. And the whole thing again when priming G1 H1 A350 F100

          I will then create a virtual axis (A) again, that should still work with RF3.

          Am I correct now that there is no way to deactivate an external trigger with RF3, which was possible with S-1 with RF2?

          Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

          danzaywerundefined 1 Reply Last reply Reply Quote 0
          • danzaywerundefined
            danzaywer @zerspaner_gerd
            last edited by

            @zerspaner_gerd
            No you are wrong, the method has changed. To get the same result as S-1 now you have to assign the trigger on the pin "nil"

            zerspaner_gerdundefined 1 Reply Last reply Reply Quote 1
            • zerspaner_gerdundefined
              zerspaner_gerd @danzaywer
              last edited by

              @danzaywer

              Thanks alot
              This information was missing to me, it is nowhere to be found.
              Perhaps this should be written down for others.

              Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

              Danalundefined 1 Reply Last reply Reply Quote 0
              • Danalundefined
                Danal @zerspaner_gerd
                last edited by

                @zerspaner_gerd said in Code change for RF3:

                @danzaywer

                Thanks alot
                This information was missing to me, it is nowhere to be found.
                Perhaps this should be written down for others.

                "nil" is in four places in the guide to converting to V3 firmware: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview

                Delta / Kossel printer fanatic

                zerspaner_gerdundefined 1 Reply Last reply Reply Quote 0
                • zerspaner_gerdundefined
                  zerspaner_gerd @Danal
                  last edited by

                  @Danal
                  That didn't catch my eye!
                  And exactly with M581 there is no information about it.
                  Thank goodness someone made me aware of it
                  (in my defense, I have to translate everything with Google translator because my english is unfortunately not good)

                  Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

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

                    I've update the M581 description for RRF3 in the GCodes wiki page.

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