Activity log for bug #1781725

Date Who What changed Old value New value Message
2018-07-14 17:19:04 Victor W bug added bug
2018-07-15 09:09:24 Nick Østergaard tags eeschema erc
2018-07-16 17:12:05 Seth Hillbrand kicad: importance Undecided Medium
2018-07-16 17:12:05 Seth Hillbrand kicad: status New Confirmed
2018-07-16 17:12:05 Seth Hillbrand kicad: milestone 6.0.0-rc1
2018-07-17 00:02:02 Victor W description When running ERC on EEScheme, it is possible for exposed hierarchical sheet pins to be unconnected on either the top level or child sheets, without triggering a ERC error. More specifically, it appears there is no check to confirm that an exposed port is electrically connected across a top level sheet and a child sheet. This can result in parts of the design not being connected. === Example 1: 1. On the top level sheet of a hierarchical design, add a child sheet, with some ports. 2. Pick a port that is connected (within the child sheet) to at least two pins. For example, select an IO port that connected within the child sheet to a capacitor and to the input port of an IC. 3. On the top level sheet, delete all connections to that port (the net to the port should be floating). 4. Run eeschema DRC. === RESULT: 1. No errors or violations will be noted. === Expected: 1. I expect that unconnected sheet ports are flagged; if we've exported them to a sheet, then that sheet should be treated similarly to a symbol; unless you deliberately place an NC on that pin, then it's clear the port should be connected somewhere else in the schematic. 2. It is also possible for this to result in floating nets within a child sheet; if the top level net on the parent sheet is otherwise connected (or passes the DRC checks), and the port within the child sheet is unconnected, this also does not flag a DRC check. === Note that there already exists a specific error in the event sheet pins are not synchronized (ie; ErrType(6): Mismatch between hierarchical labels and pins sheets), though there is no error if the hierarchical labels or pin sheet are not connected. === Version Information Application: eeschemather Libraries: wxWidgets 3.0.4 libcurl/7.60.0 OpenSSL/1.1.0h zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.4) nghttp2/1.32.0 Platform: Linux 4.17.4-1-ARCH x86_64, 64 bit, Little endian, wxGTK Build Info: wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24 Boost: 1.67.0 OpenCASCADE Community Edition: 6.9.1 Curl: 7.60.0 Compiler: GCC 8.1.1 with C++ ABI 1012 Build settings: USE_WX_GRAPHICS_CONTEXT=OFF USE_WX_OVERLAY=OFF KICAD_SCRIPTING=ON KICAD_SCRIPTING_MODULES=ON KICAD_SCRIPTING_WXPYTHON=OFF KICAD_SCRIPTING_ACTION_MENU=ON BUILD_GITHUB_PLUGIN=ON KICAD_USE_OCE=ON KICAD_USE_OCC=OFF KICAD_SPICE=ON When running ERC on EEScheme, it is possible for exposed hierarchical sheet pins to be unconnected on either the top level or child sheets, without triggering a ERC error. More specifically, it appears there is no check to confirm that an exposed port is electrically connected across a top level sheet and a child sheet. This can result in parts of the design not being connected. === Example 1: 1. On the top level sheet of a hierarchical design, add a child sheet, with some ports. 2. Pick a port that is connected (within the child sheet) to at least two pins. For example, select an IO port that connected within the child sheet to a capacitor and to the input port of an IC. 3. On the top level sheet, delete all connections to that port (the net to the port should be floating). 4. Run eeschema DRC. === RESULT: 1. No errors or violations will be noted. === Expected: 1. I expect that unconnected sheet ports are flagged; if we've exported them to a sheet, then that sheet should be treated similarly to a symbol; unless you deliberately place an NC on that pin, then it's clear the port should be connected somewhere else in the schematic. 2. It is also possible for this to result in missed connections between child and parent sheets; if the top level net on the parent sheet is otherwise connected (or passes the DRC checks), and the port within the child sheet is unconnected, this also does not flag a DRC check. === Note that there already exists a specific error in the event sheet pins are not synchronized (ie; ErrType(6): Mismatch between hierarchical labels and pins sheets), though there is no error if the hierarchical labels or pin sheet are not connected. === Version Information Application: eeschemather Libraries:     wxWidgets 3.0.4     libcurl/7.60.0 OpenSSL/1.1.0h zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.4) nghttp2/1.32.0 Platform: Linux 4.17.4-1-ARCH x86_64, 64 bit, Little endian, wxGTK Build Info:     wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24     Boost: 1.67.0     OpenCASCADE Community Edition: 6.9.1     Curl: 7.60.0     Compiler: GCC 8.1.1 with C++ ABI 1012 Build settings:     USE_WX_GRAPHICS_CONTEXT=OFF     USE_WX_OVERLAY=OFF     KICAD_SCRIPTING=ON     KICAD_SCRIPTING_MODULES=ON     KICAD_SCRIPTING_WXPYTHON=OFF     KICAD_SCRIPTING_ACTION_MENU=ON     BUILD_GITHUB_PLUGIN=ON     KICAD_USE_OCE=ON     KICAD_USE_OCC=OFF     KICAD_SPICE=ON
2019-04-01 16:14:25 Jon Evans kicad: assignee Jon Evans (craftyjon)
2021-10-09 19:26:24 KiCad Janitor bug watch added https://gitlab.com/kicad/code/kicad/-/issues/1780
2021-10-09 19:26:26 KiCad Janitor kicad: status Confirmed Expired
2021-10-09 19:26:26 KiCad Janitor kicad: remote watch gitlab.com/kicad/code/kicad/-/issues #1780