mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-27 16:51:12 -07:00
The tail after Idle is one queue depth, and it does not grow
The open item "Idle before the kernel drains" asked to decide between holding Idle until the kernel drains and stopping the continuation pads growing the lag. Measured first: on the machine, four chained 50 mm jogs against cnc/state give 171, 175, 177 and 176 ms after Idle. One queue depth, flat. The growth the item described is gone, so neither driver change was made and the item is closed. Host side agrees and says where the mechanism lives. Stream bytes are the time axis, so a dumped stream's length is how long the machine plays it: chained jogs produce 35755 bytes each with no growth, and the churn session holds at 64790 bytes at a producer lead of 2 or 10 ms. Only above the lead ceiling does it inflate. Rule 17 now holds that stream to a budget derived from the job rather than to a recorded number, so the inflation regime cannot return unnoticed; it fails at 5899 and 8005 ms with the ceiling lifted and passes at 2301 against 3800. BRINGUP carried a second error. It said every forgectrl path that stops the controller after motion waits for cnc/state idle. super.c says outright that POST /controller/stop is not idle-gated, because it is also the emergency lever, and safes the machine with cnc/stop and the latch before the signal instead. The mode switch, the cooling gate and the daemon shutdown do gate on machine_is_idle(). Both the tail figure and the gating claim are corrected, and CAMPAIGN-LOG carries the measurements and the decision not to hold Idle. Acceptance: rule 17 is a host harness rule in the grblHAL repo's CI, not a catalog case. The catalog is unchanged because no machine behavior is: the driver change is a bound on an out-of-range knob.
This commit is contained in:
@@ -132,6 +132,8 @@ def duty_for(s):
|
||||
# = 7.3 ms = ~206 ticks at 28160 Hz. 500 gives >2x margin while staying
|
||||
# far below any idle-gap pad run.
|
||||
FIRE_GAP_LIMIT_TICKS = 500
|
||||
# The machine tick: one stream byte per tick, so byte counts are durations.
|
||||
MACHINE_TICK_HZ = 28160.0
|
||||
|
||||
WAIT_IDLE = ("wait_idle",)
|
||||
|
||||
@@ -176,6 +178,13 @@ for _ in range(30):
|
||||
JOB_CHURN.append(("sleep", 0.02))
|
||||
JOB_CHURN.insert(0, "M4 S0")
|
||||
JOB_CHURN.append("M5")
|
||||
# Rule 17's budget, derived from the job rather than measured: 60 moves of
|
||||
# 0.2 mm at F600 plus the scripted gaps. A stream longer than this is dark
|
||||
# pad, and dark pad is time the machine keeps moving after the sender has
|
||||
# been told the job is done.
|
||||
CHURN_MOTION_S = 60 * (0.2 / (600.0 / 60.0))
|
||||
CHURN_GAPS_S = 60 * 0.02
|
||||
CHURN_BUDGET_S = (CHURN_MOTION_S + CHURN_GAPS_S) * 1.5 + 0.2
|
||||
|
||||
# Session D: a power ladder in the shape the bench threshold drill uses -
|
||||
# constant power (M3) so the commanded duty is the tested duty, rungs
|
||||
@@ -295,7 +304,7 @@ JOB_IDLE_S.append("M5")
|
||||
# same case one step further.
|
||||
M5_IDLE_MM = 5.0
|
||||
M5_IDLE_FEED = 600
|
||||
M5_IDLE_TICKS = M5_IDLE_MM / (M5_IDLE_FEED / 60.0) * 28160
|
||||
M5_IDLE_TICKS = M5_IDLE_MM / (M5_IDLE_FEED / 60.0) * MACHINE_TICK_HZ
|
||||
JOB_M5_IDLE = [
|
||||
"G91", "G21",
|
||||
"M3 S500",
|
||||
@@ -806,8 +815,22 @@ def main():
|
||||
fail("[churn] no FIRE bits in the stream")
|
||||
check_termination("churn", data)
|
||||
gap_c = check_fire_gaps("churn", data)
|
||||
print("PASS [churn]: %d bytes, %d fire ticks, max fire gap %d"
|
||||
% (len(data), count_fire(data), gap_c))
|
||||
# Rule 17: the churn stream carries no runaway pad. Bytes are the time
|
||||
# axis, one per machine tick, so the stream's length IS how long the
|
||||
# machine plays it. A cycle that resumes while the kernel still drains
|
||||
# re-bases production onto the wall cursor; if the producer's lead lets
|
||||
# production stay ahead of that cursor across the gap, the re-base is
|
||||
# skipped and the overshoot is inherited by every cycle after it. That
|
||||
# is what GFSINK_LEAD_MS_MAX bounds, and this is what catches it.
|
||||
churn_s = len(data) / MACHINE_TICK_HZ
|
||||
if churn_s > CHURN_BUDGET_S:
|
||||
fail("[churn] stream is %.0f ms of playout, over the %.0f ms budget: "
|
||||
"the cycle re-base is leaving pad behind"
|
||||
% (churn_s * 1e3, CHURN_BUDGET_S * 1e3))
|
||||
print("PASS [churn]: %d bytes, %d fire ticks, max fire gap %d, "
|
||||
"%.0f ms of playout (budget %.0f)"
|
||||
% (len(data), count_fire(data), gap_c, churn_s * 1e3,
|
||||
CHURN_BUDGET_S * 1e3))
|
||||
|
||||
# --- session D: power ladder, rule 10 -------------------------------
|
||||
data = run_session("ladder", JOB_LADDER, conf=ANALOG_CONF)
|
||||
|
||||
Reference in New Issue
Block a user