problem with switching to seperate Z axis drivers



  • i am trying to switch from 2 motors in series on the Z driver to 2 serperate drivers on my cr10 with duet wifi.
    i've connected the motors to the Z driver and to E1 and set it up in the config file but when moving the Z axis it just vibrates. i plugged the X axis into the z motor to confirm the motors are ok and this works as it should rulling out defect motors.

    can someone check if this file is correctly set up?

    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"cr10" ; set printer name

    ; Drives
    M569 P0 S0 ; physical drive 0 goes backwards
    M569 P1 S0 ; physical drive 1 goes backwards
    M569 P2 S0 ; physical drive 2 goes backwards
    M569 P3 S0 ; physical drive 3 goes backwards
    M569 P4 S0 ; physical drive 4 goes backwards

    M584 X0 Y1 Z2:4 E3 ; two Z motors connected to driver outputs Z and E1
    M671 X-20:520 Y0:0 S0.5 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis
    M208 X0:450 Y0:400 ; X carriage moves from 0 to 450, Y bed goes from 0 to 400

    ; Axis Limits
    M208 X0 Y0 Z0 S1 ; set axis minima
    M208 X450 Y400 Z400 S0 ; set axis maxima

    M92 X80.00 Y80.00 Z400.00 E476.50 ; set steps per mm
    M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
    M566 X300.00 Y300.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X3600.00 Y3600.00 Z900.00 E1200.00 ; set maximum speeds (mm/min)
    M201 X300.00 Y300.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
    M906 X900 Y1200 Z900 E700 I50 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Endstops
    M574 X1 Y1 S1 ; set active high endstops
    M574 Z1 E1 S1 ; set endstops controlled by probe

    ; Z-Probe
    M558 P8 I0 R0. 4 F300 X0 Y0 Z0 ; set Z probe (digital mode, NO/NC, delay, speed, not used as axis endstop)
    G31 X0 Y0 Z-0.1 P100 ; set Z probe trigger value, offset and trigger height
    M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
    M557 X50:400 Y50:350 S20 ; define mesh grid

    ; Heaters
    M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
    M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0
    M143 H0 S75 ; set temperature limit for heater 0 to 75C
    M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
    M143 H1 S230 ; set temperature limit for heater 1 to 230C

    ; Fans
    M106 P0 S0 I1 F25000 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off

    ; Tools
    M563 P0 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
    M564 H0 ; Allow movement before homing

    any help is appreciated,

    jeff



  • i forgot to add that before i made the switch i changed to the latest stable firmware on the duet as well as the browser, i dont know if that has any influence?

    jeff


  • Moderator

    If you send M906 in the gcode console, what does it reply?



  • @Phaedrux said in problem with switching to seperate Z axis drivers:

    If you send M906 in the gcode console, what does it reply?

    Thanks for your help, it replies with the correct values:
    M906 X900 Y1200 Z900 E700 I50

    It is also at 100% current.

    Jeff


  • Moderator

    I think you're going to need to add the second Z driver to your M906 command because right now I think it may be using the motor current for the extruder.

    Try M906 X900 Y1200 Z900:900 E700 I50



  • @Phaedrux said in problem with switching to seperate Z axis drivers:

    I think you're going to need to add the second Z driver to your M906 command because right now I think it may be using the motor current for the extruder.

    Try M906 X900 Y1200 Z900:900 E700 I50

    i tried as you suggested, the issue remains the same, it just makes a bunch of noise and does not turn.
    Using a different motor makes the same noise with no spinning of the motors.

    one thing i noticed is that after i tried to move the Z axis one side is resisting movement while the other side is spinning easily.

    i dont know what changed to cause this behaviour, i only took the plug from the second Z connection and placed it onto the E1 connection and then used the jumpers on the Z connection.
    besides that i updated the firmware but i dont think that would make a difference?

    jeff


  • administrators

    @Phaedrux said in problem with switching to seperate Z axis drivers:

    I think you're going to need to add the second Z driver to your M906 command because right now I think it may be using the motor current for the extruder.

    Try M906 X900 Y1200 Z900:900 E700 I50

    That's not needed, but the M906 command does need to come after the M584 command in config.g (which it already is).


  • Moderator

    @Twigz said in problem with switching to seperate Z axis drivers:

    i plugged the X axis into the z motor to confirm the motors are ok and this works as it should rulling out defect motors.

    Can you describe your test a little more? Which motor did you connect to which driver?



  • @Phaedrux said in problem with switching to seperate Z axis drivers:

    @Twigz said in problem with switching to seperate Z axis drivers:

    i plugged the X axis into the z motor to confirm the motors are ok and this works as it should rulling out defect motors.

    Can you describe your test a little more? Which motor did you connect to which driver?

    the X axis motor is close to the left Z axis motor, so i switched the connectors around so an input on the X axis would result into a movement on the Z axis and visa versa.

    The result is when i try to move the X axis via the webpage it moves up and down without any issue. no vibration and no weird noises.
    On the other hand the X axis then displays the same issue where it vibrates but does not move.

    jeff


  • administrators

    What happens if you connect the Z motors back to the Za and Zb connectors, then connect the X motor to the E1 connector, and change the M584 command to:

    M584 X4 Y1 Z2 E3

    Does the X axis move normally?



  • @dc42 said in problem with switching to seperate Z axis drivers:

    What happens if you connect the Z motors back to the Za and Zb connectors, then connect the X motor to the E1 connector, and change the M584 command to:

    M584 X4 Y1 Z2 E3

    Does the X axis move normally?

    i just tried connecting driver E1 to the X axis and it has the same result. connecting it back to Za and Zb also doesn't work anymore and gives the same result.

    jeff



  • @Twigz said in problem with switching to seperate Z axis drivers:

    @Phaedrux said in problem with switching to seperate Z axis drivers:

    @Twigz said in problem with switching to seperate Z axis drivers:

    i plugged the X axis into the z motor to confirm the motors are ok and this works as it should rulling out defect motors.

    Can you describe your test a little more? Which motor did you connect to which driver?

    the X axis motor is close to the left Z axis motor, so i switched the connectors around so an input on the X axis would result into a movement on the Z axis and visa versa.

    The result is when i try to move the X axis via the webpage it moves up and down without any issue. no vibration and no weird noises.
    On the other hand the X axis then displays the same issue where it vibrates but does not move.

    jeff

    If I've read that correctly, it's the motor or the wiring between the Duet board and the motor. Possibly a bad crimp?



  • @deckingman said in problem with switching to seperate Z axis drivers:

    @Twigz said in problem with switching to seperate Z axis drivers:

    @Phaedrux said in problem with switching to seperate Z axis drivers:

    @Twigz said in problem with switching to seperate Z axis drivers:

    i plugged the X axis into the z motor to confirm the motors are ok and this works as it should rulling out defect motors.

    Can you describe your test a little more? Which motor did you connect to which driver?

    the X axis motor is close to the left Z axis motor, so i switched the connectors around so an input on the X axis would result into a movement on the Z axis and visa versa.

    The result is when i try to move the X axis via the webpage it moves up and down without any issue. no vibration and no weird noises.
    On the other hand the X axis then displays the same issue where it vibrates but does not move.

    jeff

    If I've read that correctly, it's the motor or the wiring between the Duet board and the motor. Possibly a bad crimp?

    i dont think it is the motor as they do work on other drivers, i didn't touch any cables but i will check the cables and see if they are alright.

    edit: i think you're onto somthing, i now used the x axis wiring on E1 and this works flawlessly.
    placing both Z axis motors on Za and Zb again now works and moves the z axis but is just very noisy, getting closer
    jeff



  • @deckingman said in problem with switching to seperate Z axis drivers:

    @Twigz said in problem with switching to seperate Z axis drivers:

    @Phaedrux said in problem with switching to seperate Z axis drivers:

    @Twigz said in problem with switching to seperate Z axis drivers:

    i plugged the X axis into the z motor to confirm the motors are ok and this works as it should rulling out defect motors.

    Can you describe your test a little more? Which motor did you connect to which driver?

    the X axis motor is close to the left Z axis motor, so i switched the connectors around so an input on the X axis would result into a movement on the Z axis and visa versa.

    The result is when i try to move the X axis via the webpage it moves up and down without any issue. no vibration and no weird noises.
    On the other hand the X axis then displays the same issue where it vibrates but does not move.

    jeff

    If I've read that correctly, it's the motor or the wiring between the Duet board and the motor. Possibly a bad crimp?

    i went ahead and replaced the cables today and that resolved the issue. i don't know how the cables went bad but either way its fixed.
    Thanks a lot to you and others for the suggestions.

    jeff



  • @Twigz Pleased for you that the issue is resolved.


Log in to reply