Homing is lid-gated in practice; only the cloud hunt is not

mirror of https://github.com/openglow-org/forgefirm.git synced 2026-09-28 01:01:12 -07:00

MOTION said jogs, homing and hunts were all ungated. Jogs are:
gfsw_visible withholds the door signal while the core is idle, jogging or
homing, so a jog both starts and runs with the lid open. Homing is not.
With homing_mode = gfcloud - the only method that works today - $H hands
the cycle to a cloud homing session, and its move to the home corner is
an ordinary motion action taking the default lid_gated=True: refused with
the lid open, stopped on a lid edge mid-run. Only the lens/Z hunt inside
that session passes lid_gated=False, and that session is also the only
place a hunt happens in GRBL mode - there is no hunt outside one.

BRINGUP gains item 18: GRBL pause and resume should leave no gap in the
cut, the way the factory's does. The beam stops at the start of the hold
(disable_laser_during_hold, on by default), so the head travels the whole
deceleration dark and the resume restarts from a standstill where the
decel ended - an unburned length, then a dwell through the accel that M3
shows as a deeper spot. The kernel waypoint backtrack cloud mode uses is
refused with EPERM on a live-streamed ring, so the equivalent has to be
built above the ring, where grblHAL still holds the planned path the
kernel has already overwritten.

Two wording fixes: the cooling verdict is described as a report rather
than a file, and gfcloud homing as using the machine's builtin
credentials.

Documentation only - no behavior change, so no acceptance-catalog
consequence.

This commit is contained in:

ScottW514

2026-08-18 07:41:37 -04:00

parent 7ad6b53647

commit 7012c7d1b2

3 changed files with 44 additions and 5 deletions

									
										docs/COOLING.md
									
		+1
		-1
	
												View File
												
				@@ -59,7 +59,7 @@ is running — GRBL or cloud — is a client of it, over two channels:

				Two properties of that split are worth understanding, because they explain the

				machine's behavior in odd situations:

				**A missing verdict is a bad verdict.** If the file is absent or more than two

				**A missing verdict is a bad verdict.** If the report is absent or more than two

				seconds old, a controller treats it as *fire blocked, hold*. The engine going

				away looks exactly like a fault, never like permission.