I have been wondering about the transistor symbols. In general conversation, there seems to be the first statement of “symbols are not connected to actual devices.” Yet in the transistor library, there are a ton of similar symbols named after specific devices (which have different footprints, which I’m sure is the reason).
Is there an issue with making a set of generic transistors?
If the transistors were truly generic, I would expect to see:
(xMOSFET, xFET, xCH, or whichever prefix is ‘standard’)
It’d be nice to not have to sort through a ton of similar devices looking for a desired symbol (device type only) when putting down a first draft schematic prior to picking the exact device.
The device.lib library has generic parts, very similar to your post.
I presume transistors.lib is more of a hobbyist origin, you would be surprised how many people complain that they have to figure out which symbol a BC109 is
The transistor lib like all specialized lib is for specialized (atomic) symbols.
Or at least we hope that in future it will be that way.
Examples would be smart fets from infineon (currently in infineon lib), …
Your example bc109 is not in there (yet) but a lot of other typical tranistors exist. Yes they are not yet quasi atomic. Another lib that needs work. (Sadly the quality of the official lib varies a bit across different libs. But it gets better each day.)
This class of part is a generic part made by a number of different manufacturers with seemingly equivalent parts, but which don’t share a full MPN for the same pacakage. These part will named using the base MPN followed by a suffix of the base package type.