Endstop on one of the axis all time on hit state

ebaday

David, thanks for the answer.

I read the wiki before.

I do not think that the problem is in the endpoints themselves. I changed them in a circle and the problem always remains on the Z axis.

In order to completely eliminate the problems with the endstops, I decided to simply simulate them with two wires. Unfortunately, the opening and closing of the wires did not affect the status of the program trigger.

I also came to the conclusion that the remap of the motors between the axes in the firmware does not lead to a remap of the terminal endstops. Moreover, I did not find in the firmware to make endstops remap.

Do I need re-compile firmware for endstop remap?

dc42

Remapping motors with M584 does not remap the endstops. Your Z endstop must be connected to the Z endstop connector even if you have connected the Z motor to a different motor output.

Shorting the two outer pins of the Z endstop connector together should change the status from triggered to not-triggered in both M119 and in the Machine Properties page of DWC. Did you do that test?

All the endstop inputs are tested before a Duet leaves the factory, but it is not impossible for a fault to develop subsequently. In the case of the Z endstop input, if the endstop LED is working then the most likely cause of such a fault would be resistor R58 missing, cracked or not properly soldered.

ebaday

Shorting the two outer pins of the Z endstop connector together should change the status from triggered to not-triggered in both M119 and in the Machine Properties page of DWC. Did you do that test?

Yes, I checked it. Unfortunately, the state of the trigger did not change, so I wanted to pimp the pins to the neighboring endstop.

Also, I measured the voltage on the outer pins of all the endstops and found out that on the pins of the Z axis, the voltage is below 1.8V. On all the others it is 3.2-3.3V.

Apparently there is a faulty component on the board.

ebaday

@dc42 said in Endstop on one of the axis all time on hit state:

In the case of the Z endstop input, if the endstop LED is working then the most likely cause of such a fault would be resistor R58 missing, cracked or not properly soldered.

R58 on the place and has ~1kOm

dc42

Does the Z endstop LED light up (like the X and Y ones) when the endstop is plugged in but not triggered?

ebaday

@dc42 said in Endstop on one of the axis all time on hit state:

Does the Z endstop LED light up (like the X and Y ones) when the endstop is plugged in but not triggered?

Yes, LED light up when endstop is plugged in and not triggered and it’s light off when endstop triggered but M119 and DWC everytime stay in endstop hit.

When I check R58 I noticed that the inductance L3 looks suspicious, but I have no idea how it can affect the Z end-stop only.

dc42

Please connect the two outer pins of the Z endstop connector on the Duet together and check the reading in M119 or DWC machine properties. The LED should light and the endstop status should be "not triggered". Also send M574 without parameters and check that the Z endstop setting reads the same as X and Y (i.e. active high input).

If the M574 parameters read the same for all endstops but the status reads as "triggered" with the outer pins shorted together, then please ask your supplier to replace your Duet under warranty.

ebaday

@dc42 said in Endstop on one of the axis all time on hit state:

Please connect the two outer pins of the Z endstop connector on the Duet together and check the reading in M119 or DWC machine properties. The LED should light and the endstop status should be "not triggered". Also send M574 without parameters and check that the Z endstop setting reads the same as X and Y (i.e. active high input).

Already try to do that. No good news.

please ask your supplier to replace your Duet under warranty.

It will be difficult. The duet2 plate was a gift.

Will try to replace L3 and check again.

dc42

L3 has nothing to do with the endstop circuit.

I guess it's quite an old Duet because R58 is 10K in revision 1.03 or later. The other thing you could check is that pin 108 of the ATSAM4E chip looks properly soldered.

ebaday

Yes, it is version 1.02 and judging by the scheme with github the value of this resistor should be 1kOm. I checked for adjacent on the X and Y axes they are the same. Printer is out of reach, try to ping the line from 108 feet to C42 tomorrow.

Thanks in advance, David!

ebaday

@dc42
The problem was poorly soldered 108 pin. Soldered it yourself and checked under a microscope. Hope this was the first and the last problem ;)))

David, thank you so much for your help!