Skip to main content
6 events
when toggle format what by license comment
Sep 14, 2016 at 6:06 comment added a concerned citizen One other bad example with "hardcoding" is adding the library/model, with or without path. That will cause errors for anyone using the symbol and not on your computer. Not everyone has the same paths and/or libraries as you do. In general, the safest way to handle projects, hierarchical or not, is to put all the relevant schematics, models, libraries, symbols, etc inside one folder, and use the .inc or .lib directives without paths, simply names (LTspice will look first in the current directory). Tis way, exporting the folder will work on everyone's computer.
Sep 14, 2016 at 6:01 comment added a concerned citizen Then I'm afraid your only other option is to use a subcircuit. You can use a hierarchical schematic with a symbol, but not with two, they would have to have the same name. For the other symbol, you'll need a subcircuit (with a "block" symbol). By "hardcoded" I mean, when inside the symbol editor, do not edit the SpiceModel line, or add its instance name in any field, let it be empty and only add the instance name from within the schematic. Think of it as a blank symbol, where you place it in the schematic and add its name, value, etc on the fly, but this is more for subcircuits.
Sep 14, 2016 at 3:59 comment added FriendFX Thanks for your contribution, you are correct in that I am talking about hierarchical schematics. Unfortunately, I don't understand what you mean by "hardcoded" edits. Since my LTspice schematics and symbols are all ASCII text files, I had a look into them (using a text editor) and could not find any references to the schematic they "belong to". Also, since I use version control that treats file-system symbolic links as files, I cannot use them (I work across Windows and GNU/Linux platforms).
Sep 13, 2016 at 15:47 history edited a concerned citizen CC BY-SA 3.0
added another possibility
Sep 13, 2016 at 6:38 history edited a concerned citizen CC BY-SA 3.0
adde clarification
Sep 13, 2016 at 6:16 history answered a concerned citizen CC BY-SA 3.0