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 Q8025R5
- Part Number Q8025R5
- Manufacturer LITTELFUSE
- Last Modified Date Oct 6, 2025 1:29 PM UTC
- Pinout / Pin List Click Here (Member Only)
Q8025R5 Details
-
Manufacturer Part Number:
Q8025R5
-
Pbfree Code:
No
-
Rohs Code:
Yes
-
Part Life Cycle Code:
Obsolete
-
Part Package Code:
TO-220AB
-
Package Description:
ROHS COMPLIANT, TO-220, 3 PIN
-
Pin Count:
3
-
ECCN Code:
EAR99
-
HTS Code:
8541.30.00.80
-
Manufacturer:
Littelfuse Inc
-
YTEOL:
0
Q8025R5 Frequently Asked Questions (FAQs)
-
Littelfuse provides a recommended PCB layout and land pattern in their application note AN9313, which can be found on their website. It's essential to follow these guidelines to ensure proper thermal performance and reliability.
-
To select the correct fuse rating, consider the maximum current and voltage in your circuit, as well as the fault current and fault clearing time required. Littelfuse provides a fuse selection guide in their catalog, which can help engineers choose the appropriate fuse rating.
-
The Q8025R5 has an operating temperature range of -40°C to 125°C, making it suitable for a wide range of applications. However, it's essential to consider the derating curves and thermal performance when operating at high temperatures.
-
Yes, the Q8025R5 is compatible with lead-free soldering processes and meets the requirements of the RoHS directive. Littelfuse provides guidance on lead-free soldering in their application note AN9312.
-
Littelfuse provides reliability and MTBF ratings for the Q8025R5 in their reliability report, which can be found on their website. The MTBF rating is typically in the range of 100,000 to 1,000,000 hours, depending on the operating conditions.
Trust Checks
Trust Score Unavailable
Q8025R5 Overview
Use the download button to access the Q8025R5 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.
