I moved that rule 1.6 away and into the symbols section.
On Wed, Jul 30, 2014 at 11:51 AM, Carl Poirier <[email protected]> wrote: > This has been committed. > > BTW, is there any particular reason to having the value field of a > footprint default to "VAL**", besides indicating it has not been set ? I'll > have to add that to the convention. > > I ask because I noticed I had put rule "1.6. The Value field must be > prefilled with the object name." in the general rules, whereas I believe it > applies only to symbols. Actually most of them if not all are filled with > the reference designator by default. > > > On Sat, Jul 26, 2014 at 11:05 AM, Carl Poirier <[email protected]> > wrote: > >> Let's use the full name, then. So here are the adjustments: >> >> 2. Symbol Library Names (.lib files) >> ------------------------------------ >> >> 2.1. Manufacturer. >> 2.2. Category or family of parts. ex: "Capacitors", "Spartan6", etc. >> >> >> 4. Symbol Names >> --------------- >> >> 4.1. Name of symbol, may be shortened for common components or use >> reference designator of the symbol (IEEE 315-1975). ex: "Conn_4x2", "C"etc. >> 4.2. Manufacturer. >> 4.3. Part number, including extension for specific footprint. (JEDEC for >> common devices, ex: 1N4001) >> 4.4. Any modification to the original footprint, indicated by appending >> the reason. Ex: different pin ordering: "transistor_PNP_pinswap1" >> 4.5. Indication of quantity if symbol is an array. ex: resistor array: >> "Resistor_x8" >> >> Any other comments? >> >> >> On Sat, Jul 26, 2014 at 2:13 AM, Kerusey Karyu <[email protected]> >> wrote: >> >>> W dniu 25.07.2014 19:29, Carl Poirier pisze: >>> >>> >>> > In this case it's not much of a problem because the extra letters >>> > indicating the footprint are official names from the datasheet. But >>> > are there cases where a part is manufactured in many packages and >>> > doesn't have a distinction for it in the name? >>> > >>> > >>> I have never encountered a case where a major manufacturer does not >>> define precise name for a specific version of a device. Sometimes they >>> (eg Texas Instruments) are even very overzealous in this topic. >>> >>> It seems to me that this can happen only in the case of small >>> manufacturers from the Far East, producing own things or something >>> under license (or not :-). Although, I put a pair of elements of >>> lesser-known manufacturers in the libraries and a problem in their >>> naming doesn't occurred. >>> >>> >>> Kerusey Karyu >>> >>> -- >>> Mailing list: https://launchpad.net/~kicad-lib-committers >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~kicad-lib-committers >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >
-- Mailing list: https://launchpad.net/~kicad-lib-committers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-lib-committers More help : https://help.launchpad.net/ListHelp
