Duet 2 wifi CR10 end stops not working
-
@Smedley said in Duet 2 wifi CR10 end stops not working:
As for the TEST
X triggers YES
Y. triggers. YESIt's a bit confusing: are your endstops X and Y working or not??
Triggers Yes would mean they are working. If they trigger as LEDs, do they also are marked triggered in PanelDue/Duet Web Control DWC?I didn't ask to change anything. But please check the endstops: is it a normal open - close endstop and is it of type NO or NC? NO means normal open, i.e. if not triggered it is open, no current flows. NC means normal closed, if not triggered current flows (no resistance). From the type of endstops it depends how the configuration must be made.
-
If the LEDs on the board are changing when you click the switch that at least proves an electrical connection.
Though it's odd that the motors continue to move even though they hit the endstops. If the endstop status indicates triggered yes already before being depressed they should not move at all because the endstop is already triggered.
The only thing to change with the endstop config is the S parameter.
You have:
M574 X1 Y1 S1 ; set active high endstops
Please try:M574 X1 Y1 S0 ; set active LOW endstops -
I was referring to the test above I was asked to run from the MODERATOR.
That is why the wires were plugged in for the Z stop.I am sorry for the confusion. Did not realize I was working with two different people trying to help me.
x and y are not working. The test proved that they are wired correctly and tripping the board.
-
@Smedley do you have some electronic instrument to verify that the endstops are working? Or please post a photo, maybe we know the type and see what could be wrong.
(after the tests of Phaedrux)No problem about the confusion. Better two people help you than noone
-
Now X and Y move a couple of inches and stop. They do not go to the end stop switch. Each time I run home all they stop in a different place each time. I do a EMERGENCY STOP so Z does not hit the bed. If I run home all they will move a couple of inches from were they stopped for the last time I ran home all.
The Z comes down all the way to the bed. I under stand the Z is not set yet.
-
@Phaedrux said in Duet 2 wifi CR10 end stops not working:
M574 X1 Y1 S1
Ok then M574 X1 Y1 S1 was correct.
Are you using homeall or the individual homing files?
Can you confirm that your motor directions are correct?
-X should move to the left, +x to the right
-y moves the nozzle to the front of the bed, +Y moves it to the back.Where are the endstops physically located?
-
X+10 will move to the right each time all the way to the end.
X-10 will move to the left only to the middle of the bed.
Y+10 will move the past the back
Y-10 will move half way to the front of the bed. -
@Phaedrux said in Duet 2 wifi CR10 end stops not working:
Where are the endstops physically located?
-
It doesn't make it all the way to the end because it doesn't know where it actually is yet.
-
@Phaedrux
The switch for X is on the left side and if you home x it goes to the right a couple of inches and stops. It will not move to the switch.The Y switch is in the back. if I home Y the bed goes forward.
Before we changed HIGH to LOW they move to the switch and did not stop. Now they go away from the switch a couple of inches. And will not let me move them all the way to the switch with the Machine Movement on the screen.
-
@Smedley could you please make a M122 and show it?
-
@Smedley said in Duet 2 wifi CR10 end stops not working:
Now they go away from the switch a couple of inches.
That is the back off movement in the homing files. It still seems to think your endstops are triggered even when they are not.
Can you post a photo of the endstop switch itself? I'm assuming they are the creality endstop switches?
Posting M122 will let us verify your firmware version and hardware.
-
Perhaps a video to show what's going on? Sometimes being able to see the actual behaviour helps a lot.
-
@Phaedrux
I just put the X all the way from the switch. Hit home x it went to the switch move a way from the switch and the move back to the switch and did not stop. Basically it hit the switch and bounced and then went back to the switch and would not stop running the motor at the end stop. -
@Smedley the behaviour would be explainabe if you have firmware below 2.01 because then homing G1 H1 must be G1 S1 and H2 must be S2, but please make M122.
-
Please post the results of M122, your current config.g, and homeall.g
-
@Phaedrux
Ok I will. It is very flake. -
@Phaedrux
config.g no M122
homeall.g. no M122 -
What does that mean?
-
@Smedley he means please call M122 in the send g- code field. Some statistics are shown then. Please post them.
