3rd Party Models in Ltspice

Discussion in 'The Projects Forum' started by Bob123456, Sep 24, 2014.

  1. Bob123456

    Thread Starter New Member

    Aug 14, 2013
  2. eetech00

    Active Member

    Jun 8, 2013
    It works ok on my system.

    1. Create a folder to store the files
    2. unzip the .zip file into the folder
    3. click on one of the "TestBench.asc" files

  3. crutschow


    Mar 14, 2008
    TL431.asy is the symbol file which goes in the LTC\LTspiceIV\ lib\sym\references folder.
    TL431ED.sub is the circuit model file which goes in the LTC\LTspiceIV\ lib\sub folder.
    The others are various test and example files.

    After placing these two files in the above referenced folders, restart LTspice. The TL431 should now show in the Component [References] parts list.

    Unfortunately that symbol file does not include the reference to the model file so you have to reference it in a Spice Directive (press S) on the schematic as .lib Tl431ED.sub when you use the device in your schematic.

    Alternately if you want to avoid that, use the Edit Attribute command of the T431.asy symbol file in LTspice and add:
    TL431ED.sub for SpiceModel and
    TL431ED for Value2.
  4. eetech00

    Active Member

    Jun 8, 2013

    This method will work if you don't run into file system permission problems.

    However, the method recommended by LTSpice Group is to put all the required files into a newly created schematic folder and place all necessary files into the folder. Resist the temptation to put files into the LTSPice program install folder hierarchy (lib\sub, lib\sym) as they could be inadvertently removed by an LTSpice program update. The other problem it creates is that the sending user must remember to copy any custom library files to the zip file when exchanging schematics with other users. If all files are in the schematic folder, then the sender can simply zip the folder up and send it.

  5. wayneh


    Sep 9, 2010
    I initially wanted to use crutschow's method and had success doing that. But the guys at that Group convinced me to follow protocol. The ability to move your circuit around with all needed 3rd party models is what tipped the scales for me. Just had to accept those silly "include" statements.