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

    RepRapFirmware 3.0

    Scheduled Pinned Locked Moved
    General Discussion
    35
    176
    30.6k
    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 @mudcruzr
      last edited by

      @mudcruzr said in RepRapFirmware 3.0:

      I tried the M950 command as the very last line in my config.g and it didn't work, I also can't see anything in config-override.g that would change it. So I think it's a question for @dc42

      @dc42 David, where must the M950 command reside? I have it as the very last command in my config.g but in order to use my bltouch probe I must also put it in the deployprobe.g file immediately before the M280 for it to work.

      After the deployprobe.g file has run once, I don't need to put M950 anywhere else, everything just works. Are there any rules about where it must be either before or after certain other commands?

      Putting the M950 command at the end of config.g should work. The rules are:

      1. At the point where you run M950, the pin you are assigning must be free. So you must cancel any default or previous assignment before the M950 command.

      2. The M950 command must be executed before the command that uses the mapping it sets up - so in your case, before the first M280 command is executed.

      It may help to run M98 P"config.g" so that you can see any errors that are thrown when config.g executes.

      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
      • mudcruzrundefined
        mudcruzr
        last edited by

        No errors from config.g but I now have the probe working. I hadn't put the C"zprobe.in" in the M558 line because the probe was working without it (as long as the M950 was still in deployprobe.g). As soon as I added the C"zprobe.in" everything started working as it should. The M558 line is now:

        M558 P9 C"zprobe.in" H5 F300 T4000 A10 S0.003 R0.5 B1

        And M950 S0 C"zprobe.mod" is the last line in my config.g and nowhere else.

        Thanks guys.

        PaulHewundefined dc42undefined 2 Replies Last reply Reply Quote 0
        • PaulHewundefined
          PaulHew @mudcruzr
          last edited by

          @mudcruzr Would you care to share your config.g please. I have been looking to upgrade to RRF3 but need a template to work from!
          TIA Paul.

          RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
          Voron 2.4 disassembled..... Waiting for the RailCore Mini....

          mudcruzrundefined 1 Reply Last reply Reply Quote 0
          • mudcruzrundefined
            mudcruzr @PaulHew
            last edited by mudcruzr

            @paulhew said in RepRapFirmware 3.0:

            @mudcruzr Would you care to share your config.g please. I have been looking to upgrade to RRF3 but need a template to work from!
            TIA Paul.

            Sure, here you go:
            0_1557820856402_config.g

            Edit: I should mention that I have 2 separately controlled Y motors and 2 separately controlled Z motors.

            PaulHewundefined 1 Reply Last reply Reply Quote 0
            • mudcruzrundefined
              mudcruzr
              last edited by mudcruzr

              I've modified my Maestro 12864 menu files to work with RRF3b1, but to avoid confusion I've created a separate new repository on Github for them. There are no changes to functionality yet, they do the same as before but work with RRF3.

              Here they are: https://github.com/mudcruzr/Duet-Maestro-12864-Menu-Files-for-RRF3b1/releases/tag/v0.1.RRF3b1

              1 Reply Last reply Reply Quote 1
              • A Former User?
                A Former User
                last edited by

                Should you not be able to use M401 instead of M280 to keep the menu files the same? I thought M401 called M98 P"deployprobe.g" which then can ve version specific?

                mudcruzrundefined dc42undefined 2 Replies Last reply Reply Quote 0
                • PaulHewundefined
                  PaulHew @mudcruzr
                  last edited by

                  @mudcruzr Thank you, greatly appreciated.
                  Yes I saw the Y and Z's in the code and did wonder!

                  Time to back everything up and try it!
                  Thanks again.
                  Paul

                  RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                  Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                  1 Reply Last reply Reply Quote 0
                  • mudcruzrundefined
                    mudcruzr @A Former User
                    last edited by

                    @bearer said in RepRapFirmware 3.0:

                    Should you not be able to use M401 instead of M280 to keep the menu files the same? I thought M401 called M98 P"deployprobe.g" which then can ve version specific?

                    I guess I could, but I expect RRF2 and RRF3 to diverge more and more as RRF3 develops and trying to include new RRF3 functionality while maintaining backwards compatibility with RRF2 seems a bit like making a rod for my own back. I fully expect the whole lot to be rewritten & redesigned more than once.

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

                      @mudcruzr said in RepRapFirmware 3.0:

                      No errors from config.g but I now have the probe working. I hadn't put the C"zprobe.in" in the M558 line because the probe was working without it (as long as the M950 was still in deployprobe.g). As soon as I added the C"zprobe.in" everything started working as it should. The M558 line is now:

                      M558 P9 C"zprobe.in" H5 F300 T4000 A10 S0.003 R0.5 B1

                      And M950 S0 C"zprobe.mod" is the last line in my config.g and nowhere else.

                      Thanks guys.

                      I can see why. The default pin configuration for M558 is "zprobe.in+zprobe.mod". For your M950 command to work, the zprobe.mod pin must be free. So you need to redefine the Z probe pins as just "zprobe.in" in M558, to free up the "zprobe.mod" pin.

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

                        @bearer said in RepRapFirmware 3.0:

                        Should you not be able to use M401 instead of M280 to keep the menu files the same? I thought M401 called M98 P"deployprobe.g" which then can ve version specific?

                        M401 does a little more than that, it also records the Z probe as being deployed. This means that when you come to do a G30, the firmware knows that the probe is deployed, so it doesn't do an automatic deploy/retract around the G30 command. This can be used to deploy the probe just once at the start of bed.g and retract the proibe just once at the end. [This doesn't work for BLTouch, which needs to be deployed/retracted at every probe point.]

                        So M401 should always be used in preference to M98 Pdeployprobe.g, and similarly M402 instead of M98 Pretractprobe.g.

                        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
                        • gtj0undefined
                          gtj0
                          last edited by gtj0

                          @dc42 just did a git pull to get your latest v3-dev changes and just fyi... auto bed levelling is still non-automatic. Calculations are done but no movement.

                          If you don't have time to look at it right now, that's cool. I can take a look this weekend.

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

                            @gtj0 said in RepRapFirmware 3.0:

                            @dc42 just did a git pull to get your latest v3-dev changes and just fyi... auto bed levelling is still non-automatic. Calculations are done but no movement.

                            If you don't have time to look at it right now, that's cool. I can take a look this weekend.

                            Does it work properly on your printer using 2.03RC2 ?

                            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

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

                              @dc42 said in RepRapFirmware 3.0:

                              @gtj0 said in RepRapFirmware 3.0:

                              @dc42 just did a git pull to get your latest v3-dev changes and just fyi... auto bed levelling is still non-automatic. Calculations are done but no movement.

                              If you don't have time to look at it right now, that's cool. I can take a look this weekend.

                              Does it work properly on your printer using 2.03RC2 ?

                              I just double checked and yes it works on 2.03RC2. It does the 3 probes, calculates the offsets, then adjusts the motors to compensate.

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

                                @gtj0, thanks for confirming this. I will invesgigate the issue RRF3.

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

                                  I think I have found the reason for leadscrew moves not working. I have pushed some updates to the RRF 3 source. Please note, I have also made some changes to the M558 command.

                                  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

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

                                    @dc42 said in RepRapFirmware 3.0:

                                    I think I have found the reason for leadscrew moves not working. I have pushed some updates to the RRF 3 source. Please note, I have also made some changes to the M558 command.

                                    Working now, thanks!

                                    1 Reply Last reply Reply Quote 0
                                    • mudcruzrundefined
                                      mudcruzr
                                      last edited by

                                      Is there any chance of a new build with these changes in (for those of us without the wherewithall to compile) please?

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

                                        @mudcruzr said in RepRapFirmware 3.0:

                                        Is there any chance of a new build with these changes in (for those of us without the wherewithall to compile) please?

                                        New binaries here https://www.dropbox.com/s/fyvibzm0zl92hiy/Duet2CombinedFirmware.bin?dl=0 and here https://www.dropbox.com/s/m0r3ldy424mxf4v/DuetMaestroFirmware.bin?dl=0.

                                        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

                                        dc42undefined 1 Reply Last reply Reply Quote 0
                                        • mudcruzrundefined
                                          mudcruzr
                                          last edited by

                                          @dc42 Many thanks David

                                          1 Reply Last reply Reply Quote 0
                                          • oliofundefined
                                            oliof
                                            last edited by

                                            That last build does not move the extruder for me on a CR-20. I checked by moving the extruder motor to X and was able to move it. Downgrading to 2.03RC2 (what I ran previously) fixed the extruder.

                                            I am pretty sure that nothing in my config.g needs changing, but maybe I overlooked something in the wiki. See attached file.

                                            • 0_1558265361187_config.g

                                            <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

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