You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
EV fuse cut: a house step in the same second hides the cut's landing, and Core holds a phase over the line for evUnknownSettle #1931
A house step that lands in the same second as an EV cut hides the cut's landing. Core then counts the cut as still on its way and holds the car while a phase sits over the fuse line.
Seen as seed 69 of the random-house site sim (reported in #1914):
Core cut the car from 9 A to 6 A. In the same second a house step raised phase 3 by 2.5 A.
The meter then showed phase 3 at 26.5 A, 0.5 A below the reading the cut was sent for. To Core the cut had not landed.
The sim's charger declares no power_max_age_s, so Core waits evUnknownSettle (3 min) for the cut to show.
For those 3 min Core held the car at its 6 A minimum, with phase 3 at 26.5 A on a 25 A fuse and the heat model rising to 26.2 A.
Reproduction
A sim scenario on a 25 A fuse: house 12/8/5 A, car at 9 A, a house step on phase 3 to 2.5 A over the line, and a second house step on phase 3 in the same second the cut lands (the cut less 0.5 A). The time phase 3 stays over the line after the masked landing:
The fault is on master too; it is not new in the fuse stack. A 0.5 A margin hid part of it. With the margin at 0 by default (#1914) the cushion is gone.
Where
go/internal/control/ev_fuse_budget.go: unshownOrders, cutForA, evUnknownSettle. A cut's landing is judged against the phase reading it was sent for, so any house rise in the same second reads as "not landed".
Expected
A phase over the line after a cut should get a further cut within the heat budget, whether or not the earlier cut shows on the meter. The I²t rule (tau 60 s, instant cut at 1.2 × In) is the limit, not the charger's settle time.
Activity