Verified calculation capability

MOSFET switching loss Calculation Capability

First-order hard-switching overlap loss P_sw = ½·Vds·Id·(tr+tf)·f_sw and optional gate-drive power Qg·Vdrive·f_sw. Not a full MOSFET loss stack. · Electrical · Mosfet

Capability ID electrical.mosfet.switching_loss · version 1.0.0

Open calculator REST API MCP Evidence Evidence JSON CVP Manifest Review policy

Model

Hard-switching overlap loss

Hard-switching overlap loss: P_sw = ½ × Vds × Id × (tr + tf) × f_sw
Gate-drive power: P_gate = Qg × Vdrive × f_sw

Inputs / Outputs

Canonical symbols for this capability. Agent schemas remain the contract.

Symbol	Quantity	Unit	Role
`Vds`	Drain-source voltage during the transition (V).	—	input / output
`Id`	Switched current during the transition (A).	—	input / output
`tr`	Effective rise/overlap time (s).	—	input / output
`tf`	Effective fall/overlap time (s).	—	input / output
`f_sw`	Switching frequency (Hz).	—	input / output
`Qg`	Total gate charge (C). Requires Vdrive.	—	input / output
`Vdrive`	Gate-drive voltage (V). Requires Qg.	—	input / output
`P_sw`	Hard-switching overlap loss, first-order (W). Not full MOSFET switching loss.	W	output
`P_gate`	Gate-drive power Qg·Vdrive·f (W). 0 when omitted. Not necessarily die dissipation.	W	output
`P_total`	P_sw + P_gate (W). Switching-related power, not MOSFET junction total.	W	output

Assumptions / Validity

Declared scope for this capability. Do not use it outside this domain.

Assumptions

Linear V/I transition; neglects Coss/Qoss and diode recovery.
tr/tf are effective overlap times at the operating point.
P_gate is gate-drive power shared among driver, Rg, and Rg,int — not MOSFET junction dissipation.
Qg is total gate charge at approximately the entered Vdrive, not an unscaled datasheet Qg at a different VGS.

Example

One numerical check. The calculator page holds worked steps and FAQ.

Vds=48, Id=10, tr=50ns, tf=40ns, f=100kHz → P_sw=2.16 W

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance. Computational verification is defined by CVP. Supplemental domain review (internal) and named expert review are defined by the Review policy and do not by themselves determine CVP conformance.

CVP: CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance· View Manifest · CVP overview · Specification
Assurance: Engineering
Declared partition coverage: PASS · 3/3 declared partitions (overlap-only, with-gate, invalid-domain)
Calculation version: 1.0.0
Verification: 13/13 calculation tests · 2/2 legacy golden · 6/6 legacy boundary · 5/5 legacy property
Production surface contract: 11/11
Versions: Calculation 1.0.0 · CVP protocol 1.0.0-proposed
CVP identity: 5/5 property · digest e80c68d19929
Reference: O1 model · O2 expected_values · O2 numerical_behavior
Interfaces: PASS · UI (SSR) / REST / MCP
ui-ssr is query-result HTML, not a live browser session.
CVP suite: 2/2 golden · 6/6 CVP boundary · 6/6 invalid · 5/5 property · 1/1 cross-interface · 11/11 CVP contract
Supplemental domain review: Internal · Pass · electrical-engineer
Named expert review: Not performed
Version lock: Supported (409 VERSION_MISMATCH)
Artifact consistency: Build verified · 1.0.0 (workspace artifacts agree)
Review-policy tier: Internal engineering review — catalog token expert_verified; supplemental; not CVP status

This calculator CURRENT · Public schema 1.0.0 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

Call this capability

Human page, REST, and MCP share the same engine and calculation_version. Build verified hashes workspace artifacts only. After deploy, attest:production GETs canonical URLs twice — the public/cached view an Agent actually hits, and origin — including every /capabilities/{id} HTML page. Public Capability HTML version must match catalog before production attestation passes. Live Trust rows above fetch /.well-known/calculatorx-production-attestation.json and the output schema const. Build hashes: release integrity. That proves currently published page / engine / schema / evidence / MCP agree — not that a historical version is independently immutable. Reference Calculation Standard — Production surface contract 11/11.

Tool id: mosfet-switching-loss
Engine: mosfet-switching-loss
REST: POST /api/v1/calc/mosfet-switching-loss
MCP: execute_calculation with capability_id: "electrical.mosfet.switching_loss"
Agent input schema: Canonical (MCP / Agent)
Output schema: JSON Schema (latest)
Versioned input schema: Immutable pin (1.0.0)
Versioned output schema: Immutable pin (1.0.0)

References

Human-readable sources plus CVP reference evidence classes.

Sources

Erickson & Maksimović — Fundamentals of Power Electronics — Hard-switching loss estimates
Texas Instruments SLYT664 — MOSFET power losses and how they affect power-supply efficiency — Switching and gate-drive loss
Texas Instruments SLUA618 — Fundamentals of MOSFET and IGBT Gate Driver Circuits — Gate-drive energy split among driver and gate resistance

Reference evidence classes: O1 model · O2 expected_values · O2 numerical_behavior

Try with an agent

Inspect this capability via same-origin MCP, then call execute_calculation.

curl -sS -X POST 'https://www.calculatorx.com/mcp' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/call' \
  -H 'Mcp-Name: inspect_capability' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"inspect_capability","arguments":{"capability_id":"electrical.mosfet.switching_loss"}}}'

Inspect the trust tier and required assurance level before execution. Pin calculation_version (1.0.0) when reproducibility matters. Full protocol notes: MCP docs.