![]() ![]() Let’s understand the true purpose of the schematic, by my definition, which is to communicate the design intent in its entirety: physical limitations, thermal considerations, functionality, electrical characteristics, what the final PCB should look like, etc. I believe there is an ideal schematic the kind that leaves the engineer more aware of a design, rather than confused. We as engineers often focus on having our schematics make sense to us and be able to explain the design to other stakeholders, but I think we can go beyond that. This backwards approach to decipher a previous designer’s work, while intellectually stimulating, defeats the purpose of making the schematic in the first place to help the designer and other engineers understand what’s going on without redoing the design themselves. As I type this article, I am using KVL and KCL to back-calculate what goes where in a current design in relation to a previous PCB (and to the project overall). ![]() I should be able to read through a schematic and understand the full story of the design from start to finish without necessarily having to perform pen and paper calculations. When I see a schematic missing block diagrams, sectioned off areas, and lacking clear notes (which is practically all schematics I’ve seen), I want to throw my coffee and computer out the window. I know engineers are extremely smart, but they tend to fall short when it comes to clearly conveying their design ideas and requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |