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

    Custom Drive Mapping stopped working

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    12
    1.2k
    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.
    • PropellerHatundefined
      PropellerHat @PropellerHat
      last edited by

      @propellerhat Also tried without the tool configurating and with only the tools that were working configurated in the config.g before the changes. No help.

      1 Reply Last reply Reply Quote 0
      • PropellerHatundefined
        PropellerHat
        last edited by

        I also moved the M208 next to movement lines but no help.

        1 Reply Last reply Reply Quote 0
        • Catalin_ROundefined
          Catalin_RO
          last edited by

          Just wondering.... M584 defines 3 extruders, for drives 2, 3 and 4. In many places the E parameter is followed by 4 values, like the M350 and M92 codes. Have you tried insuring that you don't have more than 3 values for any E parameter present in the file?

          PropellerHatundefined 1 Reply Last reply Reply Quote 0
          • PropellerHatundefined
            PropellerHat @Catalin_RO
            last edited by

            Removed now all the extra E parameters from M566,M203 and M201. Also the tools are cleaned from everything else than T8.

            Still same behaviour 😞

            1 Reply Last reply Reply Quote 0
            • PropellerHatundefined
              PropellerHat
              last edited by

              Now updated the firmware to 1.21. It has been a while since updating it. After the successfull in-app update from the SD card nothing moves.

              PropellerHatundefined 1 Reply Last reply Reply Quote 0
              • PropellerHatundefined
                PropellerHat @PropellerHat
                last edited by

                Now when trying to move the axes I get this in the console: "G0/G1: insufficient axes homed"

                1 Reply Last reply Reply Quote 0
                • Catalin_ROundefined
                  Catalin_RO
                  last edited by

                  Firmware 1.21 requires all axis to be homed before allowing movements in order to properly enforce actual machine area. There are workarounds, just search the forum.

                  PropellerHatundefined 1 Reply Last reply Reply Quote 0
                  • PropellerHatundefined
                    PropellerHat @Catalin_RO
                    last edited by

                    M564 H0 got the things in movement, pity that exactly the same problem remains as before updating.

                    Drive custom mapping doing nothing.

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

                      If you run M584 from the command line, what does it report?

                      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
                      • PropellerHatundefined
                        PropellerHat
                        last edited by

                        Oh heck... Just found the flat between Duet and Duex being a tad loose. Stuff making a lot more sense now after pushing that corner in.

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