How to Check MOSFET On-Resistance at the Actual Gate Drive

1. Define the Gate-Source Drive

Identify the voltage the circuit applies between the gate and source in the intended on-state. Keep the source reference explicit, particularly where it differs from the logic ground used in a short description. Ask the design owner for the drive requirement and the documentation that supports it. A controller supply label alone is an incomplete drive description.

Nexperia's MOSFET application note separates gate-source threshold from drain-source on-resistance. Threshold has its own measurement definition, while on-resistance is specified under stated operating conditions. Use that distinction when a candidate is described as logic level or when someone proposes its threshold figure as evidence that it is fully enhanced.

Record which operating states the review covers and which remain unresolved. A gate-drive requirement should say whether it describes a normal on-state or another condition requiring separate assessment. Preserve the released device as the baseline. If the driver configuration is unknown, do not replace the missing requirement with a familiar marketing category.

2. Read On-Resistance Conditions

Locate the on-resistance entry in the exact device's electrical characteristics. Retain the gate-source voltage, drain-current condition, temperature and specification classification. Nexperia explains that RDS(on) changes with gate-source voltage and junction temperature. The comparison therefore needs the conditions attached to the value, not a detached resistance number.

Create a comparison row for the drive condition engineering requires. If a candidate is specified at another condition, identify the difference and ask whether the available evidence supports the proposed use. Do not assume that a lower headline value taken at a different bias is a better answer to the same application question.

Keep minimum, typical and maximum columns distinct where the document provides them. A typical characteristic can help explain behavior, while an engineering decision may require a specified limit. Leave the field unresolved when the relevant limit is unavailable. This article does not interpolate resistance values or provide a numerical candidate comparison.

3. Preserve Junction-Temperature Context

Ask the design owner which junction-temperature context must accompany the on-resistance requirement. Keep it separate from ambient temperature and from a thermal assumption that has not been evaluated. A catalogue test temperature describes the source data; it is not automatically the die temperature in the intended assembly.

Nexperia's note discusses the temperature dependence and includes illustrative characteristics. Treat an illustration according to its stated scope. It cannot create a guaranteed hot-resistance figure for an unidentified part. Preserve the actual device reference and the evidence needed for the reviewer's selected operating condition.

If a loss or thermal assessment is required, record its status independently. The drive/resistance review does not calculate switching loss, establish safe operating area or approve a cooling arrangement. Ask engineering to identify the additional evaluations and their inputs. Keep proposed assumptions visible rather than presenting a partial calculation as an accepted application result.

4. Keep Candidate Limitations Visible

List the candidate's supported and unsupported conditions beside the released requirement. Useful entries include the exact code, required drive, available specification basis and the reviewer's remaining questions. This creates a focused technical exception record instead of using a general cross-reference listing as evidence of equivalence.

Check that the resistance question stays connected to the wider component decision. Engineering may need separate reviews of pin functions, drive dynamics, protection behavior or other application limits. Record those requirements without claiming that this article has completed them. A satisfactory resistance entry is one input to the decision.

For an ICULTRA inquiry, identify the permitted MOSFET code and any separately proposed candidate. Link the relevant device documentation and unresolved drive-condition questions. Keep the original requirement intact until engineering accepts a change. The purpose is to make the technical comparison auditable; no stock, performance improvement or drop-in replacement is established here.

Sources and further reading

• Nexperia — Understanding Power MOSFET Datasheet Parameters, AN11158

Nexperia's application note supports the parameter distinctions. This guide supplies no plotted values, numerical loss example, thermal validation, driver approval or compatible-replacement claim.