Need to remap my corexy X axis to E1 motor

[totalitarian]

I suspect my X-axis driver is dying and want to remap it to use the E1 motor.

I tried this but now the X+10 moves X and Y and Y+10 does exactly the same

[c]M584 X4 Y1 Z2 E3;[/c]

; Configuration file for Duet WiFi (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sun Dec 10 2017 14:24:02 GMT+0000 (GMT Standard Time)
 
; General preferences
M584 X4 Y1 Z2 E3;
 
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
 
M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y275 Z300 S0 ; Set axis maxima
 
; Endstops
M574 X1 Y2 Z1 S0 ; Set active high endstops
 
; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
 
M92 X80 Y80 Z1120 E400 ; Set steps per mm
M350 X16 Y16 I1 ; Configure microstepping with interpolation
M350 Z16 E16 I0 ; Configure microstepping with interpolation
M566 X1000 Y1000 Z200 E400 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z2400 E24000 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z10 E400 ; Set max accelerations (mm/s^2)
M204 P1200.000 T1600.000 R800.000 ; more acceleration
M906 X1050 Y1050 Z1050 E840 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
 
; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C
 
; Tools
M563 P0 D0 H1 F2; 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
 
; Network
M550 PGecko ; Set machine name
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S1 ; Enable FTP
M586 P2 S1 ; Enable Telnet
 
; 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
M106 P2 S0 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off
 
; Custom settings are not configured
 
; Miscellaneous
T0 ; Select first tool
 
;BLTouch
M307 H3 A-1 C-1 D-1 ;
M558 P5 X0 Y0 Z1 H5 F320 T6000; F probe speed - T Travel speed
G31 X30 Y5 Z0.6 P25
;INCREASE VALUE WILL LOWER NOZZLE CLOSER TO THE BED, DECREASE THIS VALUE WILL RAISE THE NOZZLE FROM THE BED
M557 X40:260 Y40:260 S55   ; probe from X=20 to 280, Y=20 to 280mm with a mesh spacing of 65mm
M501
 

[deckingman]

If all you've done is move the connector and then re-map the drive, then you probably need to reverse the motor direction for the drive that you have just moved using M569. You are quite sure that you didn't update the firmware from an earlier version than 1.19 at the same time yes? To be safe, follow the instructions here https://www.duet3d.com wiki/Configuring_RepRapFirmware_for_a_CoreXY_printer

Edit….......or it could be a bad crimp on the stepper connector that got dislodged when the plug was moved.

[totalitarian]

I have updated, but why would that matter?

[dc42]

The M584 command can be after the M569 commands in config.g, must be before other commands that apply to drivers such as M906 and M350. Otherwise those commands won't be applied to the new X motor driver.

[deckingman]

@totalitarian:

I have updated, but why would that matter?

Because the release notes say this:

Important! On a CoreXY machine, if upgrading from a version prior to 1.19beta9, you need to reverse the Y motor direction in the M569 command. Similarly for CoreXYU machines.

[totalitarian]

Ah I see, sorry I was already on 1.19 and went to 1.20rc1.

[totalitarian]

@dc42:

The M584 command can be after the M569 commands in config.g, must be before other commands that apply to drivers such as M906 and M350. Otherwise those commands won't be applied to the new X motor driver.

It's at the top, so is that OK?

[deckingman]

@totalitarian:

@dc42:

The M584 command can be after the M569 commands in config.g, must be before other commands that apply to drivers such as M906 and M350. Otherwise those commands won't be applied to the new X motor driver.

It's at the top, so is that OK?

Your config.g looks fine to me. Are you still having problems? If so check movement as per the link I posted. If only one motor turns, movement will be at 45 degrees. Going back to your original post, I note that you suspected that your X axis driver was dying. Maybe it's the motor or wiring and not the driver? But then, what was happening that made you suspect a faulty driver?

[totalitarian]

Sorted it. Plugged the motor into the wrong socket!!!

[deckingman]

@totalitarian:

Sorted it. Plugged the motor into the wrong socket!!!

Oops! We've all done similar but it take real man to admit it.