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

    Z-Axis not homing

    Scheduled Pinned Locked Moved
    My Duet controlled machine
    3
    27
    1.1k
    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.
    • rickypilnikundefined
      rickypilnik
      last edited by

      Same as before. Z - Axis still not moving.

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

        And just to eliminate the homing files, If you send M564 S0 H0 to allow unhomed axis movement are you able to get the z motor to move by using the jogging buttons?

        And does it still produce the short to ground error message?

        Z-Bot CoreXY Build | Thingiverse Profile

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

          Can you also send M122 in the console and post the response?

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • rickypilnikundefined
            rickypilnik
            last edited by

            No I can't move the Z-axis, but x and y are fine even with the message of short to drivers from before.

            m122
            === Diagnostics ===
            RepRapFirmware for Duet 2 Maestro version 3.1.1 running on Duet Maestro 1.0
            Board ID: 08DJM-9X66L-LG3SN-6JKDL-3S06Q-K8X6P
            Used output buffers: 3 of 24 (10 max)
            === RTOS ===
            Static ram: 21924
            Dynamic ram: 92804 of which 52 recycled
            Exception stack ram used: 392
            Never used ram: 15900
            Tasks: NETWORK(ready,472) HEAT(blocked,1324) MAIN(running,1996) IDLE(ready,84)
            Owned mutexes:
            === Platform ===
            Last reset 00:01:06 ago, cause: power up
            Last software reset at 2020-05-20 19:20, reason: User, spinning module GCodes, available RAM 16096 bytes (slot 3)
            Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
            Error status: 0
            MCU temperature: min 32.7, current 35.3, max 35.5
            Supply voltage: min 0.0, current 15.4, max 15.7, under voltage events: 0, over voltage events: 0, power good: yes
            Driver 0: standstill, read errors 0, write errors 0, ifcount 9, reads 2644, timeouts 0
            Driver 1: standstill, read errors 0, write errors 0, ifcount 9, reads 2644, timeouts 0
            Driver 2: short-to-ground, read errors 0, write errors 0, ifcount 9, reads 2644, timeouts 0
            Driver 3: standstill, read errors 0, write errors 0, ifcount 7, reads 2646, timeouts 0
            Driver 4: standstill, read errors 0, write errors 0, ifcount 6, reads 2647, timeouts 0
            Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 2653
            Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 2652
            Date/time: 2020-05-20 19:32:27
            Slowest loop: 10.29ms; fastest: 0.12ms
            I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
            === Storage ===
            Free file entries: 9
            SD card 0 detected, interface speed: 15.0MBytes/sec
            SD card longest read time 2.6ms, write time 0.0ms, max retries 0
            === Move ===
            Hiccups: 0(0), FreeDm: 168, MinFreeDm: 168, MaxWait: 26403ms
            Bed compensation in use: none, comp offset 0.000
            === MainDDARing ===
            Scheduled moves: 14, completed moves: 13, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
            === AuxDDARing ===
            Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
            === Heat ===
            Bed heaters = 0 -1, chamberHeaters = -1 -1
            === GCodes ===
            Segments left: 0
            Movement lock held by HTTP
            HTTP is idle in state(s) 1 8, running macro
            Telnet is idle in state(s) 0
            File is idle in state(s) 0
            USB is idle in state(s) 0
            Aux is idle in state(s) 0
            Trigger is idle in state(s) 0
            Queue is idle in state(s) 0
            LCD is idle in state(s) 0
            Daemon is idle in state(s) 0
            Autopause is idle in state(s) 0
            Code queue is empty.
            === Network ===
            Slowest loop: 129.03ms; fastest: 0.02ms
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
            HTTP sessions: 1 of 8
            Interface state active, link 100Mbps full duplex

            Phaedruxundefined 1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator @rickypilnik
              last edited by

              @rickypilnik said in Z-Axis not homing:

              Supply voltage: min 0.0, current 15.4, max 15.7, under voltage events: 0, over voltage events: 0, power good: yes

              Does 15v sound correct for your power supply?

              @rickypilnik said in Z-Axis not homing:

              No I can't move the Z-axis, but x and y are fine even with the message of short to drivers from before.

              The short to ground message was only for driver 2, correct?

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • rickypilnikundefined
                rickypilnik
                last edited by

                Yes 15V sounds correct and the message is
                " Error: short-to-ground reported by driver(s) 2 "

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

                  Alright, I think we've established that the Z driver has failed unfortunately. Please hang on while I confer with DC42 in case he has any further ideas.

                  When and where did you purchase your Duet 3?

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • rickypilnikundefined
                    rickypilnik
                    last edited by

                    On the 5th May 2020, from E3D Online, and it's a Maestro

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

                      Ah yes, sorry, Maestro.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator @rickypilnik
                        last edited by

                        @rickypilnik said in Z-Axis not homing:

                        (changed all motor currents to 1875mA (max is 2.5A)

                        I think the reason I assumed it was a Duet 3 was because of this statement on motor current.

                        These motors may not be well suited to the Maestro as it's drivers are rated for 1.4a peak. The Duet wifi is 2.4a and the Duet3 6.3.

                        You'd have to run the drivers at full power to get close to 60% of the rated max for the motors. This will require actively cooling the driver chips.

                        If you send M906 in the console, what does it report back with?

                        Z-Bot CoreXY Build | Thingiverse Profile

                        rickypilnikundefined 1 Reply Last reply Reply Quote 0
                        • rickypilnikundefined
                          rickypilnik @Phaedrux
                          last edited by rickypilnik

                          @Phaedrux That is quite unfortunate to hear, but if I switch it to a duet 2 wifi you reckon things should be ok?

                          As in it should stop shorting to ground if I use a lower motor current on a different printer, say a CR-10 with motors that max out at 1.5A anyways.

                          Motor current (mA) - X:1875, Y:1875, Z:1875, E:1875, idle factor 30%

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

                            Yes a Duet2Wifi/Ethernet would be a much better match for those motors.

                            Z-Bot CoreXY Build | Thingiverse Profile

                            1 Reply Last reply Reply Quote 1
                            • rickypilnikundefined
                              rickypilnik
                              last edited by

                              So after all that, having switched boards around I think I found the underlying problem of this all......... A badly crimped factory connector on the Velleman..........AGHH
                              Anyway thanks for all your help you helped solve problems I wasn't even aware of yet!

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

                                Glad you got it figured out and the driver hasn't failed.

                                Z-Bot CoreXY Build | Thingiverse Profile

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