DEV2: Homing if endstop is much more far away than expected

I noticed that if I do a homing with a wrong microstepping there is a misleading behaviour.

In my case the microstepping was set too high, resulting in the case, that the endstops were not reached. Anyway suddenly it stopped (maybe after the maxiumum expected distance), repeted to look for the endstop and thand did the next homing.

Forme it looks like it assumes it has reached the endtsop, but in fact it has reached the maximum distance. This may result in a totally wrong behaviour. There should be a warning "endstop not found, stopping any other operation"


Sign In or Register to comment.