Threads mergedNeed for VDMOS model for MC12
This post was some time ago, but I have the same question. Using the great MC12 but need a VDMOS model. Would make my day
This post was some time ago, but I have the same question. Using the great MC12 but need a VDMOS model. Would make my day
This post was some time ago, but I have the same question. Using the great MC12 but need a VDMOS model. Would make my day
The uC lib contains several VDMOS in the DN2530 series from Supertex. They can be found under MC12/library/supertex.lib but there's no subcircuit for a general VDMOS.
I need the VDMOS model for simulations using lateral MOSFETs 20N20/20P20. The spice model for them use the VDMOS and the only alternatives I've seen is LTspice or Superspice. But I'm used to work with MC12.
Lateral MOS is available and the models (see pic) are very good, to the extent that amps using the 20P20 show a quirk, absent with the Hitachi 2SJ160.
Attachments
Thanks! I was looking for VDMOS, but the devices ARE there
I just got Superspice up and running with VDMOS Models. Mayby I should compare the results between MC12 and Superspice. Could be interesting.
Thanks! I was looking for VDMOS, but the devices ARE there
I just got Superspice up and running with VDMOS Models. Mayby I should compare the results between MC12 and Superspice. Could be interesting.
My pleasure! An interesting issue to investigate regards the difference between N- and P- versions of the 20x20: for lowest distortion in an amp where they're used as followers, uC12 suggests that the P requires a 470R gate resistor.
Yes, that and lot of other things are automated in MC.
If you need some coding for special functions, you can do it also but not like in LT spice, everything is overcomplicated for my taste...
MC continues to be updated, the last version allows faster placing of components. Right-click a component on the parts menu and choose one of its 8 possible positions. For me, drawing a diagram with MC is faster than with pen and paper.
The automated functions like THD, IMD (useful for RF too) are enough for more than 99% of my requirements and 100% for audio - for instance DC analysis provides temp stability and with AC analysis you can get input noise in dBv/(SQR(Hz) and compare with other topologies and or input parts.
Quite a few years ago I was using an ASUS A7J (32 bit machine) under Linux wine and all MC demos were running OK. The issue might be with the 64 bit version of MC: try running the demos with 32 bit version.
It's also possible that versions 11 and 12 have a different dependency on Windows. On the 32 bit Ubuntu machine I was using version 9 and you couldn't see a difference re functionality (including speed) between wine and XP.
I liked MC for one thing: it is the best didactic tool maybe. But otherwise it is compatible with nothing, it is not possible to export a MC netlist into a regular spice/pspice netlist or into another schematic format or a pcb/gerber format. Which imply it's usage is very limited. It is too bad because both its schematic and analysis are powerful and easy to use.
That's not my experience with MC. Perhaps you simply doesn't know how to do it.
- Status
- This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.