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

    I Do Not Have Config-Override File in my Latest 3.3.0 Build???

    Scheduled Pinned Locked Moved
    General Discussion
    4
    7
    326
    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.
    • Pickettundefined
      Pickett
      last edited by

      1. As the title states I do not have a Config-Override File in my fresh build of RRF 3.3.0 with all of its applicable / equivalent DWC, DSF, etc etc???

      How to obtain said file I konw what do with it after Ive got it in my hands....

      1. When I go to Home all my Axis which is the most common X, Y, and Zx2 each axis moves a very short distance as in like ten mm maybe twenty IDK have not measured the distance traveled? Each axis after "homing' the very short distance to its home position it actually never makes it to its home position however the X, Y, and Z Home Buttons turn blue and all 3 are homed but they never moved to their original, or at least what is supposed to be their original (Home) position and this is driving me nuts I really need to get my rpinter up and working for a lot of reasons. Mostly because my wife keeps getiing on to me anout it. Anywhoo please let me konw what I am missing or need to do.

      TIA!!!!,

      Mr Pickett

      fcwiltundefined 1 Reply Last reply Reply Quote 0
      • fcwiltundefined
        fcwilt @Pickett
        last edited by fcwilt

        @pickett

        The file config-override.g is created by executing M500 with certain parameters.

        M500 documentation

        If you have not done anything to create the file you may not have one - it is not required to have one.

        If you do have the file to make use of it you put a M501 at the end of the main config.g file.

        M501 documentation

        The homing behavior you are seeing suggests your axis endstop sensors are already triggered at the start of the homing procedure.

        A configuration problem in the main config.g file is possible and/or a wiring problem.

        Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

        Pickettundefined 1 Reply Last reply Reply Quote 1
        • Pickettundefined
          Pickett @fcwilt
          last edited by

          @fcwilt I was thinking there might be something going on with my endstops. Oh this one is for @Phaedrux I got an official, genuine Duet3d board now as it was the Fysetc Clone I had dang near literally exploded slash caught on fire at the SMD' chips. It was a glorious looking blaze with White slash Peachy coloration through and through!!! I feel much better now that I have a Genuine D3M5+ on my Chiron/Crearibo Mod! Couldnt be any happier. Having that 2oz copper running through the veins of the board gives me solice.

          @fcwilt anyways back to your assistance thanks so much Ill look into my endstop issue now and will be looking forward to finally commissioning my printer its been a while coming now but hey Im a perfectionist constanty seeking more perfection in an imperfect world!

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

            @pickett most likely the sensors are reporting as triggered when they are not, which is what I think @fcwilt meant in his post. Please check that you have wired them correctly as described at https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches, and post the contents of your config.g file here.

            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

            Pickettundefined 1 Reply Last reply Reply Quote 1
            • Phaedruxundefined
              Phaedrux Moderator
              last edited by

              https://duet3d.dozuki.com/Wiki/Test_homing_behaviour

              This may help

              Z-Bot CoreXY Build | Thingiverse Profile

              Pickettundefined 1 Reply Last reply Reply Quote 1
              • Pickettundefined
                Pickett @dc42
                last edited by

                @dc42 Thank you sir!!!! It was a wiring issue as it appeared that I had the Ground and 3.3volt connected but didnt actually have anything going into the io5in/io6in though the BL Touch was configured and wired correctly thanks to that Ender 3/Duet 3 Mini 5+ Installation article and a BL Touch/Ender 3/Duet3d installatio article outside of this forum/Duet3d guide.

                Anyways thanks everyone yet again Im gaining more and more experience everyday. I really like the G Code is everything Mantra as it makes the most sense with that approach given that we are dealing with a machine whom only understand certain forms of communication at certain levels of the boards structure. Anyways thanks!

                1 Reply Last reply Reply Quote 1
                • Pickettundefined
                  Pickett @Phaedrux
                  last edited by

                  @phaedrux It did thank you so much!!!!

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