kicad-lib-committers team mailing list archive

[John Beard <john.j.beard@xxxxxxxxx>]

On 10/03/14 15:10, Carl Poirier wrote:
> Let's continue our discussion about this. Lorenzo, do you have access to
> the relevant documents?
>
> On Wed, Feb 26, 2014 at 2:22 PM, Vesa Solonen <vesa.solonen@xxxxxxxx
> <mailto:vesa.solonen@xxxxxxxx>> wrote:
>
>26/02/14 11:00, Kerusey Karyu kirjoitti:
>>
>> In 25 lutego 2014 19:46 Carl Poirier wrote:
>>
>>> Regarding your last email, do you have any reason why not
>>> to put a dash between "SOT" and "23", for example?
>>>
>
>The most important thing to consider when deciding is JEDEC standard. It
>seems they say with dash.

Hi,

I don't know if this standard is the one you are looking for, but
JEDEC Publication Number 95, Section 1.6 "Outline Classification"
might be along the right lines when talking about a JEDEC Outline
Number:

> 1.6 a) Outlines are designated with two letters (DO, TO, MO, UO, CO)
> followed by sequential numbers (e.g., DO-35, TO-220, MO-16).
>
> 1.6 b) Two letters follow the number to designate which member of
> the family of variation (e.g., DO-OO1AA, TO-226AB, MO-069AE). Often
> the only differentiation between variations is the lead count.

JEDEC Standard 30 (I looked at Rev. F), section 3.1 describes a
"descriptive designation", as opposed to the outline number.

>
> 3.1 General:
>
> ...a mandatory field (shown below) consisting of a three-letter basic
> package designator that indicates the package outline style and
> terminal position or form, preceded by a field to indicate the
> package-body material. This mandatory package designator may be
> extended, through the use user-selected fields, to provide
> additional package information such specific package features,
> package differentiators, terminal count, and supplemental
> information separated from the descriptive designator by a slash (/).

An example is "TS-PDSO2-44(50)/5.3x10.2-1.27". It doesn't say
anything about the presence or not of a hyphen between "DSO" and
"2". However, the examples in Table C.1 of JESD30F uses "SOT89" as an
example. This is the only descriptive designator in the table
without a hyphen (others include T-PQFP-44).

We also don't see the hyphenation used in section 3.1 in everyday
usage of packages like TSSOPs, where TS is a "specific package
feature" (thin shink, see table 3) and "SOP" is the "package
designator" (table 1), rather we see a hyphen in between TS and the rest.

So it seems to me that JESD30 and JEDEC PN 70 don't fully define the
question that you're asking re hyphenation, and aren't even totally
consistent with their own examples. Moreover, SOT may be a bad
example to use, as it is unique in not having a hyphen in the
examples table.

Sorry to not have a cut-and-dry answer!

Cheers,

John