KCC's Quizzes AQQ304 - A pure logic
1. Quote of the month: "I am not lazy, I'm just in energy-saving mode" - unknown
2. Quiz AQQ304 about finding a pure logic puzzle
Mike is looking at Anne, but Anne is looking at Paul.
Mike is married, but Paul is not.
Question:
Is a married
View All
September Monthly Blog Quiz! Read the blog, take the quiz, and you could win a gift card
Quiz: How Well Do You Know Adaptive Power Switching?
Is your I/O module overheating? The AD74416H's Adaptive Power Switching (APS) can cut heat dissipation by up to 40% — but how well do you really understand how it works?
Read the blog first: Cooling
View All
LTspice
Production
LTspice® is a powerful, fast, and free SPICE simulator software, schematic capture and waveform viewer with enhancements and models for improving the simulation...
LTspice on Analog.com
Dear community,
I have some difficulties in correctly understanding and using the VDMOS model in order to correctly set the rise and fall time, as well as the thermal properties via the parameters.
The following parameters are given for my desired simple model: Fall time, rise time, RDS(on), UF0 (inverse diode forward voltage), Rb (diode resistance) and thermal semiconductor resistance. How can I set these specified values via the parameters of the VDMOS? For example, I know that the rise and fall times are functions of the input and output capacities, but I don't know how to parameterize the capacities in order to achieve the desired behavior (roughly).
Furthermore, I am not sure how I can connect the SOAtherm-HeatSink model to my VDMOS in order to determine the semiconductor temperature. I don't have the SOAtherm-NMOS model in my LTspice version.
If you could help me with these problems, I would be very grateful to you!
Best Regards
Falk
GenevaCooper - Moved from StudentZone (Analog Dialogue) to Other Products (EN). Post date updated from Friday, January 10, 2020 8:41 AM UTC to Monday, June 30, 2025 3:35 PM UTC to reflect the move.
GenevaCooper - Moved from Other Products (EN) to LTspice. Post date updated from Monday, June 30, 2025 3:35 PM UTC to Monday, June 30, 2025 3:38 PM UTC to reflect the move.