All axis stop moving before hitting switches
-
@Gabell20 did you add T0 and run M98?
If you only get small movements and the endstops are ok, a wrong M92 would be possible but it's strange, because it looks ok.
When you make a G1 100, does it move the distance as expected or less?Can you check that the pulleys are correctly fixed on the stepper shafts?
-
@Gabell20 Have you entered in the DWC a M208 command to verify the min/max settings?
Frederick
-
@Gabell20 the
M566 X900.00 Y900.00 Z12.00 E120.00:120.00
Z value is very low, please trying to set 100 instead.Another possibility why the movement is so slow that the steppers are connected to different axes as you expect (extruder definition to X axis eg), please recheck the wiring and wiring diagram.
Is the printer a CoreXY? Then the config and homeall would be wrong.
-
@JoergS5 The x and y axes move how they should with a g1, Ive been trying all sorts of motion and it all seems sound mechanically, belts and pulleys are tight and in place.
-
@JoergS5 Its Cartesian, and I've unplugged the extruders for debugging. X Y and Z are all independent and wired up correctly.
-
@Gabell20 you described they move, but not to the endstops. Do you see a reason why the stop? And if you make only X or only Y movement, do they move to the endstops?
Isolated
G91
G1 H1 X-1000
e.g.Can you verify firmware version please, should be 3.1.1
-
@JoergS5 They don't move regardless if I home all or home one axis independently or directly with gcode, for example G91 G1 H2 X-500 will move very far and crash as expected, but G91 G1 H1 X-500 will move roughly 6 mm.
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later -
@Gabell20 said in All axis stop moving before hitting switches:
3.01-RC9
Please update to 3.1.1 by uploading this zip file
https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip
Just to confirm, the endstops are physically located X to the left and Y at the back?
Can you manually run each line of your homeall from the console?
-
@Gabell20 I am not aware of so serious bugs for the movement, but the general advice is to upgrade to 3.1.1
I checked, there were some error corrections between 3.01 beta 9 and 3.1.1, better upgrade first before proceeding.
-
Can you show photo of the endstops and the wiring?
-
@Phaedrux how do send images t the forum on mobile ?
-
@JoergS5 Cool, I have just upgraded
-
@Gabell20 and it's all working now ?
-
@JoergS5 no
this is not as related but my z is going the opposite way -
@Phaedrux The x switch is on the left and the y switch is mounted to the x carriage and triggers at the back.
-
Can you go through these steps to test endstop and motors before homing?
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39#s145
-
@Gabell20 when I imagine that your G1 H2 runs ok, but G1 H1 stops after a few mm, and you use NC endstop, is it possible that the movement triggers the endstop, by the movement eg? If the G1 H1 stops, does the DWC show the endstop triggered?
-
@Phaedrux That is helpful, but i followed along and the problem persists.
-
@JoergS5 that could be it, I noticed that sometimes under acceleration thy show up triggered, I wonder if I can makes the axes accelerate slower but only during homing.
-
@Gabell20 said in All axis stop moving before hitting switches:
I wonder if I can makes the axes accelerate slower but only during homing.
You certainly can. Just add a new acceleration command at the start of the homing file and then change it back to the previous value at the end.
