Skip to content

Added Vishay PowerPAK 8x8L NMOS automotive lineup

I have added the current lineup of the PowerPAK 8 x 8L automotive n-channel MOSFETS to the symbol library. The symbol field layout is kept similar to the changes made in !4155 (merged). The only difference is that I maintained everything on a 50 mil grid instead of the 25 mil used in !4155 (merged). I am sorry that this is a fairly large PR, but fortunately all new MOSFET symbols inherit from the same base symbol. For better readability, I have grouped the screenshots and details in 3 sections covering the KiCad symbol, the new pinout, and a comparison to the Vishay product lineup.

Summary:

1. KiCad symbol

Vishay_NMOS_symbol Vishay_NMOS_properties Vishay_NMOS_fp_filter

The rationale behind this PR is that there are currently no compatible symbols for the PowerPAK 8 x 8L footprint/package. This package uses pin 1 as gate, pins 2-4 as source and pin 5/tab as drain as shown below using a screenshot from the Vishay datasheet. For comparison, see the new pinout from the KiCad symbol editor. The footprint itself is covered in a separate PR.

Symbol pinout Vishay_NMOS_datasheet

Vishay_NMOS_pins

The new symbol is based on the Vishay SQJQ160E, which is the MOSFET I use in my design. Since I was creating a new symbol anyway, I decided to add the rest of the lineup as well. To ease the review of this large PR, I have attached three screenshots for a side-by-side comparison of the KiCad properties and the Vishay product lineup as shown on their website.

Vishay product lineup comparison Vishay_NMOS_kicad Vishay_NMOS_1 Vishay_NMOS_2

The datasheets of all MOSFETs covered are

Do note, not all logic level FETs are denoted by a trailing 'L' (Dear Vishay, what was marketing thinking?)


  • Remove the instructional content of this template
  • Provide a URL to a datasheet for the symbol(s) you are contributing
  • An example screenshot image is very helpful
  • Ensure that the associated footprints match the official footprint library
    • A new fitting footprint must be submitted if the library does not yet contain one.
  • If there are matching footprint PRs, provide link(s) as appropriate
  • Check the output of the automated check scripts - fix any errors as required
  • Give a reason behind any intentional library convention rule violation.
Edited by Patrick Baus

Merge request reports