-
Notifications
You must be signed in to change notification settings - Fork 114
Improve S4.2 examples #478
base: master
Are you sure you want to change the base?
Conversation
Rework examples for input- and output-pin grouping/positioning (S4.2)
I always read that rule to roughly mean "stuff that stays on the board (and is a symbol in the schematics) to the left, stuff that's outside (and is a label in the schematics) to the right" (when applicable, e.g. bridge drivers and such. Not, say, logic symbols which have a clear direction). Edit: Not sure if it's clear what I mean. To employ the second example again: To me |
The common denominator for this rule seems to be a left-to-right flow in the schematic. Similar to writing text in most languages. I dislike the UART/RS232-example since there is no clear indication of the flow. It can be used in both directions and thus is not a unambiguous example. The same applies for any kind of bidir transceiver. That's why I want more examples that are not transceivers. How about I change the patch to keep the UART example but also add the new ones? |
Perhaps we should split the examples into subsections. |
While we are at it we could also add voltage-regulators where we currently allow KLC violations. Thats a point that always bugs me. I find the idea appealing to have more distinct examples. But on the other hand KLC is already pretty big, keeping it short and simple as design-goal would be violated by adding more special cases. I personally are in favor of more examples/subsections for this rule. |
Good idea. Instead of violating KLC for voltage regulators as a rule, we might as well have a rule exempting them :) We can't expand KLC to catch every conceivable corner case, but I'm all in favor of overhauling S4.2. |
Oh, and let's not forget about MCUs and such. |
Rework examples for input- and output-pin grouping/positioning (S4.2)
Related: #423