Follow the lens reference into the harness and the catalog

The lens now takes its hall-edge reference before any controller starts,
so Z is referenced on every start and M103 is gone. The laser-stream
harness opened its Z session by referencing the lens the way a
commissioning card did; it no longer has to, because Z is already open by
the time the session runs.

forgectrl.panel-serves gains the assertions for the per-axis reference:
homed_axes is an axis mask, homed agrees with it, and with a controller
running Z is referenced and reads inside the lens reach the same document
reports. That last check is the one that catches a panel showing nothing
for a Z the controller holds.

commission.check-motion already exercised the new path, because the
motion wizard's probe runs the same sequence the supervisor does, so its
covers map gains lenshome.c and its description names the lens reference
and the hard fault behind it.
This commit is contained in:
ScottW514
2026-09-09 08:06:04 -04:00
parent 74fa8a4ee6
commit 5f19ae01cd
3 changed files with 37 additions and 7 deletions
+4 -5
View File
@@ -146,12 +146,11 @@ JOB_M4 = [
"M5",
]
# Session Z: the lens is in the stream. The sender references the lens
# (M103, as a commissioning card does), then a 1 mm move up and back at
# the screw's 2.922 half-steps per millimeter: three Z steps with the
# direction bit set, three with it clear.
# Session Z: the lens is in the stream. The lens is referenced on its hall
# edge at the controller's start, so Z is already open here: a 1 mm move up
# and back at the screw's 2.922 half-steps per millimeter, three Z steps
# with the direction bit set, three with it clear.
JOB_Z = [
"M103 Z3 P14 Q20",
"G0 Z4",
"G0 Z3",
]