Temp-warning disable proven not to silence the firmware's internal temp poll; corrected-error channel stays untrustworthy, register-docs ask is the remaining path (open-questions §5)
This commit is contained in:
@@ -474,6 +474,13 @@ temperature-like values can leak into other commands' DATA1.
|
||||
temperature limit margin in °C (positive number). DATA3: Enable upper temperature warning —
|
||||
0 = Disable, 1 = Enable.
|
||||
|
||||
**Field note (hardware-verified):** disabling the warning — SET 0x8032 `(0x007D, 5, 0, 0, 0)`
|
||||
and SET 0x8034 `(0xFFD8, 5, 0, 0, 0)`, DATA3 = 0, all five params explicit, both PASS — does
|
||||
not stop the firmware's own ~3.5 s internal CMD_GET_CURRENT_TEMP poll (README
|
||||
firmware-reliability notes); the warning machinery and the internal temperature poll are
|
||||
independent. GET 0x8033/0x8035 return DATA1–3 = 0 regardless of prior SET values, with
|
||||
DATA4/5 reading leftover scratch — DATA1-answer readbacks that cannot verify anything.
|
||||
|
||||
### §1.25.1.30 GET_WAP_MODE_FRAME_TYPE (0x8023)
|
||||
|
||||
- **Description:** —
|
||||
|
||||
Reference in New Issue
Block a user