Constructive criticism requested for Kicad schematics (images added) - Page 1
Forum section: electronics / beginners

author: cbc02009
author_rank: Regular Contributor
timestamp: May 10, 2018, 12:24:02 pm
content: Hello all,I have two schematics I'm working on for a school project. We're designing a sun-tracking solar panel array, and I'm working on the (very preliminary) schematics. I really don't know much about best practices for schematic design, especially for hierarchical sheets as this is my first time using them, and so I was hoping someone could take a look and give me some advice on how to neaten them up.I'm not looking for circuitry related stuff, I wouldn't ask someone to go through all the datasheets and find all the connection and/or value errors I've made, just advice to make the schematics neater and easier to understand. (I mean, I'm not going to stop you if you want to)Especially my main question, when should I use hierarchical pins vs global labels? It seems like global labels make the thing neater, especially on things like voltage sources, but they don't really show the connections on the main sheet at all.there are two schematics, one for the panel movement controller, and one for the MPPT controller (basically a slightly different buck converter). I have them separate currently because I don't know how much processing power the MPPT needs (seems heavy, since it needs to output a frequently changing ~100Khz pwm.)It may be possible to control both functions with a single MCU, if anyone has any thoughts/advice on that, I would also very much appreciate it.Thank you very much!Adding Pictures here. Sorry, should have thought of that sooner!Panel Controller:MPPT Controller:

author: hermit
author_rank: Frequent Contributor
timestamp: May 10, 2018, 03:23:52 pm
content: You might get more interest if you post high rez pictures.With the SAM you could open the symbol in the editor and remove the unused pins or spread/move them about a little. For such a simple schematic you are over using labels which makes it look disjointed.

author: cbc02009
author_rank: Regular Contributor
timestamp: May 10, 2018, 03:49:35 pm
content: Quote from: hermit on May 10, 2018, 03:23:52 pmThank you, I should have thought of that. I will do that ASAP. So I should replace some of the global labels (like the input to the mosfet, for instance) with hierarchical pins?

author: hermit
author_rank: Frequent Contributor
timestamp: May 10, 2018, 04:06:43 pm
content: Originally I looked only at the PDF instead of downloading the project. It looks like you cleaned it up quite a bit since that was generated. This is a simple design. It easily goes on one sheet. No need for hierarchical sheets as far as I can tell.I'm using the 'nightly' version of Kicad so there might be some problems with my import. But, no power coming out of the regulator and no power into the chip or are these hidden pins?

author: cbc02009
author_rank: Regular Contributor
timestamp: May 10, 2018, 04:55:28 pm
content: I'm using kicad 4. The power should be going to the processor via Vdd in the "Power_Connections" schematic. the only reason I used hierarchical was just the sheer massive size of the sam processor. What you said about editing the pinout is probably a better option.

author: hermit
author_rank: Frequent Contributor
timestamp: May 10, 2018, 05:33:28 pm
content: There was talk on the Kicad list about offering a drop down menu for pin names. At minimum you can edit the pin function to ONLY reflect how the pin is being used. No reason to have all of those possibilities listed on the actual schematic. That is why the thing is so big. Remember to save the edited SAM to a new personal library and give it a unique name so it doesn't conflict with the standard library version.