Closed satiowadahc closed 7 months ago
This is the first I've used this since it was converted to a .comp file.
Do you have a test setup for tests/ to demonstrate the bug and ensure it is fixed?
I think that this looks deliberate. Is the intention to mask the error before (for example) homing?
The original intent for the enable is regions like tool changers, only allowing the gantry to run into it, if you are actively doing a tool change
Maybe I am missing something, but this doesn't appear to change any behaviour. It might save a little CPU, I suppose.
If the range is disabled and there is not an error, the range currently will not disable.
Max<min is a sanity check that disables the range if it is mistyped.
Enable allows ranges to be turned on/off
Enable check inside of an error check means if its disabled it'll only disable when there is an error