Coordinate issues after attempted upgrade from RRF1.18 to 3.5

[bens95]

I have a printer that used to use a modified RRF1.18 as it's firmware on a duet 2 ethernet. The manufacturer never released an update so I decided to try my hand at wiping and converting the firmware/config to RRF3.5. I am making decent progress, but for some reason my printer is making diagonal moves when given (for example) G1 H2 X100.

• I used the config tool as a baseline for my config. I based my inputs on what is in the old RRF1.18 config.g file, so something could be wrong
• The motors are plugged in and functioning fine to the best of my knowledge. I verified this in a number of ways:
• • After making a move, both motors do not rotate and are clearly magnetically locked
• • While moving in the X coordinates, one motor does not try to move at all, the opposite motor moves for Y coordinates (verified by holding lightly with finger)
• Here is the relevant section of config before my upgrade:

; Machine configuration
M569 P0 S1							; Drive 0 goes forwards
M569 P1 S0							; Drive 1 goes backwards
M569 P2 S0							; Drive 2 goes backwards
M569 P3 S0							; Drive 3 goes backwards
M569 P4 S0							; Drive 4 goes backwards
M574 X1 Y1 Z2 S1					; set endstop configuration
M667 S1								; set CoreXY mode

• here is the relevant section of config after my upgrade

 
; Smart Drivers
M569 P0 S1 D2 ; driver 0 goes forwards (X axis)
M569 P1 S0 D2 ; driver 1 goes backwards (Y axis)
M569 P2 S0 D2 ; driver 2 goes backwards (Z axis)
M569 P3 S0 D2 ; driver 3 goes backwards (extruder 0)
 
; Axes
M584 X0 Y1 Z2 ; set axis mapping
 
; Kinematics
M669 K1 ; configure CoreXY kinematics

• I did verify that nothing is plugged in to drive 4 motor. Not sure why it has a direction in the original config
• here is my m669 output

M669
Kinematics is CoreXY, no segmentation, matrix:
1.00 1.00 0
1.00 -1.00 0
0 0 1.00

What have I missed?

[fcwilt]

@bens95

Hi,

Did you read this?

https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_coreXY

It tells you what to do in each case where XY movements are not correct.

Frederick

[bens95]

@fcwilt I have now... I made two mistakes. The first was using G1 H2 and thinking it was G1 H1. Getting diagonal movements expecting horizontal sent me on a wild goose chase. The other is as mentioned in the article; 1.18 has inverted motor directions... but I hadnt even gotten there yet. All is well. Thank you!