Then again, that assumes that all the symbols are correct.
Look under the Interface ICs for the “MC6840”. That is actually the MC6821 PIA!
(I have a correctly drawn MC6840 PTM symbol in my personal library, among other rare ICs, but don’t really have the time / patience to go through the process for submitting them to gitlab) Symbols.kicad_sym (32.3 KB)
This will bring up a “Select Library” page and again use “Other Locations” to find and
highlight the new libraries you wish to add.
doesn’t allow me to select the Custom Symbol folder per se, it makes me enter it instead …
same thing happens if I try to create new Library from within Symbol Editor it tried to create a kicad_sym file (within my Custom Symbols folder) … I would expect it to create a folder, no ??!
.kicad_sym is a symbol library (and a normal file within the filesystem) so would normally hold multiple symbols, but of course a library could also contain 0 or 1 symbols.
For example here are selected lines from my nixie.kicad_sym:
in other words, the Custom Symbols folder I created manually inside my home/Kicad folder is holding a bunch of kicad_sym libraries (… what I’m incorrectly thinking of as symbol files - in the same way kicad_mod files are single footprints in my Custom Footprints folder) some of them holding one single symbol.
what I’m hearing is that the actual “symbols” themselves are but lines of code inside these librairy files and not separate file themselves.
No, not in the same way. .pretty libraries are really directories or folders, and a .kicad_mod file within a .pretty directory is a single footprint (not symbol, be careful with nomenclature, terms have defined meanings within KiCad).
The exact implementation of libraries shouldn’t concern most users since they may change in future KiCad versions, but the conceptual structure will remain.
If there is a single fact that KiCad users should know it’s that there are three major entities of interest.
symbols, what you work with on a schematic
footprints, what you work with on the PCB
3D models, what you see in the 3D viewer
The three entities are decoupled, a symbol can be associated with more than one footprint (think of components available in multiple packages), and a footprint can be used for more than one symbol (think common package outlines). Although a symbol may specify a default footprint, which can be overrriden in the schematic editor.
Within these entities, you have pins, numbers (more correctly pin IDs), pin type, pads, etc. etc.
Sorry, I’m not involved with writing the docs and I usually forget how I picked up various bits of information. I think I learnt the most from the book and course by Peter Dalmaris back in v5 days. There is a new release for v6 and I think it’s worth paying for.
Thanks for your reply jmk, this time around it made more sense … a few questions if I may:
yes, I got this far … and verified I’ve got an empty (shell) kicad_sym file with the name I gave it residing in my new Symbol folder …
by giving the library global status the listing already
appears there, all good … (I think)
from here things don’t work out somehow though,
this is where a conflict appeared as it was trying to overrite the same file name in that folder …
so, I stopped there
this is where I get confused and I don’t see them the same way at all … for me, footprints are (kicad_mod) file/objects, as I have them in my Custom Footprint folder for example - did a few projects with them, seem to work ok … bottom line, one file per footprint … whereas, so far as i get it, symbols exist as code snippets inside (kicad_sym) library files - and so don’t exist in separate files per se unless a library holds exactly one symbol (I guess)
here’s a simple way I see using this, say I want to have different 1n4148 diode symbols, one each for different vendour sources. I could see having a 1n4148.kicad_sym library file with the three symbols coded in.
Of course. But you’d have to give them different names, say ti-1n4148 for the one by TI and os-1n4148 for the one by OnSemi. If they were in different libraries, then of course they could be both 1n4148 since they are distinguished by the library they reside in.
But this is only a hypothetical example, after all how many ways are there to draw a diode with 2 pins? Footprints will differ due to different packages, sure.
editing the shape of the part is quite secondary for me at this point
let me reframe the question:
what’s the quickest way of saving a copy of a schematic symbol along with its associated properties ?!
so far, I’m not having luck saving something (anything) in the kicad_sym file inside the folder I created
the idea is to have, say, a 1n4148.kicad_sym library file inside my Diodes folder that contain “symbols” which use the same symbol graphics and settings, but have different associated vendour link and associated footprints in the properties window. Different symbols per se, but in fact different instances of the same thing but with altered property attributes
Assuming you have the symbol in the symbol editor window, do File > Save As. This will then bring up a dialogue asking what new name if any to give it, and the library to save to. Scroll down until you find your library, and save to that. The system ones will not be writable because they are meant to be read-only.
You might want to read up on the symbol inheritance feature that might allow you to derive many symbols from a parent symbol. First you have to create the parent symbol, and then when creating new child symbols, use the derived from field in the properties.
I consider it a UI flaw that you have to create the writable library ahead of time, instead of there being choice to create a new library at the save as popup.
… by way of sheer luck I finally found my problem!
Turns out after I hit “save to that” I also have to hit save a second time before closing the Symbol Edit window otherwise the kicad_sym file doesn’t get re-written … I went through this a few times and took notice of the pop-up box that warns about changes not being saved (I thought this only referred to visual shape and text edits of the symbol per se so I ignored it at first)
sure enough, the kicad_sym text file looks good testing by way of two different attribute sets (with different names) starting from a duplicated schematic symbol and edited for different properties and footprints …
now if I go to the Symbol Browser I see both symbols appear inside their designated library header while showing correct inner properties when hovering …
I can also now edit the “description” field as it shows in the Symbol Browser
must say … it’s all too beautiful
I want to thank you all for sticking with me // having this understanding is a game changer for me …
That’s true, although the system libraries still use this suffix. Probably a relic of an ancient version. So I renamed my directory with suffix .footprint and adjusted fp-lib-table. I’ve always been puzzled about what’s pretty about footprints.