printer show already homed
-
With no M564 H0 in config and fresh startup after full power cycle dwc shows all axes homed and xyz all at zero. More like x100 y150 z 120 physically. yeah!
201 firm 1.21.1 dwc
can't use dwc 1.21.2 like recommended because java errors prevent any action every time.all hardware is correct sw states are correct machine never homed but thinks it did.
-
After you power cycled the Duet, are you sure that DWC had reconnected when it was showing the axes as homed? It may take a little while for the Duet to reconnect to your router, and during this time DWC will be retrying so it won't know that the homed status has changed.
What is the exact error message you get if you use DWC 1.21.2? Have you tried pressing "Load factory defaults" followed by "Apply settings" in the Settings/User Interface page of DWC?
-
It is also possible the configuration of endstop switched need to be inverted...
What does M119 show at power up, BEFORE homing?
-
I will need to check, not sure if it's permissible during this first print. Conform that and I will respond
-
m119, if you are referring to switch states I can see through machine prop tab than endstop hit x =no y = no z = no
-
after power cycle I viewed homed state about 5 min later. I was preparing a petg instead of pla. so yeah 5 minutes after power cycle homing tabs where blue not orange.
-
@sir-printsalot said in printer show already homed:
after power cycle I viewed homed state about 5 min later. I was preparing a petg instead of pla. so yeah 5 minutes after power cycle homing tabs where blue not orange.
That's really weird. Are you certain that Duet web Control was in the Connected state?
Please post your config.g file.
-
@dc42 he's posted his config set in his other thread inconsistent operation
