troubleshooting Duet2 WiFi Z driver



  • Hi all, i recently purchased a Duet2 Wifi and Duet 5 and have got to the point of testing motors through macros. the Z motors I have work fine on any other output on the duet2 wifi board but I get absolutely nothing out of the Z. the driver chip gets warm to the touch but no power out?
    any help appreciated!


  • Moderator

    Any error messages in the gcode console?
    Can you post your config.g?
    Are these dual Z motors or just one? If just one are the jumpers installed on the second Z port?
    When and where did you purchase it?



  • @Phaedrux
    i was just running it with the basic setup with jumpers. set up through the reprap configurator.

    ; Configuration file for Duet WiFi (firmware version 2.03)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Mon Apr 20 2020 19:29:39 GMT-0700 (Pacific Daylight Time)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"printer who shall be named" ; set printer name

    M667 S1 ; select CoreXY mode

    ; Network
    M551 P"" ; set password
    M552 S1 ; enable network
    M586 P0 S1 ; enable HTTP
    M586 P1 S0 ; disable FTP
    M586 P2 S0 ; disable Telnet

    ; Drives
    M569 P0 S1 ; physical drive 0 goes forwards
    M569 P1 S1 ; physical drive 1 goes forwards
    M569 P2 S1 ; physical drive 2 goes forwards
    M569 P3 S1 ; physical drive 3 goes forwards
    M584 X0 Y1 Z2 E3 ; set drive mapping
    M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
    M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm
    M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
    M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X0 Y0 Z0 S1 ; set axis minima
    M208 X610 Y838 Z458 S0 ; set axis maxima

    ; Endstops
    M574 Z1 S0 ; set active low and disabled endstops
    M574 X1 Y1 S3 ; set endstops controlled by motor stall detection

    ; Z-Probe
    M558 P5 R0.4 H5 F1200 T6000 ; set Z probe type to effector and the dive height + speeds
    G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
    M557 X15:600 Y15:810 S60 ; define mesh grid

    ; Heaters
    M305 P0 X500 R4700 ; configure PT1000 for heater 0
    M143 H0 S185 ; set temperature limit for heater 0 to 185C
    M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
    M143 H1 S280 ; set temperature limit for heater 1 to 280C

    ; Fans
    M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

    ; Tools
    M563 P0 S"test tool" D0 H1 F0 ; define tool 0
    G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
    G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

    ; Custom settings are not defined


  • Moderator

    @koda2216 said in troubleshooting Duet2 WiFi Z driver:

    M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm

    Are you sure that 4000 steps per mm is correct for your z axis arrangement?



  • @Phaedrux
    purchased through filastruder april 16th



  • @Phaedrux
    no, but its also not set built completely yet, this was just a bare motor not connected to anything. they are the super whopper motors they work on other outputs using the "M584 X0 Y1 Z3:4:5:6" and running "g1 s2 z100 f3000"


  • Moderator

    Please try 400 for the steps per mm with the motor connected to the Z driver just to eliminate any issues arising from using such a high steps per mm (like stalling).



  • is there a way to verify that it took my config.g file with the changed steps? new config.g file. ran code
    g91
    g1 s2 z100 f3000

    no movement

    new code uploaded through dwc.

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"printer who shall be named" ; set printer name

    M667 S1 ; select CoreXY mode

    ; Network
    M551 P ; set password
    M552 S1 ; enable network
    M586 P0 S1 ; enable HTTP
    M586 P1 S0 ; disable FTP
    M586 P2 S0 ; disable Telnet

    ; Drives
    M569 P0 S1 ; physical drive 0 goes forwards
    M569 P1 S1 ; physical drive 1 goes forwards
    M569 P2 S1 ; physical drive 2 goes forwards
    M569 P3 S1 ; physical drive 3 goes forwards
    M584 X0 Y1 Z2 E3 ; set drive mapping
    M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
    M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
    M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
    M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout


  • Moderator

    You can send most gcodes without any parameters in the console and it will report back with the currently used values.

    Can you also send M122 and post the result?



  • @Phaedrux
    8:25:00 PMM122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later + DueX5
    Board ID: 08DLM-996RU-N8PS0-7JKDG-3S46S-TV93N
    Used output buffers: 3 of 24 (16 max)
    === RTOS ===
    Static ram: 25680
    Dynamic ram: 94168 of which 396 recycled
    Exception stack ram used: 332
    Never used ram: 10496
    Tasks: NETWORK(ready,660) HEAT(blocked,1236) DUEX(suspended,156) MAIN(running,3756) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:10:52 ago, cause: software
    Last software reset at 2020-05-19 20:14, reason: User, spinning module GCodes, available RAM 10516 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 8
    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 43.1, current 43.7, max 43.8
    Supply voltage: min 24.1, current 24.2, max 24.4, 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
    Driver 5: standstill, SG min/max not available
    Driver 6: standstill, SG min/max not available
    Driver 7: standstill, SG min/max not available
    Driver 8: standstill, SG min/max not available
    Driver 9: standstill, SG min/max not available
    Date/time: 2020-05-19 20:24:59
    Cache data hit count 2545255665
    Slowest loop: 2.94ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves: 1, completed moves: 1, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === 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: 201.13ms; fastest: 0.08ms
    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 1
      WiFi firmware version 1.23
      WiFi MAC address bc:dd:c2:31:a3:a5
      WiFi Vcc 3.39, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 22824
      WiFi IP address 10.0.0.10
      WiFi signal strength -76dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0

  • Moderator

    Do you have 4 motors connected, or just the one?

    I'm thinking your Z driver may not be working unfortunately.

    You say the motors work on 3:4:5:6 but not 2?

    And you've tried another motor on 2?



  • @Phaedrux
    I have 4 z motors they work on drives 3:4:5:6 when I run the command m584 x0 y1 z3:4:5:6. no matter what I do even with jumpers and running the command m584 x0 y1 z2 I get nothing. just the driver chip gets hot but no movement.


  • Moderator

    Understood. Please hang on while we see if DC42 has any other ideas.


  • administrators

    I agree, I think the Z driver has failed, and I approve a warranty replacement.



  • @dc42 thank you guys for your help!


Log in to reply