[BUG] Software endstops are ignored

[phate191]

Bug Description

After Homing with Software Endostops enabled, you can move out of the software endostops boundaries.

My Configurations

Ender 3 Pro
Version 2.0.1, commit 432decd
Marlin.zip

Steps to Reproduce

1. M211 //Check if Software Endsotops are Enabled
2. Home XY [G91 | G28 X0 Y0 | G90]
3. M211 //Check, Still Enabled
4. G1 Y-1 F4000 // Move Y and the axis move without problem...

With Software Endstops enabled the axes after home should be stopped to go below MIN_SOFTWARE_ENDSTOP_*

From Octoprint Terminal:

Send: M211
Recv: echo:Soft endstops: ON Min: X0.00 Y0.00 Z0.00 Max: X235.00 Y235.00 Z250.00
Recv: ok
[...]
Send: G91
Recv: ok
[...]
Send: G28 X0 Y0
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: X:0.00 Y:0.00 Z:10.00 E:0.00 Count X:0 Y:0 Z:4000
Recv: ok
Send: G90
Recv: ok
[...]
Send: M211
Recv: echo:Soft endstops: ON Min: X0.00 Y0.00 Z0.00 Max: X235.00 Y235.00 Z250.00
Recv: ok
[...]
Send: G1 Y-1 F4000
Recv: ok

I've also tried to disable with M211 S0 and the repeat; the beavior is the same (and it's ok).

[ellensp]

Endstops are ignored for all but homing commands. unless you enable
#define ENDSTOPS_ALWAYS_ON_DEFAULT in Configuration_adv.h

[phate191]

Yes true, but phisical endstops must be separated from software endstops.
Theoretically they have different function.
If I remeber correctly, in old versions, software endostops if are enabled are always enforced.

EDIT:
Also with #define ENDSTOPS_ALWAYS_ON_DEFAULT enabled, I can go above the bed limit (bed size 235 x 235) if I use G1 Y236 F4000

[tatusah]

Different board but for me soft endstops do work correctly with Marlin 2.0.1. What does M114 report as position after you issue the G1 Y-1 F4000?

[tatusah]

Does the LCD controls also allow going past soft endstops or is it only trough Octoprint?

[phate191]

Ok I think I find the issue.
This is the ouput from octoprint if I only home X and Y:

[...]
Send: G91
Recv: ok
Send: G28 X0 Y0
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: X:0.00 Y:0.00 Z:10.00 E:0.00 Count X:0 Y:0 Z:4000
Recv: ok
Send: G90
Recv: ok
[...]
Send: M114
Recv: X:0.00 Y:0.00 Z:10.00 E:0.00 Count X:0 Y:0 Z:4000
Recv: ok
[...]
Send: G1 Y-1 F4000
Recv: ok
[...]
Send: M114
Recv: X:0.00 Y:-1.00 Z:10.00 E:0.00 Count X:0 Y:-80 Z:4000
Recv: ok

But this is the ouput after home of X, Y and Z:

[...]
Send: G91
Recv: ok
Send: G28 X0 Y0
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: X:0.00 Y:0.00 Z:10.00 E:0.00 Count X:0 Y:0 Z:4000
Recv: ok
Send: G90
Recv: ok
Send: G91
Recv: ok
Send: G28 Z0
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
Recv: ok
Send: G90
Recv: ok
[...]
Send: M114
Recv: X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
Recv: ok
[...]
Send: G1 Y-1 F4000
Recv: ok
[...]
Send: M114
Recv: X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
Recv: ok

So, if you home only X and Y, and then you move X or Y, software and hardware endstops are ignored for ALL axis :(

[tatusah]

Well, there you are correct. Sorry, did only test general G28 previously. Software endstops are not enabled until all axis are homed and thus movement past endstops is possible.

[tatusah]

And I remembered that I saw this thing before also. The issue connects to a bigger picture. It was last raised here #16283 so I think this needs some discussion about what if anything should be done about the situation.

[kurtnelle]

I have confirmed that the software endstops are on but the joystick still allows the planner to send the axis beyond the frame of the machine.

[boelle]

@phate191 still an issue?

[kurtnelle]

I had to update to the lastest version of marlin. I think the software endstops work now. However the behaviour with the joysticks is so erratic, that I'm not sure if it actually is working.

[kurtnelle]

I've tested it some more. Its not working.

[boelle]

did you test it before or after pr #16533 was merged?

[boelle]

Lack of Activity
This issue is being closed due to lack of activity. If you have solved the
issue, please let us know how you solved it. If you haven't, please tell us
what else you've tried in the meantime, and possibly this issue will be
reopened.

we can reopen if we hear from @phate191 again

[kurtnelle]

@boelle , I haven't tested it after #16533 cause I can't figure out how to merge!

[boelle]

@kurtnelle just download from https://github.com/MarlinFirmware/Marlin/tree/bugfix-2.0.x

[italocjs]

I have the same issue, i'll try burning the latest bugfix (from today) to verify if it was solved

[italocjs]

I can confirm that #16533 has fixed the issue here!, thanks

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.