Repository navigation
minor: the fuse as a thermal model, within IEC 60269 and following ABB's gG curves, as an importable package (fuse/) - #9
Merged
Conversation
The IEC 60269 curves and the per-phase damage rule lived in package main, so FTW's fast closed-loop simulation (go/internal/sitesim) kept its own port of the gG curve. They move to package fuse at the module root, with no dependencies: Lookup, All, Profile.TripSeconds and Profile.Step on a Phase. The site loop now calls it; its JSON and behaviour are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Oct 22, 2026
The fuse was a damage counter: 1/t of its life per second above the rating, recovered linearly over a fixed cooldown. A fuse that had carried its rating for an hour blew no sooner than a cold one, and 1.13 × blew within the hour where IEC 60269-1 lets a gG carry 1.25 × for it. Now each phase is three thermal bodies in a ladder (element, fuse body and sand, holder and cabinet) heated by I² and melting at tin's 232 °C, with the ambient as a parameter. Each gG band (16, 20, 25, 32, 35, 40, 50, 63 A) is fitted to IEC 60269-1's gates and pre-arcing I²t at 0.01 s and keeps the conventional currents; aM to its gates. gM, gR and gS are gG with scaled times and say they are not calibrated. Steps are exact, so the result does not depend on the step size. The site keeps each phase's heat between ticks and clears it with the fuse. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…; refuse bad input The review of a6baf29 (#9): - The 1.4-2 × region, where home overloads land, rested on three free choices (UMin, the holder's share and time constant) that no source pinned. All six thermal parameters are now fitted per band to ABB's pre-arcing curves for OFAF gG size 000 (1SCC317001C0201 p. 14, digitized from the PDF's vector paths), keeping every IEC 60269-1 gate, I²t window and conventional current: rms 0.08-0.095 decades, at most 0.17. A temperature-dependent element resistance made the fit worse and is left out. - Ambient 0 meant unset, so a 0 °C cabinet became 25 °C. Phase.AmbientC is now a pointer; nil is the default. - A NaN current, step or ambient, an infinite step, an ambient at the melting point or a rating without a band left NaN in the state or blew a fuse that never melts. Step now refuses them, leaves the state and says why in Status.Invalid; an infinite current blows the fuse. - 10 A has other conventional currents (1.5/1.9 In) than the 16-63 A band it borrowed. gG now models 16-63 A only; the simulator refuses other sizes, and a saved 10 A site reports the refusal. - Preheat puts a phase at the steady state of a held current, for scenarios that start mid-evening. - dt = 0 is documented as a time-to-melt probe; the step-size test checks the exactness to 1e-9; the Tau wording and the modes are corrected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ays blown The re-review of 5710bba (#9): - F1: the 0.08-0.17 decades held only at the eleven fitted points. Against all 48 vertices of each ABB curve the model is rms 0.13-0.20 decades off, at most 0.22-0.46: too slow at 1.6-1.95 ×, too fast at 2.0-2.5 ×, where the body stage takes over at UMin/√(Re + Rb) = 2.02-2.09 × In. That is the three-body ladder's shape; the comment says so and a test holds every vertex within 0.5 decades. The fit now uses the curves' exact start points, so 20 A's start no longer falls below its asymptote. - F2: an infinite current reported an infinite ratio, which JSON cannot carry, and a current whose square overflows left NaN in the state. Both now blow the fuse with a finite ratio. - F3: a size is checked with its profile: gG and the profiles scaled from it at their bands, aM and manual at any size. The dashboard shows a phase's refusal and keeps a saved size in the size list. - F4: Preheat refuses a blown fuse instead of reviving it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 23, 2026
frahlg
added a commit
that referenced
this pull request
Oct 23, 2026
…10) * fix(ocpp): one heartbeat and meter loop per connection, DropConnection Each connection to a Central System started another heartbeat, MeterValues and simulation loop, and nothing ended them but Stop. After one reconnect a charger sent every heartbeat and MeterValues twice and integrated its energy twice a second. Heartbeats and MeterValues now end with their connection; the simulation runs once for the charger's life, connected or not, since a car charges through a network outage. Two hooks for scripted runs: DropConnection(d) closes the connection as a lost network does and keeps the charger away for d, with the session going on; SetFrameLog reports every OCPP-J frame the charger reads or writes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(ocpp): the car's own limits (SetCar) A car takes at most its own current per phase and charges on its own phases: a one-phase car under a three-phase order draws on L1 only, and a car that takes 10 A draws 10 A of a 16 A offer. The charger's offer (effectivePowerW) is unchanged; its draw follows the car. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(run): headless runs from a house spec, with a timeline and a record simulator run -spec house.json -port-base N -out DIR builds one house: devices by the device-drivers driver they emulate (a hybrid whose battery follows its EMS writes, OCPP chargers with their car), the site meter behind a fuse per phase, and the house load. It serves them on ports from the base, applies a timeline of events (loads, pv, soc, plug, car, offline, online, reconnect, mark, stop), and takes the same events over POST /api/run/event while it runs. It records a sample a second of what flows through each fuse, the fuse's damage and each device's state to plant.jsonl, every OCPP frame per charger, ports.json and result.json. Self-update endpoints are off in a run. The site loop read Running without the simulator's lock while a stop wrote it; it now takes the lock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(run): an outage asked for during a retry keeps its length; "meter" is reserved Codex's review of #10: - A reconnect event while the charger was already waiting to retry only moved a deadline nobody read; the retry dialled after the usual delay. Each dial now waits out DropConnection's deadline first. - A device called "meter" lost its ports.json entry to the site meter. The spec now refuses that id. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(run): draw port bases below the ephemeral range freeBase took a base from the kernel's next ephemeral port and skipped those over 65000. macOS hands ephemeral ports out in turn, so once its cursor sat near the top every try was skipped and every run test failed with "no free port range". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(run): the fuse cabinet's air and a warm start With the thermal fuse on main (#9), a run's spec can set the cabinet's air (site.fuse_ambient_c, default 25 °C) and start the fuses warm (site.fuse_preheat_a, a current per phase they have carried long enough to settle), as a house is in the evening. A fuse size the profile does not model is refused before the run touches the simulator's settings. The site loop now reads its tick before it starts: a run sets the tick before it builds its site, and the next run could set it again while the last loop was still reading it (the race detector caught it once runs followed each other within milliseconds). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * minor: faults and seeded random timelines for headless runs (#11) * feat(run): faults and seeded random timelines Faults for an EMS under test, as events in a headless run and over /api/run/event: a Modbus device that keeps its connections and answers nothing (silence), a site meter whose readings stand still (meter_late), one reading whose total disagrees with its phases (meter_glitch), phase currents that carry a sign (signed_currents), and a charger's own cap per phase (load_balancer). New model parameters, overridable per device: startup_delay_s (the car draws that long after an offer rises from zero) and load_balancer_a for an OCPP charger, signed_phase_currents for a meter. A spec's random block draws a timeline from a seed within the house's bounds (house load per phase under the fuse less 2 A), picks the open timing of each device, and writes timeline.json, a spec that replays it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(run): each session waits out the startup delay; faults keep the latest; a late meter keeps its energy Codex's review of #11: - offerSince now resets when a connector leaves its session, so every session waits out startup_delay_s, not only the first. - An earlier silence's or outage's timer no longer ends a later one: each device counts its faults and a timer acts only for the latest. - Energy that flows during meter_late shows on the counters when the readings move again; before, it was lost. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(ocpp): a charger wired on one phase wired_phases: 1 in a run spec (SetWiredPhases) wires a charger on L1. It gives an order's current there whatever numberPhases says, and max_kw is its rating as wired, so a 16 A order on a 3.68 kW charger draws 16 A on L1. Before, the order became 16 A x 3 x 230 W, was capped to 3.68 kW and spread over three phases, and a one-phase car took 5.3 A of it. FTW's site test needs it for a charger wired on one phase, under Charge now and planned charging. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
frahlg
added a commit
that referenced
this pull request
Oct 23, 2026
* fix(ocpp): send Basic auth from user:password in the OCPP URL
A Central System that requires OCPP 1.6 security profile 1 (FTW does)
refused the simulated charger: it dialled without credentials, and the
WebSocket dialer rejects user:password inside the URL. Move them to an
Authorization header and keep the password out of the logs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ocpp): deliver StartTransaction once the charger is online
A car plugged in before the charger had reached its Central System
started a local session whose StartTransaction was lost: sendRequest
failed and nothing kept the message. Queue StartTransaction and
StopTransaction while there is no connection and send them, in order,
after the next BootNotification is accepted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ocpp): profile_delay_s answers Accepted at once and applies later
A cloud charger such as Easee accepts a charging profile at once and
changes its output a minute or two later. The simulated charger applied
every profile at once, so nothing could test how a Central System
copes with that. POST /api/simulators/{id}/config {"profile_delay_s": 60}
now holds accepted SetChargingProfile and ClearChargingProfile changes
for that long, in order. Invalid profiles are still refused at once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ocpp): a 1-phase profile loads L1, not a third of each phase
The simulated charger always spread its draw evenly over three phases,
also under a profile with numberPhases 1, so a site meter never saw the
one-phase load a real car puts on L1. A charger that can switch phases
(ConnectorSwitch3to1PhaseSupported) now draws a 1-phase profile on L1
only, at most its rated current per phase, and reports it per phase:
phasePowers and per-phase currents in its state and MeterValues. The
site meter takes a charger's draw per phase instead of through the
site's phase factors.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(sungrow): write register defaults in engineering units
Register defaults are written through each register's scale, but the
Sungrow ones were raw register values: an SH10RT came up rated 100 kW
(5000, 0.1 kW) with 500 kW charge and discharge limits (33046/33047,
0.01 kW). Use 10 kW and 5 kW, in the register set, the global defaults
and the sungrow-hybrid and residential-5kw profiles.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(sungrow): ems_control makes the battery follow the EMS registers
The Sungrow model stored an EMS's writes to 13049-13051 and never
applied them, so an EMS under test commanded a battery that did not
move. With POST /api/simulators/{id}/config {"ems_control": true} the
battery does what a real SH does: in forced mode (13049 = 2) it follows
13050 (170 charge, 187 discharge, 204 stop) and 13051 watts; in any
other mode it runs self-consumption against the site meter. It answers
after ems_response_ms (default 2000), stays within 33046/33047 and the
SoC limits 13057/13058, and writes the power-flow flags (13000) the Lua
driver signs the power by. Off by default: the dashboard sets the
battery by writing the registers directly.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(profiles): each model names its driver and carries its timing
A profile now says which srcfl/device-drivers driver it emulates
(driver_id, the file stem: sungrow, sdm630, pixii, ocpp...) and carries
the model's timing in a model block, so field evidence for a driver can
later set it. command_response_s replaces the two settings this branch
added (ems_response_ms, profile_delay_s): it is how long the device
takes to act on an accepted command, the battery after an EMS write or
the charger after a charging profile. sungrow-hybrid says 2 s; applying
a profile sets it, and POST /api/simulators/{id}/config overrides it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: zero battery limits, phases in composite schedules, stop ids after a queue
Codex's review of #8:
- A Sungrow limit register holding 0 now allows no power that way; before,
0 turned the clamp off.
- GetCompositeSchedule reports the phases the charger draws on: 16 A on one
phase, not 5.3 A on three. A change of phases starts a new period.
- A session that starts and ends offline is stopped under the transaction id
the Central System gives its queued start.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* minor: headless runs from a house spec, with a timeline and a record (#10)
* fix(ocpp): one heartbeat and meter loop per connection, DropConnection
Each connection to a Central System started another heartbeat, MeterValues
and simulation loop, and nothing ended them but Stop. After one reconnect
a charger sent every heartbeat and MeterValues twice and integrated its
energy twice a second. Heartbeats and MeterValues now end with their
connection; the simulation runs once for the charger's life, connected
or not, since a car charges through a network outage.
Two hooks for scripted runs: DropConnection(d) closes the connection as a
lost network does and keeps the charger away for d, with the session going
on; SetFrameLog reports every OCPP-J frame the charger reads or writes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ocpp): the car's own limits (SetCar)
A car takes at most its own current per phase and charges on its own
phases: a one-phase car under a three-phase order draws on L1 only, and a
car that takes 10 A draws 10 A of a 16 A offer. The charger's offer
(effectivePowerW) is unchanged; its draw follows the car.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(run): headless runs from a house spec, with a timeline and a record
simulator run -spec house.json -port-base N -out DIR builds one house:
devices by the device-drivers driver they emulate (a hybrid whose battery
follows its EMS writes, OCPP chargers with their car), the site meter
behind a fuse per phase, and the house load. It serves them on ports from
the base, applies a timeline of events (loads, pv, soc, plug, car,
offline, online, reconnect, mark, stop), and takes the same events over
POST /api/run/event while it runs. It records a sample a second of what
flows through each fuse, the fuse's damage and each device's state to
plant.jsonl, every OCPP frame per charger, ports.json and result.json.
Self-update endpoints are off in a run.
The site loop read Running without the simulator's lock while a stop
wrote it; it now takes the lock.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(run): an outage asked for during a retry keeps its length; "meter" is reserved
Codex's review of #10:
- A reconnect event while the charger was already waiting to retry only
moved a deadline nobody read; the retry dialled after the usual delay.
Each dial now waits out DropConnection's deadline first.
- A device called "meter" lost its ports.json entry to the site meter.
The spec now refuses that id.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(run): draw port bases below the ephemeral range
freeBase took a base from the kernel's next ephemeral port and skipped
those over 65000. macOS hands ephemeral ports out in turn, so once its
cursor sat near the top every try was skipped and every run test failed
with "no free port range".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(run): the fuse cabinet's air and a warm start
With the thermal fuse on main (#9), a run's spec can set the cabinet's
air (site.fuse_ambient_c, default 25 °C) and start the fuses warm
(site.fuse_preheat_a, a current per phase they have carried long enough
to settle), as a house is in the evening. A fuse size the profile does
not model is refused before the run touches the simulator's settings.
The site loop now reads its tick before it starts: a run sets the tick
before it builds its site, and the next run could set it again while the
last loop was still reading it (the race detector caught it once runs
followed each other within milliseconds).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* minor: faults and seeded random timelines for headless runs (#11)
* feat(run): faults and seeded random timelines
Faults for an EMS under test, as events in a headless run and over
/api/run/event: a Modbus device that keeps its connections and answers
nothing (silence), a site meter whose readings stand still (meter_late),
one reading whose total disagrees with its phases (meter_glitch), phase
currents that carry a sign (signed_currents), and a charger's own cap
per phase (load_balancer). New model parameters, overridable per device:
startup_delay_s (the car draws that long after an offer rises from zero)
and load_balancer_a for an OCPP charger, signed_phase_currents for a
meter.
A spec's random block draws a timeline from a seed within the house's
bounds (house load per phase under the fuse less 2 A), picks the open
timing of each device, and writes timeline.json, a spec that replays it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(run): each session waits out the startup delay; faults keep the latest; a late meter keeps its energy
Codex's review of #11:
- offerSince now resets when a connector leaves its session, so every
session waits out startup_delay_s, not only the first.
- An earlier silence's or outage's timer no longer ends a later one: each
device counts its faults and a timer acts only for the latest.
- Energy that flows during meter_late shows on the counters when the
readings move again; before, it was lost.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ocpp): a charger wired on one phase
wired_phases: 1 in a run spec (SetWiredPhases) wires a charger on L1. It
gives an order's current there whatever numberPhases says, and max_kw is
its rating as wired, so a 16 A order on a 3.68 kW charger draws 16 A on
L1. Before, the order became 16 A x 3 x 230 W, was capped to 3.68 kW and
spread over three phases, and a one-phase car took 5.3 A of it.
FTW's site test needs it for a charger wired on one phase, under Charge
now and planned charging.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The house lives in this repo, and FTW's fast closed-loop simulation (
go/internal/sitesimin srcfl/ftw) should judge its fuse by the same model. This moves the fuse model into an importable package,fuse/at the module root, with no dependencies. It also replaces the model itself (Fredrik, 22 October): the simulator is the judge of Core's fuse protection, so its fuse must follow physics and IEC 60269, and must not copy Core. The model is a central estimate, one maker's mean curve within the standard's tube, not a worst case.Why the old model could not judge
The old fuse was a damage counter: each second above the rating spent 1/t of the fuse's life, and the damage recovered linearly over a fixed cooldown.
The model
Each phase has three thermal bodies in a ladder:
Stepsolves the ladder exactly for a current held over the step, from an eigendecomposition done once per band. Steps of 0.5, 1 and 2 s reach the same state to 1e-9.dt = 0changes nothing and returns the time left at that current, which makes it a "time to melt now" probe.Lookup,All,TripSeconds(multiple)at the reference band, andStep(*Phase, amps, ratingA, dt) Status;MeltSeconds(multiple, ratingA, ambientC),Band,Ratings,Supports;Preheat(*Phase, amps, ratingA), which sets the steady state of a held current, so a scenario that starts mid-evening starts warm;Phase.Theta(the state) andPhase.AmbientC *float64(nil means 25 °C; 0 is 0 °C).ratiois current over rating.trip_sis the time to melt from cold at this ratio.remaining_sis the time to melt from now.damageis the element's way from ambient to melting, 0 to 1.activemeans it will melt if the current stays.invalidsays why a step was refused.invalidsays why. An infinite current, or one whose square overflows, blows the fuse; the reported ratio stays finite for JSON.Calibration
What the standard fixes. IEC 60269-1 fixes, per rating:
These come from the standard's tables as given in:
35 A is not in those tables; its gates and I²t are interpolated on log axes between 32 A and 40 A. The reference ambient of 20 °C, with the curves approximately valid at 30 °C, is from Enel GSCL004 §6.1.
What the standard leaves open. The gates leave a wide tube. No gate constrains 1.4–2 ×, where home overloads land, and 2 × from cold is constrained by nothing. The review's sensitivity run on the a6baf29 structure shows how wide the tube is for 25 A: varying the holder's share (0.2–0.6), the holder's τ (600–2,400 s) and UMin (1.30–1.55), with every gate kept, puts a cold 1.6 × anywhere from 82 s to 2,293 s, and 2 × from 24 s to 351 s.
Fitted to a manufacturer. To pin that region, each band follows ABB's pre-arcing curves for OFAF gG fuse-links, size 000, 500 V (ABB Fusegear DIN-type HRC-fuse links, 1SCC317001C0201, page 14). The curves were digitized from the PDF's vector paths, so the read-off error is under 2 % in time (48 vertices a curve, linear on log axes between them).
All six parameters (UMin, Re, τe, Rh, τb, τh) are fitted per band, by least squares on log time from cold at 20 °C, to eleven ABB points:
The fit keeps every gate.
R(T). An element resistance rising with temperature (silver, 0.0038 per K) was tried and made the fit worse: rms 0.11–0.14 decades instead of 0.08–0.095, UMin at its bound, and the 32 A I²t outside its window. It is left out.
Ferraz Shawmut. Their NH gG chart (gGNH, F 24) was also tried. It is a raster image with label leader lines across the curves, and it could not be traced reliably, so it is not used. Read by eye it looks slower than ABB at 2–3 ×, which shows how far makers sit apart inside the tube.
Validation against ABB (from cold, 20 °C)
Each cell is ABB / model, with the model's error in decades in brackets. The last two columns give the error at the eleven fitted points and at all 48 vertices of the ABB curve.
The fitted points hide the shape between them. Against all 48 vertices the model is rms 0.13–0.20 decades off, at most 0.22–0.46:
The cause is a step in the model's curve. Where the element's quasi-steady rise over the body reaches the melting rise, at u = UMin/√(Re + Rb) = 2.02–2.09 × In (16–63 A), the body stage takes over from the holder. Between 1.9 and 2.3 × the model's log-log slope reaches −18 to −52; ABB's reaches −7 to −11. The review refitted all 48 vertices and reached only rms 0.12–0.15, so this is the three-body ladder's shape, not a poor fit. A test holds every vertex within 0.5 decades, as a regression check.
For sitesim and the site test: overloads at 1.9–2.1 × In sit on that step, so a small change of current there moves the melting time a lot. A finding there deserves a second look against the fitted points before it is called a defect.
Calibration against IEC 60269-1 (from cold, 20 °C)
* Interpolated gates.
Preload, 1 h at In, then:
At 2 × the preloaded fuse takes 9–22.5 s, against 53–139 s cold.
Short overloads, 25 A. 30 s at 1.5 × every 2 min (0.5 × between) raises the damage after each burst from 0.53 to 0.64 over ten cycles. A held 1.5 × then blows in 1,532 s instead of 1,816 s cold.
Ambient, 1.5 × on 25 A. 3,053 s at 0 °C, 1,816 s at 20 °C, 1,630 s at 25 °C and 1,191 s at 40 °C.
aM, any rating. Gates from Mersen TM-104 slide 7, and all six hold. Fitted with UMin = 4 (an assumption) and the holder's share at 0.2.
Free choices and limits
Step(invalid) and by the simulator's API and Wails binding. Above 63 A is refused too. aM and manual model any size and take any.Also here
cmd/simulator/fuse.gokeeps its names as aliases. The site keeps each phase's thermal state (Site.FuseHeat) between ticks, clears it with the fuse, its size or its profile, and takes the cabinet's air fromSite.FuseAmbientC(nil is 25 °C).Step;Preheatagainst a 6 h soak, accumulating short overloads, cooling along the slowest mode;Preheaton a blown fuse;go test -race ./...passes.What this changes for FTW
site.fuse_ambient_cand a preheat for scenarios that start warm.Part of the work described in #8. Independent of #8; either can land first.
🤖 Generated with Claude Code