- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2056013_en-US
2056013_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2056013_en-US
2056013_en-US
Hi NXP,
Please clarify the difference between DESAT_LED (Leading edge blanking time and DESAT filter time). Is it so that the DESA_LEB refers to the programmable time after which Vds will be on?
Hi Akshat,
DESAT_LEB (Leading Edge Blanking Time) - This is the initial delay after the gate driver turns ON the power device, during which DESAT detection is ignored to prevent false triggering from transient spikes. The purpose is, when an IGBT or SiC MOSFET turns ON, there is a natural transient period where VCE/VDS momentarily spikes due to switching dynamics. DESAT_LEB prevents the gate driver from falsely detecting a desaturation event during this period. Think of DESAT_LEB as a "safe startup window" where DESAT protection is temporarily disabled to avoid false faults.
DESAT Filter Time - This is the additional delay after DESAT_LEB before a DESAT fault is actually triggered. Even after DESAT_LEB ends, noise or transient overshoots may cause momentary high VCE/VDS readings. The DESAT filter time ensures that only sustained high VCE/VDS triggers a DESAT fault. Think of DESAT filter time as a "confirmation delay" to ensure only real desaturation events trigger a fault.
BRs, Tomas