CoreXY update to 3.3 gone Wrong
-
@gbusy24 what type of endstop switches are you using? If they are normally open switches, three-wire switches or Hall sensors then you probably need to invert the pin polarity in your M574 commands.
-
@fcwilt, It was one of the later 2.? FW versions, but it's been a while since I started this update and can't quite remember the exact one.
-
@dc42, I have mechanical end stop switches and I will give your suggestion a try. Had considered that might be my issue. I'll let you know how it goes. Thanks.
-
@gbusy24 said in CoreXY update to 3.3 gone Wrong:
@fcwilt, It was one of the later 2.? FW versions, but it's been a while since I started this update and can't quite remember the exact one.
Did you remember to first update to 3.0 before doing the update to 3.3?
Frederick
-
@fcwilt Yes.
-
@gbusy24 said in CoreXY update to 3.3 gone Wrong:
@fcwilt Yes.
The usual cause of what you are seeing when homing is that the endstop switches are indicating they are active when they are not. The G1 H1 moves never happen because the endstop reports active and the only moves that happen are the "back off" moves between the pairs of G1 H1 moves.
Frederick
-
@fcwilt And I go about correcting this how?
-
@gbusy24 Your current config for endstops:
; Endstops M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop M574 Z1 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop
See https://duet3d.dozuki.com/Wiki/M574. Test switches with M119. You probably want
; Endstops M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y2 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop M574 Z1 S1 P"!zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop
ie Add
!
to each endstop pin definition, to invert the input.Ian
-
@droftarts Aha! Let me try that. Thanks.
-
@droftarts Fabulous! that did it. Thanks
-
-