@phaedrux said in Solved: Homing issue with X & Y after upgrading to RRF3:

@willmackey said in Solved: Homing issue with X & Y after upgrading to RRF3:

Old topic but was relevant to me as a new user how tries to find answers with the outdated wiki.

Which part is out dated?

Just noticed some stuff not matching the reality anymore which as a fresh Duet user caused some head scratching and wasted time going through configs. Didn't keep track of them unfortunately but around this endstop topic atleat:

• Switch status page (I think it was called endstops) in the Machine-specific menu. Wiki still guides there but it no longer exists (some object model browser update is related to this but OMB isn't there either?).
• Whole endstop wiki page only describes two settings (NO / NC) and I guess there only used to be only 2 settings based on YT videos but now there's 4 settings for the endstops and I have no idea how 'active low pull-up' differs from 'active low'. Inputs seem to be pulled-up even without the pull-up selection.

But in general it is really nice to see so comprehensive documentation!

@A Former User said in Solved: Homing issue with X & Y after upgrading to RRF3:

M574 X1 S1 P"!^xstop"
M574 Y1 S1 P"!^ystop"

This worked well! Now it does indeed perform a full homing procedure without issues.

@Danal said in Homing issue with X & Y after upgrading to RRF3:

And, you generally want the switches physically wired as "normally closed" so that a broken wire or loose connector makes the switch look triggered. This stops the home move before it starts, and avoids a machine crash.

And I will definately do this, as I have had some loose connectors in "Normally Open mode" resulting in the print head hammering the side.
Great tips! And tank you a ton for your help!

Old topic but was relevant to me as a new user how tries to find answers with the outdated wiki.

Anyhow this caught my eye as everywhere NC is recommended. Yes, in general for end stops that is the safe option but with 3d printer we usually have stop just in one end and now as Duet doesn't seem to handle the start state properly during homing, this NC will just cause homing to always succeed and that in could cause the machine to fly full speed to positive end which is much worse than slow homing speed bump to negative end.

I don't know why it doesn't fail the homing, it certainly should as it's not seeing any rising or falling edges of the limit if NC loop is open.

With this functionality, I'd much rather choose the NO.