User Tools

Site Tools


pcb:drc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
pcb:drc [2019/01/29 09:45]
cparker [New DRC Violations]
pcb:drc [2019/02/18 12:05]
cparker [New DRC Violations]
Line 62: Line 62:
   * Violations for holes being too close together   * Violations for holes being too close together
   * Floating copper   * Floating copper
 +  * Pin/pad exit violations
 +  * Silk screen over pins/pads
 +  * Overlapping elements
 ====DRC tests==== ====DRC tests====
 This is to describe ways of testing the DRC code, not things the DRC should check for. This is to describe ways of testing the DRC code, not things the DRC should check for.
  
   * Go through the DRC code for different kinds of violations to check that all possible code paths are being tested   * Go through the DRC code for different kinds of violations to check that all possible code paths are being tested
-  * Review the DRC tests and check that the results are correct!+  * Review the DRC tests and check that the results are correct! ​(Done: 201901xx)
   * Generate graphical output for the DRC report   * Generate graphical output for the DRC report
   * Generate LaTeX output for the DRC report (wishlist!)   * Generate LaTeX output for the DRC report (wishlist!)
Line 76: Line 79:
   * Square pads \\ In lots of cases, square pads are handled differently than ones with round ends, so, square pads should definitely be tested.   * Square pads \\ In lots of cases, square pads are handled differently than ones with round ends, so, square pads should definitely be tested.
   * Objects in the same layer group (physical layer) but on different (logical) layers   * Objects in the same layer group (physical layer) but on different (logical) layers
 +  * End points of lines/arcs \\ The end point condition is frequently tested for, and a separate test is called for these cases.
  
 ====DRC backend work==== ====DRC backend work====
Line 90: Line 94:
  
 ====DRC interface==== ====DRC interface====
-  * Create a DRC panel in the preferences window that allows for adjusting settings (possibly with image descriptions of the violations) and running specific tests individually +  * Create a DRC panel in the preferences window that allows for adjusting settings (possibly with image descriptions of the violations) and running specific tests individually. This will require that parameterization in the back-end work to be finished first.
-  * Figure out what the lesstif HID requirements are for the DRC code (it works differently,​ presenting violation by violation)+
  
 ====DRC bugs==== ====DRC bugs====
-  * Highlight both offending objects instead of just one^^^ +  * Highlight both offending objects instead of just one (done: 4.2.0) 
-  * Find more than one "​insufficient overlap"​ or "​insufficient gap" per pin/pad/via^^^ +  * Find more than one "​insufficient overlap"​ or "​insufficient gap" per pin/​pad/​via ​\\ The insufficient overlap case cannot propagate, due to the nature of how it works, however, the insufficient gap one can, and it does now as of the 4.2.0 release. 
-  * Check for duplicate DRC errors before appending a new one (can happen if more than one pin is connected to an object)+  * Check for duplicate DRC errors before appending a new one (can happen if more than one pin is connected to an object) (done: 4.2.0)
   * On MacOS the images in the DRC window of the GTK HID are garbled   * On MacOS the images in the DRC window of the GTK HID are garbled
pcb/drc.txt · Last modified: 2020/06/28 12:37 by cparker