|
From: Joseph C. <18...@bu...> - 2019-09-12 22:01:51
|
Public bug reported:
As of version 4.2.0 my PCB layout has 176 new DRC errors. I have many
pads which are connected to polys by setting the pad clearance to zero.
The DRC previously ignored theses. I understand that this looks like a
legitimate clearance violation but there is no way, as far as I can
tell, to tell PCB that the connection from the pad to the poly is
intentional. A flag on the pad indicating that it should be connected
would be ideal.
The "clearline" flag on lines is related. If there were a "noclear"
flag for pads, I could add this to all the pads that were intentionally
connected to polys. Ideally, "noclear" would both prevent the DRC from
calling the connection an error *and* cause the poly router to ignore
the pad clearance setting.
This is fairly easy to reproduce.
1. Start a new project
2. Add a poly rectangle on the top layer.
3. Add a component that has a pad.
4. Set the clearance of a pad to zero (Shift-K).
5. Run the DRC.
See attached file.
** Affects: pcb
Importance: Undecided
Status: New
** Tags: drc
** Attachment added: "drc_pad_clearance_problem.pcb"
https://bugs.launchpad.net/bugs/1843834/+attachment/5288396/+files/drc_pad_clearance_problem.pcb
** Description changed:
As of version 4.2.0 my PCB layout has 176 new DRC errors. I have many
pads which are connected to polys by setting the pad clearance to zero.
The DRC previously ignored theses. I understand that this looks like a
legitimate clearance violation but there is no way, as far as I can
tell, to tell PCB that the connection from the pad to the poly is
intentional. A flag on the pad indicating that it should be connected
- such as "pininpoly" would be ideal.
+ would be ideal.
The "clearline" flag on lines is related. If there were a "noclear"
flag for pads, I could add this to all the pads that were intentionally
- connected to the poly. Ideally, "noclear" would both prevent the DRC
- from calling the connection an error *and* cause the poly router to
- ignore the pad clearance setting.
+ connected to polys. Ideally, "noclear" would both prevent the DRC from
+ calling the connection an error *and* cause the poly router to ignore
+ the pad clearance setting.
This is fairly easy to reproduce.
- 1. Start a new project
- 2. Add a poly rectangle on the top layer.
- 3. Add a component that has a pad.
- 4. Set the clearance of a pad to zero (Shift-K).
- 5. Run the DRC.
+ 1. Start a new project
+ 2. Add a poly rectangle on the top layer.
+ 3. Add a component that has a pad.
+ 4. Set the clearance of a pad to zero (Shift-K).
+ 5. Run the DRC.
See attached file.
--
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1843834
Title:
New DRC flags zero-clearance pads
Status in pcb:
New
Bug description:
As of version 4.2.0 my PCB layout has 176 new DRC errors. I have many
pads which are connected to polys by setting the pad clearance to
zero. The DRC previously ignored theses. I understand that this
looks like a legitimate clearance violation but there is no way, as
far as I can tell, to tell PCB that the connection from the pad to the
poly is intentional. A flag on the pad indicating that it should be
connected would be ideal.
The "clearline" flag on lines is related. If there were a "noclear"
flag for pads, I could add this to all the pads that were
intentionally connected to polys. Ideally, "noclear" would both
prevent the DRC from calling the connection an error *and* cause the
poly router to ignore the pad clearance setting.
This is fairly easy to reproduce.
1. Start a new project
2. Add a poly rectangle on the top layer.
3. Add a component that has a pad.
4. Set the clearance of a pad to zero (Shift-K).
5. Run the DRC.
See attached file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1843834/+subscriptions
|