3
\$\begingroup\$

This is my first time making schematic components, of which I will then be making the footprints for PCB designs. I'm using KiCad.

I don't know the best "layout" for the components I'm making. For example, some component libraries seem to bunch different connections together logically (e.g. Power and ground pins are next to each other, microcontroller ports are placed next to each other in order etc.) and then you get components where they have just randomly drawn any old shape and put the connections anywhere.

For example, these two components I've picked, the connections are in groups (note that this is a direct screenshot of one schematic page, I haven't resized either image):

enter image description here

My questions are:

  • Firstly, what shape should I use? I see some components as rectangles, other one as squares.
  • Is there a industry standard or something similar that states where the connections/pins should be displayed on the components (e.g. "put power and ground on the bottom side", that type of thing.)
  • What size should I make the schematic components? As can be seen above, there is quite a large difference between the size of the component, it's text, and the font used.
  • What colours/fonts should I use? Above one uses white one uses yellow as the filler colour.
\$\endgroup\$
1
  • \$\begingroup\$ It depends how fancy you want to get. As long as the text is legible and the wiring is easy to follow I don't worry too much about what pin number is where. Sometimes I will move pin numbers out of order so that the schematic wiring is easy to follow, especially with high pin count components. With chips that have pins on 2 sides, if the wiring is simple, I just make the component match the actual part as far as pin location (if chip has pins 1-4 on left side I'll do same on component). Sometimes I'll match to the component on the datasheet for ease of comparison. \$\endgroup\$
    – I. Wolfe
    Feb 21, 2015 at 1:41

2 Answers 2

1
\$\begingroup\$

I generally want signals to flow from left to right, so I put inputs on the left of the box, and outputs on the right. Power connections (if shown) go on top, and power (again, if shown) on the bottom edge. The box must, of course, be tall enough to show all the pins, but only needs to be wide enought that the pin names don't overlap. I would usually put the reference designator and part type above the part, not inside it.

Spacing of pin/signal groups, as in your right example, can be helpful in separating functions on a part.

\$\endgroup\$
1
\$\begingroup\$

It really depends on the designer.

The schematic symbol is something that is visually useful for you. A jumbled set of pins will have the same functional effect as a set of pins that is more organized. It's entirely up to you.

For instance, when I create a component, about half the time, I'll create the symbol as what's presented in the datasheet. It makes verifying the component pins against the datasheet slightly easier. But I'll also create an alternate view where I group similiar inputs together and group the outputs togethe such as the image below. enter image description here

On other occasions, if the part has multiple sub components like a quad AND gate, I'll just have the logic symbol without any box around it.

Other times, I'll have the pins arranged like in the datasheet, but I'll include a visual representation of the circuitry, such as an opamp, so I know what the function of a particular pin is, and any other pins associated with that component.

I do these various methods, for one reason. Readability for myself or someone else looking at it.

So the answer to all your questions is - it's really whatever best works for you. What makes it easy for you to connect your wires, so that your schematic looks cleaner and more readable.

\$\endgroup\$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.