, add a small enough value to the Maximum Timestep command in the. So the actual problem is with the IPW60R041C6_元 (from Infineon) which worked okay with LTSpice IV but just results in the time step too small error with LTSpice XVII referencing the 2N7002 MOSFET M6. If LTspice gives the error Analysis: Time step too small.
I thought originally some of that circuitry could be causing the problem! Removing the 1 off 2N7002 or the 2 off IPW60R041C6_元 removes the error! I originally tried the variations of the 2N7002 included in the. I have removed all the original complicated drive, sensing and variable load circuitry for the MOSFETs (i.e. So the time step gets small either when youre doing something that challenges the algorithm (like a stiff system), or when youre asking for too much (like the relative tolerance that jrive) spoke of. I am assuming that this is an issue with convergence since this. Nearly all such solvers adjust the time step dynamically, trying for the largest possible time step while maintaining accuracy. Im a little fuzzy on how I might correct this or what is causing it. Now, I have taken out almost all of my circuit and it is left with 1 off 2N7002 MOSFET M6 which is referenced in the time step too small error and 2 off IPW60R041C6_元 M1 and M2 which includes a Thermal model. I am running the following file and getting the error: doAnalyses: TRAN: Timestep too small time 3.66683e-10, timestep 5e-22: trouble with node '3'. I appreciate that a schematic and/or models are really needed! I was hoping that someone would have some idea why it might give the time step too small error using LTSpice XVII versus LTSpice IV.
0 kommentar(er)
