Schematic styles are always an interesting thing to observe. Do you try and fit it all on 1 page or spread it among several pages where signal flow is not as easy to follow? Do you keep it architecturally flat or use the logical, but hard to follow, hierarchical design? Do you place critical components like decoupling capacitors near their respective integrated circuits, or show them all in a common area connected to supply rail? Do you make it clean looking by using wire stubs with node names for virtual connections, or make it easier to follow by showing complete lines of connectivity? Do you use descriptive net names to aid in understanding, communicating, and documenting degugging efforts? Do you include net name locators for on-sheet of off-sheet connections, or leave the user to search the schemtic to find them? How do you deal with multiple grounds?
One general observation I have made over the years is the folks responsible for implementing and debugging systems have a drastically different approach from folks whose primary design responsibility is ASICs or FPGAs.
HI Bill. I loved the old transistor radio schematic (being British by extraction I still prefer Circuit Diagram even though it takes longer to say and write). Obviously from a coil manufacturer trying to sell his wares (note the list of trnasistor types you can use at the bottom!)
I think the nice thing about diagrams like this is that you have the power rails running along the top and the bottom and it's obvious what they are. Looking at the EDN one, one IC is supplying the other two ICs but It takes a bit of examination to find this.
The worst as you say are MCU diagrams where the tendency seems to be to put ICs in isolation with a funny shaped box on each pin with a cryptic signal name in each. Somewhere on the rest of the diagram is another box, going into another IC, with the same signal name. Look, Ma, no wires! :-) But to be fair some of those circuits would be very difficult to draw without looking like spaghetti.
I recently had to trace the circuit of a drill charger from its PCB. I ended up with a real rats nest on a piece of paper. I managed to draw it properly with only 2 crossovers. It made it obvious how the circuit worked. and I found the tidying-up process very satisfying.
They have to look good, for heaven's sake, like any other art form. In the tube days, the tubes were often lined up on top, and all the passive components feeding them underneath. In the early transistor days, I noticed the same drawing style. But now, and I think for good reason, the active components are not typically separated.
There's nothing like a well executed, complementary symmetry analog circuit diagram, NPN on top, PNP on bottom, IMO. I like the power supply bypass capacitors to be shown close to the component they are bypassing for. And yes, chips tend to not have their inner workings show, because aside from the simplest of chips, that would be practically impossible.
I remember Heathkit schematics as being particularly well-drawn. I think a lot of the quality of the older drawings was that mechanical drawing was at that time a required engineering skill and something people did with great pride. A sloppy drawing indicated sloppy engineering. In Jules Verne's The Begum's Fortune (1879), the hero infiltrates into the enemy's Metropolis-like factory through outstanding mechanical drawing ability.
One of my pet peeves is the terrible automatically-generated logic diagrams one gets from logic synthesizers. IMO they're practically useless for anything but the simplest designs -- I'd much rather have textual equations.
Drones are, in essence, flying autonomous vehicles. Pros and cons surrounding drones today might well foreshadow the debate over the development of self-driving cars. In the context of a strongly regulated aviation industry, "self-flying" drones pose a fresh challenge. How safe is it to fly drones in different environments? Should drones be required for visual line of sight – as are piloted airplanes? Join EE Times' Junko Yoshida as she moderates a panel of drone experts.