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

    z motor loses strength?

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    2
    17
    1.3k
    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.
    • Napalm1432undefined
      Napalm1432
      last edited by Napalm1432

      i'm using all on the expansion board, but i have 2nd extruder free, and regular Z connection free.
      EDIT: Issue solved, just changed drives!

      1 Reply Last reply Reply Quote 0
      • Napalm1432undefined
        Napalm1432
        last edited by Napalm1432

        Soo it was solved, and it sort of still is BUT:
        When i jog the Z motors they all work fine.
        But when i start a print, somehow one of the motors loses strength again, but when i takeover manually it works again......
        Getting quite sick of getting these lil bugs fixed
        edit: i'm testing my last open drive right now, but it's sad that i would keep losing drive after drive
        Edit2: issue remains after switching drives....

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

          When you used M584 to assign drivers to the Z axis, did you remember to redefine the extruder drivers too?

          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
          • Napalm1432undefined
            Napalm1432
            last edited by

            I'm currently only reassigning the axes in the homez.g file, and when I home manually everything is fine, only when i print a gcode it fails when homing.
            Do i need to reassign the extruder everytime?

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

              @napalm1432 said in z motor loses strength?:

              I'm currently only reassigning the axes in the homez.g file, and when I home manually everything is fine, only when i print a gcode it fails when homing.
              Do i need to reassign the extruder everytime?

              No, but you must reassign the extruders in the M584 command in config.g where you do the initial driver remapping.

              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
              • Napalm1432undefined
                Napalm1432
                last edited by

                i do reassign the extruder in config.g at the end of the file

                dc42undefined 1 Reply Last reply Reply Quote 0
                • Napalm1432undefined
                  Napalm1432
                  last edited by

                  I did some more testing, and a had a gcode made in the newer version of cura, because of the M106 command missing the P parameter, but it only fails on that motor with a file from this version of cura, before i used Cura 15.04.6 and in that version it doesn't have the problem with the motor

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

                    @napalm1432 said in z motor loses strength?:

                    i do reassign the extruder in config.g at the end of the file

                    That should be done in the same M584 command that you reassign Z, and should be before any M906, M915 and M350 commands.

                    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
                    • Napalm1432undefined
                      Napalm1432
                      last edited by Napalm1432

                      okay, i changed the config to reflect this change, but still having the same issue, right now it also happened with the older cura's gcode.
                      It seems to not even be powered, might it help to include the extruder mapping in each M584?

                      EDIT: Never mind this comment, forgot to change my homing code, i'll be back after this!

                      1 Reply Last reply Reply Quote 0
                      • Napalm1432undefined
                        Napalm1432
                        last edited by

                        Yup my bad, it works now! (haven't tested with the newest version of Cura yet though)

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

                          You don't need to reassign the extruders in all M584 commands that you use, just in the first one - because when you assign any driver numbered 4 or higher to be an axis, it keeps its default assignment as an extruder as well unless you redefine the extruder drives.

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