Q about expected operation of homing and limit switches about core

[terjeio]

However, a more desireable outcome and what I am used to from 8 bit grbl, is the ability to reset and unlock and electrically move off the sensor and then manually choose to re-home. The problem is I do not have that option right now.

The "Override locks" flag in $22 is not working? $$=22 output:

$22: Homing cycle as bitfield where setting bit 0 enables the rest:
    0 - Enable (1)
    1 - Enable single axis commands (2)
    2 - Homing on startup required (4)
    3 - Set machine origin to 0 (8)
    4 - Two switches shares one input pin (16)
    5 - Allow manual (32)
    6 - Override locks (64)
    7 - Keep homed status on reset (128)

Enables homing cycle. Requires limit switches on axes to be automatically homed.

When `Enable single axis commands` is checked, single axis homing can be performed by $H<axis letter> commands.

When `Allow manual` is checked, axes not homed automatically may be homed manually by $H or $H<axis letter> commands.

`Override locks` is for allowing a soft reset to disable `Homing on startup required`.
ok

Thoughts?

On my Mach 3 based machine I have a limits override switch that allows me to reset the machine and jog off any triggered limit switch while I keep it pressed. I like that and I have added support for it in the core, but only a few (one?) driver has support for it for now. Could that be a solution? It is likely a lot easier to add than the other options you have outlined.

core/protocol.c

Lines 107 to 114 in 71dc5ac

	} else if (settings.limits.flags.hard_enabled && settings.limits.flags.check_at_init && limit_signals_merge(hal.limits.get_state()).value) {
	if(sys.alarm == Alarm_LimitsEngaged && hal.control.get_state().limits_override)
	state_set(STATE_IDLE); // Clear alarm state to enable limit switch pulloff.
	else {
	// Check that no limit switches are engaged to make sure everything is good to go.
	system_raise_alarm(Alarm_LimitsEngaged);
	grbl.report.feedback_message(Message_CheckLimits);
	}

[5ocworkshop]

On my Mach 3 based machine I have a limits override switch that allows me to reset the machine and jog off any triggered limit switch while I keep it pressed. I like that and I have added support for it in the core, but only a few (one?) driver has support for it for now. Could that be a solution? It is likely a lot easier to add than the other options you have outlined.

Yes, an override button on an aux pin like this could definitely work for my situation. That's an elegant way to do it. What would need to happen for this on the Teensy platforms?

I'll double check my config tomorrow at the machine, but my initial impression is that the override locks command is not functioning in my build.

[5ocworkshop]

The "Override locks" flag in $22 is not working? $$=22 output:

Thank you for this. I went back to using IOSender and I could easily see that this was not set. I had set it in the firmware but I guess my local config is taking precedence and it wasn't set.

I want to switch off CNCjs and be fully on IOSender, I just need to get my probing macros working, now that I have the soft limits resolved.

Will ask my probing question in the probing thread I started and close this one as resolved.

[terjeio]

Thank you for this. I went back to using IOSender and I could easily see that this was not set. I had set it in the firmware but I guess my local config is taking precedence and it wasn't set.

Be aware that most of the firmware settings are default values, a settings reset is required after changing them.