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 Q6025R6
- Part Number Q6025R6
- Manufacturer LITTELFUSE
- Last Modified Date Oct 6, 2025 1:29 PM UTC
- Pinout / Pin List Click Here (Member Only)
Q6025R6 Details
-
Manufacturer Part Number:
Q6025R6
-
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
Q6025R6 Frequently Asked Questions (FAQs)
-
Littelfuse recommends a thermal pad with a minimum size of 100mm² and a thickness of 1.5mm to ensure optimal heat dissipation. Additionally, a thermal via array with a minimum of 10 vias is recommended to connect the thermal pad to the bottom layer of the PCB.
-
Yes, the Q6025R6 is designed to meet the requirements of high-reliability applications. It is built with a robust design and undergoes rigorous testing to ensure its performance and reliability in harsh environments.
-
The Q6025R6 is designed to withstand surge currents up to 200A and voltage spikes up to 600V. It has a built-in surge protection mechanism that helps to absorb and dissipate the energy of the surge, protecting the downstream circuitry.
-
Yes, the Q6025R6 is compatible with lead-free soldering processes. It is designed to meet the requirements of RoHS (Restriction of Hazardous Substances) and is suitable for use in lead-free soldering applications.
-
Littelfuse recommends storing the Q6025R6 in a dry, cool place away from direct sunlight and moisture. It should be handled with care to avoid mechanical stress, and electrostatic discharge (ESD) precautions should be taken to prevent damage to the device.
Trust Checks
Trust Score Unavailable
Q6025R6 Overview
Use the download button to access the Q6025R6 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.
