# Complete temperature-control profile recovery and regulation

Status: deferred
Type: campaign
Updated: 2026-09-03
Next Action: keep deferred while preserving the recovered Controller A profile as partial evidence; reactivate when an actual chamber is scheduled, attended heater-safe testing is authorized, quantitative thermal acceptance limits are approved, and the successor firmware scope is ready
Campaign ID: 017-complete-temperature-control-profile-recovery-and-regulation
Campaign Number: 017
Outcome: In a separate chamber-gated successor-firmware tranche, complete temperature-control profile recovery and prove steady-state stability, overshoot, settling, door recovery, and power-recovery behavior on an actual chamber; dev fixtures may qualify preparatory logic but not thermal-plant behavior. Focus areas: 1 Firmware; 6 Qualification, release, and supply change.
Depends On: none
Decision: Do not hold the SD qualification baseline for this work. Full thermal qualification requires an available actual chamber, attended heater-safe authority, and approved quantitative acceptance limits; any inherited SD qualification for the successor firmware requires reviewed change-impact analysis and focused SD regression.
Detour For: none
Return To: none
Completion Gate: The workpackage is explicitly reactivated, implementation and fixture-level logic checks pass, actual-chamber stability, overshoot, settling, door-recovery, and power-recovery qualification meets approved limits, SD qualification inheritance or requalification is dispositioned, and current temperature-control policy and evidence are documented.
Completion Evidence: partial only; 2026-09-03 read-only Controller A reconciliation proves an operational nonzero I-limit profile and correct above-setpoint heat-off behavior, but not service-524 recovery or chamber performance
Disposition: Final temperature stability, overshoot, settling, door-recovery, and power-recovery qualification requires an actual test chamber. Dev fixtures may support preparatory logic work but cannot satisfy the thermal completion gate, and this separate successor-firmware tranche must not hold the SD qualification baseline.
Reactivate When: an actual chamber is scheduled and available, attended heater-safe testing is authorized, quantitative thermal acceptance limits are approved, and the successor firmware scope is ready for chamber qualification

## 2026-09-03 Reconciliation

The owner observed that Controller A appeared to regulate. Read-only J-Link
sampling was reconciled with the exact current Debug ELF before interpreting
RAM: the first 32 bytes of `calculateTemperatureControlPoints()` at
`0x0005F2AC` matched the local image exactly.

The live controller proves that the specific installed configuration has been
recovered from the July zero-I-limit state:

- effective configuration permission was true and main-temperature control
  was enabled;
- the configured I-limit schedule was 125, 250, 400, 525, and 675 ticks with
  factor 1.10;
- the active 21.000 C setpoint produced a computed I limit of 138 ticks;
- three samples over ten seconds showed adjusted temperature declining from
  21.887 C to 21.873 C while above setpoint, with zero heater output; and
- the focused semantic source-contract check passed 16/16, including the
  requirement for positive nonzero I-limit capacity.

This is partial resolution, not campaign completion. The samples show correct
heat-off behavior above setpoint; they do not establish steady-state accuracy,
integral regulation under holding load, overshoot, settling, door recovery, or
power recovery. Source review also confirms that service 524 still restores
all five cached I-limit values unconditionally and services 48--53 still edit
and save individual fields rather than applying one validated profile.

The campaign therefore remains deferred. Its remaining product work is narrowed
to the unresolved soft-reset and atomic profile-application behavior plus the
actual-chamber qualification gates; recovery of Controller A's current stored
profile is no longer an open prerequisite.

## Request

Primary deferred workpackage:
`work/wp/deferred/wp-temperature-control-profile-recovery-and-steady-state-regulation.md`.

Fixture-only preparation may cover control logic, persistence, fault injection,
and test-plan readiness, but it must not be represented as qualification of
thermal stability or recovery. Reactivate the delivery campaign only when an
actual chamber is scheduled and available, attended heater-safe testing is
authorized, quantitative limits are approved, and the successor firmware scope
is ready for chamber qualification.

## Completion Check

The workpackage is explicitly reactivated, implementation and fixture-level logic checks pass, actual-chamber stability, overshoot, settling, door-recovery, and power-recovery qualification meets approved limits, SD qualification inheritance or requalification is dispositioned, and current temperature-control policy and evidence are documented.
