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

    A Z motor does not rotate ONLY when homeall

    Scheduled Pinned Locked Moved
    General Discussion
    3
    7
    385
    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.
    • peirofundefined
      peirof
      last edited by

      Hi,

      As I mentioned, I have had a problem recently, in which one of the Z motors (of the 3 used by the printer) does not turn... After exploring several possibilities, I have isolated the problem a little more.

      -Engine runs, i have connected to other driver
      -Duet Driver works, I explain it below
      -When I command in gcode (M564 H0), to be able to move without homing, the motor rotates....

      When not spinning:

      • When i homing

      I enclose the content of my homing, in case it was something that was not right, but notice this same file, it has worked until the day before yesterday.

      homeall.g

      G91 ; relative mode
      G1 H1 Z30 F1000
      
      ; BLTouch
      M280 P0 S160           ; Precautionary alarm release
      M280 P0 S90            ; Ensure the pin is raised
      
      
      G91 ; relative mode
      G1 H1 X-500 Y500 F2000 ; coarse home X or Y
      G1 H1 X-300 ; coarse home X
      G1 H1 Y300 ; coarse home Y
      G1 X4 Y-4 F600 ; move away from the endstops
      G1 H1 X-10 ; fine home X
      G1 H1 Y10 ; fine home Y
      G90                     ; absolute positioning
      
      
      G1 X0 Y0 F2000 ; go to first probe point
      G30                 ; home Z by probing the bed
      
      G91                    ; relative positioning
      G1 Z5 F100             ; lift Z relative to current position
      G90                    ; absolute positioning
      

      I go try downgrade to stable version....

      Ideas welcome...

      I use these Firmware:

      Board: Duet 3 Mini 5+ (Mini5plus)
      Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.4.0rc1+1 (2022-02-10)
      Duet WiFi Server Version: 1.26

      peirofundefined fcwiltundefined 2 Replies Last reply Reply Quote 0
      • peirofundefined
        peirof @peirof
        last edited by

        One more thing....

        At the start of my homing.g, there are there 2 lines

        G91 ; relative mode
        G1 H1 Z30 F1000
        ...
        

        These Z30 moves, the not spining motor, DO it....

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

          @peirof

          The command G1 H1 Z30 F1000 suggests you have a Z axis endstop.

          Do you have a Z endstop?

          If you are just trying to insure the probe is clear of the bed, for homing X and Y, you should use a H2 parameter which doesn't expect an endstop.

          You generally want to avoid using the M280 command to raise the pin. The M401/M402 commands allow the firmware to keep track of the state of the pin. The M280 might put things out of sync.

          Frederick

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

          peirofundefined 1 Reply Last reply Reply Quote 0
          • peirofundefined
            peirof @fcwilt
            last edited by

            @fcwilt I use those lines, at the beginning of the Homeall, to separate the bed from the Hotend and that the BlTouch can be deployed without problems, since it happened to me in some test, that the bed was very close to the nozzle, and when I hit Home, no the BlTOuch was displayed correctly

            peirofundefined 1 Reply Last reply Reply Quote 0
            • peirofundefined
              peirof @peirof
              last edited by

              @peirof more news... I have downgraded... from version 3.4 beta, to 3.3. final. And when I pressed home, it tells me that Driver 2 has detected a "short to ground", with the previous firmware it didn't give me any errors

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

                @peirof I think some of the 3.4beta versions did not report short-to-ground errors other than in M122; but 3.4RC2 should.

                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

                peirofundefined 1 Reply Last reply Reply Quote 0
                • peirofundefined
                  peirof @dc42
                  last edited by

                  @dc42 wow.... on this occasion, it would have been of great help... that "short to ground" track has made me suspect the wiring, as it seems that it was....

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