eeschema ERC: "pin connected to some other pins but no pin to drive it" error is useless
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Fix Released
|
Unknown
|
Bug Description
I have a lot of ERC errors like this:
ErrType(3): Pin connected to some others pins but no pin to drive it
@ (133,35 mm,147,32 mm): Pin 4 (Power input) of component U4 is not driven (Net 212).
However, this is not helpful, because the ERC's ability to reason about the power inputs is limited:
- When you have a passive filter (eg. serial R) between the power input and power output, ERC thinks that the power input is not powered. (This can be "fixed" by littering the schematic with PWR_FLAG components, which is very inconvenient.)
- When you drive a component from an MCU GPIO pin, it complains that the power input is not powered, even though in reality the GPIO can source the necessary current. (This cannot be fixed by a PWR_FLAG because that will create yet another severity error.)
Also, this error message cannot be silenced, even though connecting power inputs to bidirectional pins is allowed in the ERC settings. This results in a lot of "noise", ie. useless error messages in ERC, and makes it hard to notice real bugs.
I understand that it's impossible for the ERC to figure out whether my GPIO can source enough current, and how the filter works. Suggestion: please add an option to silence this warning.
tags: | added: erc |
Changed in kicad: | |
importance: | Undecided → Wishlist |
tags: | added: eeschema |
Changed in kicad: | |
importance: | Wishlist → Unknown |
status: | Expired → New |
Changed in kicad: | |
status: | New → Fix Released |
KiCad bug tracker has moved to Gitlab. This report is now available here: https:/ /gitlab. com/kicad/ code/kicad/ -/issues/ 2067