Here we have the microbug layout at the very first stage (only have imported the footprints): Let's see how this looks like with an example: You don't need to always think about the layout as a whole, you can start by only worrying about the layout of each group of components, how they should be oriented in relation to each other, etc.
During layout, you can think of the grouped components as a form of abstraction.
This means if you properly block out your schematic into the different function areas, you have also mostly figured out how you should group your components together in the layout. In fact, in most cases, the device designs would like you to place the supporting components as close as possible to the main IC device! (always check the component's datasheet for any guidance on the layout for that part). The basic idea is: if we know that a group of components are meant to function together to perform one part of the task (for example: a DC-DC power conversion IC and its supporting passives and diodes), there is no good reason to separate them in the layout.
#Layouteditor set origin how to#
While net labels, minimizing crossing wires, and good use of sheet whitespace / functionality blocking are core ways to keep your schematic clean, they also do something fundamentally important for your layout: tell you how to place your components. Bad schematics make you decipher themĪnd then we showed you a bunch of best practices for making your schematic readable and easy to follow. One of the first things we said about schematics was: But as you move to more difficult boards, you may find that there are some standard tips and tricks, and so far unmentioned or unexplained tools in KiCad, that may help you. You're able to generate simple schematics, verify a valid ERC, assign footprints, and move to the layout editor to place and route the components according to a set of Design Rules.
By now, hopefully you've gotten used to the basic tools and flow of designing PCBs in KiCad.
0 kommentar(er)
