3D Models
Note! To download footprints and symbols, use the build and request forms below
Request (48 hours)
- Datasheet Download Datasheet
- Stock & Prices $ Price & Stock for Q2010L5
- Part Number Q2010L5
- Manufacturer LITTELFUSE
- Last Modified Date Oct 6, 2025 1:29 PM UTC
- Pinout / Pin List Click Here (Member Only)
Q2010L5 Details
-
Manufacturer Part Number:
Q2010L5
-
Rohs Code:
Yes
-
Part Life Cycle Code:
Obsolete
-
Part Package Code:
TO-220AB
-
Package Description:
TO-220, 3 PIN
-
Pin Count:
3
-
ECCN Code:
EAR99
-
HTS Code:
8541.30.00.80
-
Manufacturer:
Littelfuse Inc
-
YTEOL:
0
-
Case Connection:
ISOLATED
Q2010L5 Frequently Asked Questions (FAQs)
-
Littelfuse recommends a PCB layout with a large copper area connected to the thermal tab of the device to dissipate heat efficiently. A minimum of 1 oz copper thickness and a thermal relief pattern around the device are also recommended.
-
Yes, the Q2010L5 is designed to meet the requirements of high-reliability applications. It is qualified to AEC-Q101 and is suitable for use in automotive and aerospace applications.
-
In a fault condition, the Q2010L5 is designed to open quickly to minimize damage to the device and the surrounding circuitry. The device will typically open within 1-2 ms of a fault condition, depending on the specific application and circuit design.
-
Yes, the Q2010L5 can be used in parallel to increase the overall current rating, but it is essential to ensure that the devices are properly matched and that the circuit design takes into account the potential for current imbalance between devices.
-
Littelfuse recommends storing the Q2010L5 in a dry, cool place, away from direct sunlight and moisture. The devices should be handled with care to prevent mechanical damage, and electrostatic discharge (ESD) precautions should be taken to prevent damage to the device.
Trust Checks
Trust Score Unavailable
Q2010L5 Overview
Use the download button to access the Q2010L5 3D model. You can still request or build the schematic symbol and PCB footprint by using the respective build or request forms on this page.
