tutorials:pcb_design_tips
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Last revision | |||
— | tutorials:pcb_design_tips [2013/11/21 21:15] – created jarrett | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== PCB Design Tips ====== | ||
+ | ===== Software ===== | ||
+ | |||
+ | There are two common free (as in beer) software choices. | ||
+ | * Eagle [[http:// | ||
+ | * KiCAD [[http:// | ||
+ | |||
+ | As of 2013, Eagle is more widespread in use, there is a much stronger library support available but KiCAD is catching up. | ||
+ | |||
+ | On the other hand, Eagle' | ||
+ | |||
+ | ==== Eagle Libraries ==== | ||
+ | |||
+ | Lots of open hardware vendors use Eagle for their PCBs so there is an excellent range of libraries available. | ||
+ | |||
+ | * Adafruit [[http:// | ||
+ | * Sparkfun [[https:// | ||
+ | * Dangerous Prototypes [[http:// | ||
+ | |||
+ | ==== KiCAD Libraries ==== | ||
+ | * Dangerous Prototypes [[http:// | ||
+ | |||
+ | ==== Eagle Example Designs ==== | ||
+ | |||
+ | * [[http:// | ||
+ | * [[https:// | ||
+ | |||
+ | ==== Eagle Tutorials ==== | ||
+ | * [[https:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | |||
+ | ===== Get PCBs Made ===== | ||
+ | |||
+ | There is an excellent tutorial at [[http:// | ||
+ | |||
+ | ==== Manufacturers ==== | ||
+ | |||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * (please add some in Canada) | ||
+ | |||
+ | ==== VHS Member Notes ==== | ||
+ | |||
+ | === Tom's Tips === | ||
+ | |||
+ | This is how I work in Eagle. | ||
+ | * Draw the schematic and make sure the ERC (Engineering Rules Check) is ok | ||
+ | * Switch to the PCB view and use one of the Dangerous Prototypes PCB outlines (see Eagle libraries above) | ||
+ | * Lay out parts that have fixed locations (mostly connectors but also LEDs and switches too) | ||
+ | * Save and rename so you can come back here easily | ||
+ | * Lay out the rest of the parts rotating them to minimise the number of crossed connections | ||
+ | * Save and rename | ||
+ | * Lay out the power using thick traces (24mil if possible), leave the ground unconnected for later | ||
+ | * Save and rename | ||
+ | * Load the itead studio design rules file and increase the minimum track size to something like 12 or 14 mil | ||
+ | * Use the autorouter to see if it can lay the board out, if not decrease the minimum track size and repeat until close | ||
+ | * Save and rename | ||
+ | * Hand work remaining tracks by ripping up, using ratnest to cleanup the unwired traces and then laying out manually | ||
+ | * Run DRC again and ensure all is clean, fix any issues | ||
+ | * Follow the steps in this [[http:// | ||
+ | |||
+ | === Richard' | ||
+ | |||
+ | I generally follow a very similar process to Tom, with a few additions and differences: | ||
+ | * Make use of Net names in the schematic. This allows you to have visually disconnected components that are electrically connected, and makes the schematic a lot cleaner and easier to rearrange as you work. Give yourself room, and make use of Group to move blocks around. | ||
+ | * When doing a tight PCB layout, change the grid to a multiple of your desired trace/ | ||
+ | * Generally I'll have the schematic in Inches (by convention schematic symbols are almost always on 0.1& | ||
+ | * Remember that PCB traces are wires, and wires have resistance - and thus a voltage drop that is a function of their length and the current being drawn. This becomes important at higher currents (motors, high-power LEDs, displays, etc), where a component on the ' |
tutorials/pcb_design_tips.txt · Last modified: 2015/12/12 14:31 by 127.0.0.1