Skip to content
This repository has been archived by the owner on Oct 26, 2021. It is now read-only.

[KLC] Clarify NC pin handling #377

Merged
merged 10 commits into from
Sep 14, 2019
12 changes: 8 additions & 4 deletions content/klc/S4.5.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,14 @@
brief = "Pins not connected on the footprint may be omitted from the symbol"
+++

Often a component has pins that are not physically connected, and in such cases, unconnected pins may be omitted from the schematic symbol.
Often a component has pins that are not physically connected.
Even these pins should be included in the symbol. Refer to the link:/libraries/klc/S4.3[requirements for hidden pins].
poeschlr marked this conversation as resolved.
Show resolved Hide resolved

However in some cases unconnected pins may be omitted from the schematic symbol.

. Pins may only be omitted if they are never to be connected _under any circumstances_
. Unconnected pins may only be omitted if including them would make the symbol unnecessarily large.
. If pins are designated `NC` but the datasheet specifies that these must be pulled to ground or otherwise connected to a specific net, then these **must** be shown on the schematic symbol
. If the pin-count in the schematic does not match the pad-count on the footprint, the footprint filter must include the pad-count of the footprint (see also link:/libraries/klc/S5.2[requirements for footprint filters])
* `SOT?23?5`
* `SOIC?8`
. The footprint filter must include the pad-count of the footprint if the pin-count in the schematic does not match the pad-count on the footprint (see also link:/libraries/klc/S5.2[requirements for footprint filters])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe it sounds better to use "match the pad-count of the footprint".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

* `BGA?144`
* `QFN?20`
11 changes: 6 additions & 5 deletions content/klc/S4.6.adoc
Original file line number Diff line number Diff line change
@@ -1,14 +1,15 @@
+++
brief = "Hidden pins"
brief = "Symbol pins must not be hidden unless they are not connected, part of a stack or power symbols"
+++

Hidden connection pins are generally not allowed for schematic symbols. Any connection point must be visible, otherwise unexpected net connections can occur.
Hidden symbol pins are generally not allowed for schematic symbols. Any connection point must be visible, otherwise unexpected net connections can occur.

Hidden power pins are also not allowed.

**Exceptions**

. Unused NC pins can be set to invisible. In this case the electrical type must be `Not Connected`. The end of the pin should lie on the symbols outline box to prevent unwanted connections to the invisible pin (see screenshot below).
. Power input pins must not be invisible unless used in power symbols. (Hidden power input pins are global labels.) Refer to the link:/libraries/klc/S4.3[requirements for pin stacking]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Punctuation is a bit odd on this sentence.
Otherwise, I think this PR looks OK.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason for the strange punctuation might be because i tried to use this strange RFC defined standardized language. #289

Do you have a better suggestion?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something like this maybe?

Power input pins must not be invisible unless used in power symbols (hidden power input pins are global labels). Refer to the link:/libraries/klc/S4.3[requirements for pin stacking].

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Am i blind or is yours word for word the same?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wording is the same. It's just the punctuation and capitalisation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed (forgot to mark it as such)

. Pins that are not intended to be connected must be set to invisible. In this case the electrical type must be `Not Connected`. The end of the pin should lie on the symbols outline box to prevent unwanted connections to the invisible pin (see screenshot below).
* Pins specified as not connected may be shown if they are expected to be connected in a significant number of use-cases.
. Invisible pins may be used in a pin stack to allow one-to-many connections. Refer to the link:/libraries/klc/S4.3[requirements for pin stacking]

{{< klcimg src="S4.6" title="Hidden NC-pins in a symbol and hidden pins as part of a power-pin-stack" >}}
{{< klcimg src="S4.6" title="Hidden NC-pins in a symbol and hidden pins as part of a power-pin-stack" >}}
2 changes: 1 addition & 1 deletion content/libraries/klc.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ aliases = [ "/klc/" ]
toc::[]


**link:/libraries/klc/history/[Revision: 3.0.17]**
**link:/libraries/klc/history/[Revision: 3.0.18]**

---

Expand Down
4 changes: 4 additions & 0 deletions content/libraries/klc_history.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,10 @@ url = "/libraries/klc/history/"
+++

---
== 3.0.18 - 2019-01-25
* Clarify rules regarding NC pins
* Clarify when they may be omitted
* Clarify that they must be hidden when included.
== 3.0.17 - 2018-12-31
* Correct Pin length definition for staggered TO (image in F3.5)
* Document rules for handling oval holes (new rule F7.7)
Expand Down