Can not home z and y

JoergS5

@Finnls this looks ok.

If you trigger the endstops manually (with the finger), does it show triggered correctly, for the right axes?

Finnls

Yes the do.

G1 H1 X-1005 Y-505 F1800 - do not move y
G1 H2 X5 Y5 F1000 - do move y

I have run homeall.g ono by one in console

JoergS5

@Finnls said in Can not home z and y:

G1 H1 X-1005 Y-505 F1800 - do not move y

what do you mean by "do not move y", it only moves X? With cartesian, both axes should move until both endstops are hit. Like described in https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_The_homeall_g_file

But you can test split command of course:
G1 H1 X-1005 F1800
G1 H1 Y-505 F1800

The M574 S1 with ! means normally open switches, is this correct?

Finnls

When I send G1 H1 Y-505 F1800 - Y moves between 1 to 6-7 mm and stops.

But Y is 0.0 in status.

My endstops are micro sw 2wire, one to gnd, and one to in

JoergS5

@Finnls looks like the Y endstop is activated immediately, maybe it's of type NC (normally closed) and you need to remove the ! in the M574 for Y.

Or a disturbing signal closed the switch immediately, please try moving the endstop wires with a little distance to other wires. (That's the reason why NC is recommended).

Or the printer vibrations trigger the endstop.

The Y 0.0 is a hint that the y endstop was triggered, because G1 H1 mode stops at the endstop and sets Y to the M208 limit, which is 0 in your case.

Finnls

Not vibrations, but disturbing signal, I think you are on to something - maybe i need a resistor between in and 5v

Finnls

@JoergS5 said in Can not home z and y:

(That's the reason why NC is recommended).

Sorry I did not seen that - i can make it to NC. I will do that - Thanks

JoergS5

@Finnls said in Can not home z and y:

maybe i need a resistor between in and 5v

you would not need it, Duet 3's io.in have already pullup resistors:
https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Duet_3_endstop_inputs

But I expect using NC will solve the issue.

Finnls

Thank you JoergS5 it is solved

JoergS5

@Finnls I'm pleased, thank you for confirmation!