|
|
|
|
|
by m-ee
1920 days ago
|
|
As someone that actually uses LTSpice I’ve never considered speed to be an issue. The main draws for it are 1. It’s free unlike Altium addons or orcad p-spice 2. Graphical, I’m happy to code things but code literacy varies widely among EEs. Much easier to share results when it looks like a schematic 3. Good enough component library. The time spent finding and inputting component parameters are gonna be way bigger than any savings on the actual computation I mostly work on small embedded systems boards and use simulation to probe behavior of analog sub systems I’m concerned about, rather than simulating the whole board. Maybe more complex designs get more like CFD models where computation time is measured in hours or days. Would love to see someone use this as a backend for an alternative to the major spice programs, LTSpice UI isn’t exactly pleasant, and is unusable on Mac so it wouldn’t take a whole lot to get me to switch. |
|
I only simulate one pulse (about 3 ms), but the simulation takes minutes to resolve the inrush. Tuning circuit impedances to match measurement is a real pain. At this point I'm just going to take many more direct measurements. If it was quick I would have written a script to scan through unknown parameters to maximize correlation with measurements, but that isn't reasonable when the simulation fails after several minutes of trying for most values.