One reason one wants (labeled) NC nets can be isolation of nets via net classes to ensure proper distances between not connected pins and other signals.
Regards, André PS: This reminds me that eeschema correctly recognizes NC symbols as termination for nets (via ERC) but still shows a “not terminated" marking on that NC terminated net ending. Is there a bug filed for this somewhere? On June 5, 2018 2:38:24 AM UTC, Jon Evans <j...@craftyjon.com> wrote: >Hi all, > >In the current netlisting algorithm, pins with no-connects sometimes >appear >in the netlist, with auto-generated names like Net-(U1-Pad1). > >This seems to not always happen, but I haven't investigated why yet, >since >I'm approaching netlisting from a different direction with my new >connectivity algorithm. In my algorithm, a pin with a no-connect >attached >will never generate an entry in the netlist. > >Is there some reason we should be including these pins on the netlist? >It >seems like if they are marked as no-connects and don't actually connect >to >anything, we shouldn't be forwarding them to the layout. > >-Jon
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
