When sorting out a lab (or garage or work space) I prefer to categorize by TOOLS and MATERIALS.
These are a very different sort of thing... and can be thought of as Permanent and Consumable.
A third category is a Kit, or working area... and this is an amalgamation of tools and consumables that are required for a task.
(Lab Setup 101
All three are required for a happy crew)
Part of the reason many people can not get comfortable in a work space is because these three distinct boundaries are not clearly set, or overly defined.
The same is true with folks inability to grasp programming.
Programming is intimidating... because at first one does not know the difference between a tool, material, and mix of the two.
Comments, operands, variables, constants, hardware port... once one can clearly identify these the problem dissolves.
This is why color coding is so important... and indenting for that matter.
But - on to this subject:
When creating library parts we have Symbols, Footprints, and the amalgamation - the device.
A Device is a mapping of Symbol pins to actual physical footprint pins.
Footprints are "standard" and must conform to reality (more on that later)
We will start with building a Symbol, in this case using Eagle PCB.
A Symbol consists of some lines (strictly for the eye to follow). They are in red.
The pins are the area of interest... and they have three attributes which are important:
The Name is the name... it should match the name in the data sheet and describe the function.
I like to include the pin name in the name... like... 1,VCC or 7,GND... this is important for error checking
Getting back to our two earlier analogies the biggest hurtle to laying out PCB's is understanding what is important and what is not.
Ok... well... the most important thing is that YOUR PCB ACTUALLY WORKS AND EVERYTHING IS MAPPED CORRECTLY.
If you fail at this... you will learn about "haywire"... which will make your mind go haywire if you duplicate the mistake by 10X or 100X
(I have actually seen this in production many times)
So - Name your pins.
The Direction attribute may not seem so important... until you get really busy and make a mistake. Direction is used during error checking to make sure you have not made a silly mistake. If you mark a pin as IN and wire it to another pin named IN well.... the compiler will throw a warning. Important point - tho second order.
Swap level has to do with Auto Routing and it tells the Compiler how much flexibility it has in the knapsack solution.
0 means... do not fool with this
1 means... you can possibly swap this (or something like that)
For a resistor... we may want the Auto Router to swap leads if it is beneficial for routing
On a Ceramic Cap we may wish to do the same
On a polarized cap... we would set to 0
Now... here is the Symbol that I built for the LTC6811. I was unable to find one.
When building symbols (and Schematics for that matter) there are two primary approaches:
Old School means that you make your symbol match your part as best you can. This is very helpful in manual error checking (as auto did not exist back in the day) but it makes for a messy looking schematic.
New School means you focus on how clean your schematic is and utilize the LEAP OF FAITH that you have everything right... and you trust your Compiler.
For overall style of a schematic...
Old School shows everything on a single page such that you can highlight traces and manually figure things out. Its a gnarly spaghetti mess.
New School means you break everything up onto different pages with layer after layer of abstraction.... more on that later.
I am more comfortable with Old School, and this is my project, so I will proceed as I desire
(tho if you pay me I will do whatever you like)
All of these things will be open source once verified.
Increasing battery voltage and controller current limit will result in a non linear experience