Schematic capture by default uses a 50 mil grid, so keeping symbol pin
ends on that grid should work well and provides more flexibility when
creating symbols.

But keep pins spaced 100 mils from each other so that having pin texts
which indicate the pin number sized at 50 mils does not look silly.

This required a renumbering of many of the schematic symbol rules.

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

60 mil for field texts is the default, so use it to ease development.
Other texts can easily have a default text size of 50 mils (this setting
is often retained from part to part once changed once by the user) and
it looks nice, so use it.

Use "should" rather than "shall" as there may be cases where the text
sizes may necessitate being different, but this should be rare.

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Both .bck and .bak backup files are created automatically by KiCad and
should not be tracked in version control.

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

To match project renaming.

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Signed-off-by: Attila Kinali <attila@kinali.ch>

Start symbols

No actual symbols yet, just infrastructure.
KiCad really wants to have a project, schematic, and layout.

See merge request !5

Ignore files ending in "bak" and files with "cache" anywhere in their
name.

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

These files are required to exist for the project in order to edit
symbols and footprints but do not actually capture any schematic or
layout in them.

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

With these files in place, we should be able to create schematic symbols
and footprints (modules).

All default KiCad libraries have been removed from the project,
schematic, and layout.

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Readme footprints v2

Builds upon merge request !3 but with corrections discussed.  Adds two new commits to cleanup symbol grammar and clarify that symbol pin locations must not be changed due to KiCad current operation.

See merge request !4

To avoid situations where this git repo is updated causing schematic
nets to break due to symbol pin locations changing unexpectedly.  KiCad
does  not cache the symbols within the schematic itself (which is unlike
how footprints are often cached within a layout itself so that in order
to cause a change to a footprint that the newer version of a footprint
must be imported by the user in an explicit operation).

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Later, in rule 8, it is described about power symbols having potentially
many phases, so it is possible to not have a P and N side of an AC
symbol, such as in a 3 phase system where you have A, B, and C legs but
none is the positive or negative phase and a neutral may not exist
(delta configuration).

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Simplifies the symbol library naming convention and allows for easy
placement of parts as dual-sourced parts all go in the same library and
there is no confusion on generic parts.

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Readme fixes

Just something little. Also fixes note 5 made on electronics/kicad-libs#1.

See merge request !2

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Signed-off-by: Attila Kinali <attila@kinali.ch>

readme: initial sensible rules for sch and pwr symbols

See if you think this is a good place to start.  I fixed the numbering to use FORTRAN numbering (starts at 1) and the phases/pins issue on AC sources.

I'm not sure if my whole nomenclature on the last rule in power symbols is clear or worth having in such detail or not.

See merge request !1

Signed-off-by: Andrew Bradford <andrew@bradfordembedded.com>

Signed-off-by: Attila Kinali <attila@kinali.ch>