ERC doesn't flag unnannotated "phantom" sheet V5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Expired
|
Low
|
Bug Description
I don’t know if this is a bug but it is somehow “not right”
eeSchema error check does not flag unannotated reference designations in a “phantom” second instantiation of a sheet.
In this project: https:/
LCD.sch is only present in 1 copy on the main sheet (zoom out: they are below the bottom of the sheet).
In the file there appears to be 2 instantiations:
$Comp
L TERES:RCLAMP0524P U?
U 1 1 57E655B9
P 12050 2500
AR Path="/
AR Path="/
F 0 "U15" H 11870 2770 50 0000 L BNN
F 1 "RCLAMP0524P(
F 2 "OLIMEX_
F 3 "" H 12050 2500 60 0000 C CNN
1 12050 2500
1 0 0 -1
$EndComp
Note the U?, meaning there was no annotation. Running electrical rules check on the schematic shows no errors associated with no annotation (I get 6 warnings and 1 error not related to the lack of annotation).
I have no idea how this second instantiation happened – it does not appear to be in the PCB file – but essentially the lcd.sch file is corrupt and not flagged as such.
Application: kicad
Version: (2018-02-09 revision 07fff6ed3)-makepkg, release build
Libraries:
wxWidgets 3.0.3
libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
wxWidgets: 3.0.3 (wchar_t,wx containers,
Boost: 1.60.0
Curl: 7.54.1
Compiler: GCC 7.1.0 with C++ ABI 1011
Build settings:
USE_
USE_
KICAD_
KICAD_
KICAD_
KICAD_
BUILD_
KICAD_
KICAD_SPICE=ON
Changed in kicad: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in kicad: | |
assignee: | nobody → Jon Evans (craftyjon) |
milestone: | none → 6.0.0-rc1 |
tags: | added: eeschema erc |
@Brian, did you at one point have the "eDP LCD" sheet in the "Power Supply, Extensions and MiPi-DSI" sheet and then move it to the root sheet? Judging by the time stamps, that appears to be the cause of the phantom hierarchical component definitions. I don't think this will cause any issues but I am curious as to how this happened. I've never seen this behavior before but then again I don't look at every schematic file after I create a schematic. @JP, have you ever seen this before and if so should we be concerned about it? I would think that any left over hierarchy definitions would get removed when the file either moved or saved.