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

    New duet wifi board; Z driver not working.

    Scheduled Pinned Locked Moved
    General Discussion
    3
    6
    238
    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.
    • bluedust2undefined
      bluedust2
      last edited by

      I have just set up the board to test all the hardware is working and I can't get a motor running on the z driver. The z driver is also hot to touch while in idle. I have checked motors that work on the x,y,e0,e1 drivers and they don't work on the z driver.

      Is there anything else I can check?

      1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by

        are the jumpers installed on the second connector?

        1 Reply Last reply Reply Quote 0
        • bluedust2undefined
          bluedust2
          last edited by

          yes jumpers are on the zb connector.

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

            It sounds like a faulty driver, but please check the following:

            • Does the Z driver chip run hot even with no motor connected?
            • Have you checked that the Z motor connector pins on the underside of the Duet are not shorting against anything metallic underneath the Duet?
            • When you send M122, what status does it report for driver 2?

            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

            bluedust2undefined 1 Reply Last reply Reply Quote 0
            • bluedust2undefined
              bluedust2 @dc42
              last edited by

              @dc42 No shorting, I have it in an abs enclosure bottom half to keep it safe.

              The z driver chip was hot even when no motor was connected so I put a small heatsink on it, no improvement.

              M122
              === Diagnostics ===
              RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
              Board ID: 08DGM-917DA-G4MS4-6JTD2-3SN6N-TTXH9
              Used output buffers: 3 of 20 (7 max)
              === RTOS ===
              Static ram: 25524
              Dynamic ram: 98832 of which 0 recycled
              Exception stack ram used: 280
              Never used ram: 6436
              Tasks: NETWORK(ready,680) HEAT(blocked,832) MAIN(running,3844) IDLE(ready,200)
              Owned mutexes:
              === Platform ===
              Last reset 00:00:33 ago, cause: power up
              Last software reset at 2019-11-25 19:04, reason: User, spinning module GCodes, available RAM 6344 bytes (slot 2)
              Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
              Error status: 0
              Free file entries: 10
              SD card 0 detected, interface speed: 20.0MBytes/sec
              SD card longest block write time: 0.0ms, max retries 0
              MCU temperature: min 24.4, current 28.3, max 28.4
              Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
              Driver 0: standstill, SG min/max not available
              Driver 1: standstill, SG min/max not available
              Driver 2: standstill, SG min/max not available
              Driver 3: standstill, SG min/max not available
              Driver 4: standstill, SG min/max not available
              Date/time: 2019-11-25 23:31:05
              Cache data hit count 117292142
              Slowest loop: 5.81ms; fastest: 0.07ms
              I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
              === Move ===
              Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
              Scheduled moves: 0, completed moves: 0
              Bed compensation in use: none
              Bed probe heights: 0.000 0.000 0.000 0.000 0.000
              === Heat ===
              Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
              Heater 1 is on, I-accum = 0.0
              === GCodes ===
              Segments left: 0
              Stack records: 1 allocated, 0 in use
              Movement lock held by null
              http is idle in state(s) 0
              telnet is idle in state(s) 0
              file is idle in state(s) 0
              serial is idle in state(s) 0
              aux is idle in state(s) 0
              daemon is idle in state(s) 0
              queue is idle in state(s) 0
              autopause is idle in state(s) 0
              Code queue is empty.
              === Network ===
              Slowest loop: 15.83ms; fastest: 0.00ms
              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
              HTTP sessions: 1 of 8

              • WiFi -
                Network state is running
                WiFi module is connected to access point
                Failed messages: pending 0, notready 0, noresp 0
                WiFi firmware version 1.23
                WiFi MAC address 84:0d:8e:b2:f2:32
                WiFi Vcc 3.36, reset reason Turned on by main processor
                WiFi flash size 4194304, free heap 25720
                WiFi IP address 192.168.178.86
                WiFi signal strength -53dBm, reconnections 0, sleep mode modem
                Socket states: 0 0 0 0 0 0 0 0
              1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators
                last edited by

                I am sorry, if the Z driver gets hot with no motor connected to it, and nothing is shorting against the Z motor terminals, then the Z driver has failed. As your board is new and assuming it's a genuine Duet, you are entitled to a replacement under warranty, so please contact your supplier.

                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