So, because I haven't posted a schematic for review before, I have no idea how to do it. Apparently, my previous attempt was poor. I got some actionable feedback, but I'm looking for more!
I would be very happy if you could give me concrete feedback on what I can do with this schematic to make it more easy and straightforward to review.
The main functions are:
– input from wall wart
– LDO regulated to 6V
– provides 5.15V on VCC when connected
– MOSFET switched current to a Li-ion battery
– output of battery (as well as LDO output) stepped-up to 5V to VCC
The charge voltage will be sensed through one line, and PWM controlled through another line.
As a secondary concern, I assert that the dual input to VCC is safe, because if both systems are running at the same time, D2 and the fact that Vsense at R25 is higher than target will essentially just "idle" the switching controller.
Best Answer
I agree with much of what Fake said, but some of his points seem to be religious issues with little validity.
Another good reason for net names is short comments. I sometimes name and then show the names of nets only to give a quick idea what the purpose of that net is. For example, seeing that a net is called "5V" or "MISO" could help a lot in understanding the circuit.
Physical pin order layouts obfuscate the circuit and make debugging more difficult. Don't do it.
This also causes common subcircuits to be drawn similarly most of the time. Once you get more experience looking at schematics, these will pop out at you and you will appreciate this. If stuff is drawn every which way, then these common circuits will look visually different every time and it will take others longer to understand your schematic.
Good schematics show you the circuit. Bad schematics make you decipher them.
There is another point in this case. A sloppy schematic shows lack of attention to detail and is a irritation and insult to anyone you ask to look at it. Think about it. It says to others "Your aggrevation with this schematic isn't worth my time to clean it up" which is basically saying "I'm more important than you". That's not a smart thing to say in many cases, like when you are asking for free help here, showing your schematic to a customer, teacher, etc. Neatness and presentation count. A lot. You are judged by your presentation quality every time you present something, whether you think that's how it should be or not. In most cases people won't bother to tell you either. They'll just hire someone else, go on to answer a different question, not look for some good points that might make the grade one notch higher, etc.