#Schematic Gut Check for ESP32 PRoject

1 messages · Page 1 of 1 (latest)

opaque raptor
#

first glance, the voltage regulator has a 0.9v nominal voltage drop (at 1A, which is the only spec given), so your +3.3v, assuming the lipo cell drops to 3.4v, would be closer to 2.4v. Even with vin, there are two diode drops so that would be ~3.6v when powered from vin, so ~2.7v after the voltage regulator

#

with the li-po or vin circuit you have with the PFET, I think you flipped source and drain.

#

I would also not have one ground wire connected thoughout the entire circuit and instead use the gnd net (like you have in other places), makes the schematic more readable

#

also the TLV767 is not an LDO, just a regular voltage regulator

opaque raptor
#

for charging, you can get some ICs that basically do what you already want with selecting wither VIN or battery power, like the BQ2407x series battery chargers

#

breaking into different sections is generally a good idea, but also there are some changes that can be done to make it more readable:

  • don't have one long wire for the gnd trace, can be subjective, but imo it's easier on the eyes to have gnd nets instead
  • if you designed the symbols yourself, I would map it out based off functionality rather than the physical footprint, for example for the MCP73831 (which there already is a nice KiCAD symbol)
  • try to keep gnd facing down (rather than sideways) if possible, just more of an opinion of mine when drawing schematics
  • some sections, like the pfet selection circuit, can be redrawn like attached, which imo is more readable functionally
opaque raptor
#

while I may be biased (this is a KiCAD server after all), I 100% recommend moving to KiCAD. While I haven't used easy eda myself, I think KiCAD is more mature of an ECAD software, imo like 70-80% of what Altium Designer has that most people use (as somebody who uses both, one personal one for work)

#

plus for official symbols and footprints, unlike some ecad software (*cough* *cough* Altium), there's actual quality control, thanks to librarians and the klc