Posts made by 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!

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!

@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 Thanks!

@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.

@t3p3tony
Is it possible to put MPZ2012S221AT000 instead of BRL3225T1R0M on the board at 1.02? There is a suspicion that the inductance does not work, but the BRL3225T1R0M is not available in stores. Analogues in the same building could not find

Thanks in advance!

@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

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.

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?

Hi, I am new in duet world.
Three days ago I completed replace old MKS Sbase by Duet WIfi on Tevo Little monster.

There is one problem that I can not resolv. I can't homed delta because Z-axis endstop all time said triggered state and carriage don't move. But I can manuly move Z-axis via G1 commands.

In this case, the electronics of the board and the LED on endstop indicate that no operation is triggered. With the coin test, the endstop is triggered(LED on both side off) , but the state in the microcode (GCODE M119) does not change:

Endstops: X: not stopped; Y: not stopped; Z: at max stop; Z probe: not stopped.

I tried to replace the wires, replace the optical sensor, switched Z-motor to E1. Nothing helps.

0_1534550259927_config.g

config.g in attachment. I don't know what I can to do yet.

Firmware: 2.01
DuetWifi: 1.02

Can you help me?