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

    One z motor don’t always move

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    driver issue warranty claim support
    4
    16
    826
    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.
    • droftartsundefined
      droftarts administrators @elliott.griffiths
      last edited by

      @elliott-griffiths It's fine to run the two motors on the same axis on independent drivers. It allows the axis to be levelled automatically. See https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

      @Alucardi you could run both Z motors from the Z driver as @elliott-griffiths suggests, but no, you can't then use G32. On the plus side, once you level the bed by hand, they are far less likely to go out of sync. If you want to test this, rewire the motors (with POWER OFF, or you risk damaging the stepper drivers), do the changes to config.g I say above, then change M584 to:
      M584 X0 Y1 Z2 E3

      Ian

      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

      1 Reply Last reply Reply Quote 1
      • Alucardiundefined
        Alucardi @droftarts
        last edited by Alucardi

        @droftarts firmware is 2.05.1
        I will try your suggestions tonight. I know I could run of same driver but if it’s a defective drive I would still get it fixed but let’s hope it’s just firmware and nothing else.

        1 Reply Last reply Reply Quote 1
        • ChrisPundefined
          ChrisP
          last edited by

          M8 S30 should also be M84 S30 too, FWIW.

          Alucardiundefined 1 Reply Last reply Reply Quote 1
          • Alucardiundefined
            Alucardi @ChrisP
            last edited by

            @ChrisP do I really want that command? It mentioned that it won’t be that great during a print. If I do layers that above the idle time won’t it be able to sag if z goes to idle if not being used?

            ChrisPundefined 1 Reply Last reply Reply Quote 0
            • ChrisPundefined
              ChrisP @Alucardi
              last edited by ChrisP

              @Alucardi It's a good question, tbh. I was under the impression that any move on any axis would reset the counter. I've just gone and had a quick look at teh firmware source, and that does appear to be the case too. So as long as your printer is moving at least on motor in that time, I think you should be fine.

              Reference: see here, that the S parameter is parsed independantly of the axis.

              droftartsundefined 1 Reply Last reply Reply Quote 1
              • droftartsundefined
                droftarts administrators @ChrisP
                last edited by

                @ChrisP said in One z motor don’t always move:

                @Alucardi I was under the impression that any move on any axis would reset the counter ... So as long as your printer is moving at least on motor in that time, I think you should be fine.

                Yes, that's correct. It will only idle the motors when ALL motors have stopped moving for over 30 seconds, if M84 S30 is set.

                Ian

                Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                1 Reply Last reply Reply Quote 0
                • Alucardiundefined
                  Alucardi @droftarts
                  last edited by

                  @droftarts i changed the code and after running a g32 I got a motor sound (after it adjusted the bed when printer was idle it gave a sound froM the motor) which I never heard before so I guess something changed. I will try homing and a few other more tonight, hopefully it’s fixed but it’s hard to force the issue so time will tell.

                  1 Reply Last reply Reply Quote 0
                  • Alucardiundefined
                    Alucardi @droftarts
                    last edited by

                    @droftarts well I have I bin running the printer a lot tonight with short prints. I have bin trying to get PA calibrated which really is a pain. So far no issues.

                    droftartsundefined 1 Reply Last reply Reply Quote 0
                    • droftartsundefined
                      droftarts administrators @Alucardi
                      last edited by

                      @Alucardi Great, hopefully that's fixed it.

                      Ian

                      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                      Alucardiundefined 1 Reply Last reply Reply Quote 0
                      • Alucardiundefined
                        Alucardi @droftarts
                        last edited by Alucardi

                        @droftarts Still no problems. My g32 usually reported like deviation of -0.150 or so. Now its always below -0.014 or less. So i would think this is a fixed problem now. I appreciate al lthe support and help.

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