Problem with dual z



  • Hi, i have a problem with my new duet board. When i connect one Z-motor to ZA with the jumpers still attached it works just as it should. But when i remove the jumpers and connect the second motor to ZB both motors stops working. They are making a buzzing sound and they try to move back and forth. But they are not spinning. https://imgur.com/a/IRHDlpV here is the wiring, it's hard to see the first connector but they are wired the same as ZB (notice the gray wire is the black one from the motor).

    My Drive config looks like this
    ; Drives
    M569 P0 S1 ; Drive 0 goes forwards
    M569 P1 S1 ; Drive 1 goes forwards
    M569 P2 S1 ; Drive 2 goes forwards
    M569 P3 S1 ; Drive 3 goes forwards
    M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
    M92 X80 Y80 Z400 E420 ; Set steps per mm
    M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
    M203 X6000 Y6000 Z30 E1200 ; Set maximum speeds (mm/min)
    M201 X500 Y500 Z250 E250 ; 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

    What am I missing?



  • Forgot to post the firmware versions.

    Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
    Firmware Electronics: Duet WiFi 1.02 or later
    Firmware Version: 1.21 (2018-03-21)
    WiFi Server Version: 1.21
    Web Interface Version: 1.20


  • administrators

    It may mean that you have high inductance motors that won't work in series unless you use 24V power. If that is the case then you should connect both motors in parallel to just one connector. Or, if you are not using the E1 motor output, you can connect one of them to that connector and add this line to config.g, before any M350 or M906 commands:

    M584 X0 G1 S2:4 E3

    If you can tell us the model number of your Z stepper motors, we can tell you if this is the reason for the problem.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.