DRC does not connect tracks that pass through pads rather than ending on them (lp:#1718831)
Original report created by Strntydog (strntydog)
Tracks which intersect with pads (but do not terminate at the anchor point
of the pad) are listed as unconnected.
This is wrong from a physical model of the board, the Copper features
overlap, and so they are "electrically" connected, and DRC should report
them as such.
It is also inconsistent with DRC violations, which do obey copper
connectivity, a track crossing a pad of another net, at any point will
issue a DRC violation when checked.
There is an edge case where a track only slightly touches a pad, and is
electrically connected, but Not connected sufficiently for the design,
but that is not the same thing as being "unconnected" and isn't handled
by DRC now in any event.
There may be a requirement to report tracks which touch pads, but do not
terminate on the anchor point of the pad, but that is a different
requirement, and not the same as a track being unconnected.
Version:
Application: kicad
Version: no-vcs-found-e2505cb260ubuntu17.04.1, release build
Libraries:
wxWidgets 3.0.2
libcurl/7.52.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) librtmp/2.3
Platform: Linux 4.10.0-33-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
Boost: 1.62.0
Curl: 7.52.1
Compiler: GCC 6.3.0 with C++ ABI 1010
Build settings: USE_WX_GRAPHICS_CONTEXT=OFF USE_WX_OVERLAY=OFF KICAD_SCRIPTING=ON KICAD_SCRIPTING_MODULES=ON KICAD_SCRIPTING_WXPYTHON=ON KICAD_SCRIPTING_ACTION_MENU=ON BUILD_GITHUB_PLUGIN=ON KICAD_USE_OCE=ON KICAD_SPICE=ON
Original tags: drc pcbnew
Edited by KiCad Bot