Y axis homes in correct direction, but moves in wrong direction
This is a slight problem I have been having.
On my printer, all other axis/motors are performing correctly, it is just the Y axis.
In the configuration, it is set to be a Min Endstop (M574 Y1 S1), and the motor needed to be reversed (M569 P1 S0). This cause the homing to work perfectly - it homes to the same location (front left).
However, and this is where it gets strange, when I use any of the jog commands, the movement is completely inverted: I can't command it to move a negative amount (since it just homed), but commanding it to move a positive amount (away from the endstop), causes it to simply ram the head further into the endstop. After having rammed it into the endstop (skipping steps), I am able to command negative values, and it then moves away from the endstop.
Just for completeness, my relevant config code:
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S0 ; Drive 3 goes backwards
M574 X1 Y1 S1 ; Set active low endstops
Any idea what I am doing wrong?
I am using the latest stable versions for the DuetWifi, PanelDue and Duet Web Control.
Please run M208 to display the axis limits and report the results.
The M208 reports the following: Axis limits - X: 0.0 min, 310.0 max, Y: 0.0 min, 210.0 max, Z: 0.0 min, 210.0 max
These limits are slightly more than what the printer physically can do, so that I can get the actual while jogging the printer to the maximums.
That looks OK. Please post your complete config.g file and your homeall.g and homey.g files. Where is the Y endstop switch located?
Kezat last edited by
If i remember correctly my default Homeall.g came with positive homing moves that i had to change to negative, could it be that you have the axis inverted and also have the homing backwards?
I found it: while looking through the code to paste, I checked the homey.g file, and noticed that for some reason, when moving in the Y direction, it is not negative the maximum. So it was like Kezat said, it homed backwards and was inverted.
Undoing the invert fixed the issue.
Thank you for the help.
When starting this thread I knew it was something small and simple that just did not want to work, but it is getting late here.