LTSpice uses whatever you type. No matter what the case usage in the MODEL statement, any combination of upper/lower case letter can be used in the schematic, and the model will be picked up from the file perfectly well.LTSpice uses capitals as well.
The original usage of the letters was meant to be upper case
The list to choose from when you change part is upper case.LTSpice uses whatever you type
Ah, got you. Since I'm using external libraries I have to key in the name, not use the drop down.The list to choose from when you change part is upper case.
I'm using LTSpice on Linux, but under Wine. I know Windows apps have a bias towards case-insensitivity. As a Unix guy since '86, this drives me crazy.I get careful of case here as Unix origin software like NGspice tend to be case sensitive
Originally transistor naming followed the Mullard valve convention: 0C81= zero volt heater single 'triode'. Later the redundant '0' was dropped and A or B added where A = germanium B = silicon so BCxxx = silicon 'triode'. Much more info here, but always upper case: https://www.electronics-notes.com/a...nts/transistor/transistor-codes-numbering.phpQuestion for the tidy minded. In a component like the bc546, is it conventional to use block caps (BC546) or lower case (bc546).
That's a VERY helpful link/response. It answers my question about caps, and tells me so much more besides. Joy to my slightly completist side!Originally transistor naming followed the Mullard valve convention: 0C81= zero volt heater single 'triode'. Later the redundant '0' was dropped and A or B added where A = germanium B = silicon so BCxxx = silicon 'triode'. Much more info here, but always upper case: https://www.electronics-notes.com/a...nts/transistor/transistor-codes-numbering.php